01
THINK
IN SYSTEMS.
A feature belongs to a larger whole. Map the dependencies, the people and the information before deciding what to build.
Start with: a system map and a clear statement of the problem.
02
CUT
THE NOISE.
A focused first release needs explicit boundaries. Choose the work that answers the central question and let the rest wait.
Start with: the essential journey and a short list of non-goals.
03
LEAVE
IT LEGIBLE.
Readable interfaces and readable engineering support the same aim: make the next person’s decision easier.
Start with: consistent language, clear states and useful documentation.
A small set of
strong principles.
- 01 — Context before tooling.
- 02 — Simplicity takes work.
- 03 — Constraints are design material.
- 04 — Explain the important choices.
A tangled brief is a good place to begin.
Describe what is happening, what is getting in the way and what a useful first change would look like.
START WITH A QUESTION ↗