3
Three outcomes per day
Finished outcomes, not a backlog.
3-2-1
3-2-1 is a visibility model for work. It keeps inputs visible, choices explicit, and progress trustworthy.
Why this exists
Most systems start with tools. This one starts with primitives: capture, choose, see. When those are right, tools become optional.
The 3-2-1 model
2
Two modes of work
Heap for raw capture. Stack for intentional, maintained work.
1
One place to see the system
What came in, what moved, what is being built.
One-day proof
Heap inputs (morning capture)
- Notes from a user call about onboarding friction
- A rough sketch for the landing page layout
- A new idea for logging daily outcomes
- Two TODOs from yesterday that did not finish
Three outcomes chosen
- Draft the page outline and copy
- Ship a minimal layout without styling
- Record a daily log entry
What moved by end of day
- Copy drafted and saved as a single source of truth
- Layout shipped in the app
- Log entry captured in Stack
If one day is clear, the system scales.
System view
The system is only as trustworthy as its visibility. One place to see what arrived, what moved, and what is now real.
What came in
Raw inputs captured without friction.
What moved
Outcomes finished and logged.
What is being built
Active Stack work that remains.
Experiments over opinions
This is not advice. It is a set of experiments that produce artifacts and conclusions.