Throughline

Learn in cycles. Move in a line.

A learning log for what happened, what it taught, and what changed because of it.

Get the toolRead the practice

The Line

Most systems organize work by state. This one organizes business 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 learning log instead. Intentions, events, evidence, decisions, exclusions and outcomes occupy positions on it because each can teach the organization something. Completed work, captured artifacts and discoveries become history rather than piling up in a column.

NOW
past → now → future

The line itself becomes the durable learning record.

Cycles

The work is cyclical. The line is not.

We plan, do, study, adjust, and go again. But progress does not travel in circles — time moves forward, so the cycle unrolls onto the line. Every experiment, decision, adjustment, release, mistake, screenshot, call summary and discovery becomes another point on it.

Inquiry manages the cycle. Plan is intention ahead of Now. Do and Study become events, evidence and results behind Now. Adjust is the answer to what changed next.

TIME ───────────────────────────────────────────────────▶

 Plan → Do → Study → Adjust → Plan → Do → Study → Adjust
 └────────── cycle ──────────┘ └────────── cycle ───────
the loop, unrolled

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.

NOW
behind Now is history — ahead of it is intention

The Window

Nobody has to hold the whole line 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 line 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.

THE WINDOWNOW
the window moves forward — and detail fades with distance

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 or a decision made. It is something learned and carried forward. Each pass asks the same five questions, and each answer changes the line ahead.

  1. What do we know?
  2. What do we need to learn?
  3. What should we try next?
  4. What happened?
  5. What does that change?

The last one is the one that moves things. An answer that changes nothing was not worth asking.

Learning

Accountability means making the organization smarter.

Throughline does not measure whether reality matched the plan. A plan is a snapshot of what the organization believed at the time, not a promise that future reality must obey.

Good work may ship the planned thing. It may also invalidate an assumption, explain why something should be excluded, connect a screenshot to a customer decision, or make the next experiment better informed.

Accountability means carrying learning forward until it changes what the organization does.

A thread is accounted for when the organization can say what it meant, what it changed, or why it should not change anything yet. Unconnected threads are prompts for inquiry, not evidence for blame.

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.

LAUNCHNOW
post-launch work is a place, not a container

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 learning log ordered through time.
Flow
Movement along the Line. One direction: forward.
The Window
Our current field of attention. It moves; the line 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.

tlflow

A practice needs an instrument.

tlflow 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.

$ tlflow window
  ● sketch the method
  ● pick the name
  │ NOW
  ○ write the method doc
  ○ parse line.md

$ tlflow add "ship v0.1" --after ^r7e
$ tlflow advance --result "round-trip tests pass"
placement is required — there is no backlog to drop things into

It also speaks MCP, so a coding agent gets typed tools instead of parsing terminal output — and the handshake teaches it the vocabulary, so it arrives already knowing what Now means.

$ cargo install --path tlflow
$ tlflow init
$ tlflow