Alternatives to Top-Down Change Management

You announced it, your managers repeated it, and the deck went out to every office. Six weeks later, the new process is running in two places and nowhere else. Nobody pushed back at any point, which is usually the part that stings.

The main alternatives to top-down change management are co-creating the strategy with the people who'll live with it, handing implementation planning to the teams doing the work, and replacing broadcast messaging with two-way conversation. You can use one, two, or all three. None of them means giving up the decision about whether the change happens.

Key takeaways

• Top-down isn't wrong; it's incomplete. It's good at deciding and announcing, and poor at the part where people change what they do.

• Willingness is rarely the bottleneck. In CEB's 2016 workforce research, 74% of employees said they were willing to change to support an organizational change and 64% had most of the skills to do it. Only 26% agreed they'd actually changed how they work.

• The three alternatives are co-creating the strategy, letting teams plan their own implementation, and talking instead of telling. CEB grouped the three under the name Open Source change.

• Having a say has moved near the top of what people react to at work. Over thirteen span, it went from last on that list to second.

• You can keep the deadline. What you hand over is how the work gets done, not whether it gets done.

Why the cascade stopped working

It used to work better. You told your leadership team, they told their managers, managers told their teams, and enough of it landed for the initiative to move.

Two things changed. The first is volume. Your leaders aren't carrying one message down the line anymore; they're carrying several, and yours is one item on a Thursday agenda. The second is using a traditional cascade approach.

A cascade is built to deliver one thing: what's happening and when. It gives people no part in deciding how the work gets done. . The NeuroLeadership Institute's 2025 SCARF® data, from more than 15,000 assessment responses, puts fairness first at 26% and autonomy second at 24%, with certainty last at 14%. In 2012 it was close to the reverse: certainty at 46%, autonomy at the bottom with 3%. Look at that information as an order of priority rather than a measure of harm. What a cascade buys you has lost ground, and what it costs you has gained. I've written about what that means for a change plan in The Neuroscience of Stress and Change Management.

David Rock said this plainly back in 2009, in strategy+business: "People rarely support initiatives they had no part in designing; doing so would undermine both autonomy and status." In the same article, he gave the practical version. An inclusive planning process, he wrote, "can prevent the kind of unconscious sabotage that results when people feel they have played no part in a change that affects them every day."

Notice that he says unconscious. Nobody in your offices has decided to undermine the rollout. They're busy, the new way is slower for the first month, and nobody asked them anything. So they do the work the way they already know how, and the rollout stalls without a single objection on the record.

One small shift: list the decisions inside this change that are genuinely yours, then list the ones you've taken by default. The second list is where you have something to hand over.

What are the alternatives to top-down change management?

In 2016, CEB's Corporate Leadership Council studied this and gave the alternative a name: Open Source change. Their definition is "Open Source change uses the workforce to plan and implement change," and they built it on three things.

The three are worth taking one at a time, because they ask different things of you and they aren't equally hard.

1. Co-create the strategy. The people who'll live with the change help shape it. Not a focus group after the fact, and not a feedback survey on a plan that's already printed. In practice, it's a small number of the people closest to the work, brought in while the shape of the change can still move, with a real question in front of them.

2. Hand implementation planning to the teams. This one's the easiest to start, and most leaders can begin on Monday. You set the outcome and the date. Each team decides how they get there. A title office handling mostly refinances will sequence a new system differently from one doing commercial closings, and both will be right.

3. Talk instead of telling. Replace the broadcast with conversation. That means fewer slides going down and more questions coming up, and it means somebody has to do something with the answers.

CEB also found something uncomfortable. In their survey of 102 heads of function, 71% said their organization used a top-down change approach. Of the 29% who said they used an Open Source approach, only 11% actually did. Most organizations that believe they've moved on from top-down haven't.

CEB reports a large payoff for doing all three parts of the Open Source approach. The probability of change success rises by as much as 24 percentage points, the number of people resisting falls by up to 19 points, and the number who feel ownership for making it work rises by up to 29. Those are ceilings from the firm's own model, not averages to build a business case on.

What this looked like on a program I sponsored

In 2019 I was the program sponsor on a change effort behind a national system rollout at a Fortune 500 title insurer. The first version of the plan was a cascade. My kickoff deck set the goal: managers would understand how change affects their employees and learn to use brain-based methods with them. Train the managers, and the managers carry it down.

Two weeks later I rewrote it. The audience became Champions rather than managers, people already doing the work in their own offices. The definition of success changed with it, and that week's deck puts it in three words. End in mind equals adoption. Not understanding, and not attendance.

That came out of the audience work. We'd listed what would get in a Champion's way, and it was the same list that would have buried the managers: their time, the extra responsibility, how comfortable they were with the technology, and the disruption to their own work. What differed was what we were asking for. A manager would have had to teach the change to a team on top of a full day. A Champion had to run it in their own office and let people watch.

So the Champions and the managers got the content directly, in two thirty-minute webinars, and they got something to do with it. Each one worked out the new habit for their own role, in their own office. Then we ran a nudge campaign behind them: short videos, instant messages. It was small, it repeated, it came from several directions, and none of it was a cascade.

The rules we wrote for that campaign focused on the person receiving it rather than the message. Keep it short and give them something to do. Send it early in the week. Take the jargon out. Give this particular person a reason to care. And leave room for curiosity, because people pay attention to things they didn't expect.

