If we can build faster, test faster, and iterate faster… why plan as much? It’s a fair question. But it leads to the wrong conclusion. Roadmaps aren’t becoming less important. They’re more important. Because when the cost of building drops, the cost of building the wrong thing can increase. A roadmap isn’t about slowing teams down. It’s about making decisions visible. The difference is simple: A decision-based roadmap says: We are doing this instead of that. A collection-based roadmap says:...

Most companies are still thinking about AI as a productivity layer. “How do we help engineers code faster?” “How do we help product write requirements faster?” “How do we help support respond faster?” That’s all valid. But it misses the bigger shift. AI isn’t just improving how teams work. It’s forcing a rethink of how teams are structured in the first place. When: -One engineer can ship 2–3× more -Product work can be partially automated -Prototypes can be built in hours, not weeks Then......

The biggest impact I’m seeing from AI right now is not chatbots. It’s what’s happening inside product and engineering teams. AI coding tools are collapsing the distance between idea and execution. What used to, at minimum, require: A product manager to define the problem An engineer to build the solution …is increasingly being done by one person. Call it the “product engineer.” Someone who can: 1) Understand the customer problem 2) Shape the solution 3) Use AI tooling to build and iterate...