Transforming Agile: How to Shift from Blame to Systemic Solutions for Better Team Dynamics

I often find myself reflecting on a saying that resonates deeply with my experiences in the agile world: “Don’t attribute to malevolence what can be explained by incompetence.” This phrase has become a guiding principle for me, especially when navigating the complexities of organisational dynamics as an agile coach, Scrum Master, or product owner.

Understanding Behaviour in Agile Environments

In my journey, I’ve observed that when people engage in behaviours that hinder our ability to deliver effectively, it’s rarely out of malice. More often than not, these actions stem from the way they are measured within the organisation. Here are a few key insights I’ve gathered over the years:

• Measurement Drives Behaviour: The metrics we use to evaluate performance can significantly influence how individuals act. For instance, if developers are assessed based on the number of lines of code they produce, it can lead to counterproductive practices, such as excessive copying and pasting. This not only inflates their metrics but also detracts from the quality of the code.

• The Pitfalls of Traditional Metrics: I’ve seen organisations flip the script, rewarding fewer lines of code in an attempt to optimise efficiency. However, this can lead to a culture where developers are incentivised to do the bare minimum, resulting in a lack of innovation and engagement.

• Culture as a Reflection of Measurement: Many leaders focus on changing the culture within their teams, believing that this will solve their problems. However, I’ve come to realise that culture is merely a shadow cast by the underlying measurement systems. To effect real change, we must first address how people are evaluated and incentivised.

The Systemic Nature of Challenges

When I encounter resistance or feel as though I’m fighting an uphill battle to deliver a product, I remind myself that it’s often a systemic issue rather than a personal one. The systems in place can create barriers that inhibit progress. Here’s how I approach these challenges:

• Identify Systemic Issues: If you find yourself constantly thwarted by compliance checks or bureaucratic processes, it’s crucial to recognise that these are symptoms of a flawed system. The system is designed in a way that makes it difficult to adapt and respond to change.

• Simplifying Change Requests: A common frustration in many organisations is the cumbersome process of handling change requests. When a customer needs to pivot, the response often involves lengthy forms and negotiations. This rigidity is a byproduct of a traditional project mindset that seeks to minimise variance. While this approach may work in manufacturing, it is ill-suited for software development, where flexibility and responsiveness are key.

• Shift the Focus: Instead of viewing resistance as malevolence, consider it a reflection of systemic incompetence. By addressing the root causes, namely, the measurement systems and processes, we can create an environment that fosters collaboration and innovation.

Moving Forward

In my experience, the path to agility is not about changing people but about transforming the systems that govern their behaviours. Here are a few steps to consider:

• Re-evaluate Metrics: Assess the metrics you use to measure success. Are they encouraging the right behaviours? If not, it may be time to rethink them.

• Foster a Culture of Adaptability: Encourage teams to embrace change and view it as an opportunity rather than a burden. This shift in mindset can lead to more innovative solutions and a more engaged workforce.

• Engage in Continuous Improvement: Always be on the lookout for ways to improve processes and systems. This commitment to continuous improvement will help create a more agile and responsive organisation.

In conclusion, the challenges we face in agile environments are often not due to the actions of individuals but rather the systems that shape their behaviours. By focusing on changing these systems, we can create a more conducive environment for agility to thrive.

If you found this discussion valuable, I encourage you to engage with me further. Whether you have questions about agile practices or want to share your experiences, feel free to reach out or book a coffee chat through Naked Agility. Let’s continue the conversation!