<?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 Tomk on Medium]]></title>
        <description><![CDATA[Stories by Tomk on Medium]]></description>
        <link>https://medium.com/@tomkoch444?source=rss-8ae4f131e4e2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zAXlg3OMal3iQtbpsDfKeg.png</url>
            <title>Stories by Tomk on Medium</title>
            <link>https://medium.com/@tomkoch444?source=rss-8ae4f131e4e2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:56:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tomkoch444/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[What’s on the minds of CTOs regarding Engineering Excellence]]></title>
            <link>https://engineering.backmarket.com/whats-on-the-minds-of-ctos-regarding-engineering-excellence-f81da0431990?source=rss-8ae4f131e4e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f81da0431990</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[tech-culture]]></category>
            <category><![CDATA[engineering-excellence]]></category>
            <category><![CDATA[technical-program-manager]]></category>
            <category><![CDATA[product-engineering]]></category>
            <dc:creator><![CDATA[Tomk]]></dc:creator>
            <pubDate>Tue, 22 Apr 2025 08:02:24 GMT</pubDate>
            <atom:updated>2025-04-22T08:02:24.794Z</atom:updated>
            <content:encoded><![CDATA[<h4>How 10 CTOs inspired Back Market to enhance problem identification, prioritization, and success measurement practices.</h4><p>In July 2023, Back Market’s Engineering leadership launched a series of Continuous Improvement (CI) programs to address challenges across six key areas: <strong>Engineering Excellence, Architecture, Organizational Efficiency, Employee Development, Automation, and Accountability</strong>. The objective was to refine our practices in identifying, prioritizing, and measuring engineering challenges while driving alignment with broader business goals.</p><p>At Back Market, we define <strong>Engineering Excellence </strong>as the ideal where technical debt is meticulously managed, and a scalable culture of superior engineering practices thrives. Tech companies effectively control maintenance costs while rapidly delivering high-quality products and new features to users. Robust incident management, effective information sharing, and facilitation are key components, leading to insightful post-mortem and continuous improvement. This culture of engineering excellence supports ongoing scalability and a steady time-to-market.</p><p>To benchmark our efforts, we interviewed 10 CTOs and technology leaders from organizations, including Red Hat, L’Occitane, Veepee, BPI France Digital, Malt, Playplay, Sipios, Batch, and OpenClassrooms (Appendix 1). These interviews provided valuable insights into how different companies approach continuous improvement, enabling us to identify best practices that can be tailored to Back Market’s context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EmjW-bKkzNBsK9ypGhqiZQ.jpeg" /></figure><p>This white paper outlines our findings, internal perspectives, and the specific actions we are taking to enhance our engineering excellence practices. The focus is structured around four critical themes:</p><ol><li><strong>Identification of challenges</strong></li><li><strong>Prioritization of initiatives</strong></li><li><strong>Measuring success</strong></li><li><strong>People and governance</strong></li></ol><p>For each theme, we present:</p><ul><li>External insights from the interviews</li><li>Back Market’s internal perspective and alignment</li><li>Concrete actions agreed upon by our leadership team</li></ul><h3>Identification of Challenges</h3><h4>How CTOs are identifying Engineering Excellence challenges</h4><p><strong>Automatic, Individual, and Group Identification:</strong> According to surveyed CTOs, challenges within engineering ecosystems are typically identified through a combination of automated tools and human-driven processes. Programmatic identification involves incidents, monitoring tools, and key performance indicators (KPIs), which provide quantitative insights into recurring issues. Complementing this, qualitative feedback is gathered through structured discussions during recurring rituals, which can be broadly categorized into two types:</p><ul><li><strong>Governance Rituals:</strong> These include activities such as preparing transversal roadmaps, conducting monthly or quarterly reviews of Technical Initiatives (TINs), and hosting regular committee meetings. These forums ensure that overarching challenges and cross-functional dependencies are addressed strategically.</li><li><strong>Staff Engineering Rituals:</strong> <a href="https://engineering.backmarket.com/what-is-a-staff-engineer-at-back-market-288eebe7c70b">Staff Engineers</a> play a pivotal role through mechanisms like 1:1 meetings, Staff Community sessions, <a href="https://medium.com/coyo-tech/how-spotifys-chapters-helped-us-overcome-our-engineering-silos-and-regain-alignment-ad419a96549f">Chapter</a> gatherings, and workgroups. These settings foster collaboration to drive engineering discoveries, generate Architecture Decision Records (ADRs), and lead systemic changes within the organization.</li></ul><p><strong>Effective Framing:</strong> Both automated and qualitative channels contribute to identifying gaps between the current state and the desired state. However, when these gaps are not clearly defined, some organizations conduct engineering discoveries — time-boxed explorations designed to refine problem definitions and clarify desired outcomes. The goal is to focus on actionable and measurable results, such as influencing a single KPI, rather than engaging in broad and unfocused research.</p><p>Additionally, OpenClassrooms emphasizes the importance of the developer experience alongside desired outputs when framing initiatives. By embedding high standards for developer experience into the problem-definition process, organizations can ensure initiatives are both impactful and aligned with the needs of the engineering team.</p><h4>Back Markets’ perspective</h4><p>Our existing channels for problem identification — such as 1:1 meetings, Chapters, and monthly rituals within the Staff+ community — have proven effective. However, we recognize an opportunity to further enhance decision-making and prioritization by improving how we frame engineering challenges. Precise and well-structured framing, supported by clearly defined outcomes and tangible endpoints, can elevate discussions and ensure that initiatives are actionable, focused, and impactful.</p><p>To achieve this, we propose introducing focused exploration sessions led by Staff Engineers. These sessions, conducted within clearly defined, time-boxed periods, would allow dedicated task forces to deeply analyze complex challenges, clarify objectives, and propose actionable solutions. Embedding these framing practices into our governance forums would ensure a structured process for both initiating and concluding initiatives.</p><p>Additionally, we aim to strengthen our governance rituals by incorporating regular discussions on transversal issues — those that span multiple teams or domains. By focusing on the criticality and maturity of these issues, we can refine delivery priorities, enhance coordination, and manage cross-topic dependencies more effectively.</p><p>Through these enhancements, we aim to ensure that every initiative is not only well-defined but also strategically aligned with our organizational goals, paving the way for improved collaboration, execution, and results.</p><h4>Improvements Back Market Engineering leadership group agreed on</h4><ul><li>Developed a standardized process for initiating and driving CI initiatives, including framing guidelines and success metrics.</li><li>Instituted a requirement for all CI initiatives to include a clear Definition of Done (DoD) and measurable success outcomes.</li><li>Introduced a monthly review to identify and confirm cross-functional challenges, ensuring alignment with organizational priorities.</li></ul><h3>Prioritization of initiatives</h3><h4>Insights on the prioritization challenge</h4><p><strong>Integrating Tech and Product Objectives:</strong> Effective prioritization begins with embedding technical considerations into the development of new features. This approach ensures that technical compliance is not an afterthought but an integral part of product design. PlayPlay illustrates this with its dual criteria of “Tech Lovable” and “Product Lovable,” emphasizing that features must meet both technical and user-focused standards.</p><blockquote>Hervé from Batch aptly notes that “a stand-alone technical debt project is merely an admission of past failure to incorporate adequate technological investment during feature development.”</blockquote><p>To prevent such scenarios, organizations like PlayPlay and Veepee recommend allocating 30% of engineering capacity to technical initiatives, striking a balance between feature development and technical maintenance.</p><p><strong>Judgment-Based Rituals and Holistic Focus: </strong>Maintaining focus on a manageable number of priorities is essential, and most organizations achieve this through recurring governance mechanisms, such as monthly or quarterly prioritization meetings. These rituals often combine <strong>top-down strategic directives</strong> with bandwidth allocation for <strong>evolutions, bug fixes, and tactical projects</strong>.</p><p>A common theme across these rituals is their reliance on judgment-based assessments to evaluate initiatives based on their potential macro-level impact. For example:</p><ol><li><strong>Macro-level gains:</strong> L’Occitane prioritizes initiatives that “generate value,” “reduce risk,” or are “critical for the company,” while Sipios focuses on “bug reduction,” “time-to-market improvements,” and “cost savings.”</li><li><strong>Alignment with broader goals:</strong> Organizations like OpenClassrooms and Malt map initiatives to OKRs using tools like Tech OKRs or “Opportunity → Solution trees.”</li></ol><p>To ensure continuous attention across all software dimensions, many organizations use <strong>rotating themes</strong> in their governance rituals. Sipios, for instance, evaluates initiatives across categories such as functional quality (testing), non-functional quality (security), scalability, developer experience, architecture, and data. Similarly, BPI prioritizes work based on stability, security, quality, and data quality.</p><p><strong>Frameworks and Exploratory Validation:</strong> When prioritization becomes challenging, organizations often turn to <strong>time-boxed engineering discoveries</strong> to validate assumptions before committing resources. These exploratory efforts provide clarity and confidence in decision-making.</p><p>Additionally, various frameworks are employed to support governance and prioritization processes, such as:</p><ul><li><strong>Benefit/Effort Analysis</strong> with P1–P4 categorization.</li><li><strong>RICE</strong> (Reach, Impact, Confidence, Effort).</li><li><strong>SWOT</strong> (Strengths, Weaknesses, Opportunities, Threats).</li><li><strong>LUV-ME</strong> (Legal Users Value Maturity rest-Effort).</li></ul><p>These tools, combined with structured budget allocations that consider technical maintenance needs, provide organizations with a systematic approach to balancing short-term demands and long-term sustainability.</p><h4>Back Markets’ perspective</h4><p>In accordance with the interviewees, we firmly believe in the importance of integrating tech compliance into objectives and, more broadly, incorporating technical work into the development of new features. To align with industry best practices, we are committed to dedicating 30% of our engineering capacity to technical initiatives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ioe5RCYpMTDtliv4bSdNRw.jpeg" /></figure><p>This commitment will be reinforced at the company level through the following actions:</p><ol><li><strong>Defining Technical vs. Product Work:</strong> We will establish a clear and shared definition of what constitutes technical work versus product-related tasks. This distinction will ensure alignment across teams and eliminate ambiguity.</li><li><strong>Standardizing Time Allocation:</strong> To operationalize the 30% commitment, we will standardize it as one week per month dedicated exclusively to technical work for all engineers. This structured approach will provide engineers with a predictable time for addressing technical challenges.</li><li><strong>Highlighting Technical Work:</strong> We plan to introduce a dedicated ritual to showcase and spotlight critical technical initiatives, including our Continuous Improvement (CI) programs. This forum will openly invite contributions from across teams, fostering collaboration and transparency. By making these initiatives more visible, we aim to empower engineers to take ownership of technical challenges, much like they do with squad-level tasks. This visibility will also help engineers and contributors better understand the impact and value of these efforts.</li></ol><p>In addition to dedicating time for technical work, we see significant value in revisiting and streamlining our backlog of Work In Progress (WIP) and upcoming (NEXT) topics. Regularly reviewing these items, as recommended by interviewees, will provide an opportunity to reduce the number of active topics and improve overall prioritization.</p><p>To achieve this, we propose establishing a new ritual focused on evaluating current deliverables</p><p>and identifying which items can be paused or reprioritized. This practice will help maintain focus on the most critical initiatives while enhancing delivery outcomes. Although we have not yet formalized a prioritization framework for this process, we plan to start with a judgment-based approach to ensure flexibility and responsiveness while gradually incorporating more structured prioritization methodologies as needed.</p><p>By implementing these measures, we aim to strike a balance between innovation, technical excellence, and efficient delivery, ensuring long-term sustainability and alignment with our organizational goals.</p><h4>Improvements Back Market Engineering leadership group agreed on</h4><ul><li>Built in one week per month for every engineer for non-product work, and communicated the change to all EMs</li><li>Wrote a definition of what should be considered as Tech work</li><li>Created a quarterly prioritization mechanism over the CI WIP and NEXT initiatives, and a monthly reflection of the relevancy of WIP</li><li>Established a quarterly ritual in the BoT (Bureau of Technology — our Engineering department) where we share Tech work being done, an opportunity to render visible the CI programs on top of Squads&#39; work</li></ul><h3>Measuring success</h3><h4>How CTOs Measure Engineering Excellence</h4><p><strong>Defining minimum thresholds<em>:</em> </strong>Achieving peak engineering excellence is complex and costly, requiring a balance of costs and benefits. Hugo from Malt emphasizes the importance of clear metrics monitoring to address performance dips or incident spikes. The tech industry often faces the temptation to invest endlessly for marginal improvements, but the key is to recognize when the level of excellence is satisfactory and maintain it without over-investing. Achieving a standard in engineering isn’t permanent due to changes in team dynamics, project requirements, and product evolution. Most interviewees agree that maintaining a specific KPI threshold long-term isn’t effective; instead, it’s better to define minimum threshold expectations for engineering excellence.</p><blockquote>“We have a tremendous difficulty in characterizing what good engineering is, but today, we can characterize what bad engineering is.” — Arnaud from VeePee</blockquote><p><strong>Reaction and simplicity:</strong><em> </em>The interviewees agree that reacting to changes to ensure production systems work well leads to tangible improvements, similar to addressing customer claims, rather than solely relying on data points, which can be misinterpreted. The complexity and cost of defining KPIs in engineering encourage some to simplify measurements, such as L’Occitane’s “<em>1 initiative 1 KPI</em>” approach, ensuring satisfactory deliverables.</p><p>OpenClassrooms defines quarterly goals with simple criteria, and Veepee encourages setting minimum guidelines impacting engineers. For OpenClassrooms, Effectiveness is measured by whether the team is working on the right things, aligning with business and product outcomes, and is tracked across all engineering squads.</p><p><strong>Top-level view of the engineering levers:</strong><em> </em>However, all interviewees agree that KPIs and indicators are essential for providing visibility into overall engineering efficiency and rely on them to steer their engineering activities (Appendix 2) , even though some are more complex to measure. For example, BPI uses a watchtower ritual for decision-making, while Malt embeds KPIs in a global dashboard within a Devportal, with local replicas by team. Both Batch and Malt emphasize the need for an engineering dashboard that aggregates critical metrics to offer a comprehensive view of engineering health and performance.</p><p><strong>Mutual ownership and accountability:</strong><em> </em>Most interviewees agree that driving necessary changes often falls to leaders such as Engineering Managers (EMs) and Staff Engineers. Veepee highlights the importance of Staff/Principal Engineers in encouraging and challenging minimal guidelines. On Playplay’s side, changes are steered through commitments, follow-ups, and efficiency in predictability: comparing project outcomes versus initial projections and analyzing root causes of drift. There is an emphasis on breaking down projects into deliverable elements within a timeframe of 4 to 6 weeks to avoid project delays and uncertainties. This approach aims to maintain a steady pace of delivery and minimize risks.</p><p><strong>Systemic changes:</strong><em> </em>OpenClassrooms adopts a systemic approach to quality, integrating standards into the process, such as requiring 100% test coverage for certain tests, enforced through continuous integration (CI) systems. This ensures quality by design rather than relying solely on post-delivery measurements.</p><blockquote>“We realized that you can implement all the good collaboration practices you want, but scaling can truly be achieved through automation or even by eliminating the need to write code” — Romain from OpenClassrooms</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Va_DAd-ocqEIqhZOp9ALXw.jpeg" /></figure><h4>Back Markets’ perspective</h4><p>At Back Market, we have taken a primarily reactive approach to improving our engineering practices, focusing on refining our Incident Management processes and follow-up actions. However, we recognize an opportunity to adopt a more proactive and consistent approach to evaluating engineering metrics over time. Inspired by the concept of creating a top-level view of engineering levers and fostering mutual ownership and accountability, we aim to empower teams to understand their unique contributions to the company’s overall engineering efficiency.</p><p>To support this, we plan to introduce a <strong>monthly review ritual</strong> dedicated to key engineering performance metrics. This initiative will:</p><ul><li>Encourage ongoing evaluation and improvement of data quality and reliability, fostering trust in decision-making processes.</li><li>Align all teams on critical engineering metrics, promoting a shared, data-driven mindset.</li><li>Define clear thresholds as benchmarks for success, driving systemic improvements and raising our standards for engineering excellence.</li></ul><p>Regularly reviewing a focused set of KPIs, which reflect our vision of Engineering Excellence, will enable us to identify root causes behind deviations from expected outcomes. This approach will ensure accountability is maintained at all levels of the organization. Each Squad will not only understand its individual metrics but also how these metrics contribute to company-wide goals, ensuring alignment and clarity across teams.</p><p>Achieving these improvements requires systemic change. To facilitate this, we acknowledge the need for a robust change management framework to ensure teams are equipped to adapt to technical changes and expectations. This transition will be implemented gradually, allowing teams to integrate new standards seamlessly into their daily workflows.</p><p>Since the summer of 2024, the Developer Experience team has been working on defining clear and achievable engineering categories, including <strong>quality &amp; reliability/stability</strong>, <strong>velocity</strong>, <strong>security &amp; compliance</strong>, and <strong>cost &amp; performance</strong>. To support these efforts, each Squad has been provided with a <strong>Scorecard</strong> to monitor their technical health, identify improvement areas, and take ownership of their contributions to overall engineering excellence. By building on these foundational efforts, we aim to drive continuous improvement, foster accountability, and sustain long-term engineering success.</p><h4>Improvements Back Market Engineering leadership group agreed on</h4><ul><li>Scheduled a monthly forum “Monthly Engineering Metrics Review” where engineering leaders will steer engineering excellence core metrics at Back Market for improvements on a rotation basis.</li><li>Shortlisted a list of KPIs we would want to look at consistently at Back Market (Appendix 3)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DDHc2Fv1Rsc4vcW43GjJVw.jpeg" /><figcaption>Speed, or the Obelix of Engineering Excellence</figcaption></figure><h3>People and Governance</h3><h4>How People and Governance contribute to CTOs’ strategy</h4><p><strong>Hire and develop: </strong>Companies like Malt emphasize that while processes are essential, the success of any initiative ultimately depends on people understanding their roles and responsibilities. Providing effective support and setting clear expectations for lead engineers and staff is critical for fostering success. Similarly, PlayPlay underscores the importance of prioritizing recruitment and maintaining high individual performance standards, complemented by mechanisms to consistently elevate team capabilities.</p><p><strong>Knowing people’s skill gaps:</strong><em> </em>Sipios adopts a comprehensive approach to competency mapping, covering three areas:</p><ul><li><em>techno-agnostic skills</em> such as refactoring,</li><li><em>technology-specific skills,</em> including front-end and back-end expertise,</li><li><em>project-specific skills</em> such as client libraries and integrations.</li></ul><p>OpenClassrooms also places a strong emphasis on competency mapping and career development, ensuring employees have clearly defined pathways for skill acquisition and growth. Their approach incorporates detailed surveys and feedback tools, such as Culture Amp, to gather actionable insights on aspects like the work environment and managerial effectiveness. These surveys, conducted in collaboration with HR, maintain anonymity while providing demographic breakdowns to identify specific areas for improvement.</p><p><strong>Investment in learning:</strong><em> </em>L’Occitane has heavily invested in internal training over the past three years, evolving from 36-week courses for global groups to 12 eight-week modules. These training sessions cover topics from full-stack development to rational thinking and encourage peer discussions that strengthen collaboration and departmental alignment. A few examples of effective governance mechanisms that worked for tech leaders are accessible in Appendix 4.</p><h4>Back Markets’ perspective</h4><p>We are generally satisfied with the clarity of roles and expectations for both individual contributors and managers. However, we acknowledge a gap in obtaining in-depth feedback from our engineers, which some other tech companies seem to gather effectively for assessing skills mapping and maturity, and driving related improvements. While we have conducted “health checks” at the squad level and company-wide employee surveys, we recognize that we could enhance this practice by gaining a better understanding of training needs through in-depth surveys and skills mapping. Additionally, we should invest more heavily in targeted training areas to address those knowledge gaps.</p><h4>Improvements Back Market Engineering leadership group agreed on</h4><p>To date, our governance mechanisms have focused on enhancing <strong>Identification</strong>, <strong>Prioritization</strong>, and <strong>Success Measurements</strong>. While we recognize the importance of addressing knowledge gaps and training needs as part of our continuous improvement strategy, this area has not yet been a primary focus. However, it remains a key consideration on our roadmap for future initiatives.</p><h3>Conclusion</h3><p>Insights gathered from 10 leading CTOs have influenced Back Market’s journey to improve its engineering practices. These conversations provided clarity and actionable strategies for identifying opportunities, prioritizing initiatives, and measuring success, enabling us to build a robust framework for continuous improvement and data-driven decision-making.</p><p>A key takeaway was the industry-wide alignment on the value of integrating technical work into feature development, with a dedicated 30% bandwidth allocation. This approach reinforces our commitment to maintaining a balance between innovation and operational excellence. Additionally, the emphasis on streamlining deliverables and adopting prioritization frameworks has inspired us to focus on<strong> </strong>execution efficiency while aligning with strategic objectives.</p><p>Equally impactful was the understanding of how global engineering metrics can be reviewed more effectively. By refining our approach to metric evaluation and alignment, we aim to maintain and elevate our standards of engineering excellence while fostering greater accountability across teams.</p><p>Beyond operational improvements, the interviews underscored the vital role of people and skill development in sustaining long-term excellence. We have identified this as a critical focus area for 2025, with plans to strengthen skill mapping, expand training opportunities, and foster knowledge sharing across the organization.</p><p>As we move forward, we remain committed to tailoring these best practices to Back Market’s unique context, ensuring alignment with our people, processes, and technologies. By bridging external insights with our internal realities, we aim not only to refine our engineering practices but to set new benchmarks for excellence within our industry. This comprehensive approach will empower us to drive innovation, deliver exceptional results, and sustain a culture of improvement for years to come.</p><h3>Special thanks to</h3><p>A heartfelt thank you to the interview participants who generously dedicated their time: <a href="https://www.linkedin.com/in/alexismonville/"><strong>Alexis Monville</strong></a><strong>, </strong><a href="https://www.linkedin.com/in/buzzacaro/"><strong>Alain Buzaccaro</strong></a><strong>, </strong><a href="https://www.linkedin.com/in/alexmass/"><strong>Alexandre Masselot</strong></a><strong>, </strong><a href="https://www.linkedin.com/in/aporterie/"><strong>Arnaud Porterie</strong></a><strong>, </strong><a href="https://www.linkedin.com/in/florent-p-a063801/"><strong>Florent Poissonnet</strong></a><strong>, </strong><a href="https://www.linkedin.com/in/vianneybriois/"><strong>Vianney Briois</strong></a><strong>, </strong><a href="https://www.linkedin.com/in/hervelourdin/"><strong>Hervé Lourdin</strong></a><strong>, </strong><a href="https://www.linkedin.com/in/hugolassiege/"><strong>Hugo Lassiege</strong></a><strong>, </strong><a href="https://www.linkedin.com/in/romain-kuzniak/"><strong>Romain Kuzniac</strong></a><strong>, </strong><a href="https://www.linkedin.com/in/woodyrousseau/"><strong>Woody Rousseau</strong></a><strong>, and </strong><a href="https://www.linkedin.com/in/ludiakue/"><strong>Ludi Akue</strong></a>.</p><p>We also extend our gratitude to the Tech Rocks Community and <a href="https://www.linkedin.com/in/dbaeli/"><strong>Dimitri Baeli</strong></a> for facilitating connections between tech leaders and Back Market.</p><p>A sincere thank you to <a href="https://www.linkedin.com/in/farhatsami/"><strong>Sami Farhat</strong></a><strong> </strong>for co-organizing the workshop with Back Market Engineering Leadership that allowed us to internalize these insights and convert them into actionable strategies.</p><p>—</p><p><em>Co-written by </em><a href="https://www.linkedin.com/in/tom-koch-20a18494/"><strong><em>Tom Koch</em></strong></a><em> — Staff Technical Program Manager &amp; </em><a href="https://www.linkedin.com/in/bertrandlehurt/"><strong><em>Bertrand Lehurt </em></strong></a><em>— Director of Product Engineering at </em><strong><em>Back Market</em></strong></p><p>Don’t hesitate to drop a comment, and if you want to join our Bureau of Technology or any other Back Market department, <a href="https://jobs.lever.co/backmarket">take a look here, we’re hiring!</a> 🤗</p><h4>Appendix 1</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*pXyWISZfd6pzw94YqpqDTA.png" /></figure><h4>Appendix 2</h4><p>If a company isn’t listed next to a KPI in the table below, it doesn’t necessarily mean they don’t use it: only that it wasn’t explicitly mentioned during the interview.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*9qs5hK3iv_zDwye56C-N1g.png" /></figure><h4>Appendix 3</h4><p>Below are the most voted metrics that we agreed to measure and/or monitor in the Monthly EMR (Engineering Metrics Review).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*F-pQ8KEKx3lktBNfOeNukg.png" /></figure><h4>Appendix 4</h4><p>Here are some governance rituals we explored with leaders: offered as inspiration for effective ways of working.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sz80Xckqfrm8mcMQ4u4-6A.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f81da0431990" width="1" height="1" alt=""><hr><p><a href="https://engineering.backmarket.com/whats-on-the-minds-of-ctos-regarding-engineering-excellence-f81da0431990">What’s on the minds of CTOs regarding Engineering Excellence</a> was originally published in <a href="https://engineering.backmarket.com/">Back Market Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>