"If we open this up, we'll lose control of the timeline"

This is the real objection, and it's almost always the first one. Let's break this down using The Shift Method, applied to your own belief rather than your team's.

Identify the belief. If I let teams plan their own implementation, the dates will slip, and I'll be the one explaining it.

Question the evidence. Ask what actually caused the last slip. In most of the rollouts I've seen, the date moved because the tech wasn't ready or the adoption was slower than planned, not because a team was given too much say.

Reframe. You're not handing over the deadline. You're handing over the route. The deadline, the standard, and the things that can't move stay with you, and you should say all three out loud so nobody has to guess which is which.

Vision. Picture the first Monday after go-live. You want each office to be able to answer one question: what are we doing differently today? If the answer comes from the office rather than from your deck, the change is already theirs.

Act. Pick one team this week. Give them the outcome and the date, and let them write the how. Look at what they produce before you widen it.

You'll hear pushback in that first conversation, and most of it is useful. I've written about what to do with it in How to Reduce Resistance to Change.

When top-down is still the right call

Co-creation is a method, not a principle you apply everywhere. Some changes call for the opposite.

Regulatory and compliance changes. When the requirement is fixed by law, inviting input on whether it happens wastes everyone's time and reads as dishonest. Be top-down about the requirement, and open about how teams meet it.

Genuine emergencies. A system outage, a security incident, a deal that closes Friday. Speed beats ownership for a short window, and people accept that when the window really is short.

Small changes with an obvious answer. A new expense form doesn't need a design process, and running one makes the next invitation to participate look like theater.

Decisions that aren't open. If the office is closing, say the office is closing. Asking people to co-create inside a decision you've already made is the fastest way to lose the trust you'll need for the next change.

Most large initiatives end up as a mix, and the trouble starts when leaders are vague about which is which.

Why this is easy for a senior leader to miss

NLI's 2025 report also looked at role level, and the two groups want opposite things. In their words, "as individuals move up the ladder into senior leadership, their sensitivity to Certainty tends to decrease while their need for Autonomy increases." Team members, especially individual contributors, need much more explicit certainty and fairness.

Here's the trap. You want room to decide how you do your own work. A cascade removes exactly that from everyone below you. At the same time, your people want explicit detail, and they want to know this is being handled fairly. You already have the detail, because you wrote it, and you already think it's fair, because you decided it.

NLI's own read is that leaders under-communicate and micromanage without meaning to. Those two things sound opposite. They come from the same place. You're running the change the way you'd want it run.

So open up the how, and be more specific than feels necessary about everything else. Say plainly who you're asking to do what, by when, and why them.

One small shift: in your next update, name one thing you decided and one thing the teams decided. Two sentences. People will believe that far faster than a values statement.

Frequently asked questions

What are the alternatives to top-down change management?

There are three, and they can be used separately or together. Co-creating the change strategy with the people who'll live with it, giving teams ownership of their own implementation planning, and replacing one-way announcements with two-way conversation. CEB's 2016 research grouped these three under the name Open Source change. The easiest place to start is implementation planning, because you keep the outcome and the deadline.

Why does top-down change management fail?

It usually doesn't fail at the decision, it fails at adoption. A cascade spends everything it has on telling people what's happening, and leaves them no part in deciding how the work gets done. In the NeuroLeadership Institute's 2025 SCARF data, having that say is what respondents rank second of the five, up from last place in 2012. As David Rock wrote in 2009, people rarely support initiatives they had no part in designing.

Is bottom-up change management the same as Open Source change?

Not quite. Bottom-up usually describes change that starts with employees and works upward, which leaves open the question of who decides. Open Source change, as CEB defined it in 2016, keeps the decision with leadership and moves the planning and the conversation to the workforce. That distinction is what makes it usable in a regulated business where the what often isn't negotiable.

How do you involve employees in change without losing control of the timeline?

Separate the what from the how, in writing, before you ask anyone anything. State the outcome, the date and the things that can't move, then hand the route to the teams. Start with one team rather than all of them, and look at what they produce before you widen it. A plan a team wrote tends to slip visibly and early, which is easier to manage than the quiet slippage of a plan nobody owns.

When is a top-down approach still the right choice?

When the requirement is fixed by regulation, when you're in a genuine and short emergency, when the change is small and the answer is obvious, and when the decision has already been made and isn't open. In that last case, say so. Running a participation exercise inside a closed decision costs you the trust you'll need for the next change.

What is the first step if our cascade has already stalled?

Talk to the teams where it landed and the teams where it didn't, and ask what they did rather than why they resisted. Then write the one behavior you need per role, in one sentence, in their words. Most stalled rollouts turn out to have no agreed answer to that question, which is why repeating the announcement doesn't help.

If your initiative has stalled and you can't name why, that's the work I do. Feed Your Brain | Consulting helps leaders in title insurance and financial services find where a change stopped, and get it moving again.

About this article. Tiffany Whitney is a NeuroLeadership-trained brain-based coach with 18 years in Fortune 500 learning and development, and the Amazon bestselling co-author of Strength with Kathy Ireland. Every statistic here was checked against its primary source before publication, and where a figure comes from an organization's own data rather than independent research, that is stated in the text. This article is educational and is not medical, psychological or clinical advice.

SCARF® is a registered trademark of the NeuroLeadership Institute. Feed Your Brain is not affiliated with, or endorsed by, the NeuroLeadership Institute.