A hill chart measures understanding
Most project indicators describe activity: tasks closed, hours spent, or work moved to “in progress.” A hill chart describes something different—the team’s confidence that it understands how to complete a meaningful part of the project.
The curve has two sides. On the uphill side, the team is still discovering the shape of the solution. At the top, the key unknown has been resolved. On the downhill side, the path is understood and the remaining work is execution.
Why percentages hide the difficult part
A percentage looks precise but rarely explains its basis. A scope can consume most of its expected effort while the central technical or product question remains unresolved. Calling it 80% complete can create confidence exactly when the project is most exposed.
Hill positions are deliberately qualitative. They do not predict an exact delivery date. Their value is making the team state what it knows and where uncertainty remains.
Start with scopes, not every task
A scope is a coherent part of the project that can move through uncertainty and execution. “Onboarding” or “invoice approval” may be useful scopes; every button, query, and test case usually is not.
Choose enough scopes to reveal the important areas without turning the hill into a task board. If one scope contains two parts with very different uncertainty, split it. If several items always move together, combine them.
- Name scopes by meaningful outcomes or system areas
- Keep task-level checklists in the tool where execution happens
- Split a scope when its parts tell materially different stories
Update positions through conversation
Ask the person closest to a scope where it belongs and why. Moving uphill means the team has learned more but still has open questions. Crossing the top means the approach is understood—not that most of the hours are finished. Downhill movement shows execution against that understood approach.
Do not move scopes simply because another day passed. A stable position can be useful information: it may indicate that the same unknown still needs attention.
Use snapshots to tell the cycle story
The current chart is best for today’s decision. Snapshots preserve meaningful checkpoints, and Hillchart’s timeline lets you revisit those saved states across a cycle. Add a short summary when you capture one so a later reader understands what changed.
A good review looks at movement: which scopes crossed the top, which stayed uncertain, and whether shaping left a difficult area hidden. That makes the hill a learning tool, not just a reporting image.