Throughline
Learn in cycles. Move in a line.
A practice of continuous inquiry and forward flow.
The Line
Most systems organize work by state. This one organizes it by sequence.
Backlog, ready, doing, blocked, done, someday, version two, post-launch. Each is a place work can sit, and several of them quietly mean not now.
Throughline has one ordered stream instead. Every piece of work occupies a position on it. Completed work becomes history rather than piling up in a column. Future work sits ahead of the present, in the order we currently believe it should happen.
The line itself becomes the durable record of the project.
Cycles
The work is cyclical. The project is not.
We plan, do, study, adjust, and go again. But a project does not travel in circles — time moves forward, so the cycle unrolls onto the line. Every experiment, decision, adjustment, release, mistake and discovery becomes another point on it.
TIME ───────────────────────────────────────────────────▶
Plan → Do → Study → Adjust → Plan → Do → Study → Adjust
└────────── cycle ──────────┘ └────────── cycle ───────The loop is how we learn. The line is how we move.
That tension is the mark at the top of this page. The curve is inquiry — try something, observe, learn, adjust. The straight run is flow. Neither dominates the other.
Now
Done is not a state. It is a location.
Now is the boundary between what we have observed and what we intend. Finishing something means moving it behind Now — which records that it happened before everything still ahead.
There is no completion flag to drift out of sync with reality, because completionis the ordering.
The Window
Nobody has to hold the whole project in their head.
Attention is local. A window of focus slides forward along the line as work progresses — early exploration, then implementation, then deployment, observation, refinement. The project was never reorganized. Our attention simply moved.
Detail follows the same rule. Near work can be concrete because we know more about it. Far work should stay coarse, because pretending otherwise manufactures certainty that does not exist.
Old work isn’t clutter. It’s farther away.
Inquiry
We are not executing a plan. We are answering questions.
The unit of progress is not a completed task. It is something learned. Each pass asks the same five questions, and each answer changes the line ahead.
- What do we know?
- What do we need to learn?
- What should we try next?
- What happened?
- What does that change?
The last one is the one that moves things. An answer that changes nothing was not worth asking.
Buckets
If something should happen later, put it later.
“Post-go-live”, “version 2”, “blocked”, “someday” — these accumulate into destinations where work goes to disappear. A position on the line says the same thing without building a room for it.
Changing the order is not a failure of planning. It is planning.
Vocabulary
Seven words carry the whole practice.
- Practice
- The whole of it. You get better at it by doing it, and you never complete it.
- The Line
- The ordered continuity of work through time. Everything goes on the Line.
- Flow
- Movement along the Line. One direction: forward.
- The Window
- Our current field of attention. It moves; the project does not get rearranged.
- Inquiry
- The learning that decides what comes next.
- Cycles
- Repeated experiments, unrolled onto the Line rather than spinning in place.
- Now
- The constantly moving boundary between observation and intention.
tl
A practice needs an instrument.
tl keeps one line in one readable file in your repository. It is a terminal tool and a command line at once, so a person and a coding agent can both work from the same record.
$ tl window
● sketch the method
● pick the name
│ NOW
○ write the method doc
○ parse line.md
$ tl add "ship v0.1" --after ^r7e
$ tl advance --result "round-trip tests pass"