Put four things on one slide: a drift trend line, the number of reachable or time-bound risks closed, the work in flight with dates, and one decision you need from leadership. Leave out raw vulnerability counts and tool screenshots. The slide should let a busy reader say yes, no, or ask one question.
What leadership wants to know
Executives rarely need the mechanics. They want to know whether risk is going down, whether the team is on track, and whether they must do something. Answer those three in that order.
The four blocks
1. Drift trend. A simple line of one freshness measure over the last four quarters. Choose something you can explain in a sentence, such as the number of direct dependencies a major version behind, or a libyear total. Our post on libyear targets explains the trade-offs.
2. Risk closed. Count only what matters: reachable advisories fixed, and end-of-support deadlines met. State the number and the definition in small print. Raw scanner counts invite the wrong questions.
3. Work in flight. Three to five named items, each with an owner, a status and a date. Mark any that are blocked, and by what.
4. Decision needed. One ask, phrased so it can be answered quickly. For example, approve a named block of capacity, or accept a documented deferral until a stated date.
A layout that works
| Block | Position | Format |
|---|---|---|
| Drift trend | Top left | Small line chart, four points |
| Risk closed | Top right | Two numbers with definitions |
| Work in flight | Bottom left | Table, owner and date |
| Decision needed | Bottom right | One sentence, highlighted |
What to leave out
- Total vulnerability counts with no context.
- Screenshots of tool dashboards.
- Jargon such as transitive, reachability or SBOM, unless you define it on the slide.
- Ten bullets of everything the team did.
If someone wants detail, link a backup page. The slide is a summary, not a report.
Keep the numbers honest
State how the numbers are produced and keep the method steady from quarter to quarter. If you change a definition, say so and restate prior quarters. Leaders notice when a trend line improves because the rule changed.
Be careful with any statement about standards or customer commitments. Describe what you do, such as how quickly you act on reachable advisories, without claiming a certification or attestation you do not hold. For wording on that topic, see how to answer a patching speed question honestly.
Try it yourself
Click through it at your own pace, or open it full screen. Look at which figures update over time, since those are candidates for your trend line.
Where Safeguard fits
Safeguard's dependency scanning, policies and compliance evidence automation can supply the trend and closed-risk numbers for this slide. A free scan is at gold.safeguard.sh/scan.
Quick check
Can I use more than four blocks?
You can, but each extra block dilutes the decision you need. Move extras to a backup page.
How often should this slide be updated?
Quarterly for leadership, with a lighter monthly note if your organisation likes a cadence.
Last reviewed: 19 October 2026.
