Most strategy tools roll progress up: team percentages average into department percentages, which average into a company number. The number is easy to report and almost always reassuring, because averaging is very good at hiding the one thing that’s going wrong.
In this guide
Key Takeaways
- →Blending: one failing bet averaged with nine healthy ones scores 90%.
- →Incomparable measures: percent of a revenue target averaged with percent of a training program.
- →Activity bias: milestone items reach 100% easily, so the average rises with activity.
- →Hidden spread: 70% could be everything at 70%, or half at 100% and half at 40%.
- →Roll up results against trajectory, exception counts and lists, status distribution and contributions.
- →None of those is a single number, and that is the point. Strategy rarely fails evenly.
Four ways averages mislead
Four separate problems, all of which push the headline number the same way: up.
| Problem | What happens |
|---|---|
| Blending | A failing bet averaged with nine healthy ones scores 90% |
| Incomparable measures | Percent of a revenue target averaged with percent of a training program |
| Activity bias | Milestone-based items reach 100% easily; result-based items lag; the average rises with activity |
| Hidden spread | 70% average could be everything at 70%, or half at 100% and half at 40% |
An averaged roll-up answers “how busy are we?” and is read as “is the strategy working?”
What to roll up instead
| Roll up | Why |
|---|---|
| Strategic results against trajectory | The few results the strategy depends on, not a blend of everything below them |
| Exceptions, as counts and lists | How many bets aren’t moving their results, and which ones |
| Distribution of status | How many items are on track, at risk, off track, not yet judged |
| Contributions to each result | Which units or initiatives are carrying the result, and which aren’t |
None of these is a single number, and that’s the point. Strategy rarely fails evenly. Reports that preserve unevenness show where it’s failing.
How to order those sections for a leadership audience is in Reporting Up: Progress vs Evidence.
Keeping the drill-down close
- Every roll-up item links to the objectives and initiatives beneath it.
- Exceptions are one click away, not three levels down.
- Weights are explicit, so a contribution’s share of a result is visible.
A worked example: 78% and failing
Here are five hypothetical initiatives under one objective. Read the progress column, then read the effect column:
Five initiatives under one objective. Read the progress column, then read the effect column.
| Initiative | Type | Progress | Effect on result |
|---|---|---|---|
| Service network | Milestones | 90% | Attach rate flat |
| Service portal | Milestones | 100% | Online orders up slightly |
| Sales retraining | Milestones | 100% | Attach rate +1 point |
| Contract model | Milestones | 60% | Not yet live |
| Service pricing | Result | 40% | Margin flat |
| Average | 78% | Services share 0.8 points behind trajectory |
A dashboard tile would read 78%, amber-to-green. The strategic result is behind, three of the five initiatives are finished or nearly finished without moving it, and the one measured by results is at 40%. The average rewarded the initiatives measured by activity.
What a reassuring number costs
A 78% tile buys a quiet board meeting and a lost quarter. The cost is not the reporting effort; it is the months of funding that keep flowing to bets the number says are fine. By the time the strategic result forces the conversation, the reallocation that should have happened in Q2 is happening in Q4.
Among published alternatives, OnStrategy lists $200 per month for unlimited users. i-nexus publishes a free Starter tier for up to five users and $28 per user per month at its Standard tier. Ask either one to show the distribution behind a roll-up number, and whether the failing item is one click away or three.
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate. Explicit contribution weights, the exception queue and the four-quadrant view sit in Essentials with OKRs and Goals, Balanced Scorecard, Hoshin Kanri and Strategy Roadmap. The 30-day free trial is enough to load one objective and see what your current average is hiding.
Distribution in Profit.co
In Profit.co, objectives show contributing key results with explicit weights, the exception queue lists bets that aren’t moving their results, and a four-quadrant chart shows initiative progress against result progress for each objective. See the strategy deployment software page and Hoshin Kanri Dashboards: What to Show and What to Leave Out.
Each of those replaces a part of the average:
- Explicit weights answer which unit is carrying the result, instead of blending all of them into one figure.
- The exception queue is the count and the list, so “three bets aren’t moving” is a number you can click.
- The four-quadrant chart is the distribution, showing the 90%-complete-and-flat initiative sitting apart from the rest.
The state that chart exists to expose is described in Alignment Isn’t Effect: Why Well-Aligned Plans Still Miss.
Free Product Demo
See what your roll-up is hiding
A 30-minute walkthrough, tailored to your team.
Book a free demo
What happens in the call
How your teams set goals, track progress and review results.
Strategy, performance, projects and engagement on one platform, with AI.
A practical path to align teams, execute faster and drive results.
Questions this article answers
They average working and failing bets, mix incomparable measures, favor activity-based items and hide how unevenly progress is spread.
Strategic results against trajectory, counts and lists of exceptions, the distribution of status and the contributions to each result.
Not as the headline. A single number hides where the strategy is failing; distributions and exception lists show it.
Milestone-based items reach 100% as soon as the work is done, while result-based items move slowly and lag. Averaging the two lets activity carry the number.
One click. If the failing item is three levels down, the roll-up is hiding it in practice even if the data exists somewhere.
