PlatformEngr® Platform fundamentals course

Cheat notes · Module 06 · Prove it

Measuring value: outcomes, not output

A five-minute review for when you have done this module and want it back in your head. Open the full module for the steps and the lab, or the full text to print.

The idea

Measure outcomes against a baseline, not output. DORA's five delivery metrics, adoption, developer experience and cost show whether the platform and AI help; counts of code and pull requests rise even when they do not.

Remember

  • DORA throughput: change lead time, deployment frequency, failed deployment recovery time.
  • DORA instability: change fail rate, deployment rework rate.
  • DORA 2025: AI's "primary role is as an amplifier" of existing strengths and weaknesses.
  • METR 2025: experienced developers took 19% longer with AI and believed they were 20% faster.
  • baseline: unknown is honest; a missing baseline fails M2.
  • Output counts as metrics fail M3; put them under avoid with a reason (M5).

Pitfalls

  • "Share of code written by AI" as a target rewards volume, not outcomes.
  • Trusting how fast people feel instead of measuring lead time.
  • No cost metric once agents have budgets fails M4.

Test yourself

Answer in your head first, then open the answer.

Which metric answers "is AI helping?" here?

Change fail rate of AI-assisted changes compared with the rest, next to lead time.

Name DORA's two instability metrics.

Change fail rate and deployment rework rate.

What is the first month's work on this scorecard?

Measuring the four unknown baselines.

Where module 06 leaves you: metrics/scorecard.yaml passes the check: eight metrics, at least one each of delivery, stability, adoption, experience and cost, four baselines still unknown, and two metrics under avoid with the reason.