Work as a river

Most task managers end each task with a tick in a box. Andon has no "done", on purpose. This chapter explains why, and what that changes day to day.

A flow, not a checklist

Think of a project as a river. The water keeps moving: it changes course, meets rocks, joins other streams. The four states don't measure how much is finished. They describe how the water is moving right now.

• White: the water hasn't started to flow.
• Green: the water flows. Nothing to report.
• Orange: a rock in the stream. The water is held back, for now.
• Red: a channel that runs dry. The water won't go that way.

Why there is no "done"

A river doesn't finish: it reaches the sea and becomes part of something larger. Work is the same. Something you deliver gets used and built upon; a decision you make becomes the context for the next one. Ticking a box invites you to close and forget. Andon keeps the work, and the story behind it, where you can find it again.

• A task that went well stays green. Its notes keep the why and the how.
• When a whole project has reached the sea, archive it. It leaves the list and stays searchable.
• Kanban boards follow their own logic: their steps do finish, and a green step means done (chapter 10).

Green is more resilient than done

A "done" task is a snapshot: true on the day you ticked it, silent afterwards. When something changes later, you have to reopen it, and often you don't notice that you should.

A green task stays alive in the flow:

• It can still react. If a problem appears, the task turns orange, and its project shows it at once.
• Its context grows with it. Notes, files and history stay attached and keep accumulating, so the next change starts from everything known so far.
• Nothing has to be reopened. The work was never closed, so it absorbs change instead of breaking under it.

Rocks in the stream

Water doesn't fight a rock. It waits, rises, or finds a way around. Orange is the same: a temporary blocker, not a failure. Write what you are waiting for, follow up, and let the flow resume. Pushing harder on a blocked task rarely moves it; working on something that flows usually does.

Channels that run dry

Sometimes a route goes nowhere: the approach doesn't work here and now, with these means. Forcing it wastes effort. Set it to red, write why, and let the water take another channel. The red task isn't thrown away: it marks where the water couldn't pass, and the idea may flow again in a different context.

When many channels run dry in the same project, the riverbed itself may be wrong. That is the moment to branch: move the ideas worth pursuing into a project with a better context (chapter 12).

Small changes, steady flow

A river shapes its valley grain by grain, not in one flood. Work is the same. Small changes made every day keep the flow going:

• They are easy to understand. One step, one line in the notes, and anyone can follow what happened.
• They are easy to undo. The note history keeps every version, and a small step that goes wrong costs little.
• They keep the colors honest. Each change shows on its own, so the project list stays a true picture.

A big change all at once is a flood. Many tasks move at the same time, the reasons get lost, and the flow can stop altogether. When a large change can't be avoided, split it into steps you can follow one by one, or branch it into its own project (chapter 12), so the main flow keeps running.

Flowing day to day

• Look at the flow, not at a score. The project list shows where the water moves and where it is held back.
• Keep your attention on the step at hand. The last task in each list is where the water is now.
• Prefer a small step today over a big change next month.
• When something changes, pause before reacting: write a line in the notes, or consult the Yi Jing (chapter 14).
• Let finished work flow on: keep it green, and archive projects that have reached the sea.