Colleagues, as Project Managers, we are usually the ones driving change. However, I want to talk about what happens when there is simply too much of it.
Nowadays, organizations are constantly implementing new software, changing internal processes, or restructuring departments—often all at the same time. This leads to "change saturation" or "change fatigue," where teams become overwhelmed, lose motivation, and start resisting even the good projects.
I would love to hear your experiences on this topic.
Questions for the community:
What are the early warning signs you notice when a team has reached its limit for change?
How do you manage a project when the team is already exhausted from previous implementations?
Have you ever had to push back and tell stakeholders, "We need to pause; the organization cannot handle another new initiative right now"? How did that go?
Looking forward to reading your strategies!
Francisco