How can a small team of engineers create a disproportionately large impact on an entire organization's productivity? Fabien Deshayes, Platform Engineering Manager at Monzo, recently shared his playbook for building highly efficient Developer Experience (DevEx) teams. His presentation detailed Monzo's journey of transforming internal development, proving that a strategic focus on team skills, product mindset, and impact communication can yield massive returns.
A Case Study in Velocity: Monzo's Experimentation Platform
The power of this approach is exemplified by Monzo's "Developer Velocity" squad. A small team of just three engineers successfully replaced a cumbersome, in-house experimentation platform in only seven months. The results were staggering:
- The number of experiments run doubled (from 70 to 134).
- The time to a decision was halved (from 43 to 21 days).
This success wasn't an accident; it was the result of a deliberate strategy for building and running a DevEx team.
Building the Team: Beyond "Superhero" Engineers
According to Deshayes, you don't need a team of "superheroes." Instead, you need a balanced mix of specific skills and attributes:
- Product Acumen: DevEx engineers must view their internal users as customers. This means making pragmatic trade-offs, understanding user pain points, and thinking long-term about the platform's evolution.
- Company Tenure: Engineers with experience at the company bring an invaluable network for user research and a deep understanding of existing systems and cultural context.
- Soft Skills: A great internal product is useless if no one adopts it. The ability to "sell" the platform, build relationships, and convince other teams of its value is non-negotiable.
Platform as a Product: A Core Principle
The most critical mindset shift is to treat your internal platform "as a product." This involves a comprehensive, user-centric approach:
- Align with Company Values: Build solutions that feel native to your organization's culture. For Monzo, this meant making tools that were "magically simple."
- Solve Real, High-Value Problems: Focus on the most significant pain points that, when solved, will provide the most leverage.
- Find Champions: Identify leaders and influential early adopters who can advocate for your platform and drive adoption.
- Meet Users Where They Are: Integrate with existing, popular workflows. At Monzo, this meant building Slack bots and integrating with established tools rather than forcing developers into a new context.
- Iterate with Early Feedback: Engage continuously with users—including non-engineers like data scientists and designers—to gather feedback and ensure the product is heading in the right direction.
- Plan for Adoption: Have a clear strategy for both "carrot" (a product so good people want to use it) and "stick" (mandating use for critical systems) approaches.
Communicating Impact: Making the Invisible Visible
A common challenge for DevEx teams is articulating their value to leadership. Deshayes breaks down impact metrics into several key categories, moving from the straightforward to the more complex:
- Time & Money Saved: These are the easiest to quantify (e.g., reducing CI build times, optimizing cloud costs).
- Productivity: Frame improvements using established frameworks like DORA Core 4 (Deployment Frequency, Lead Time for Changes, etc.) or SPACE (Satisfaction, Performance, etc.).
- Adoption: Track organic usage as a powerful indicator of product quality and the scale of its impact.
- Future Enablement: Show how current platform work is a prerequisite for future product features and capabilities.
- Risk Reduction: Instead of just highlighting risks, frame the work in positive terms, such as preventing incidents or ensuring compliance.
- Cognitive Load Reduction: Demonstrate how streamlining workflows and integrating tools allows developers to focus on what matters.
- Developer Happiness & Retention: Use surveys to measure satisfaction and argue that a positive developer experience is a key factor in retaining top talent.
Conclusion
Fabien Deshayes' insights from Monzo provide a clear and actionable framework for any organization looking to level up its developer experience. By assembling the right team, adopting a rigorous product mindset, and learning to speak the language of impact, platform engineering teams can move from being a cost center to a critical driver of business velocity.
Reference: Achieve Optimal Efficiency for Your Developer Experience Teams