Bottom-Up Change at Work: A 2026 Playbook for ICs and Middle Managers

Real change at work almost never arrives as a dramatic keynote from the CEO. It arrives as a quiet workflow fix from a senior IC, a new template from a team lead, or a Slack channel that turns into the place decisions actually happen. Greg Satell, writing in Fast Company in May 2026, makes the case that top-down transformations stall while bottom-up shifts compound. For individual contributors and middle managers, that is permission to stop waiting. The career skills that keep you employable through constant change and the manager behaviors Google identified in Project Oxygen both point the same direction: influence beats authority.

Why does change rarely come from the top?

Satell argues that executives are structurally the worst-positioned people in a company to drive practical change. They control budgets and headlines, but they sit too far from the actual work. By the time a problem reaches the C-suite, it has been filtered through three or four layers of reporting, polished into a slide, and stripped of the texture that would make it solvable. The person who knows the fix is usually the team lead who has been working around the broken process for eighteen months.

There is also a political problem. CEOs who push hard for change are betting their tenure on it, and most are not willing to do that until the change is already half-won inside the company. That is why so many AI rollouts are failing on a broken foundation and why 74 percent of enterprises rolled back AI customer agents this year. The vision came from the top. The practice never caught up. Even the CEOs themselves are quietly worried about losing their jobs when those AI bets fail.

The Blockbuster story is the cleanest illustration. As Marc Randolph recounts in his memoir That Will Never Work, he and Reed Hastings flew to Dallas in 2000 to offer Netflix to Blockbuster for around fifty million dollars. Blockbuster CEO John Antioco passed. The standard reading is that Antioco was a fool, but Satell would argue the opposite. Antioco was looking at a profitable late-fee business, a national footprint, and a board that wanted predictable quarterly returns. The information that would have made the deal obvious was not in his briefing book. It was in the inboxes of the regional managers who watched customers walk out of stores empty-handed every Friday night. The signal existed inside the org. It just never reached the CEO in a form he could act on.

What is the bottom-up change playbook?

Satell sketches a pattern that researchers in organizational change have documented for decades. The shorthand is small groups, small wins, then a story. You start with a problem you can actually fix at your level, you recruit two or three peers who feel the same pain, and you run a pilot small enough that nobody has to ask permission. You measure the win in language the next level up already cares about, and then you let the result do the lobbying for you.

That sequence works because it inverts the usual mistake. Most ICs and middle managers try to convince leadership of a vision before they have proof. Satell would argue that order is backwards. Leadership does not buy visions. Leadership buys evidence that something is already working. The job is to generate the evidence first, then frame it in a way that lets a VP take credit for noticing it.

The other reason it works is trust. The people who can actually carry the change are your peers and direct reports, not the executives. If you have built relationships across teams, if you have helped other people ship work, and if you have a reputation for being someone who fixes things rather than someone who complains, you have the social capital to run a pilot without anyone questioning it. Drashti's earlier piece on building trust in your first ninety days is essentially the prequel to this playbook.

There is also a long lineage of skunkworks-style precedent here. Kelly Johnson's original Lockheed Skunk Works in the 1940s was built on the idea that a small, semi-autonomous team near the work would out-ship a large coordinated program. That is the same shape Satell is describing in a 2026 office. The names change, the principle does not: keep the team small, keep the scope tight, keep the data visible, and let the result travel before the org chart does.

How do you push change up the org chart?

Pushing change upward is mostly a communication problem, not a strategy problem. You already have the strategy because you live inside the work. What you need is a way to translate what you are doing into the format leadership consumes. That usually means three things: a number, a customer story, and a clear ask that costs the executive almost nothing to say yes to.

The number does not have to be revenue. It can be a cycle-time reduction, a complaint-volume drop, a retention bump on your team, or an hours-saved figure that maps to headcount. The customer story is the texture that makes the number stick in someone's head a week later. The ask is the part most ICs and managers get wrong. They walk into the room asking for budget, authority, or a strategic pivot. The version that works is asking for air cover. You tell the executive that the pilot is already running, the result is already in, and you just need permission to keep going and a sentence of public support at the next leadership meeting.

The scripts matter. A workable Slack DM to a senior sponsor looks like this: "Quick heads-up. Three of us have been running a pilot on X for six weeks. We are seeing a Y percent improvement on Z. Could I get fifteen minutes before our next staff meeting?" That is twenty seconds to read, asks for almost nothing, and gives the sponsor an early claim on the win. The email version is the same shape: subject line names the metric, first paragraph names the result, second paragraph names the ask.

Credit-sharing is the other piece nobody likes to talk about. The version of the story that travels is the one where the senior sponsor looks smart for spotting it. You will not get a fair share of public credit on the first pilot. You will get something more valuable, which is a sponsor who learns that betting on you pays off. That is also why knowing how to say no without burning bridges matters as much as knowing how to push yes. Bottom-up change requires constant negotiation about scope, and the people who win are the ones who can decline gracefully when a senior leader tries to expand the pilot into something it cannot yet support. Likewise, the ability to explain what you actually do at work becomes the difference between a pilot that gets funded and one that gets quietly shelved.

What do middle managers get wrong about change?

The classic middle-manager failure mode is trying to be a miniature CEO. The instinct is to gather the team, announce the new direction, and then drive execution from the front. Satell would call that a smaller version of the same top-down mistake that fails at the C-suite level. Middle managers who succeed at change usually do the opposite. They identify the two or three people on their team who already see the problem clearly, give those people room to run, and spend their own time clearing obstacles and translating upward.

