Nick QuirkEvery agency has had this conversation. A client asks how the site migration is going, the PM says "about 70%," and three weeks later it's still 70%. Nobody lied. The number was just measuring the wrong thing.
Hill charts fix this by tracking certainty instead of completion. Each piece of work is a dot on a curve. On the uphill side, you're still figuring out how the work will be done. Over the crest, you know exactly what's left and it's just execution. A dot stuck at the top of the hill tells you something a progress bar never will: the team thinks they've solved it, but nothing has shipped yet.
Why percent-complete lies on campaign work
Percentages assume the work is knowable up front. That's fine for printing 5,000 flyers. It's terrible for a technical SEO audit, where you don't know whether the crawl budget issue is a faceted navigation problem or a legacy CDN rule until you're four days in.
Here's the pattern we see constantly in agency retainers:
- Week 1: "20% done" — actually means "we've opened the files"
- Week 2: "50%" — the team is deep in discovery and genuinely doesn't know the scope yet
- Week 3: "70%" — a comfortable number that signals progress without committing to anything
- Week 4: "70%" — the hreffang implementation turned out to need dev work nobody scoped
- Week 5: "95%" — three days of frantic execution once the problem was finally understood
The real story is that weeks 1–4 were all uphill and week 5 was the entire downhill. A hill chart shows that shape. A percentage flattens it into a lie that gets discovered late.
The two halves of the hill
Uphill: unknowns still outnumber knowns
Uphill work is thinking, research, discovery, negotiation, and the first ugly attempt. You're uphill when you can't yet describe every remaining step. Examples from a typical SEO engagement:
- Auditing 40,000 URLs to find out why indexation dropped
- Deciding the information architecture for a 60-page content hub
- Waiting on the client's dev team to confirm whether server-side rendering is even possible
- Interviewing three subject-matter experts before a single brief is written
Downhill: it's known work, just not done work
Downhill is when the remaining effort is predictable. You have the brief, the template, the approved outline, the dev ticket. It can still be a lot of hours — writing 12 articles at 1,800 words each is downhill but not fast. The point is that surprises are unlikely.
The crest of the hill is the single most valuable moment in the chart. It's when your team says: we now know exactly what shipping looks like. If a scope has been sitting just below the crest for two weeks, you have a problem worth escalating today, not at the end of the month.
How to scope a hill chart for agency campaigns
The most common mistake is putting individual tasks on the hill. "Write meta description for /pricing" doesn't belong there. Hill charts work at the scope level — a meaningful chunk of outcome that one or two people own.
A good rule: 4 to 8 scopes per campaign or per monthly retainer cycle. Fewer than four and you lose resolution. More than eight and the chart becomes a dot cloud nobody reads.
Example: 90-day SEO engagement, six scopes
- Technical crawl & fix list — owner: technical lead
- Keyword and SERP mapping for 3 priority clusters — owner: strategist
- Content production, cluster 1 (8 pages) — owner: content lead
- Internal linking rework — owner: strategist
- Dev implementation of schema + Core Web Vitals — owner: PM, blocked on client dev
- Digital PR angle development — owner: outreach lead
Each of those has a genuine uphill (what should we do?) and a genuine downhill (do it). That's the test. If a scope is pure execution from day one — "publish the 8 approved articles" — it belongs on a task list, not a hill.
The weekly update ritual
A hill chart that isn't updated is worse than no chart, because it looks authoritative while being wrong. Make it a fixed 10-minute ritual.
Who updates it: the scope owner, not the PM. The person doing the work is the only one who knows whether they've crested. When PMs drag the dots, the chart becomes a management fiction.
When: same time every week. Thursday morning works well if your client check-ins are Friday — it gives you 24 hours to react to a bad signal before the client sees it.
What gets written: the dot move plus one sentence. "Moved from uphill-mid to just below the crest — we confirmed the CMS can handle dynamic canonicals, waiting on one answer from their dev lead about the staging environment." That sentence is the whole value. The dot is the headline; the note is the story.
Two rules that keep it honest: dots can move backwards, and moving backwards is not a failure. If discovery reveals a bigger problem, the dot slides back uphill and everyone learns something real. Second, a dot that doesn't move for two consecutive weeks triggers a conversation, automatically. No debate about whether it's worth raising.
Reading the chart: five patterns worth knowing
1. Everything clustered at the bottom of the uphill, week 3
The team is spread across too many scopes and nothing is getting focused attention. Kill or park two scopes and concentrate.
2. One dot parked at the crest for 10+ days
Classic false summit. Someone believes they've solved it but hasn't validated the solution. Ask for the first piece of shipped output — one page, one ticket, one draft.
3. A dot that leaps from uphill to 90% downhill in one update
Usually means the scope was too small or the owner is reporting optimistically. Worth a quick check rather than a celebration.
4. Dots sliding backwards repeatedly
Requirements are changing underneath the team. That's not an estimation problem, it's a scope creep problem, and the chart just gave you the evidence to raise it with the client.
5. Everything downhill by mid-month with hours left in the retainer
Good news, but check capacity planning. You may have under-scoped and can pull forward next month's work — or you're about to leave billable hours on the table.
Using hill charts with clients
Hill charts are unusually good for client communication because they explain why timelines behave the way they do. Most client frustration comes from the invisible uphill: they see four weeks of "in progress" and assume nobody's working. A chart showing a dot climbing steadily, with weekly notes, makes discovery legible.
Trim the client version. Three to six scopes, plain labels ("Site health fixes," not "TC-114 crawl remediation"), and one sentence each. Drop it into your project overview rather than sending it as a standalone artifact — a dot chart with no narrative invites questions you don't want to answer over email.
It also pairs well with the conversation every SEO agency has to have about
