All guides
Free checklist
For product, engineering and IT leaders at U.S. software companies planning AI in their own software
Your API docs describe the system you planned.
Before you build AI: inspect the system, agree on done
Find out how the real system works, and agree what done means, before anyone writes code.
This answers
- What must we know about our own product first?
- What does done mean, in lines anyone can test?
- Who decides what, before anyone writes code?
Checklist · 8 pages, PDF · Proposed approach
What is inside
- 1Write the outcome so anyone can test itA filled example
- 2Documents say what was planned. These show what is trueRead the real system
- 3Six things to find out firstInspect every system the AI will touch
- 4Agree on done, one name per lineThe one-page brief
- 5We inspect first, and agree on done before we buildFrom our work
- 6Bring this page to the Product ReviewYour notes for the call
You also get
- Six things to find out in every system the AI will touch
- Four places that show how the system really works
- A filled one-page brief: eight lines, from the outcome and its baseline to the off switch
- A page to bring to a free Product Review, if you want a second look
Preview



