The distinction between problem space work and solution space work I think is pretty underrated across the industry. I've seen so many teams (mine included) get seduced by the speed of AI and skip straight to building just to realize we prototyped the wrong thing fast.
The "can you write the problem, user story, and rough shape in one paragraph?" litmus test is something I'm going to steal immediately. Thanks!
The distinction between problem space work and solution space work I think is pretty underrated across the industry. I've seen so many teams (mine included) get seduced by the speed of AI and skip straight to building just to realize we prototyped the wrong thing fast.
The "can you write the problem, user story, and rough shape in one paragraph?" litmus test is something I'm going to steal immediately. Thanks!
My own take (I’m a pm) on how to build anything well (from my personal experience using ai from prototyping to full rollouts) https://abbasda.substack.com/p/the-blueprint-paradox-why-your-best?r=1g085&utm_medium=ios