A sponsor dashboard is the short view a sponsor reads to decide whether to intervene. Before a Friday steerco, that view has to work for people in the room and people on the line. The room is often in Johannesburg, sometimes Sandton, sometimes a Midrand office park. The people still in Pretoria, including a project lead at 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157 or in Centurion, will not see a printout on the table. A short view earns its place here: a small set of numbers, refreshed from the work, that a person can trust when the next decision is due.
A gallery of charts is a different product. The sponsor needs the decision, the date, the money, and a plain answer on whether people are using the change. Everything else can wait one click away for the project manager.
Five things, in this order
- The outcome this phase promised, in one sentence.
- Whether the date still holds, and what moved it since last time.
- Money: spent, committed, and left. One variance is enough. A cost history can live underneath.
- The decisions needed this week, each with an owner and a date.
- Adoption, if the project changes how people work. A finished build and a quiet floor is an incomplete story.
Keep the sponsor view short enough to read before the meeting, including for the person joining from Pretoria who will not be handed paper in a Johannesburg boardroom. If the steerco is in Midrand and the analyst who built the numbers is remote, the same link should open the same view. A pack that only exists as a slide in one room will be retold differently on the drive back.
A colour is a sentence
Red, amber, and green need a reason. Amber should say what would turn it red, and what the team is doing before the next meeting. If everything is green for months, the scale is being polite. Sponsors would rather see one honest amber than a page of green.
Tie the colour to a number the team already tracks: days of slip, rand of variance, or the share of people who completed the new step. When the reporting work and the project team share that definition, the steerco spends its time on the decision. Pretoria and Johannesburg should not arrive with two spreadsheets that disagree about the same date.
Write the sentence next to the colour
A red box with no words forces the sponsor to ask what it means, and the answer then depends on who is in the room. Put one sentence beside the colour: what changed, who owns the response, and the date you will look again. The person on mute in Midrand can read that sentence without waiting for the room to explain it.
Name the constraint that can move the date
South African delivery has constraints a template from elsewhere will skip. Supplier lead times that slip around month-end. Site access in a business park that winds down on a Friday, which is common in Pretoria offices, including parks out towards Centurion and 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157. A team split across cities, so a decision made in the room is a decision only once the people on the call have it in writing.
The dashboard should name the constraint that can move the date. A line that says "resources" does not help. A line that says "training seats are only in the Pretoria room, so the Johannesburg crew and the Midrand site team have not been through it" tells the sponsor where to act. That is also a change problem, which is why the risk review that keeps delivery moving and the dashboard should point at the same few items.
Keep the local constraint specific to this programme. A Midrand building that only grants access on certain days is a date risk if the work needs that building. A Johannesburg finance freeze at month-end is a date risk if the next release needs a finance sign-off in that window. Leave off constraints that are true of the country and false of this project. A dashboard full of generic worries hides the one line the sponsor can move.
One pack, drawn from the work
The dashboard is a view of the work, pulled from the same board and the same numbers the team uses in the week. If an analyst spends a day rebuilding it before steerco, the pack will drift from the kanban board the team still opens. Agree the fields once. Refresh them. Spend the meeting on the decision.
Adoption belongs on that same view. Count a behaviour: a manager opened the report, a site used the new handover, a clerk closed on the new form. Count it the same way in Pretoria, in Johannesburg, and on the Midrand site. Training attendance is a start. Use is the result. A view that only samples the head-office floor will report that head office is fine.
MetaServ's project management services build these views with the sponsor and the people who must keep them current. The way we set the work up is to agree the few fields that change a decision, then leave the team able to refresh them without a second project. We are based at 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157, and we join steerco rooms in Johannesburg and Midrand on-site or on the call.
If Friday's pack is still being rebuilt on Thursday night, talk to MetaServ about the sponsor view. Bring the pack you have. The useful question is which decision it is supposed to unlock.
Frequently asked questions
How should the report treat what a sponsor dashboard should show before Friday's steerco in Johannesburg?
A Friday steerco might sit in Johannesburg or Midrand, with people still on the line from Pretoria. The dashboard that helps names the decision before the meeting starts.
Which line from what a sponsor dashboard should show before Friday's steerco should Johannesburg keep?
The dashboard that helps names the decision before the meeting starts.
What should a sponsor bring to the working session?
Bring the current note as it stands today, not a blank example.
