Lesson 5 of 6
Transparent reporting and stakeholder trust
11 min
A program in trouble has usually lost more than time. It has lost the trust of its sponsor, its process owners and often its users. Trust comes back slowly, through reporting that is consistently honest, measured and predictable. This lesson covers how to report so that stakeholders believe you, including when the news is bad.
Principles of honest reporting
- Measure, do not assert. Status comes from data (execution, defects, mocks, gates), not from self-assessment against milestones.
- Show trends. A single week is noise; four to six weeks show direction.
- Forecast, do not just report. Say when the current pace will finish the work, and with what contingency.
- Keep definitions stable. If "executed" or "critical" changes meaning, say so and restate history.
- Red early is a service. A risk raised early is an option for the sponsor; a risk raised at the gate is a crisis.
One source of truth
Disputes about whose spreadsheet is right waste steering committee time and erode trust. Agree one source of truth for each measure, and report from it. For test progress and defects, that is typically the test management tool, for example test plans, Test Execution Analysis and defects in SAP Cloud ALM; for scope, the requirements and their status; for cutover, the runbook and mock reports. When a number is challenged, anyone can go to the source and check.
A recovery dashboard
| Measure | This week | Trend (6 weeks) | Forecast |
|---|---|---|---|
| End-to-end SIT cases executed | 72% of 180 | Rising 8–10 points a week | Complete in 3 weeks |
| Open critical and high defects | 14 | Falling from 41 | Under 5 by SIT exit |
| Defect reopen rate | 9% | Down from 22% | Stable under 10% |
| Mock 2 float | 1.5 hours | First full-volume run | Target 4+ hours in dress rehearsal |
| Key-user hours given vs plan | 85% | Up from 55% | On plan with backfill approved |
| Contingency remaining | 60% | Used 40% in 6 weeks | Sufficient at current burn |
A recovery dashboard in the what-if: values, trends and forecasts, all from source tools.
Delivering bad news
Bad news is easier to hear when it comes with understanding and options. Use a simple structure: what happened, what it means for the outcome, what we are doing about it, what we need from you, and when we will know more. Avoid both minimizing ("a small slip") and dramatizing. In the what-if, Grace told the steering committee that the original go-live date was no longer achievable with acceptable quality, showed the evidence from the assessment, and presented two options with dates, scope and costs.
- What happenedFacts and evidence, without blame
- What it meansEffect on date, scope, cost or quality
- What we are doingActions already under way, with owners
- What we needDecisions or support from the audience
- When we will know moreNext checkpoint and what it will show
Rebuilding trust with process owners
Process owners such as Dan and Maria carry the sign-off. If they have been surprised before, they will hesitate to sign again. Bring them into the recovery: show them the evidence for their processes weekly, let them see defects and workarounds in their area before anyone else reports them, and invite them to re-execute a sample of critical cases. A process owner who has seen the evidence develop over weeks signs with confidence.
What would you do?
Two weeks after the re-baseline, a mock load reveals a reconciliation difference in open receivables for company code 1710. The cause is not yet known. The steering committee meets tomorrow. What should Grace report?
- Measure, show trends, forecast, keep definitions stable, and raise red early.
- Agree one source of truth per measure, and trace every summary number to evidence.
- Deliver bad news with facts, impact, actions, needs and a next checkpoint.
- Rebuild process owner trust through weekly evidence reviews and kept commitments.
Check your understanding · not graded
Lesson check
1. Why report trends rather than single-week values?
2. What is a single source of truth for test progress typically?
3. Which structure helps deliver bad news well?
4. How can trust with process owners be rebuilt?