{"id":25,"date":"2026-07-27T08:12:31","date_gmt":"2026-07-27T08:12:31","guid":{"rendered":"https:\/\/prequake.ai\/resources\/?p=25"},"modified":"2026-08-01T14:34:41","modified_gmt":"2026-08-01T14:34:41","slug":"what-is-change-fatigue","status":"publish","type":"post","link":"https:\/\/prequake.ai\/resources\/what-is-change-fatigue\/","title":{"rendered":"What is Change Fatigue?"},"content":{"rendered":"\n

Change fatigue<\/strong> is the accumulated resistance an organization develops after repeated transformations, regardless of whether any individual change was well-managed. It’s not about this initiative \u2014 it’s about the fifth one this year, and the eight before that.<\/p>\n\n\n\n

The distinction matters because change fatigue gets diagnosed backwards more often than not. A team that pushes back on a well-designed rollout looks, from the outside, exactly like a team resisting a badly designed one. The difference is invisible unless you ask about history, not just this project.<\/p>\n\n\n\n

It’s a credibility problem, not an attitude problem<\/h2>\n\n\n\n

The mechanism is straightforward: every past change that was announced with urgency and then quietly stalled, descoped, or never followed up on teaches people a lesson \u2014 that “this is important” and “this will actually happen the way it’s described” are two different claims, and only one of them reliably comes true. Once that lesson is learned, the next announcement gets a smaller, more guarded reaction, no matter how good the plan actually is.<\/p>\n\n\n\n

This is why change fatigue often looks like apathy but isn’t. Apathy is not caring. Change fatigue is caring enough to have been burned before and calibrating accordingly.<\/p>\n\n\n\n

Why “communicate more” makes it worse, not better<\/h2>\n\n\n\n

The default response to visible resistance is usually more messaging \u2014 another town hall, another email, another slide reinforcing why this change matters. If the underlying issue is genuine change fatigue, this doesn’t help. It repeats the exact pattern that caused the fatigue in the first place: another confident announcement, with no new reason to believe this one will land differently than the last four.<\/p>\n\n\n\n

What actually addresses it is different: naming the pattern explicitly (“we know the last two initiatives didn’t fully land \u2014 here’s specifically what’s different this time”), and then being visibly, verifiably right about at least one near-term commitment. Trust rebuilds through small kept promises, not larger claims.<\/p>\n\n\n\n

How to tell it apart from resistance to this specific change<\/h2>\n\n\n\n

A few signals distinguish general fatigue from a specific objection: fatigue tends to produce vague, low-energy pushback (“here we go again”) rather than pointed objections about this initiative’s actual content. It correlates with how many changes a team has been through recently, not with the merits of the current one. And it often coexists with genuine belief that the change is a good idea in principle \u2014 the resistance isn’t “this is wrong,” it’s “I don’t believe this will actually happen the way you’re describing it.”<\/p>\n\n\n\n

Missing that distinction is expensive: treating fatigue as if it were a disagreement about this specific change means addressing objections nobody actually has, while the real issue \u2014 a credibility debt built up over several prior initiatives \u2014 goes untouched.<\/p>\n","protected":false},"excerpt":{"rendered":"

Change fatigue is the accumulated resistance an organization develops after repeated transformations, regardless of whether any individual change was well-managed. It’s not about this initiative \u2014\u2026<\/p>\n","protected":false},"author":1,"featured_media":26,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-25","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-glossary"],"_links":{"self":[{"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/posts\/25","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/comments?post=25"}],"version-history":[{"count":1,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/posts\/25\/revisions"}],"predecessor-version":[{"id":27,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/posts\/25\/revisions\/27"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/media\/26"}],"wp:attachment":[{"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/media?parent=25"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/categories?post=25"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prequake.ai\/resources\/wp-json\/wp\/v2\/tags?post=25"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}