Change Fatigue: Is It OK to Pause the Continuous Improvement Journey? with Eric Landes

Published: Jan. 21, 2022, 1 p.m.

This week, Dan Neumann is joined by a colleague, friend, and Professional Scrum Trainer, Eric Landes.

\xa0

In this episode, Dan and Eric are answering a listener\u2019s question that arises from an episode in which Change Fatigue was discussed; the listener wants to hear more about cases observed of Change Fatigue in Teams and Organizations and how they can be dealt with. They wonder if it is ever OK for a team on the path to Agility to say: \u201cWe made a really good progress; let\u2019s take our foot off the pedal of continuous improvement and just cruise for a while!\u201d

\xa0

Key Takeaways

\u25cf What does Change Fatigue look like?

\u25cb One-week sprints can exhaust Teams; speed is good but the Team\u2019s engagement is a priority.

\u25cb The retrospective after a Sprint is designed to be a moment to take a step back and reflect, maybe celebrating what is working well as opposed to meaningful process change.

\u25cf How to avoid Change Fatigue?

\u25cb A way of avoiding Change Fatigue is by hosting the retrospective after a Sprint in another setting where the Team can unwind.

\u25cb Try to change the mood, promoting a fun and easy atmosphere.

\u25cb Think of places where you can give your Team a little rest and also listen to your Team\u2019s suggestions about where would they like to go for a little relaxation.

\u25cb The change might be needing to pause on changing.

\u25cf There is a potential of doing Change wrong.

\u25cb Change is done wrong when you\u2019ve lost the ability to deliver.

\u25cb In Scrum, when you bring changes on they can only be one or two into a Sprint.

\u25cb Ask yourself: Is this change effective?

\u25cf Apply, reflect, and adjust.

\u25cb You not only have to be constantly doing!

\u25cb It is OK to rest (by the way, it is needed!)

\u25cb Every task is in a series; just work on one at a time. Don\u2019t worry about the whole thing, just about the next thing.

\xa0

Mentioned in this Episode:

Listen to Episode 53: \u201cWhy Should Scrum Teams Continually Improve\u201d where Change Fatigue was first discussed

Agile Retrospective: Making Good Teams Great, by Esther Derby and Diana Larsen, with forward by Ken Schwaber

\xa0

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!