<?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 Laurent PY on Medium]]></title>
        <description><![CDATA[Stories by Laurent PY on Medium]]></description>
        <link>https://medium.com/@laurentpy?source=rss-f42a4aa26c55------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cv_184zPPucAzkut_T3bCw.png</url>
            <title>Stories by Laurent PY on Medium</title>
            <link>https://medium.com/@laurentpy?source=rss-f42a4aa26c55------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:08:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@laurentpy/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[Creating a culture of engineering excellence and team progress]]></title>
            <link>https://medium.com/promyze/creating-a-culture-of-engineering-excellence-and-team-progress-08b9835469d8?source=rss-f42a4aa26c55------2</link>
            <guid isPermaLink="false">https://medium.com/p/08b9835469d8</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Laurent PY]]></dc:creator>
            <pubDate>Mon, 03 Jun 2024 13:16:49 GMT</pubDate>
            <atom:updated>2024-06-03T13:16:49.563Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oQPySjAaQi4rpY4UqgYo2Q.png" /></figure><p>In the first post of this series about <a href="https://www.packmind.com/secret-high-performing-software-teams/">building high-performing teams</a>, I highlighted the most critical factor for developer performance: skills! The second post touched on the importance of fostering a generative culture. Now, I want to delve into a more controversial topic 🙂: performance, and how to cultivate a culture of high performance.</p><p>Having led organizations ranging from a single engineering team to over 100 engineers, my north star has been the same with these three fundamental pillars:</p><ul><li>Developing leaders with a growth mindset</li><li>Investing in goal setting and measurement</li><li>Accountability</li></ul><h3>Growth mindset</h3><p>The most talented and impactful individuals I’ve encountered are those who are impressively eager to learn and push the boundaries. This is what I mean by a growth mindset. People with a growth mindset embrace challenges, persist through obstacles, learn from criticism, and find inspiration in the success of others. They see effort as a path to mastery and view failures as opportunities to grow and improve. This is why having a <a href="https://www.packmind.com/generative-culture/">generative culture</a> is so important — failure is part of the process!</p><p>Setting the right attitude and approach towards achieving goals is critically important as it significantly influences the motivation and behavior of individuals. Goal orientation typically divides into two main types:</p><ol><li><strong>Approach Orientation</strong>: Focuses on achieving success and mastering new skills. Individuals with this orientation are motivated by the desire to improve, learn, and accomplish goals. They tend to engage in behaviors that promote learning and growth, viewing challenges as opportunities.</li><li><strong>Avoidance Orientation</strong>: Focuses on avoiding failure and negative outcomes. Individuals with this orientation are motivated by the desire to prevent mistakes and protect their self-esteem. They may avoid challenging tasks to minimize the risk of failure and criticism, which can limit their learning and growth.</li></ol><p>Understanding goal orientation helps create environments that foster a positive, growth-oriented approach, encouraging individuals to pursue success and view mistakes as part of the learning process rather than as setbacks.</p><p>When building from scratch or up-leveling a team, the key for me is to first hire leaders with a growth mindset and the ability to coach and mentor, as these people become the biggest lever for team performance. Experts who have achieved a certain level of mastery don’t necessarily know how to share that knowledge, so I look for those who can do both. When hiring more junior developers, I prioritize eagerness to learn and coachability over specific language expertise or knowledge. The goal is to upskill the team because ultimately, skill is what enables delivery performance as measured by the <a href="https://www.packmind.com/secret-high-performing-software-teams/">DORA metrics</a>.</p><p>With engineering leaders who have a growth mindset and the right attitude towards achieving goals, you are in a good spot. This leads to the next crucial part: goal setting and measurement.</p><h3>Goal setting and measurement</h3><p>We can’t discuss performance without addressing metrics and measurement. However, this isn’t about measuring developer productivity, a hot topic recently highlighted by a <a href="https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/yes-you-can-measure-software-developer-productivity">McKinsey article</a>. Many weighed in on this, including Dan North:</p><blockquote>Just don’t try to measure the individual contribution of a unit in a complex adaptive system, because the premise of the question is flawed. DORA metrics, for example, are about how the system of work works, whether as Westrum culture indicators or flow of technical change into production. They measure the engine, not the contribution of individual pistons, because that makes no sense.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*kHaLxkeo6SLzPB_X.png" /></figure><p>Delivery performance and DORA metrics are better proxies for team productivity, but they are not sufficient on their own. While DORA metrics measure the efficiency of the “engine,” businesses care about the direction: where are we going, and when will we get there?</p><p>This is where business outcomes come into play, and these outcomes should be shared by the whole team. Customers care about the business impact of processes, tasks, or activities, not just the immediate output. Outcomes can be challenging to measure as they may be long-term consequences. In such cases, define smaller units of value toward the outcome that can be delivered in a week or quarter rather than defaulting back to output metrics. Here is an example:</p><p>Assume as part of a team developing a test management tool, we plan to release a new feature using GenAI to automate manual tests. We have several definitions of success:</p><ul><li><strong>The feature being released</strong> 🚀. This is still what a lot of teams use as a success definition. Don’t 🙅🏻‍♂️. This is just the output and users may not care about the new feature. It may be just a waste of time.</li><li><strong>The number of users #️⃣.</strong> This is slightly better. Usage of this next-gen test automation feature is an indicator but not nearly good enough to be a proxy of the value delivered.</li><li><strong>Change in behavior and benefits 😇</strong>. The real outcome of a new feature is often a change in behavior that leads to a benefit. We could track, for example, the average number of tests automated per organization thanks to this new feature and correlate that number to a benefit: $x saved by test run.</li></ul><p>Using outcome-oriented metrics as shared goals is a game changer for the teams because they stop thinking about just releasing a feature but now work creatively to deliver an impact to the business. Delivery performance (and DORA metrics) tracks doing things right, while outcome-based goals ensure you’re doing the right thing.</p><h3>Accountability</h3><p>For developers, being accountable means taking ownership of their work, responsibilities, and the outcomes of their actions. Accountability around DORA metrics and business goals involves a commitment to delivering high-quality code, meeting deadlines, and adhering to best practices. It extends beyond completing tasks to ensure the code is efficient, maintainable, and free of critical bugs. Accountable developers understand the impact of their work on the overall project and strive to contribute positively to the team’s success.</p><p>Accountability also means being transparent and honest about progress and challenges. Developers should regularly communicate with their team and stakeholders, providing updates and alerting them to any issues or delays. This openness builds trust and ensures that problems are addressed promptly, minimizing their impact on the project. Taking responsibility for mistakes demonstrates a commitment to continuous improvement and learning, essential for personal and team growth.</p><p>Accountable developers actively seek feedback and learn from their peers. They recognize the importance of collaboration and knowledge sharing in a successful development process. By participating in code reviews, pair/mob programming, and team discussions, they contribute to a culture of mutual support and collective responsibility. This collaborative approach enhances code quality and fosters a sense of shared ownership and accountability.</p><p>Ultimately, accountability for developers means high agency. They anticipate potential issues and continuously seek ways to improve their skills and the development process. By embodying these principles, developers enhance their professional growth and contribute to their teams’ overall success and resilience.</p><h3>Final thought</h3><p>Creating a culture of engineering excellence and team progress hinges first on developing leaders with a growth mindset, who not only learn aggressively but also mentor and upskill their teams. It also means aligning teams with ambitious business goals, pushing boundaries, and fostering accountability. By focusing on these pillars, organizations can cultivate high-performing teams that achieve their goals while continuously improving and building new talents. This has been my recipe for ensuring that teams do the right things, the right way, ultimately driving business success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=08b9835469d8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/promyze/creating-a-culture-of-engineering-excellence-and-team-progress-08b9835469d8">Creating a culture of engineering excellence and team progress</a> was originally published in <a href="https://medium.com/promyze">Packmind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Embracing generative culture: the foundation to building high performing teams]]></title>
            <link>https://medium.com/promyze/embracing-generative-culture-the-foundation-to-building-high-performing-teams-dd6363d34944?source=rss-f42a4aa26c55------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd6363d34944</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Laurent PY]]></dc:creator>
            <pubDate>Fri, 24 May 2024 12:47:28 GMT</pubDate>
            <atom:updated>2024-05-24T12:47:28.787Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TNeO-KxWeh6KUmWV6CcWUw.png" /></figure><p>In my first post of the series about <a href="https://www.packmind.com/secret-high-performing-software-teams/">building high performing teams</a>, I shared the single biggest factor in developer performance: <strong>skills</strong>!</p><p>In this second post, I’ll focus on a pivotal aspect that can make or break the journey: organizational culture, specifically the generative culture. Based on my experience and the insights offered by the DevOps Research and Assessment (DORA), I will share a few concrete steps you can undertake to cultivate a generative culture, a critical enabler of the 10x factor in engineering performance.</p><h3>What the hell is a generative culture?</h3><p>Dr. Ron Westrum, a sociologist, researched and identified a correlation between a robust culture, which facilitates the flow of information, and positive business outcomes.</p><p>From his research, he formulated a typology to describe various organizational cultures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4ErE52w95D0PNftb.png" /><figcaption>Credits: dora.dev</figcaption></figure><p>Building a <a href="https://dora.dev/devops-capabilities/cultural/generative-organizational-culture/">generative culture</a> is one of the 27 DORA capabilities, with demonstrated leverage in increasing team performance. As you can see in the chart below, generative culture and process capabilities required to improve delivery performance build on and reinforce each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MJEC9LjYFt-54vZ5.png" /><figcaption>Credits: dora.dev</figcaption></figure><p>And that makes sense. Have you seen many examples of teams deploying multiple times a day in a culture that is bureaucratic and where failure leads to punishment? Another way to think about Westrum’s findings is to consider code as text — <strong>information that flows</strong> through the dev lifecycle to ultimately be transformed into an experience for the end user. Back to the initial statement: there is a correlation between a robust culture that facilitates the <strong>flow of information</strong> and positive business outcomes.</p><h3>Leading by example</h3><p>So the generative culture promotes an environment where information flows freely, and innovative ideas are nurtured, creating a fertile ground for high performance and continuous improvement. Cool, but how to get there?</p><p>First, let me get back to a moment that was eye-opening for me. During a 360-review, one piece of feedback really caught my attention: ‘Sometimes Laurent will elaborate and make up an answer even if it is clear that he doesn’t know the answer.’ For a long time, I always wanted to appear right and avoid showing any vulnerability to the extent that I wasn’t able to say, ‘I don’t know or I failed.’ The message this sent to the team was terrible: it is not acceptable to lack answers or to fail. That was an aha moment for me that completely transformed my approach.</p><p>Yes, as leaders, we should often be right, as per one of Amazon’s leadership principles. However, it is okay to be wrong sometimes. Being humble, open to being wrong is an opportunity to learn and improve. It also shows your team that you are authentic and vulnerable. This is how you create the psychological safety necessary for a team to thrive, give their best, and sometimes fail.</p><p>Same goes with failure. Failure should lead to inquiry instead of scapegoating. There is no innovation without failure. Failures that lead to learning have compounding effects. Without learning, this is just a waste. And this is really aligned with the lean principle of seeking constant improvement. Interestingly I have seen engineering teams way more comfortable with the approach to failure than their leadership.</p><h3>Concrete steps to create a generative culture</h3><p>Here are some concrete steps you can take to create a generative culture:</p><ol><li><strong>Demonstrate Leadership Commitment and Role Modeling: </strong>Leadership must visibly commit to and model the behaviors that encourage a generative culture. This includes showing vulnerability, admitting mistakes, and fostering an environment where learning from failures is valued over assigning blame.</li><li><strong>Encourage and Reward Collaboration:</strong>Implement systems that reward teamwork and collaboration over individual accomplishments. This can include revising performance metrics to reflect team achievements and promoting cross-functional projects. Many teams have found success using Objectives and Key Results (OKRs), among other goal-setting frameworks. The key point is to measure success at the team level, reinforcing the concept that the team is the primary unit of progress.</li><li><strong>Promote Psychological Safety: </strong>Actively foster an environment where all team members feel safe to express their ideas, concerns, and questions without fear of retribution. Encourage open debates and constructive conflict to create healthy cognitive friction. It’s crucial for teams to engage in explicit debates, disagree openly, and commit to decisions once everyone has been heard, rather than silently disagreeing and potentially undermining the decisions made.</li><li><strong>Implement Blameless Postmortems: </strong>Focus on learning, not blame, when issues arise. Blameless postmortems are critical for uncovering root causes without finger-pointing, thereby nurturing a culture of learning and continuous improvement. This approach is a key marker of a generative culture. Toyota’s adoption of the <a href="https://www.packmind.com/dantotsu-best-practices/">Dantotsu</a> Radical Quality Improvement method, transforming it into a symbol of quality excellence, exemplifies this principle at its best. This approach to quality has been successfully implemented by the tech industry as well.</li><li><strong>Strive for Information Transparency and Clarity</strong>: Promote open access to information necessary for decision-making at all levels. The more information teams have about the strategy, finances, and goals of the organization, the better their decisions will be. Of course, this means that these elements must be clearly defined and without ambiguities. This context becomes the enabling constraints for the teams, guiding them within a framework that empowers autonomy while aligning with the organization’s overall objectives.</li><li><strong>Celebrate Innovation, experimentation: </strong>Create programs that reward innovation and experimentation, even when they don’t always lead to success. Recognizing and celebrating attempts at innovation encourages a culture of continuous improvement and risk-taking. Leverage hackathons to create opportunities for cross-functional learning, aiming to explore new territories.</li><li><strong>Foster Continuous Learning: </strong>As discussed in my first post, learning and upskilling are the biggest levers for improving engineering performance. Invest in your team’s continuous development by providing access to training and education, supporting participation in industry conferences and workshops, and emphasizing learning by doing — the biggest missed opportunity. The most successful organizations implement mentoring programs, pair or mob programming, Brown Bag Lunches (BBL), and internal conferences to promote a culture of knowledge sharing and learning by doing. Retention rates are significantly higher. These principles underpin <a href="https://www.packmind.com/">Packmind</a>, the platform enabling developers to <strong>share, learn, and refine their craft daily while enhancing their workflow</strong>.</li></ol><p>This is obviously not an overnight transformation and it starts from the CEO and ELT. It always struck me how much influence the CEO has on the culture compared to the relative influence on the execution. And that’s okay, because culture is a significant lever on people’s behavior and organizational outcomes. By fostering an environment of psychological safety, collaboration, and continuous learning, organizations can unlock the 10x factor, driving unparalleled performance and innovation.</p><p>I am eager to learn more about your experiences. How have you fostered a Generative culture within your organization? What challenges and successes have you encountered in this journey?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd6363d34944" width="1" height="1" alt=""><hr><p><a href="https://medium.com/promyze/embracing-generative-culture-the-foundation-to-building-high-performing-teams-dd6363d34944">Embracing generative culture: the foundation to building high performing teams</a> was originally published in <a href="https://medium.com/promyze">Packmind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is the secret of high-performing teams and how to achieve this 10x factor?]]></title>
            <link>https://medium.com/promyze/what-is-the-secret-of-high-performing-teams-and-how-to-achieve-this-10x-factor-23ee389d2e0f?source=rss-f42a4aa26c55------2</link>
            <guid isPermaLink="false">https://medium.com/p/23ee389d2e0f</guid>
            <category><![CDATA[craftsmanship]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Laurent PY]]></dc:creator>
            <pubDate>Fri, 17 May 2024 15:30:16 GMT</pubDate>
            <atom:updated>2024-05-17T15:30:16.124Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the past 20 years, I’ve had the privilege of leading high-performing teams that delivered quality software continuously, multiple times per day. I have also been responsible for product teams struggling to release once a quarter, hampered by quality issues.</p><p>The contrast in skills and behaviors between these teams has been stark. Reflecting on these differences, I’ve been driven to understand the root causes. Turns out, it’s not that simple. The environment, especially the role of top management, plays a big part. I could easily write an essay about top management being in the way 🙂. But, once you manage to fix that, what actually prevents a team from achieving excellence and how do you really measure performance?</p><p>I decided to write a series of posts about it starting with this one:</p><ul><li><strong>What is the secret of high-performing teams and how to achieve this 10x factor?</strong></li><li>The Westrum organizational culture and the importance of creating a safe environment. Dont coddle devs</li><li>Creating a culture of engineering excellence and team progress. ⇒ Context-based driven by business contraints. Exemple of Netflix. Cuklture of sharing</li><li>Deep dive into developers’ mentoring. do assesment and focus on what natters for team and business. Sparing partner VS coach</li><li>How will AI impact engineering performance?</li></ul><h3>So, what is the secret of high-performing teams?</h3><p>One week, as I was traveling and meeting a newly acquired team, the engineering lead described their CI/CD process to me:</p><ul><li>him: <em>We have the build that can take about an hour. Then we run our API tests, about 1000 in a staging environment for a couple of hours, and then…</em></li><li>me: (I interrupted him) <em>How long does it take from a code commit to release/production?</em></li><li>him: <em>Well, about 2 weeks if we include the manual testing.</em></li><li>me: <em>Is that a problem? I mean, such a long feedback loop for your developers.</em></li><li>him: <em>No, because in the meantime, our developers work on something else, another branch.</em></li></ul><p>That was a rough start…</p><p>Interestingly, on the same day, the lead of one of my top-performing teams reached out with a different kind of concern: “<em>Laurent, I think we need to ease up on rolling out new features. Our tests, all 7000+ of them, are now taking over 15 minutes to run. That’s too slow for us and is holding the team back. We need to fix this ASAP</em>.”</p><p>These 2 conversations perfectly highlight the massive gap in performance, skills, and expectations across teams. The difference couldn’t be starker.</p><p>So, you might wonder if there’s a playbook to go from being a low-performing team to a high-flying one, and what’s the biggest game-changer to make that leap? But first, let’s get clear on what we actually mean by ‘performance’.</p><h3>Decoding Performance with the DORA Framework</h3><p>Enter the <a href="https://dora.dev/">DORA</a> framework (DevOps Research and Assessment), our GPS for navigating the complex world of software delivery, showing us exactly where to zoom in for improvement. It proposes 4 metrics (Deployment Frequency, Change Lead Time, Change Failure Rate, Failed Deployment Recovery Time). Their research, based on 36,000 professionals worldwide, shows a causation between these metrics, delivery performance, and organizational performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*vXz7zbIWoV-fmCshVdviDg.png" /></figure><p>You don’t have to pick between velocity and quality. That was a lie. You can and should have both. And this is backed by science. And, DORA proposes a playbook, 27 <a href="https://dora.dev/devops-capabilities/">capabilities</a> that you should invest in to improve your performance as measured by the 4 metrics. It includes technical capabilities like CI, Test Automation, Loosely Coupled Architecture, and many others, including process and culture capabilities.</p><p>Building these capabilities will improve your delivery performance and your business! That’s precisely why investing in our developers’ growth is so critical. Building skills is the root of any progress on these capabilities. The Playbook is there, opensource, knowledge is accessible and free.</p><h3>Then, it’s all about upskilling the team</h3><p>Upskilling developers is not just about enhancing their technical capabilities; it’s a holistic approach that includes improving their problem-solving skills, adaptability, and ability to work collaboratively. Focusing on upskilling helps create a culture of continuous learning and innovation. It involves:</p><ol><li><a href="https://dora.dev/devops-capabilities/cultural/learning-culture/"><strong>Continuous Learning</strong></a> (one of the DORA capabilities)<strong>:</strong> Encourage and provide resources for continuous learning. This can include access to online courses, attending workshops and conferences, and regular training sessions.</li><li><strong>Mentoring and Coaching:</strong> Pair less experienced developers with mentors who can guide them, fostering an environment where knowledge sharing becomes second nature. This not only accelerates the learning curve but also builds a strong sense of community and support within the team.</li><li><strong>Feedback Culture:</strong> Cultivate a culture where <a href="https://www.packmind.com/tech-leader-the-power-of-listening/">constructive feedback</a> is regularly exchanged. Make it clear that feedback is a tool for growth, not criticism. This encourages developers to stretch their boundaries and continuously improve.</li></ol><p>These are the three levers I have used to upskill the newly acquired team I mentioned at the beginning of this post. A few of my best tech leads have spent weeks with this team, mentoring and coaching them on TDD, automation, design patterns… And after a 2-year journey, they were able to deploy without downtime and release at the end of their 2-week sprints.</p><p>So, it’s all about upskilling teams, and this is exactly why I joined <a href="https://www.packmind.com/">Packmind</a>. Its mission resonates deeply with me: to elevate developers by putting the human element at the core of creating sustainable software. The <a href="https://www.packmind.com/">Packmind</a> platform accelerates the skill growth of developers by integrating learning directly into their workflow, making knowledge accessible right when and where it’s needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QRyJSRIow9R0kIMy906DAg.png" /></figure><h3>Skills are also the biggest factor contributing to the value delivered</h3><p>Frameworks like DORA have dramatically improved our approach to team performance. Yet, the value delivered by a team remains an elusive notion. Regis Medina, during <a href="https://www.youtube.com/watch?v=U3D39kspGaA">FlowCon 2022</a>, brilliantly summarized this value in a simple formula:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IbFjXMchHEnnijL8FJHrAA.png" /></figure><p><strong>Value = Quality / Total Cost,</strong> where:</p><ul><li><strong>Quality</strong> encompasses all quality attributes of the project, including the achievement of functional scope, reliability, maintainability, scalability, security, etc.</li><li><strong>Total Cost</strong> includes not only the development cost but also the costs of operation, support, and maintenance of the project over time.</li></ul><p>Thus, exceptional teams know how to maximize quality while optimizing costs. And guess what! Developer skills are the key factors in maximizing the value produced!</p><p>Skilled developers and teams are more adept at identifying opportunities for cost reduction and, therefore, maximizing the value produced. They will know how to create sustainable software that can be run and supported cost-effectively using DRY, KISS S.O.L.I.D, and the right design. Skills are key to achieving that cost reduction.</p><p>On the numerator side of the equation, there is always a tension between quality and total cost. Establishing the right compromises is what truly defines the success of a project. The developer’s expertise also consists of better understanding customer requirements, constraints, and focusing on what really matters to build a quality product.</p><p>So, developer skills are what really enable them to maximize the value produced, thus ensuring the project’s success.</p><h3>Conclusion</h3><p>And that’s why my playbook has always been about creating a learning organization. The secret to unlocking a team’s full potential lies not only in the tools and processes we implement but in continuously investing in our developers’ growth. Upskilling is the cornerstone of transforming average teams into high-performing powerhouses, capable of not just meeting but exceeding expectations and delivering exceptional value at speed.</p><p>This is beneficial for the individuals and the business. I have never compromised on that. Invest in your developers, coach, mentor, train them, and they will take care of your product! That also means that when I hire, I look for people who are eager to learn and coachable. That’s at the top of the list.</p><p>This is the 10x factor that distinguishes the extraordinary from the ordinary.</p><p>I am really curious about your own experience. What has been your most effective strategy for upskilling your team? How do you foster a culture of continuous learning in your organization? Please share in comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23ee389d2e0f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/promyze/what-is-the-secret-of-high-performing-teams-and-how-to-achieve-this-10x-factor-23ee389d2e0f">What is the secret of high-performing teams and how to achieve this 10x factor?</a> was originally published in <a href="https://medium.com/promyze">Packmind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>