Where the work is, not how much is left.
Hill charts for teams. Every scope is a dot: climbing while you are still figuring it out, descending once you are just building it.
- 1Onboarding flowUphill
- 2Import pipelineUphill
- 3Search rewriteDownhill
- 4Auth and billingDownhill
Import pipeline is still being figured out. Any date you give for it today is a guess.
Drag it over the summit
80% done is a lie you tell twice.
Once when you are stuck, and again a week later when you are still stuck. A percentage can only go up, so it goes up whether or not anything was figured out. A hill has two sides, and that is the whole point.
Uphill
Figuring it out
Unknowns, spikes, I think it works this way. Progress here is understanding, and it is not visible from outside.
The summit
Nothing surprising left
You can describe the rest of the work in sentences that do not contain the word probably.
Downhill
Making it happen
Execution. Boring, predictable, mostly typing. The kind of work an estimate is actually good at.
Two scopes both halfway done are in completely different amounts of trouble if one is climbing and the other is descending. Position on the hill says which.
One line in your README. It redraws itself.
Paste it into a README, a PR description, or a wiki page. Every time someone moves a dot, the image everyone is looking at changes with it.
Markdown
[](https://shape-hill.vercel.app/your-slug/view)Two styles ship with it: warm paper, or one that disappears into a GitHub README.
Renders as
That is this project's own chart, live. Click it for the full view.