Embracing Discomfort: The Path to Agile Mastery

In the realm of project management, one of the most formidable challenges is managing change, even when it's change for the better. We've all encountered situations where introducing new practices, ceremonies, or rules is met with resistance. Team members and stakeholders might offer explanations like "I'll provide the details later; let's prioritize for now" or "This is just an exception; it's not a big deal."

So what’s the problem?

The issue is that these responses often stem from fear—the fear that change will lead to even greater missteps. And to some extent, they're correct. For instance, if stories aren't meeting the definition of ready, it's essential not to include them in the sprint. Missing that timeboxed segment to bring in the work can indeed slow things down. But what often gets overlooked is that by instituting these changes, we're establishing stability and clarity.

Expectations become crystal clear: Do X at Y time for Z result. This logical progression allows teams to find their groove, a place of rhythm and consistency that's vital for productivity. Sure, there may be an initial slowdown, but with effort and dedication, it paves the way for accelerated performance.

Story Time

I have a friend who types with only three fingers per hand, which I found to look very strange and awkward. I tried to encourage them by saying “Have you ever tried using all of your fingers?”. After a brief consideration, they tried it for a few seconds before responding “This is uncomfortable and slowing me down. I’ve been using six fingers my whole career and It’s not a problem.”

What is highlighted here is not that using less fingers is a problem, but rather the fact we’re not fighting against that discomfort is stopping us from achieving our full potential. Yes, the change in hand positioning will be awkward and slow you down, but I don’t know that Mozart, Bach, or any of the great artists would have been half as successful without the full use of range their hands offered.

Why are we talking about pianos?

At its heart, that story has nothing to do with pianos, typing, or artistic talent. This story is about battling the discomfort that comes with change. It is by fighting through the initial awkwardness we can start to learn and enhance our abilities and that of our teams. As leaders, it's our duty to empower our teams to navigate through this perceived pain. We must align our expectations with the transitional dip and provide the necessary resources to educate and elevate our teams. It's about embracing discomfort as a necessary part of the journey and leading hesitant team members toward the other side. Once we hit our stride, the acceleration is unlike anything we've experienced before.

So what do we do?

Before we start making changes it’s important that we provide the “why”, and even that is not enough! We need to do our best to metricize and quantify the “why”. It’s easy to combat anecdotes, which is what makes metrics our best friends. Here are some key thoughts to keep in the back of your mind:

1) Change Doesn’t happen overnight. Its not about ability, or will. Its about understanding and impact.

2) Be patient with change. Plant the seed of idea and allow it to grow on its own, even if it means some plants will wilt temporarily.

3) Be consistent. Bringing up a recommendation a single time does not impact change. Consistent tracking, reporting, and messaging will be what wins. Build a cadence for this and stick to it!

In conclusion, the road to agile mastery is paved with discomfort and change. But it's precisely these challenges that lead to growth, efficiency, and success. As leaders, it's our responsibility to guide our teams through this transformative journey, helping them discover their full potential and accelerating toward excellence.

Previous
Previous

The Heart of Product Management: Building Bridges with Your Agile Team 💡

Next
Next

Extreme Programming: An Underdog Story