That's always been the case though. Much of our job is figuring out as quickly as possible how wrong we are and in what way. And the best way to do that, now and 5 years ago, is the scientific method. Try something, and then listen to your users to hear what sucks and why, and then adapt.
Believing you can figure out the right requirements through a lot of thinking, analysis, and talking is called the waterfall approach, and it's as wrong now as it was four decades ago.
Believing you can figure out the right requirements through a lot of thinking, analysis, and talking is called the waterfall approach, and it's as wrong now as it was four decades ago.