Boosting Your Teams' Productivity? Why DORA Will Not Save Your A**

Contrarian take on team-productivity metrics from someone who's implemented them 30+ times.

For: CTOs, VPs of Engineering, Directors, Heads of EngineeringFormat: 45-60 min keynote
Marian Kamenistak leading a workshop in front of a screen reading "Measure your team's productivity" with strategy notes on the whiteboard.

Why doesn't DORA measure team productivity?

DORA four keys, deploy frequency, lead time. You instrumented all of it and the team still feels slow. Thirty-plus implementations later the pattern is consistent: the metrics measure the pipeline, not the decisions. We go through what moved, and what I got wrong the first ten times.

You leave with the Engineering Leadership Benchmarks dataset, first-party numbers from 3,400+ sessions under CC BY 4.0, so you compare your team against something real instead of a vendor blog post.

Why this talk, not a generic version of it

Thirty-plus DORA rollouts in, the pattern stayed consistent: the four keys measure the pipeline, not the decisions. Teams instrument everything, deploy frequency, lead time, and still feel slow. This talk includes the ten times that pattern wasn't obvious yet, what got misread before it became a pattern at all.

Built for CTOs and VPs of Engineering who've already got the dashboards and still can't explain why the team feels stuck. The close is the Engineering Leadership Benchmarks dataset, first-party numbers from 3,400+ mentoring sessions under a CC BY 4.0 license, so the comparison runs against something real instead of a vendor blog post.

What the room walks out with:

Read the DORA-alternatives post →

Quick answers

Who is "Boosting Your Teams' Productivity? Why DORA Will Not Save Your A**" for?
CTOs, VPs of Engineering, Directors, Heads of Engineering
What format is it delivered in?
45-60 min keynote

More talks

← Back to all talks