Making change happen inside a team is rarely about one bold announcement. Understanding how to make change happen matters because the real work is not persuasion alone; it is aligning behavior, process, and leadership so the new way of working can survive busy schedules, skepticism, and old habits. In the sections below, I break down the parts that usually decide whether a transformation sticks: the outcome you are actually aiming for, the rollout style, the human side of adoption, and the metrics that tell you whether the change is real.
The essentials before you move
- Define the behavior you want to see before you write the launch message.
- Pick a rollout style that matches the level of risk and resistance.
- Give managers real support, not just a slide deck and a deadline.
- Measure adoption and quality of use, not only awareness or attendance.
- Reinforce the new norm through routines, incentives, and visible follow-through.
Start with the behavior you need, not the announcement you want
I usually begin by asking one practical question: what should people actually do differently on an ordinary Tuesday? If the answer is vague, the change is still a slogan. If the answer is specific, you can build the rest of the plan around it.
This is especially important in inclusive leadership and workplace culture work, where “be more inclusive” is too broad to execute. Better targets are visible and testable: rotate meeting facilitation, use structured interview questions, document promotion criteria, or make space for every voice before a decision is closed.
| Change target | What actually changes | What you can measure |
|---|---|---|
| Inclusive meetings | Facilitation rotates, interruptions are managed, decisions are summarized clearly | Speaking balance, meeting feedback, decision clarity |
| Bias-aware hiring | Structured interviews, consistent scoring, fewer ad hoc judgments | Scorecard usage, candidate consistency, hiring cycle quality |
| Flexible work norms | Core hours, response expectations, manager rules are published | Policy adoption, team compliance, retention or satisfaction data |
Prosci’s research has pointed out that strong change management makes organizations far more likely to meet project objectives, which is another way of saying that adoption is the real finish line. Once the behavior is clear, the next decision is how much structure the rollout needs.
Choose the rollout style that matches the risk
Not every change should be handled the same way. Some shifts need speed and clarity. Others need co-creation because the local context matters and people will only commit if they have helped shape the answer.
I like to think about three broad rollout styles. None is perfect on its own, but each works well in a different situation.
| Rollout style | Best when | Strength | Main risk |
|---|---|---|---|
| Directive rollout | There is legal, safety, or compliance urgency | Fast, clear, and unambiguous | Can create quiet resistance if used for everything |
| Co-created rollout | You need behavior change and local buy-in | Builds ownership and surfaces practical barriers early | Can move slowly if the decision itself is treated as open-ended |
| Pilot-and-scale rollout | The new process is unfamiliar or likely to need adjustment | Lets you test, learn, and fix friction before full launch | Can stall if the pilot is never turned into a real scale plan |
For culture change, I often prefer a co-created or pilot-first approach. People support what they help shape, but that does not mean every decision needs a vote. It means the decision needs a rationale, clear boundaries, and enough participation that the final version works in practice. Once you know the rollout style, the work becomes operational.
Turn the plan into visible daily actions
A good change plan is not a manifesto. It is a sequence of actions that people can follow without guessing. If the plan depends on memory, it will drift. If it depends on one heroic leader, it will fade the moment that person gets busy.
I try to define the rollout in three layers: ownership, timing, and reinforcement. Ownership means one person is clearly accountable for each step. Timing means the sequence is realistic, not idealized. Reinforcement means the new behavior is built into calendars, dashboards, performance conversations, or team routines.
Name an owner for each step
The sponsor is the senior leader who visibly backs the change. The manager translates it into day-to-day work. The working group handles the details. If everyone owns the change, nobody does. If only one leader owns it, the change never reaches the front line.
Sequence the rollout around friction
Start with the points that will block adoption first. For example, if managers need to run more inclusive meetings, give them a script, a simple agenda template, and a one-page explanation before asking for perfect execution. If employees need to use a new process, remove the old version from circulation as soon as the new one is stable.
Build reinforcement into the calendar
A 30/60/90-day rhythm works well because it forces follow-through. In the first 30 days, make the expectations clear. In the next 30, watch where the process breaks. By day 90, the question should no longer be whether the change is real, but whether it is becoming normal. That still leaves the human side, which is where many change efforts lose momentum.
Lead the people side before you ask for compliance
In U.S. workplaces, one of the biggest mistakes is assuming that a memo is the same thing as alignment. It is not. People align when they understand the reason for the change, believe leadership is serious, and know what support they will get while they adapt.
SHRM has reported that only 57% of managers feel they have enough capacity to support their teams through change. I take that seriously, because managers are the layer that turns strategy into behavior. If they are overloaded, uncertain, or skeptical, the change will slow down whether or not the launch deck looked polished.
Bring managers in first
Managers need the context before they need the talking points. If they understand the business reason, the expected behavior, and the trade-offs, they can answer questions without improvising. That matters even more for inclusive workplace changes, where employees watch manager behavior closely for signs that the new norm is real.
Make communication a conversation
Communication is not just about volume. It is about credibility. People want to know what is changing, why it matters, what is staying the same, and what support they can expect. The strongest communication also creates space for pushback, because pushback often contains useful information.
Read Also: Strategy vs. Plan - Why Most Change Efforts Fail
Treat resistance as data
Resistance is not one thing. I separate it into three buckets: confusion, disagreement, and friction. Confusion means the change is not clear enough. Disagreement means people do not buy the logic or fairness of the change. Friction means the new process is simply too hard to use. Each problem needs a different fix, and if you treat them all as attitude problems, you will miss the real issue. Once people understand the change, the next question is whether it is actually taking hold.
Measure adoption, not just activity
A launch email, training attendance, and a polished rollout are all activity. They are not proof of adoption. The change is real when the new behavior shows up consistently and produces the result you wanted.
I look at four types of signals:
- Awareness - Can people explain the change in plain language?
- Usage - Are they using the new process, policy, or behavior?
- Quality - Are they using it well, or just technically?
- Outcome - Did the change improve the business or culture result you care about?
For example, if the goal is more inclusive hiring, success is not that recruiters attended a workshop. Success is that interviews use the same scorecard, hiring decisions are easier to defend, and more candidates experience the process as fair. That is the difference between activity and adoption.
Reinforcement matters here too. Recognition, manager coaching, updated policies, and visible rituals all help the new behavior survive the initial burst of energy. The point is not to keep repeating the launch. The point is to make the new standard feel ordinary.
The mistakes that quietly kill momentum
The biggest failures are usually not dramatic. They are small, predictable, and easy to ignore at first. I see the same pattern again and again:
- Launching before the path is clear - People cannot execute what they do not understand.
- Confusing communication with change - Awareness is useful, but it is not adoption.
- Leaving managers out - The middle layer carries most of the translation work.
- Adding change on top of full calendars - A new expectation with no time buffer becomes a resentful one.
- Keeping old incentives in place - People do not trust what the system does not reward.
If you want a transformation to hold, the design has to match the reality of the workday. That is why the first 90 days matter so much.
The first 90 days decide whether the change sticks
In the early phase, I would rather see a small change executed consistently than a large change described beautifully. Consistency teaches people what to expect. It also reveals where the system is still fighting the new behavior.
- Days 1-30 - Make the behavior, owner, and message unmistakable.
- Days 31-60 - Watch adoption closely, remove friction, and coach managers.
- Days 61-90 - Update routines, performance signals, and policy language so the new way is easier to repeat than the old one.
If those three windows produce visible behavior change, you are no longer trying to force a transformation. You are managing a new operating norm, and that is where change finally becomes durable.
