Reporting for different audiences

The same test data serves very different readers. A tester needs to know what to run next. A process owner needs to know whether their area is on track. A steering committee needs to know whether the program will hit its go-live date and what could stop it. Good reporting builds each view from the same data, so the numbers always agree, and changes only the level of detail and the questions answered.

The daily view

Keep it operational and short. Most daily stand-ups at Contoso run through four lists: tests blocked and why (missing data, defect, environment), new critical and high defects since yesterday, defects ready for retest, and environment or access problems. Nobody needs percentages at 8:30 a.m.; they need names and actions.

The weekly view

The weekly report is where process owners like Dan and Maria see their own areas. Organize it by value stream (order to cash, procure to pay, record to report, plan to produce) and show execution, coverage of in-scope processes and high risks, and open defects by severity for each. End with a short list of decisions needed: a scope change to approve, a defect priority to confirm, a key user to free up.

The steering view

Steering committees have minutes, not hours. Lead with the answer, then the reasons. A one-page steering view for Contoso might say: "Testing is amber overall. Order to cash and record to report need two more weeks of retesting. One critical defect in period-end close blocks the exit criterion for record to report; fix expected Friday. We need finance key users released for three days next week." Supporting numbers go in a backup slide.

Making RAG status mean something

Red, amber and green are only useful if everyone knows what triggers each color. Define them against the exit criteria in your test strategy. For example: green, on track to meet all exit criteria by the planned date; amber, at risk but with a credible recovery plan; red, will not meet exit criteria by the planned date without a decision (more time, less scope, accepted risk). Always show the reason next to the color. A color without a reason invites people to argue about the color instead of the problem.

Visuals that help

A few simple visuals carry most reports. A burn-down of remaining planned tests against the days left shows schedule position at a glance. A stacked bar per value stream (passed, failed, blocked, not run) shows where the problems sit. A defect trend line by severity, covered in the next lesson, shows whether quality is converging. Avoid three-dimensional charts, gauges and traffic-light dials that need explanation; if a chart needs a paragraph to interpret, replace it with the paragraph.

Finally, keep a short narrative at the top of every weekly and steering report: three or four sentences saying what changed since last time, what worries you, and what you need. Numbers support the narrative; they do not replace it. Executives remember the sentence "record to report is red because the close test is blocked by missing intercompany data" long after they forget the percentages.