The other common mistake is moving too fast. Fast-moving leaders fail when they create disengagement, and that finding maps directly onto bottom-up change work. Speed feels productive but it costs trust, and trust is the entire balance sheet of a change effort. The managers who get pilots across the finish line are the ones who slow down enough to make sure their team actually owns the new way of working, not just complies with it.

It also helps to contrast this with John Kotter's classic eight-step change model. Kotter leads with "create a sense of urgency" and "form a guiding coalition" before anything ships. Satell's 2026 update flips the priority. The guiding coalition still matters, but the urgency comes from a working pilot, not a slide deck. Middle managers who try to manufacture urgency without evidence usually end up burning the trust they will need when the real change arrives.

A third trap is burnout. Driving change without title authority is exhausting. The middle-manager-burnout-and-fractional-work data shows that this layer of the org is already under more strain than any other. Middle manager burnout is feeding the rise of fractional work precisely because so many of these people are running quiet change efforts on top of their day jobs and getting no credit. If you are leading change without a title, you have to protect your own energy with the same discipline you bring to the work.

When does top-down change actually work?

Satell is not arguing that the C-suite is useless. He is arguing that the C-suite has a specific job in change work, and pretending it has a different job is what makes most transformations fail. Executives are uniquely good at three things: clearing political obstacles, allocating large budgets, and creating cover for risky decisions. They are bad at designing the actual change.

The best transformations pair both layers. The bottom-up coalition designs and proves the change. The top-down sponsor clears the political path and signs off on resources once the pilot has produced results. Duolingo's recent reversal is a useful example. When the CEO walked back his AI-first memo and the company kept hiring humans even as it grew AI usage, what actually happened was that the practitioners inside the company had already established a workable hybrid, and leadership had to catch up to the practice that had emerged below them.

The same pattern shows up in the research on workplace culture deciding AI project success. Culture is downstream of practice, and practice is owned by the middle. Leadership can amplify or block what the middle has built, but it cannot manufacture the culture by itself, no matter how many town halls it runs. The HBR work on treating AI agents as tools rather than employees lands in the same place: the people closest to the workflow decide whether a new system actually gets used, and an executive announcement does not change that.

How do you stay motivated when leadership ignores you?

The hardest part of bottom-up change is the stretch where you are doing the work and leadership has not yet noticed. The pilot is running, the early data looks good, and yet nothing about your day-to-day visibility has changed. This is the moment most change efforts die, not because the idea was wrong but because the person carrying it ran out of patience or capital.

The way through is to compress your feedback loops. Instead of waiting for the quarterly review, build a weekly rhythm with the two or three peers who are running the pilot with you. Celebrate small wins inside that group. Document the wins in a shared doc so that when leadership finally asks, you have a trail. Persisting through workplace uncertainty is mostly about shrinking the time between effort and visible result. You cannot control when an executive notices. You can control how clearly you can tell the story when they do.

It also helps to remember that bottom-up change is rarely the reason people quit their jobs. The real reasons workers are quitting in 2026 point to compensation, management, and lack of agency. Running a change pilot is one of the few ways to manufacture agency inside a role that does not natively give it to you. The NBER data on CEO hiring tilting toward ages 47 to 55 reinforces the same point at the career level: the people who eventually run companies built a documented track record of leading change without waiting for permission. That is a career asset even when the pilot itself stalls.

People Also Asked

Q: Can an individual contributor really drive change without a title?

A: Yes, but only if the change is scoped to something the IC can actually influence with the relationships and tools they already have. A senior IC can rewrite a workflow, propose a new template, or pilot a tool with one or two willing peers. What an IC cannot do is mandate adoption across an org. The trick is choosing changes where adoption is voluntary at first and becomes obvious once the result is visible.

Q: How long does a bottom-up change pilot usually take to get noticed?

A: Most successful pilots take three to six months from first peer conversation to executive visibility. The first month is recruiting your small coalition. The next two are running the pilot and gathering evidence. The final stretch is translating the work into the language and metrics leadership consumes. Pilots that try to compress this timeline tend to burn the people running them.

Q: What is the biggest risk of running change without leadership backing?

A: The biggest risk is not being fired. It is being quietly written off as someone who works outside the lines. The defense is documentation and relationships. Keep your manager looped in early, even if you do not ask for permission. Frame the pilot as something you are learning from, not something you are protesting against. That language difference protects your standing while you build the evidence.

Related Articles

• Google Project Oxygen: 10 manager behaviors that put technical skill last in 2026
• Fast-moving leaders fail when they create disengagement in 2026
• Middle manager burnout is fueling the rise of fractional work in 2026
• Workplace culture decides AI project success in 2026
• How to build trust in your first 90 days at a new job
• If you cannot explain what you do at work, your career stalls in 2026
• How to say no at work without burning bridges
• Five strategies to end overthinking in leadership
• Persist nonetheless: how to handle workplace uncertainty
• Career skills that keep you employable through constant change in 2026
• CEO hiring age 47 to 55: NBER career growth playbook
• State of the Workforce: April 2026

Ready to level up?

If you are an IC or a middle manager trying to push change up the org chart, the most important skill you can build right now is influence without authority. Metaintro tracks the trends, manager behaviors, and career moves that decide who gets to lead the next wave of workplace change. Subscribe for the weekly playbook on how the job market is actually shifting, and what to do about it before the C-suite catches up.