The dashboard a leadership team actually opens
Most dashboards go unopened because they answer a question nobody is asking. This one starts from the executive’s real constraint, not from the tool’s capability.
“Can I press a button and it gives me a beautiful Gantt chart or a beautiful slide that I can share with my leadership team? Because normally we’re asked to come and present. And I hate writing slides.”
Director, Business Operations — international pharmaceutical group
Anatomy of a steering setup
Five views, one project identifier that binds them all, and a single rule: whatever needs attention is visible without clicking.
Health
Portfolio state on one page: progress by phase, late milestones, plan against actual. The default view.
Calendar
Inflection points over the next four to twelve months, with RAG status and detail on click. The view that replaces meeting preparation.
Resourcing
Actual effort by project and phase, available capacity, contributors. Restricted access: this view carries data identifying individuals.
Investment
Committed against invoiced, actual against plan, by quarter and by phase. Under-investment is flagged as clearly as overspend.
Leadership
A view that produces the leadership pack. The logic is documented, the figures come from the model, nobody recompiles by hand.
An example, with fictional data
The figures below are illustrative. The structure is the one running in production at an international pharmaceutical group.
Milestone progress
ActualPlanA rolling twelve months. The last point is the last closed month — partial months are never shown.
Status by workstream
Status entered by the project manager, never computed. A non-green status requires a comment.
The rules we apply
- Around ten indicators, no more. Beyond that, a leadership team’s attention wanes.
- The age of the data is on screen. A number without a refresh date is not a number.
- Only closed months are shown. A partial month misleads, every time.
- Status entered by the project manager is kept distinct from status computed by the system. Both belong — not in the same place.
- Refresh frequency follows business frequency. If the source is weekly, refreshing three times a day adds nothing.
- What leaves the dashboard cannot be edited offline. The figure shown to the leadership team is the system’s figure, not a version retouched along the way.
What we say in advance, not afterwards
- A dashboard is no substitute for a decision. It removes the excuse for not making it.
- The leadership pack is produced by the system: it mirrors the source and cannot be edited. Your comments go beside it: that is the price of a figure that stops moving once it is shared.
- Linking spend to a project assumes your finance system knows which project it belongs to. When it does not, we say so at the framing stage — and we choose another way in.