Resistance is any behavior that maintains the status quo against pressure to change, and it can be active (vocal opposition, public objections, escalation) or passive (quiet non-compliance, slow adoption, workarounds, withholding effort). Change resistance data — objections, delays, workarounds, and usage patterns — reveals where adoption is struggling. Treating resistance as information about what's broken in the plan, rather than an obstacle to overcome, turns it into a design input. Empathy interviews, day-in-the-life exercises, and shadowing the user surface practical adoption frictions that affected people may not be able to articulate.
Change fatigue is the exhaustion and skepticism that build when people face too many initiatives without enough support. Change saturation is the point where stakeholders cannot absorb additional change because too many initiatives are already underway, and initiative overload launches more changes than the organization can complete, so most stall or fail because none get sustained attention. Change capacity is the organization's bandwidth for absorbing change, depleted by concurrent initiatives and restored by completion and recovery; the 70-20-10 capacity model suggests roughly 70% of capacity for normal operations, 20% for adopting new ways, and 10% for innovation, so any change must fit within this envelope.
The messy middle is the disorienting phase after the change has started but before the new state is reliable, and it is usually the highest-risk window. The post-launch dip is a predictable performance drop in the weeks after go-live as people relearn, requiring a planned capacity buffer. The silence-after-launch trap occurs when project communications stop on launch day and the organization assumes the change is over, though adoption work is just beginning. Change debt is the unresolved residue of past poorly managed changes — distrust, scar tissue, and skepticism — while a change scar is a specific past failure people still reference, which must be acknowledged for the next change to be believed. Adoption itself is the degree to which people actually start using the new behavior consistently, and adoption signals matter more than verbal agreement or one-time compliance. Other signals include shadow IT (workarounds outside official tools), process drift (slow erosion as exceptions accumulate), policy decay (stated policies stop being enforced), and the long tail of adoption where a stubborn minority lingers in the old way and needs targeted support rather than broadcast messaging. Compliance does the minimum to avoid trouble while commitment voluntarily extends effort, and lasting change needs commitment.