Engineering Productivity Manager
Engineering Productivity Managers lead the teams and initiatives that measure and improve how effectively software engineers work, requiring them to communicate complex sociotechnical ideas to both engineers and senior leadership in English. This path covers the DORA and SPACE frameworks, developer experience survey language, inner source programme vocabulary, and the business case language for DPE investments.
Topics covered
- DORA & SPACE Metrics
- Developer Experience Language
- Inner Source Vocabulary
- DPE Programme Design
- Tooling Strategy Writing
- Engineering OKRs
Vocabulary spotlight
4 terms every Engineering Productivity Manager should know in English:
A DORA metric measuring how often an organisation successfully releases software to production, used as a proxy for delivery agility
"After rolling out trunk-based development, the team's deployment frequency improved from weekly to multiple times per day within two quarters."
The total mental effort required of a developer to understand, navigate, or operate a system or tool, often cited as a barrier to productivity
"The platform team's audit found that excessive cognitive load caused by fragmented tooling was the top frustration reported in the quarterly DevEx survey."
The practice of applying open-source collaboration patterns — such as contribution guides, maintainer roles, and pull requests — to proprietary code within a single organisation
"The inner source programme doubled the number of cross-team contributions to shared libraries in its first six months."
A condition of uninterrupted, focused work in which a developer is most productive, often measured as the proportion of time spent in deep work
"The SPACE survey revealed that developers entered flow state for fewer than two hours per day, largely due to excessive meeting load."
📚 Vocabulary Reference
Key terms organised by category for Engineering Productivity Managers:
DORA Metrics
SPACE Framework
Developer Experience
Tooling Strategy
Recommended exercises
Real-world scenarios you'll practise
- Presenting the quarterly DORA metrics report to the VP of Engineering, explaining why lead time for changes has plateaued despite increased tooling investment.
- Writing the business case for a new developer portal investment, quantifying the productivity gains in language that the CFO's office will accept.
- Facilitating an inner source governance meeting, proposing a new contribution tier structure and handling pushback from senior engineers.
- Running a DevEx survey debrief workshop with team leads, turning raw feedback into a prioritised roadmap of friction-reduction initiatives.