<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Michaël Bétemps on Medium]]></title>
        <description><![CDATA[Stories by Michaël Bétemps on Medium]]></description>
        <link>https://medium.com/@mb1407?source=rss-4b87e381b26f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oYJ0wmWj3I0WHtimFVxL8w.jpeg</url>
            <title>Stories by Michaël Bétemps on Medium</title>
            <link>https://medium.com/@mb1407?source=rss-4b87e381b26f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:34:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mb1407/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[DevEx: From Theory to Practice]]></title>
            <link>https://medium.com/criteo-engineering/devex-from-theory-to-practice-bb74e7923f5a?source=rss-4b87e381b26f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb74e7923f5a</guid>
            <category><![CDATA[developer-experience]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[developer-workflow]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[developer-productivity]]></category>
            <dc:creator><![CDATA[Michaël Bétemps]]></dc:creator>
            <pubDate>Tue, 15 Oct 2024 06:51:39 GMT</pubDate>
            <atom:updated>2024-10-15T06:51:39.537Z</atom:updated>
            <content:encoded><![CDATA[<p>Explore how to start your DevEx journey with practical strategies that boost developer satisfaction, productivity, and overall performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TEJsFIe7TzyNcJ9rHxK7cA.png" /></figure><p>In my previous article “<a href="https://techblog.criteo.com/why-your-devex-journey-matters-704d33d5ba06">Why your DevEx journey matters</a>”, I introduced the concept of “Developer Experience” (“DevEx”) and explained how it helps development teams deliver high-quality software (and hopefully with a lot more fun).</p><p>In this follow-up piece, we’ll delve deeper into bringing DevEx to life by exploring:</p><ol><li><strong>The Reality of DevEx:</strong> A look at how DevEx manifests in real-world settings and its tangible impact on development teams.</li><li><strong>Building the Foundations: </strong>The key pillars essential for establishing a strong DevEx program.</li><li><strong>Criteo’s DevEx Journey:</strong> An inside view of the initial steps taken at Criteo.</li></ol><p>Join me as we explore how a dedicated focus on DevEx creates meaningful change to help your organization innovate and deliver faster!</p><h3><strong>The Reality of DevEx</strong></h3><p>The SPACE framework — <a href="https://techblog.criteo.com/why-your-devex-journey-matters-704d33d5ba06#d372">which I introduced in my previous article</a> — does a good job at laying the foundation of what DevEx is and the areas it covers:</p><ul><li><strong>S</strong>atisfaction and well-being</li><li><strong>P</strong>erformance</li><li><strong>A</strong>ctivity</li><li><strong>C</strong>ommunication and collaboration</li><li><strong>E</strong>fficiency and flow</li></ul><p>However, this framework remains a little bit too theoretical and depends much on the specific context of your software delivery organization. What are the kinds of problems and questions that will arise during your DevEx journey, explained in plain and simple words? Let’s explore.</p><p><strong>Satisfaction and well-being </strong>—<em> “Satisfaction is how fulfilled developers feel with their work, team, tools, or culture; well-being is how healthy and happy they are, and how their work impacts it.”</em></p><ul><li><em>Culture, Environment: </em>Does our culture let the developers work in the way that best suits them?</li><li><em>Well-being:</em> Is the work environment preserving the developers’ well-being and health? How do they feel about being here?</li><li><em>Image, Reputation</em>: Do the developers feel valued for their expertise? What image do they have of the company? Are they proud to work here?</li></ul><p><strong>Performance</strong> — <em>“Performance is the outcome of a system or process.” : Quality, Impact… </em>Feedback loops can positively or negatively influence how developers see the outcomes of the processes they are part of.</p><ul><li><em>Perceived quality:</em> How do developers feel about the quality (performance, stability, …) of what they produce? Are they satisfied with the code they craft?</li><li><em>Measured quality</em>: Are developers fed with actual production data and benchmarks to help them understand where they stand compared to others, within the organization and against their competitors?</li><li><em>Impacts</em>: Are developers fed with business data showing the impact of what they delivered? Client satisfaction scores? Or even achievements with business value (cost-saving, opportunity…)</li></ul><p><strong>Activity </strong>— <em>“Activity is a count of actions or outputs completed in the course of performing work.”</em></p><p>Developer Experience is factored in all the activities performed. Activities must be analyzed and optimized wherever possible.</p><ul><li><em>Performance</em>: How many activities are performed successfully (Review code, Push code, Deploy, Tickets completed…)? How valuable is it to complete so many tasks?</li><li><em>Value</em>: Is the task required from the developer meaningful? Does it bring value? Will it bring a sense of achievement or, on the contrary, feel irrelevant?</li><li><em>Cognitive load:</em> Is the task complex to master? Do we have efficient tools or procedures? Can the documentation be easily found?</li><li><em>Feedback loop:</em> Do the developers receive proper feedback on the task’s performance and on what could have been done more efficiently?</li></ul><p><strong>Communication and collaboration </strong>— <em>“Communication and collaboration capture how people and teams communicate and work together.”</em></p><p>Good communication and collaboration across the teams sound like obvious requirements, but there might be other things required to prevent a “collaboration overload.”</p><ul><li><em>Healthy relationships</em>: Are the relationships between coworkers healthy? Is there for example a peer-feedback process to ensure that people get the opportunity to voice out their concerns and appreciation?</li><li><em>Complexity of the connections:</em> Do we understand how many connections exist between the teams? How much collaboration is required to perform a task?</li><li><em>Clear boundaries</em>: How efficient are the interactions? Do we have a clear process for managing hands-off between teams? Is there a transversal capability that can be used to offload teams, such as standardized documentation for the most common interactions?</li></ul><p><strong>Efficiency and flow </strong>— “Efficiency and flow capture the ability to complete work or make progress on it with minimal interruptions or delays, whether individually or through a system.”<strong>.</strong></p><p>Developers are eager to perform their tasks as fast as possible, without the feeling of wasting their time performing low-value tasks and without constantly stumbling on issues or disruptions.</p><p>Their workflows must be analyzed and then optimized to:</p><ul><li><em>simplify the processes and reduce the number of steps,</em></li><li><em>eliminate inefficiencies and interruptions,</em></li><li><em>reduce complexity and low-value (aka boring) stuff,</em></li><li><em>improve each step and automate what can be.</em></li></ul><p>Do you now better understand how a managed approach to handling those topics could improve the overall experience of your developers?</p><p>The developers get interrupted less often, and the teams will eventually become more productive thanks to fewer inefficiencies, complex procedures, and inefficient context switching….</p><h3><strong>Building the Foundations</strong></h3><p>How do you actually bring these improvements to life? I believe there are <strong>3 key pillars </strong>that<strong> </strong>should support your DevEx transformation journey.</p><h4>#1 DevEx concerns everyone</h4><p>The success of a DevEx transformation depends on the organization’s ability to spark actions and ideas from across <strong>all</strong> the organizational layers.</p><p><strong>At the development team’s level,</strong> a good DevEx is the consequence of well-thought workflows and efficient collaboration between the members of your team, embodying topics such as the onboarding of the new developers, how we run the Agile ceremonies, or how we maintain the knowledge of how to operate our systems…</p><blockquote>Having a shared documentation describing how to install a local development environment in a repeatable way, in a standard format including troubleshooting steps for the most common issues, is a good DevEx practice.</blockquote><p><strong>Between development teams,</strong> a good DevEx is also the result of efficient interactions with the other teams. How easy is it to consume each other’s resources? Use the APIs? Reuse code? Leverage each other’s knowledge?</p><blockquote>Designing developer-friendly APIs and write documentation for the developers consuming the service is strongly beneficial to your DevEx.</blockquote><p><strong>For the teams building the transversal capabilities and tooling </strong><em>(what we call here at Criteo the “Platform Team”) </em>— DevEx is a compass that sets clear expectations on how efficient and developer-friendly the internal tooling must be.</p><blockquote>DevEx challenges the performance of the centralized CI pipeline in aspects such as the speed of the workflow, the quality of the feedback loops and error handling, or the ease of its integration with the local development environment.</blockquote><p><strong>For the management</strong> — DevEx is a performance driver for the organization, which means that the leadership team must foster transparency, facilitate inspection, and fully support what is done to improve the Developer Experience by prioritizing the right topics.</p><h4>#2 DevEx is a journey, not a set of requirements</h4><p>Identifying new areas of improvement is an ever-going process that requires the teams to allocate time to inspect the data and feedback, define actions, and then prioritize those actions based on their expected return value.</p><blockquote>DevEx is about Listening, Learning, and Tailoring our approach.</blockquote><p>While there is no out-of-the-box list of areas to cover, a good place to start with is the list of DevOps capabilities from DORA:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*oLjbZ1EyOTMyB3v445108g.png" /><figcaption>DORA Capability — from <a href="https://dora.dev/capabilities/">https://dora.dev/capabilities/</a></figcaption></figure><h4>#3 Make of DevEX a habit</h4><blockquote>Always remember that at its core, DevEx is about enhancing <a href="https://en.wikipedia.org/wiki/Flow_(psychology)">the flow state</a> of developers, reducing their cognitive load, and creating effective feedback loops.</blockquote><p>Achieving this requires a methodical approach: our focus should be on systematically transforming the data and signals gathered across the organization into actionable improvement strategies.</p><p>By taking a holistic perspective, we can implement changes that enhance developers’ work lives, leading to a more efficient and supportive environment.</p><p><em>How do we get there? What data should we rely on? How will we analyze it? What guidance will we provide dev teams for inspecting this data? And how do we ensure that action items are consistently addressed? </em>We need to answer these crucial questions to make DevEx improvement a lasting habit.</p><p>I hope that by now, it is clear that there is no silver bullet for achieving the first-class developer experience your team dreams of. Instead, we must nurture a strong culture that will gradually transform the organization.</p><p>With that in mind, let’s take a closer look at how we began this journey at Criteo.</p><h3>Getting started with DevEx @ Criteo</h3><p>Openness. Criteo’s R&amp;D culture has fully embraced the Agile principles of self-organization, trust, and shared accountability.</p><blockquote>At Criteo this value is reflected through <strong>our engineering practices</strong> (all the developers have access to the whole code base, internal open-source projects, opportunity to dedicate 10% of your time to work on a project of your choosing…), how <strong>we share information</strong> (full open access to Jira and Confluence Spaces, teams’ roadmap publicly available, regular All-Hands meetings…), but also how we <strong>manage projects</strong> and programs.</blockquote><p>That’s why It quickly became clear that for a DevEx program to succeed at Criteo, it would need to be rooted in awareness and empowerment, supported by the right level of expertise and guidance from our central teams.</p><p>Each of the below topics plays a crucial role in building a DevEx culture:</p><ol><li><strong>Foster transparency</strong>: Transparency is essential for enabling inspection and adaptation.</li><li><strong>Talk about DevEx</strong>: Make DevEx a core part of your development culture.</li><li><strong>Empower the teams</strong>: Trust your developers to take ownership.</li><li><strong>Invest in your Platform team</strong>: Centralize and leverage your DevEx knowledge.</li></ol><p>Let’s explore each of these areas in more detail, beginning with the importance of transparency.</p><h3>Foster transparency</h3><p>Should you invest in the latest fancy tool, revamp your CI/CD pipeline, offer more autonomy to your teams, or perhaps adopt a new framework for documentation?</p><p>The truth is, you won’t know until you ask your developers what truly matters to them.</p><p>Effective feedback loops are crucial for gathering the correct data to inform your decisions. In other words, managing Developer Experience is about capturing the right tangible and intangible signals from your environment and transforming them into action items.</p><p>But what kind of data are we talking about?</p><ul><li><strong>Product Metrics</strong> (DevOps/DORA metrics, Product KPIs, Delivery KPIs, SLAs, …) are collected to monitor the quality and performance of the service delivered by the Internal Platform team. While those metrics are not directly related to DevEX, improving them might often indirectly impact a better experience for your developers.</li><li><strong>DevEx Signal Metrics</strong> capture the tangible and intangible factors that drive the developer experience across the organization. You can see this as a radar showing all the things that are going well and not going so well in our software delivery organization, which will eventually drive up (or down) the developers’ perception and satisfaction. For example, the data could come from surveys based on the SPACE framework drivers or from interviews.</li><li><strong>Unstructured information</strong>, such as comments received through feedback forms, change requests, or even informal discussions with the developers.</li></ul><p>At Criteo, we’ve implemented various approaches to gather and utilize feedback effectively:</p><ul><li><strong>Perception-based Surveys</strong>: Sent quarterly to gauge developers’ satisfaction and feelings on various topics, detect pain points and anti-patterns, and measure satisfaction on internal products.</li><li><strong>Dashboards</strong>: These aggregate internal product metrics, KPIs, and data from our release pipeline to give us a clear view of performance.</li><li><strong>Fast Feedback Forms</strong>: Integrated into our internal tools for quick insights.</li><li><strong>Self-Service Tickets</strong>: Allowing developers to request new features or services.</li></ul><p>By consolidating these inputs, we ensure that problems receive the attention they deserve and are prioritized effectively.</p><h3>Talk about DevEx!</h3><p>The first step in improving the Developer Experience is raising awareness by leveraging the data you’ve collected and communicating the successes of your DevEx initiatives.</p><blockquote>“A truly successful DevEx program is one where everyone — from developers to senior leadership — recognizes and discusses DevEx as a pivotal tool for driving operational excellence.” <em>— Famous last words</em></blockquote><p>DevEx should be seen as a shared responsibility across the organization: Raising awareness ensures that all stakeholders — from developers to managers and cross-functional teams — understand the critical role a positive DevEx plays in driving overall success.</p><p>When DevEx is widely recognized, developers feel more empowered to voice their challenges and suggest enhancements, fostering a culture of collaboration and transparency. This creates a virtuous cycle of continuous improvement, essential for sustaining your DevEx transformation.</p><p>Among the things that could help you get started:</p><ul><li><strong>Communicating Data and Metrics</strong>: Foster transparency by communicating often on the quantitative and qualitative data you’ve collected. This will show people that you care about their problems and communicating the progress will keep the teams motivated.</li><li><strong>Organizing Events and Workshops.</strong> At Criteo, we organize an annual event called “<a href="https://techblog.criteo.com/tagged/developer-experience">DevX Days</a>.” This week-long initiative is dedicated to discussing Developer Experience, where our Platform teams have the opportunity to showcase their expertise and promote their products — whether it’s driving adoption, providing support, or sharing best practices — with their internal clients.</li><li><strong>Running Communication Campaigns</strong>: Newsletters, blog posts, and live Q&amp;A sessions are good tools to communicate the success stories and talk about what is being worked on.</li><li><strong>Recognizing Contributions.</strong> Recognize the teams and individual contributors who have taken DevEx seriously and accomplished meaningful progress. A good way to do this is to mention them in your newsletter.</li></ul><h3>Empower the teams</h3><p>Development teams are the ones who interact most closely with the tools, processes, and systems that shape their day-to-day workflows. They have firsthand knowledge of what works and what doesn’t, making them uniquely positioned to identify inefficiencies and bottlenecks.</p><p>At Criteo, we recommend that teams conduct an inspection-adaptation cycle focused on their Developer Experience once per quarter. This inspection usually happens during a workshop or Sprint Retrospective.</p><p>Here’s how a typical cycle unfolds:</p><ol><li><strong>Review of the data by the Lead</strong>: The Team Lead reviews available data and feedback to identify patterns and create a list of topics to be discussed further with the team. One key input of this process is the latest DevEx snapshot (a perception-based survey we do once per quarter), which helps map out issues and areas of improvement.</li><li><strong>Inspect the data with the Team</strong>: The team discusses the data, focusing on items identified as top priorities. They ask critical questions: Is our code review process inefficient? Do we have all the runbooks needed for smooth operation? Is our legacy code too hard to maintain? Cross-referencing survey results with operational data ensures that the problem is fully understood before any action is taken.</li><li><strong>Build the action plan</strong>: The team brainstorms to identify actionable steps. What is the smallest yet impactful step we can take next quarter to improve the DevEx in our team?</li><li><strong>Consistent Follow-Up</strong>: One of the most common pitfalls of retrospectives is the lack of follow-through on action items. To ensure these efforts lead to real change, we recommend dedicating time and resources in the next quarter to work on the identified improvements (At Criteo, we rely on OKRs to plan the work of the quarter).</li></ol><blockquote>Tip<em>: Time-boxing this process keeps the team focused on top priorities and realistic improvement targets.</em></blockquote><p>This continuous improvement cycle not only keeps development teams ahead of the curve but also fosters a culture of ownership and accountability: As developers see their work environment evolving, they will become more engaged, motivated, and invested in proactively seeking out and implementing further improvements.</p><h3>Invest in your Platform team</h3><p>At Criteo the Platform team serves as the central hub where an organization’s software delivery systems and tools are unified and optimized for use by all development teams.</p><p>By having a dedicated space — whether it’s a team, engineering group, or even a guild/community — focused on optimizing DevEx, you can ensure that the entire organization benefits from the <strong>insights</strong> and <strong>best practices </strong>gathered across different teams.</p><p>At Criteo we expect our Platform team to:</p><ul><li>Craft the internal tools to build quickly great apps for our business</li><li>Maintain the stack and services needed to monitor and operate a large-scale data platform</li><li>Support the dev teams, Foster adoption of the best practices</li></ul><p>From my experience, when your organization is getting started with DevEx it is very difficult to find dedicated resources or sometimes even to know where to first focus your energy. In such a situation it is best to stay as lean as possible: <strong>start small</strong>, <strong>experiment</strong>,<strong> find out what works</strong> and what does not, then build on top of the knowledge you gained.</p><p>Among the basic steps you could take, you could:</p><ol><li>Create <strong>a shared home </strong>for all the best DevEx practices and tools, and foster their adoption.</li><li>Invest in your <strong>internal product management:</strong> A managed approach will always produce better results than just throwing your resources up in the air hoping to make an impact.</li><li><strong>Learn to listen to your dev teams and internal clients</strong>: All the insights from the DevEx campaigns and feedback from the internal clients must feed the <a href="https://medium.com/criteo-engineering/product-roadmaps-for-platform-teams-a-trick-or-a-treat-a8c58b9f9d5e">roadmaps of your internal products</a> to make sure you build the right capabilities (product, service, support, documentation…).</li><li>Focus your <strong>internal product management</strong> on identified use cases and workflows, where it has the best return on investment for your business.</li><li><strong>Build a</strong> <strong>Developer Onboarding process</strong>: The onboarding is the first impression a new joiner will get from your company, you want to make sure to make it memorable! Continuously refine the onboarding process, ensuring the developers have easy access to the tools, documentation, and resources they need to be productive from day one.</li></ol><p>One of the cool initiatives that we started implementing around DevEx at Criteo was what we called the “golden paths initiative”: a project that aimed to identify the key workflows needed by our internal clients, map them with all the existing systems, processes, and tools already existing, then work together to drastically optimize them.</p><p>While this project is still ongoing, we already noticed that not only did it sharpen the collaboration within the Platform teams, but it also helped put the experience and performance of the developers back at the center of the discussions we have.</p><h3>What happens next?</h3><p>In this article, we have learnt that…</p><ul><li>DevEx is everyone’s responsibility</li><li>DevEx definition must be aligned with the org’s goals and priorities</li><li>Finding ways to measure DevEx is key for understanding what’s going on within the organization, within the teams, between the teams, or with the service provided by the central teams</li><li>The data collected must be analyzed in a way that makes sense in your specific context</li></ul><p>Now that we’ve started on our DevEx journey, in our next article we will discuss the challenges and impacts on our organization, and how we tackled them at Criteo. To be continued….</p><p><em>Did you enjoy reading this article? You can find all our articles about Developer Experience </em><a href="https://medium.com/criteo-engineering/tagged/criteo-devxdays"><em>on the Criteo R&amp;D Blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb74e7923f5a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/criteo-engineering/devex-from-theory-to-practice-bb74e7923f5a">DevEx: From Theory to Practice</a> was originally published in <a href="https://medium.com/criteo-engineering">Criteo Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why your DevEx journey matters]]></title>
            <link>https://medium.com/criteo-engineering/why-your-devex-journey-matters-704d33d5ba06?source=rss-4b87e381b26f------2</link>
            <guid isPermaLink="false">https://medium.com/p/704d33d5ba06</guid>
            <category><![CDATA[developer-experience]]></category>
            <category><![CDATA[devex]]></category>
            <category><![CDATA[criteo]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[space-framework]]></category>
            <dc:creator><![CDATA[Michaël Bétemps]]></dc:creator>
            <pubDate>Tue, 20 Feb 2024 07:47:31 GMT</pubDate>
            <atom:updated>2024-02-20T07:47:31.283Z</atom:updated>
            <content:encoded><![CDATA[<p>Despite software development’s rich legacy of over 70 years, a surprising number of companies still overlook the management of their developers’ experience, an essential aspect that can significantly enhance innovation and productivity. Could Developer Experience revolutionize the tech industry just as UX transformed the client experience?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rPIVvhwt04S1WC4LAdrNrw.png" /><figcaption>A developer lost in the maze of the poor DevEx</figcaption></figure><p>Developer Experience (DevEx) is a relatively new concept that encompasses the holistic journey and environment in which software developers perform their work, but how does it translate into actual actions that will improve the daily lives of the people working in your organization?</p><p>Let’s find out together…</p><h3>Developer Experience (DevEx): A definition</h3><p>DevEx is about making developers happy and eventually more productive by optimizing their tools and processes, but it is also about enhancing the workflows to boost their efficiency, creativity, and satisfaction.</p><blockquote>By nature, the exact definition of DevEx is specific to each company. Want to understand more about how we defined it at Criteo? Look<a href="https://medium.com/criteo-engineering/developer-experience-what-is-it-and-what-are-we-doing-about-it-at-criteo-410e559d750b"> at this blog post </a>from Clement Boone.</blockquote><p>By prioritizing developer-friendly interfaces, automated tasks, and rapid feedback loops, DevEx aims to minimize friction and empower developers to produce high-quality software with speed and enjoyment.</p><p>You could argue this is nothing new, and you would be right. Let’s look at how we have been managing developer experience until now…</p><h3>Existing frameworks and paradigms</h3><p>Developer Experience is an emerging field of expertise built upon the knowledge and practices explored by various frameworks and research studies. Let’s look at the main paradigms.</p><h4>The DORA Metrics <strong>(2014)</strong></h4><p><a href="https://dora.dev/">DORA is a well-known research organization</a> that has developed a set of key performance indicators (KPIs) to measure the effectiveness of DevOps practices. Monitoring these metrics helps teams assess the impact of their DevOps efforts on the development process, deployment speed, and system reliability.</p><p>DORA metrics include:</p><ul><li><strong>Deployment Frequency:</strong> How often code is deployed to production.</li><li><strong>Lead Time for Changes:</strong> The time it takes to go from code commit to production deployment.</li><li><strong>Mean Time to Recover (MTTR):</strong> The time it takes to recover from incidents or failures.</li><li><strong>Change Failure Rate:</strong> The percentage of deployments that result in failures.</li><li><strong>Reliability:</strong> The measured availability, performance, or accuracy of the service.</li></ul><p>While DORA metrics can be useful in some contexts, they come with issues that could lead your organization in the wrong direction. In other words, those metrics should not be used in isolation but instead in combination with other data points.</p><ul><li><strong>Lack of focus on people:</strong> DORA metrics are purely technical and do not reflect the satisfaction, well-being, or performance of the developers working in the organization.</li><li><strong>Lack of focus on the value delivered</strong>: Frequent delivery of small items will push the metrics up regardless of the value those changes bring to the organization or their quality.</li></ul><h4>Accelerate: The Science of Lean Software and DevOps (2018)</h4><p><a href="https://en.wikipedia.org/wiki/Accelerate_(book)">Accelerate </a>is a book by Nicole Forsgren, Jez Humble, and Gene Kim, which presents a research-based approach to software development and DevOps practices, focusing on how high-performing organizations achieve better software delivery and organizational performance.</p><p>The book introduces a framework built upon extensive research and empirical data collected over multiple years. The framework defines several key metrics and practices associated with high-performing teams and organizations. These metrics align closely with the DORA metrics mentioned above, as DORA is one of the research efforts that contributed to the insights presented in this book.</p><p>Over the past years, we’ve seen more and more companies (especially IT services companies) promoting Accelerate as a way to become more efficient and productive, but we should not forget that Accelerate is not a one-fit-all solution but merely a compass pointing us toward the best practices and solutions that worked at other companies.</p><h4>The SPACE framework (2021)</h4><p>The <a href="https://queue.acm.org/detail.cfm?id=3454124">SPACE framework</a> is a research-based approach to measuring, understanding, and improving developer productivity.</p><p>This framework was developed by a group of researchers from GitHub, Microsoft, and the University of Victoria (Canada), and it encourages engineering leaders to have a holistic approach to developer productivity.</p><p>The SPACE framework identifies five dimensions for developer productivity:</p><p><strong>Satisfaction and well-being</strong></p><p><em>“Satisfaction is how fulfilled developers feel with their work, team, tools, or culture; well-being is how healthy and happy they are, and how their work impacts it.”</em></p><p><strong>Performance</strong></p><p><em>“Performance is the outcome of a system or process.” (for whatever it means in the specific context of your organization in terms of quality, productivity, impact…)</em></p><p><strong>Activity</strong></p><p><em>“Activity is a count of actions or outputs completed in the course of performing work.” These include outputs like design documents and actions like incident mitigation.</em></p><p><strong>Communication and collaboration</strong></p><p><em>“Communication and collaboration capture how people and teams communicate and work together.”</em></p><p><strong>Efficiency and flow</strong></p><p><em>“Efficiency and flow capture the ability to complete work or make progress on it with minimal interruptions or delays, whether individually or through a system.”</em></p><h4>The Three Dimensions of DevEx (2023)</h4><p><a href="https://queue.acm.org/detail.cfm?id=3595878">Through a whitepaper </a>written by Abi Noda (from <a href="http://getdx.org/">getdx.org</a>) and the team behind the SPACE framework, the three dimensions of DevEx came in 2023 as a simplified, more practical version of the framework.</p><p>According to this article, DevEx really comes down to mastering the art of Flow State, lightening the Cognitive Load, and perfecting Feedback Loops.</p><p><strong>Cognitive Load</strong></p><p>Context-switching, overly complex processes, and unnecessary tasks kill productivity and drag down the developers’ satisfaction.</p><p><strong>Feedback Loops</strong></p><p>Fast, frequent and meaningful feedback loops through the entire development lifecycle reduce friction and interruptions and contribute to the continuous improvement of the overall process.</p><p><strong>Flow State</strong></p><p>Complete work or make progress on it with minimal interruptions or delays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8EXSfHuIaYR8jS6b4uyQXQ.png" /><figcaption>The Three Dimensions of DevEx</figcaption></figure><p>The impact and performance of this model was studied <a href="https://queue.acm.org/detail.cfm?id=3639443">in this whitepaper </a>from GitHub and DX, published in 2024. Without surprise, it successfully demonstrated the strong relationship between operational performance and developer experience.</p><h3>DevEx, yet another gimmick?</h3><p>We’re seeing so many new trends in our industry, but often, those new methodologies or tools are not put into practice the way they should. Take Agile, for example: how many companies are actually doing it the right way? How many companies really get some value out of it?</p><blockquote>To remain time and resources efficient, we must apply DevEx only when it makes sense to do so, with our expectations and constraints stated clearly upfront.</blockquote><p>We might be stating the obvious here, but seamless tools, intuitive interfaces (UX/UI, APIs…), and developer-friendly documentation let developers focus on <strong>solving problems </strong>and<strong> delivering business value</strong>. This has more or less always been the case, and DevEx is just a way to put this under a managed process.</p><p>In a way, this is aligned with the Lean principle of getting rid of all kinds of waste to achieve flow, as defined by Mihály Csíkszentmihályi<a href="https://en.wikipedia.org/wiki/Flow_(psychology)"> in his eponymous book</a>.</p><h4>Time is money</h4><p>According to <a href="https://stripe.com/files/reports/the-developer-coefficient.pdf">a 2018 survey by Stripe</a>, engineering teams spend an average of<strong> 41% of their time</strong> dealing with bugs, technical debt and maintenance.</p><p>In other words, this means companies waste billions of dollars because of avoidable inefficiencies in the software development process. Improving DevEx can help reduce this time and allow developers to focus on value-added tasks, positively impacting an organization’s revenue and innovation while lowering costs.</p><p>At <strong>Criteo</strong>, our 2023 perception-based developers survey showed that our developers were wasting — or at least, believed they were wasting — around <strong>20% of their time </strong>on development environment-related issues alone. We had to do something about it!</p><p>While those problems can be hard to identify or could feel petty if not backed by meaningful data, <strong>addressing them in a consistent, data-driven way can surely bring significant benefits</strong> to the organization.</p><h4>An organizational booster</h4><p>A great Developer Experience accelerates development cycles, fosters creativity, and helps attract top talent. By continuously challenging the experience we offer to our developers, we achieve the following goals:</p><ul><li>Increase engagement &amp; retention</li><li>Increase productivity</li><li>Reduce friction</li><li>Onboard faster newcomers</li><li>Attract (more) top talents</li><li>Deliver higher-quality code</li><li>Enhance collaboration</li></ul><blockquote>At <strong>Criteo</strong>, we’re organizing an annual Devx Days event where each team gets to share with the rest of the organization what they learned about developer experience and foster the adoption of the best practices and tools at their disposal.</blockquote><h4>DevEx, another name for User Experience (UX)?</h4><p>The ultimate goal of DevEx is to increase developer productivity and satisfaction by improving the tools, processes, and workflows developers use to perform their daily software development work.</p><p>UX (User Experience), on the other hand, is about optimizing how end-users interact with and experience a product or service. It focuses on making the user’s journey intuitive, efficient, and enjoyable, ultimately aiming for high customer satisfaction.</p><p>In other words, UX is a good practice for the teams to design better User Interfaces and deliver a smoother User Experience to their developers or clients.</p><p>While the concept of DevEx isn’t entirely novel, adopting a managed approach will introduce the necessary awareness to facilitate change in a deliberate and systematic manner. Our industry is just embarking on a long journey; let’s see where it leads us.</p><p>We have set the stage by defining what DevEx means, now let us try to define in a next article how it can or should impact the organization. To be continued…</p><p><em>Did you enjoy reading this article? You can find all our articles about Developer Experience </em><a href="https://medium.com/criteo-engineering/tagged/developer-experience"><em>on the Criteo R&amp;D Blog</em></a><em>.</em></p><p><a href="https://bit.ly/eng-careers-medium">Engineering</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=704d33d5ba06" width="1" height="1" alt=""><hr><p><a href="https://medium.com/criteo-engineering/why-your-devex-journey-matters-704d33d5ba06">Why your DevEx journey matters</a> was originally published in <a href="https://medium.com/criteo-engineering">Criteo Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>