Developer Experience Measurement Template

Quarterly is the standard cadence. More frequent surveys cause fatigue and do not give you enough time to act on feedback between cycles. Less frequent surveys miss emerging issues. If you are making a major infrastructure change, add a targeted pulse survey (3-5 questions) one month after the change. For designing effective surveys, see the [survey design template](/templates/survey-design-template).

On a 1-10 scale, scores above 7.5 indicate a healthy engineering environment. Scores between 5-7 suggest meaningful friction that is tolerable but reducing productivity. Scores below 5 indicate systemic issues that are likely causing attrition. Compare your scores to the industry benchmarks published in the annual DORA State of DevOps Report.

Yes. Platform teams benefit from outcome-based goals tied to DevEx metrics rather than output-based goals like "ship X features." An example OKR: "Reduce P50 CI pipeline duration from 18 minutes to 10 minutes (measured via GitHub Actions data)." The [OKR template](/templates/okr-template) provides a structured format for setting these goals.

Bug reports describe broken functionality. Friction logs capture anything that slows an engineer down, including things that work as designed but are confusing, slow, or require unnecessary steps. A CI pipeline that takes 18 minutes is not a bug, but it is friction. Friction logs reveal the "death by a thousand cuts" problems that never make it into a bug tracker.