What a Kanban board communicates
A Kanban board organizes work into workflow columns such as ready, in progress, review, and done. Teams can see where items are and manage work in progress.
That state is valuable, but an item in “in progress” may be nearly understood or blocked by a fundamental unknown. The column alone does not distinguish those conditions.
What a hill chart adds
A hill chart asks the team to judge uncertainty. Uphill scopes are still being understood; scopes over the top have a known path and are moving through execution.
The position is a qualitative project signal, not a promise of time remaining. It helps a conversation start in the right place.
Choose based on the question
Use Kanban when the primary question is where work sits in a repeatable process. Use a hill chart when the important question is whether the team knows how to solve each part of a shaped project.
- Workflow and work-in-progress: Kanban
- Uncertainty and confidence: hill chart
- Need both perspectives: keep the board and summarize meaningful scopes on the hill
A practical way to use both
Keep task-level execution in the system your team already uses. Represent larger, meaningful scopes in Hillchart and move them only when understanding changes. This avoids duplicating every task while adding an uncertainty view for project reviews.