The kanban board is the default view in almost every project tool, and for good reason. It is simple, visual, and easy to update. But it answers one question well and another poorly.
What a board is good at
A board answers “what is happening right now?” You can see what is in progress, what is in review, and what is stuck. For a team's daily work, that is often enough.
What a board hides
A board treats every card as independent. It cannot show that App integration is waiting on Payments API, which is waiting on Auth service. So when Auth slips, the board still shows two healthy cards further right.
The impact of a delay is invisible until someone traces the chain by hand, usually at the next standup, sometimes at launch.
What a dependency graph adds
- Impact. Move one task and every downstream task shows its new date.
- Priority. The critical path tells you which tasks actually decide the launch date.
- Honest risk. A task can be “in progress” and still be the reason the launch is at risk.
Use both, but lead with the graph
You do not need to give up the board. It is a fine view for daily work. The point is that the board and the graph should be two views of the same data, so they never disagree, and that the graph should be where you look when you ask “are we going to make it?”
Questions a board cannot answer
- If this task is three days late, does the launch move?
- Which of the twenty cards in progress actually decides our date?
- Who is blocked, and on what?
- How much room is left before the deadline?
Each of these needs dependencies and dates, which a column of cards does not have.
How to start using a graph
- Pick one upcoming launch, not the whole backlog.
- For each task, record what it waits on.
- Add rough durations.
- Let a tool compute dates and the critical path.
- Review the graph in your next planning meeting instead of the board.
Most teams find one or two surprises in the first session: a task nobody thought was critical, or a dependency that was never written down.
In Keel the graph is the main view and the board is a secondary one. See the board or the graph.
