What we have learned, written plainly
Practical guides for people buying or shipping software, with the diagrams we draw for clients. Each one is something we wish someone had told us earlier.

- AIHow to scope an AI system before you build itMost AI projects that disappoint were never short of a clever model. They were short of a clear job, firm boundaries and someone to run them. Here is how to scope one so it earns its place.
- PlanningDiscovery before you build: why a short first step saves moneyThe most expensive changes are the ones you make after something is built. A short, time-boxed discovery finds them while they still cost an afternoon instead of a month.
- Running softwareLaunch is the start: keeping software healthy afterwardsLaunch day gets the attention, but it is the start of a system’s life, not the end. What keeps software healthy is a handful of plain decisions, made before you go live.
- BuyingHow to choose a product engineering partnerMost partners look alike from their websites. The differences show up in what they can prove, how they begin, and what they say about the months after launch. Here is what to look for.