Visual project management, built on lessons learned.
Open source · Windows and Linux · no account required
AI forgets everything between sessions. Every conversation starts from scratch.
Past attempts are forgotten. Which approach failed, and for what reason?
Context is lost. The same mistakes recur.
Week 1
✓ AI generates the auth module
→ Works.
Week 4
✗ Same approach for payments
→ Fails. What was the cause again?
Week 10
? New developer, same mistake
→ No one remembers.Traditional project management tools encourage you to delete failed tasks.
Only the chosen path remains visible. The attempts, the blockers and the dead ends are lost.
Lost context is lost time,
for you and for your team.
jīng
to go through · to experience
“The river does not erase
the obstacles it met.”
On a factory line, an andon shows at a glance whether a station runs normally or needs help.
Not started. No action taken yet.
Work is proceeding normally. Green does not mean done.
Awaiting resolution. Always visible, up to project level.
Set aside with its rationale, pending a more suitable context.
A classic tool
Project: Server migration
└─ Approach A deleted
└─ ✓ Final solution kept
Result: context lostWith Andon
Project: Server migration
└─ ● Approach A: in-place upgrade
corrupted 3% of the test rows
└─ ● Approach B: new server and cutover
Status: NTR · the whole story keptA red dot is a documented record, not a failure.
A year later, when someone asks why Approach A was discontinued, the answer is on record: why it stopped, the situation at the time, and the conditions for resuming it.
A different context can make a past attempt viable today.
As work progresses, information accumulates in the tasks: decisions, attempts, blockers and results.
When the time comes to write the documentation, everything is already available: in order, structured, with the context of each step.
Andon does not replace documentation. It makes it considerably easier to write.
→ Months later, the project shows the full picture: the attempt, the blocker, the resolution and, above all, the rationale.
A card advances only once its definition of done is met.
Built-in profiles: Bug fix · Dev board · Sprint · Content, and more.
A Diagram tab on each task, to formalize the sequence of steps and the decision points. Each step becomes a child task tracked by the colors.
In what order, and through which decisions?
When a task turns orange, or before setting it to red: a short, structured review. Cast a hexagram, interpret it, and record your decision in the notes.
What is the nature of the change, and how should you respond?
UI and application
Data
Andon in a real-world setting.
andon.daelis.fr
Three colors. One objective: never lose the context.