Not a folder with a board on it.
Most tools give you a canvas and let you draw whatever you like on it. Convenient, and the tool never understands a single thing you drew.
A board that means something
Nodes are typed objects, not boxes with text in them. An objective is an objective, a budget is a budget, and the brain can answer questions about either.
Tasks and a timeline
What has to happen, who has it, and when it lands, in the same place as the thinking that produced it.
Documents that were read
The material attached to a project is material the brain has already ingested, so asking about it works immediately.
A decision log
What was decided and why, kept next to the work. This is the part that is still there in six months when somebody asks.
Every project answers questions.
A project is part of the brain, not a silo beside it. Ask what changed, what is blocked, or why something was decided, and the answer comes back with its source.
- Ask a project directly, in plain words.
- It draws on the board, the docs and the decisions together.
- The reasoning stays attached to the work that produced it.
Somebody will ask why in a year.
A finished project is usually a folder nobody opens again, and the person who could explain it has moved on. Here the decision stays in your company brain, so the next person to ask gets an answer instead of a reconstruction.
- What was decided is kept with why it was decided.
- It stays answerable long after the work is closed.
- Nobody has to reconstruct it from a thread.
Ship mobile before the API rewrite.
Two deals were blocked on mobile. Nothing was waiting on the rewrite.
“Why did we push the API rewrite?”
Keep the reasoning.
Join the waitlist and keep the decision next to the work that came from it.
Join the waitlist