Build for the user, not the roadmap
The roadmap is a business document. Users don't care about it. They care about whether the product solves their problem. They care about whether it's fast, clear, and worth comi...
Tagged Topic
6 Dispatches
The roadmap is a business document. Users don't care about it. They care about whether the product solves their problem. They care about whether it's fast, clear, and worth comi...
A decade in product and the problems are always the same. Different industries, different team sizes, different tech stacks — the surface changes. Underneath it's always some ve...
The point of an MVP isn't to ship a small successful product. It's to find out, as quickly and cheaply as possible, what users actually want. Most teams forget that. They build ...
Most teams treat discovery as a phase. There's a kickoff, a few weeks of research, a synthesis deck, and then the team moves to build. Discovery is something you do at the start...
Empathy gets dismissed as a soft skill. Something for the people side of the job, irrelevant to the actual decisions about what to build. That framing is wrong twice over. First...
A roadmap that wasn't built on user evidence isn't a plan. It's a wishlist with dates on it. That sounds harsh. It's also what most roadmaps actually are. Stakeholders contribut...