Observation·
Guide-driven development
Write the user's guide first. Then let AI write the spec from it.
For years, product teams turned a customer's needs into specs and acceptance criteria, the checks that say when a feature is done. Developers built from the spec. A spec says what the system must do. It rarely says why a user needs it.
Every check traces back to a user and their problem.
With AI agents in the team, I start somewhere else. The customer's needs first become a clear user's guide. It explains how the whole concept serves the user and solves their problems, step by step.
The product owner reviews the guide. That review is easy, because a guide reads like the product in use. A missing step or an unsolved problem shows at once.
Then AI extracts the specs and acceptance criteria directly from the guide. Every check traces back to a user and their problem. Nothing ends up in the spec that the guide does not ask for.
The guide is also what the product is tested against. AI tests the built product and reviews the work against the guide: can a user do what the guide promises?
So the product owner approves one document, written in the user's words, and everything else is drawn from it. That is guide-driven development.
Reel transcript · 0:55
For years, product teams turned customer needs into specs. With AI, a new path is opening: start with the user's guide.
Needs in. Specs out.
The old way: the client explains their needs, and the team writes specs and the checks that say when it's done. A spec says what the system must do, and rarely why the user needs it.
Write the user's guide first.
Now the customer's needs first become a clear user's guide. It explains how the whole product serves the user and solves their problems, step by step.
AI writes the spec.
The product owner reviews the guide, and that's easy: it reads like the product in use. A missing step or an unsolved problem shows at once.
Then AI extracts the specs and acceptance criteria straight from the guide, so every check traces back to a user and their problem. And AI tests and reviews the product against the same guide.
The takeaway
Take one feature you're planning next. Write its user's guide first, and let AI take the specs from there.