Join Benjamin Kitt // Software Development Manager at Lob, and Jon Kern, the co-author of Agile Manifesto from the Adaptavist Group as they dive into an essential topic in Developer Experience [DevEx]: how to clear roadblocks that dev teams face and turn DevEx insights into actions by collaborating closely with teams.
DevEx is pivotal in delivering high-quality software quickly, yet the challenge remains: how do we actively engage brilliant engineers in this process?
In conversations with Heads of Engineering (HoE), I've learned that DevEx surveys are some of the most holistic and accessible tools for improving both DevEx and overall work quality. But the question remains: are they merely for measuring, or can they truly drive change?
We'll be exploring two key DevEx metrics—DORA and FLOW—which spotlight different delivery aspects. The central question is how to harness these insights while continuously engaging teams in improvement efforts.
The webinar will be held on November 6, at 10:00 EDT | 16:00 CEST (50 min).
Save your spot here and take a look at the key topics we’ll be discussing.
We’ll start with a fundamental question: Why does Developer Experience (DevEx) matter? The answers might surprise you. For instance, an engineering manager I recently spoke with highlighted how, as companies dive into software integration, DevEx has become essential for engineering leaders. Many organizations are adopting matrixed structures, where teams share a common platform but manage their products independently, requiring seamless integration. Without measuring and improving DevEx, this handoff process often results in repeated integration efforts across multiple teams.
From my discussions with HoE, I’ve found DevEx surveys to be highly effective for improving both Developer Experience and delivery quality.
They offer a comprehensive view across different facets of our work, allowing engineers—who excel at evaluating complex situations—to share valuable improvement ideas.
I’ll be asking the experts what aspects of DevEx surveys they find most powerful.
A common concern among tech leaders is low response rates. Survey fatigue is a real issue, but some tech organizations have achieved outstanding engagement, with DevEx survey response rates as high as 90%.
My key question here will be: What’s the secret to driving high engagement and response rates?
We’ll discuss how to transform survey insights into actionable conversations and tangible improvements. In my experience, this is often a significant challenge. It might start with a question like, How satisfied are you with…? but the real task is translating that feedback into meaningful changes.
DevEx surveys provide a framework for identifying priorities and planning actions, yet accountability, team agreements, and clear follow-through are essential to drive progress. While many improvements happen at the team level, sometimes there’s a need for tough conversations with top leadership to make real strides. I’ve observed that leadership often juggles numerous priorities, making it challenging to secure their commitment to initiatives requiring substantial investment.
Success stories do exist. A Head of Engineering at a large company recently shared some impressive results: they reduced deployment time by 50%, improved stability by 80%, increased satisfaction with DevOps tools by two points, and cut down wasted hours in development environments weekly. Now, their teams deploy to production up to 150 times a day. It’s possible—but the question is, How do we get there?
We’ll broaden our understanding of Developer Experience by examining both DORA and FLOW metrics. DORA metrics reveal insights into development quality and potential automation, while FLOW metrics focus on value delivery, helping us gauge how well we’re meeting customer needs.
Together, FLOW and DORA metrics offer a complete picture of our development processes and their true impact on end-users.