5 articles in Product discovery
Even a good hypothesis needs a map before it needs code. AI agents build whatever ticket lands in front of them — they can't see the journey the ticket sits inside. User story mapping is the practice that turns a backlog of features into a walking skeleton of the user's journey. It's the second unlock.
Your PM writes prose. Your engineer translates it to code. QA finds the gaps. Your AI agent just compressed this broken loop from weeks into hours — without fixing any of the misalignment. Specification-driven development is the contract layer both sides can read, write, and execute. And it's the practice that separates teams who get leverage from AI agents from teams who ship the wrong thing, faster.
Most developer tools fail adoption not because they're poorly built, but because they're designed from the wrong starting point. Here's how Jobs-to-be-Done thinking explains why engineering tools succeed or sit unused — and what it reveals about AI adoption.
AI coding agents are the most powerful tools engineering has ever had. But the teams getting unreal results aren't just prompting — they're combining AI with practices that unlock outcomes nobody else can explain. Hypothesis-driven development is the first unlock.
Harness engineering gives coding agents guides and sensors to make output reliable — the downstream controls that ensure things are built right. Shape is the upstream control that ensures the right thing is being built. Here's what the shape discipline looks like — and why AI teams that skip it ship well-built fragments of the wrong product.