When new processes are introduced, the assumption is often that resistance comes from reluctance to change. That explanation is convenient, but it is usually incomplete.
In most cases, resistance is a signal. It points to something that has not been fully addressed.
One common issue is lack of clarity. If a process is introduced without a clear explanation of how it improves the current state, agents will default to what they know. From their perspective, the new approach may feel like additional steps without obvious benefit.
There is also the question of trust. If previous changes have created more work or failed to deliver results, teams become skeptical. Each new process is viewed through that lens.
Another factor is practicality. Processes that look clean in documentation can break down in real-world use. Edge cases, unclear ownership, and tool limitations can make the process harder to follow than intended.
Leaders who want better adoption should focus less on enforcement and more on alignment. Start with a specific problem that the team recognizes. Backlog growth, inconsistent responses, or slow escalations are all good starting points.
Then show how the new process addresses that problem. Be explicit about what is changing and why. Where possible, involve the team in refining the approach. This does not mean handing over decision-making, but it does mean acknowledging that the people doing the work have useful context.
Adoption improves when the process feels like a solution, not an imposition.