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...

Most product teams know the frameworks. They can write stories, run ceremonies, and ship consistently. What separates good from great isn’t process — it’s judgment. Judgment shows up when:  • A team says no to a loud request  • Complexity is removed instead of added  • The right metric is chosen, not the convenient one Judgment can’t be automated. It’s built through context, customer exposure, and trust. When organizations don’t trust product judgment, they add:  • More process  • More...

A simple test when leadership teams are presented with product roadmaps: If it takes more than a few minutes to explain why each major initiative exists — something’s off. Not because the work is bad. But because strategy isn’t visible. A strong roadmap doesn’t require narration.  You can see the logic:  • What problem it solves  • Who it’s for  • What outcome it drives When roadmaps become collections of projects, dates, and dependencies, teams lose the thread. Execution becomes efficient,...