Skip to content
The title slide and first slides of the Developer Productivity Review template

Developer Productivity Review

Presentation template for Google Slides and PowerPoint

Make a copy in Google Slides
Price
Free
Slides
10
Style
Modern
Difficulty
Beginner
Updated
November 12, 2026

Every slide (10)

Overview

Engineering leaders need to know whether delivery is getting faster and whether reliability is slipping, yet most reviews answer both questions with opinion. This deck replaces opinion with trends: build times, review waits, survey scores and results, each shown against a target or the prior period. The slides follow the order a leadership team reads them, starting with the headline, then the evidence, then the bets and what they should achieve.

The sample covers Birchfield Software for one quarter, using medians and 90th percentiles rather than averages, a chart of survey scores and a matrix of improvement bets. Every figure matches across the slides. Replace the headline numbers with your own four quarters of data, state where each one comes from, set the targets, and keep actions to three, each with a named owner.

Useful for

  • A monthly leadership review where the CTO asks whether builds and releases are getting faster
  • An engineering manager checking whether the team's review waits sit above the company median
  • A platform lead choosing two or three improvement bets to fund for the next quarter

What's included

  • Build times slide with the median, the slowest steps and the next action
  • Card slide on installs, the test suite, the runner pool and the build target
  • Review times slide with four bullets on waits and a note on what is measured
  • Survey score chart with insights and a source line marked as sample data
  • Two-by-two matrix of improvement bets by effort and impact, with one highlighted
  • Results stats slide, a guide slide and a closing slide with contacts

How to use it

  1. 1

    Click Make a copy in Google Slides, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Replace the four headline figures with your last four quarters of data and name the source.

  3. 3

    Set a target for each metric, and flag any that are off track in the results.

  4. 4

    Link each incident to its postmortem, and drop incidents below your severity threshold.

  5. 5

    Delete the guide slide, then share the deck with leaders or present it at the review.

What you need

Requirements

  • A Google account with access to Google Slides

Works with

  • Google Slides
  • Microsoft PowerPoint (File → Download → .pptx)

Questions

Can we use medians for some metrics and averages for others?

Use medians and 90th percentiles for anything with a long tail, such as build and review times, and say so on the slide. Averages hide the slow cases that cause most of the frustration.

Are the Birchfield Software figures and people real?

No. The organisation, people, email addresses and every figure are fictional sample data, set in a plausible range for a UK software team. Replace them with your own measured numbers before you share the deck.

Should we track individual developer output here?

No. The deck reports team-level trends only, because individual output figures distort behaviour and invite unfair comparisons. Keep survey results anonymous and report them by team.

  • #engineering-metrics
  • #dora-metrics
  • #delivery-review
  • #engineering-kpis
  • #google-slides
  • #quarterly-review
  • #developer-experience

More engineering metrics report templates

See all 8

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…