Lesson 7 of 7
The one-page value report
16 min
Listen to this lesson
Executives read the first page. Everything the quality council and the CFO need to know about the TCoE each quarter should fit on it: whether the capability is delivering, what it is worth against the business case, what is going wrong, and what they need to decide. The KPI cards, the register and the root-cause reviews sit behind it for anyone who wants to check.
The structure
Contoso's year-end report
Headline: "In its first year the TCoE halved regression effort, had no severity 1 escape, and is $87,000 ahead of its business case on conservative claims; we ask the council to release the second investment tranche for procure-to-pay automation and data recipes."
| Family | KPI | Latest | Trend | Target | Status |
|---|---|---|---|---|---|
| Quality | Severity-weighted escapes per quarter | 14 | Improving | Under 8 | Amber |
| Quality | DDP | 94% | Flat | Above 95% | Amber |
| Quality | Critical process coverage | 80% | Improving | 100% | On track |
| Speed | Regression cycle time | 6 days | Improving | 5 days | On track |
| Speed | Change lead time (median) | 21 days | Improving | 20 days | On track |
| Cost | Cost per regression cycle | 700 h | Improving | 700 h | Green |
| Cost | Cost of quality mix | Prevention 6%, external 13% | Improving | 8% / under 15% | On track |
| Service | Service level attainment | 88% | New | 90% | Amber |
| Service | Key-user hours in close weeks | 64 a year | Improving | Zero | Amber |
Contoso's scorecard at the end of year 1. Figures are illustrative course data consistent with lessons 2 to 4.
Below the scorecard the report shows the value block from lesson 4 (claimed $360,810 gross, −$164,590 net against −$251,800 planned), then three sentences of commentary per family. The commentary for quality says what the numbers cannot: the 14 weighted escapes a quarter come mostly from procure to pay, with five of the year's eight severity 2 escapes; it has the lowest regression coverage, and that is why the decision requested is procure-to-pay automation and data recipes. The report ends with the decision, its cost (the second tranche), and the KPIs it should move.
Writing rules
- Lead with the verdict and the ask. Executives who read one sentence should know both.
- Show trend and target beside every number; a number alone means nothing.
- Use status colors defined on the KPI cards, so amber means the same every quarter.
- Write commentary in plain business terms: "billing errors reaching customers," not "S2 escapes in SD."
- Put bad news on the page. A report that is always green stops being read.
- Link every figure to its evidence, so finance can check any line in minutes.
Dashboards help the TCoE team watch automation and execution health day to day, and SAP Cloud ALM is adding AI help here too: its Overview app can generate dashboard cards through Joule, based on SAP's dashboard generation agent. Dashboards are not the value report, though. They show what the tools see; the report adds escaped defects from the service management tool, cost from finance, attribution and judgment.
What would you do?
The CIO asks Priya to replace the one-page report with a live dashboard "so we can see the numbers any time." What should Priya propose?
- Fit the verdict, scorecard, value, commentary, risks and decisions on one page.
- Lead with the headline and the ask; show trend and target beside every number.
- Put bad news on the page and link every figure to its evidence.
- Dashboards serve daily watching; the quarterly report serves value judgment and decisions.
Check your understanding · not graded
Lesson check
1. What must the headline of the one-page value report contain?
2. Why does the report include commentary written by a person?
3. Which TCoE KPI cannot come from a test tool's dashboard alone?
4. What is the role of a live dashboard next to the quarterly one-page value report?