> ...learn how far a new technology can be trusted
I think you've missed the point of this statement: > Starting with business needs first is essential
This is a negative shift I've seen in product now. Instead of emphasizing with the user and trying to understand the domain, processes, real-world usage scenarios, product teams are now building junk prototypes and throwing these over the wall at the user. Maybe this works for some spaces and domains.But the reality is that for many end consumers of software, it's not a good experience to use janky software that changes behaviors, flows, and screens on a whim now because product can.
I think AI has had a negative effect on product teams; I can see all pretense of thoughtful design and execution after understanding the customer being thrown out the window and leaving a much worse end-user experience as designs and capabilities shift around without foresight and product teams "feel" their way through.
Perhaps I should have mentioned that if you built something in ignorance of the business' needs, you shouldn't then go exposing the business' customers to that thing.
If somebody is shipping the prototypes, that's a problem. I was just speaking up for the utility of playing around as a necessary part of learning your tools.