Talk about your next project
Command Zero executive brief

The lesson

Attack a metric your buyers already report, then give them a named replacement set they can adopt without dropping the old one.

The move

The piece opens with a dek stating the claim, then a bold lead line: 'Fast averages can hide wrong answers, and a SOC running AI first-pass work produces a lot of fast averages.' Labeled paragraphs ('The big picture:', 'Why it matters:', 'By the numbers:') explain why a mean-time metric has no field for correctness and stack sourced figures from SANS, Gartner, Unit 42 and CrowdStrike. The core section, 'The verified-outcome scorecard: six measures for a SOC where machines go first,' gives each numbered measure, such as 'Escape rate' and 'Escalation precision,' a definition and how to collect it. It closes with 'What industry experts are saying,' 'The limits of the new scorecard,' and a 'Terms in this post' glossary of FAQ-style definitions.

Why it works

  • Our readSaying nobody should throw out MTTD and MTTR lets a security leader accept the argument without a fight with the board or auditors who already ask for those numbers.
  • Our readGiving the replacement a name and a numbered list turns an essay into something a reader can take into a metrics review.
  • Our readA section on the scorecard's own limits shows the author expects pushback and makes the position easier to trust.

What not to copy

Don't copy the SOC metrics, the third-party statistics, or the verified-outcome scorecard name. Keep the sequence of naming a broken default metric, showing exactly how it breaks, proposing a named measure set, and stating its limits.

More from Command Zero

More executive briefs

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.