Outcome
First
How we deliver software with AI: start from the outcome, define done in writing, and let evidence decide.
Download the PDF- Start from the outcome and the date that cannot move.
- Get “done” in writing before the build.
- Make evidence the unit of review.
| Conventional | Outcome First | |
|---|---|---|
| Definition of done | Features complete | Go/no-go criteria met |
| Who writes the code | Engineers write, peers read | AI agents draft, people decide |
| Unit of review | The code change | An evidence report |
| When quality is checked | A QA phase near the end | On every change |
20 pages.
One case study.
- 01The business outcome
- 02The baseline
- 03The process
- 04How it differs
- 05How success was measured
- 06Lessons learned




















Replacing a Commercial EHR in 11 Weeks with an AI-Driven Process
- 11 weeks
- AI-built prototype to production
- 3/10 → live
- Go-live readiness at the start
- 16 of 20
- Spec modules delivered
- 686
- Merged pull requests, every one reviewed