This guide walks through five phases, each with a specific diagnostic question and a set of concrete actions, so your next change effort starts strong and ends stronger.
TL;DR: Enroll local individuals, teams, and communities as stakeholder in managing their own efforts, for sustainable change.
Phase 1 — Diagnose: Observe and Understand
You can’t define a good solution until you know what you’re facing. Skipping thorough this step too quickly is a common failure. A slow-to-adapt team appears to be sabotaging your efforts, when a normal tempo is confused for malicious resistance.
Distinguish between hard resistance and reactive friction. Audit the things people cite as impediments. Does this friction change if the pace changes? If no, then it’s resistance. Fix it structurally, before changing anything else. If yes, then it’s reactive friction, and it needs pacing (their pacing), not removal.
Find the organization’s native rhythm. Map the cycles already running: budget cadence, sprint rhythm, review cycles, hiring waves. These are the recurring cues already governing behavior. A change pushing against this rhythm amplifies pushback, a change timed to align with it, reduces friction and benefits from existing momentum.
Estimate the size and pacing of change that the organization has the capacity for. If the gap between where things stand and where you want them to be is large, then find the largest single step that still falls within what the organization can absorb, and treat that as a milestone.
Map locally specific approaches, and identify who’s already working closely with whom. Change invites the unexpected, things not in the plan. These are problems where the solution requires real, working relationships. Existing connections and approaches allow change to spread easily, where the effort require a bridge built deliberatly to reach isolated or loosely connected teams.
Equitably distribute the costs, risks, and benefits of change initiatives. Ensure that the people being asked to make most of the change effort, or bear moat of the burden of risk, are the ones who benefit most from the change.
Phase 2 — Design: Make the least amount of change
Define the solution. We’re all very good at defining the problem. Enrolling the impacted teams in the planning and coordination of their own futures and needs, embeds a necessary dose of reality in an otherwise imaginary set of numbers.
Build a translation layer and commit the resources. Identify who can turn intention into team-level action. Give them that mandate explicitly. They will translate your vision into what it means for their day-to-day.
Choose a recurring cue, not a single launch event. A kickoff is just a moment. Decide now what the sustaining structures will be (a weekly review, a visible dashboard, a standing check-in) and dedicate resourcing to it.
Match the solution to the situation. Trust the teams to divide the effort into steps that make sense for them. The full transition usually takes longer than the original plan expects; plan for this.
Plan for full engagement everywhere. Cherry picking with the greatest ROI, the greatest impact on the bottom line, or the most visibility, ensures isolation and misalignment in those teams and the ones where the change effort is less complete.
Pick your starting teams based on the existing connections. Start with the groups already closest to where you’re trying to go, not necessarily the most visible ones. Let the change (the solutions, the pitfalls, the resources, the gained knowledge) spread outward through existing relationships instead of trying to reach everyone from afar. Recognize the relationships that exist within the systems and networks. Help them to preserve these, even if it doesn’t work for you.
Phase 3 — Manage: help teams and communities manage their own reality
Resistance will arise. Change is difficult, threatening even. Only teams and communities, invested in their own futures, will build the strongest version of it.
Expect a lag between announcement and behavior. Don’t panic at the dip. Set the first real checkpoint after a reasonable absorption period, not immediately after launch. New ways of doing things need time to unseat the old, largely because the old ways are easier to do, even when the new ways are better.
Recruit the people most affected and let them shape the process of change, not just the goals of change. We push back hardest against the things we see as restricting our choices, limiting our opportunities, or rescinding our hard-fought rewards and privileges, this is reactance. It is a very human response to any perceived threat to our autonomy. Allowing individuals and teams to choose they path toward a goal (ideally one that connects to the greater community and its purpose) preserves choice. Applying more pressure, would only worsen the reaction to change.
Integrate action with learning. Then share that knowledge and learning. Engage individuals, teams, and communities. Draw on their knowledge, their needs, and their evolving experience. Then, set up communities that can help seed that learing across all teams.
Check the edges, not just the center. If people only comply while someone’s actively watching, and it evaporates the moment attention moves elsewhere, that’s command-driven compliance, not real buy-in. The teams most likely to drift back to old behavior first are the ones loosely connected to the initiative’s core group. Check in there deliberately.
Track whether leadership’s own behavior is shifting too. Real change is mutual, it affects all sides. If management and leadership aren’t impacted by change, if they haven’t also struggled to adopt new behaviors and discard old habits, if the change effort hasn’t structured in a protected time, space, and mandate to monitor and evaluate this openly and honestly, then the effort has already failed. You just can’t see it yet.
Phase 4 — Evaluate: Observe and Understand… again
Practice participatory monitoring, evaluation and learning. Every change effort needs a robust participatory monitoring system that can adopt and share knowledge, has the authority to adjust planning and resources, and will to respond to the impacts of the change over time, and in real time. Monitoring should prioritize local goals and concerns, but not to the detriment of a Coherent whole.
Sort outcomes by cause, not just by result, or the wrong lesson gets drawn from a right or a wrong answer alike. Was it hard resistance (structural friction), malabsorption (the effort was too infrequent, too large, or poorly timed), “too much, too hard, too fast,” or maybe the group was never reached by the effort to begin with. Each situation reflects a different underlying dynamic. Misclassifying it means pulling the wrong lever; wasting effort, or making the situation worse.
Check for durability. Monitor for recidivism. After adoption, old habits sneak back in, often when pressure is high.
Audit how much of the effort actually converted into outcome. How much total organizational energy went into the effort (meetings, status updates, politics) versus real, changed behavior? This is an outputs-versus-outcomes question; reported activity is not the same as the experience before, during, and after.
Check the edges: the old ones, and the new. Did the change effort reach loosely connected groups? Did it result in new loose edges?
Accountability is about open trust not public shame. Failing to meet a dictated expectation is always a demand problem, and a failure to negotiate a common understanding, it is not an integrity problem.
Phase 5 — Maintain the capacity for the change
Don’t let working connections atrophy between initiatives. The relationships and rituals that let this change spread are an asset. Help teams maintain a cross-team connections (standing local syncs, rotation, shared review rhythms). Invest the resources, prioritize these structures, and give the authority to protect themselves.
Protect the slack. An organization running at full capacity has nothing left in reserve for learning, exploration, or change. Everything will be met as friction. Stacking too many changes, too close together, leads to fatigue and forces teams to choose short-term high-visibility delivery over long-term higher-value investments.
Rotate who plays the translation role. If the same one or two people are always the bridge between vision and execution, the organization’s capacity for change is bottlenecked by their individual (and probably diminishing) bandwidth. Build the capability into more teams, if not all teams.
Quick reference
| Phase | Core question | Most common mistake |
|---|---|---|
| 1. Diagnose | What is the experience today? | Treating every individual, team, or community the same |
| 2. Design | What’s the least amount of change for the most complete engagement? | Defining only a beginning and an end |
| 3. Manage | Are the teams and communities managing themselves? | Allowing knowledge to remain locally siloed |
| 4. Evaluate | What is the experience of change? | Measuring success right after launch, not weeks later |
| 5. Maintain | What is the experience after? | Making a change rather than building a capacity for change |