FOUNDATION GUIDE / REVIEWED JULY 22, 2026
Intended outcome: A one-page current-state map and a short problem statement.
Inventory the work before buying another system
Map the current workflow, systems, owners, data, pain points, and non-negotiable constraints before writing requirements.
Work through the change in order
- 01
Name the business outcome in observable terms.
- 02
Walk one ordinary case from trigger to completion.
- 03
List systems, spreadsheets, messages, owners, and handoffs.
- 04
Mark duplicate entry, delay, error, access, and reporting problems.
- 05
Record constraints, current costs, and the manual fallback.
Save evidence for these checks
- The map reflects what people actually do.
- One accountable owner confirms the problem.
- The desired outcome does not assume a product.
Hold the rollout when a boundary breaks
- No process owner
- Unknown sensitive data
- A purchase deadline replacing discovery