Organizational Change Strategy That Sticks

I'm Kurt Schmidt, founder of Schmidt Consulting Group, and after years of advising B2B services firms and agencies, I keep running into the same pattern. A leadership team is stuck. Something feels broken. They reorg, or they switch project management tools, or they debate remote versus in-office for the third quarter in a row. And nothing actually changes. The root problem stays buried while everyone argues about the symptoms sitting on top of it.

Effective organizational change strategy doesn't start with a framework or a workshop agenda. It starts with the discipline to ask whether you're solving the right problem in the first place. That distinction, between the real strategic challenge and the operational symptoms masking it, is where most change efforts collapse before they get started.

I recently talked through this topic with Sarah Herberg and Ashley Penrod, two consultants who specialize in guiding organizations through complexity with what they call a human-first approach. Their perspective reinforced a lot of what I've observed working with agencies and services firms at inflection points. I want to share what I think are the most practically useful ideas from that conversation, filtered through my own experience.

Why Do Organizational Change Strategies Keep Failing?

Most organizational change strategies fail because skilled operators reach into a toolbox full of operational solutions and aim those solutions at problems that are fundamentally strategic in nature.

A reorg, for example, is a real tool with real use cases. But if your team doesn't have shared clarity on where the organization is going, the reorg solves nothing. Six months later the same friction resurfaces and the leadership team is genuinely confused, because they thought they fixed it. This is the symptom-as-problem trap, and it shows up constantly in fast-growing firms.

I've been inside fast-growing companies where growth itself was the mask. When you're adding 30 people every quarter, you can skip the hard conversations about purpose and direction because nothing feels broken enough to stop and address. The company is just a different company in six months anyway. But growth slows eventually. And when it does, every unresolved strategic question is still waiting.

The pattern Sarah and Ashley described from their own client work maps exactly to what I've seen: leaders who are super skilled operators, whose instinct is to reach for an operational lever when something goes sideways. It's just the wrong tool for a different category of problem.

The first discipline of organizational change strategy is diagnosing which category you're actually in. Are you dealing with an operational execution gap, or a strategic alignment gap? Those require completely different interventions.

What Does Change Fatigue Actually Look Like Inside Organizations?

Change fatigue in 2025 isn't just tired employees. It runs through every layer of an organization, from frontline staff through middle management and straight into the C-suite.

After years of pandemic-driven disruption, political and economic turbulence, and near-constant internal reorganization, many organizations are already deep in a change journey, and the people inside are exhausted from years of that. Leaders included.

What makes this particularly tricky is that exhaustion changes how people receive new ideas. A leader might bring a genuinely good vision to their team, full of energy and optimism, and get almost no reciprocal excitement. The natural instinct is to diagnose that as resistance. But often it's simpler: people are processing what they're being asked to give up in order to move toward the new thing. Change involves loss. People who were good at the old way need time to figure out whether their skills still matter in the new one. That's a reasonable human response to uncertainty.

I talked with a leader recently who had brought a significant new idea to their team and gotten shot down hard. They were genuinely frustrated. As we unpacked it, what became clear was that this leader had a pattern of arriving with big ideas, rallying the team, and then shifting to the next thing before the previous one landed. The team wasn't resisting the idea. They were tired of the cycle.

There's a useful framework here, originally from Kurt Lewin's force field analysis and extended by subsequent organizational change practitioners, that categorizes how people respond to change: champions who get on board quickly, skeptics who need to understand the benefit before committing, cynics who are largely in retreat, and the much larger fence-sitter group who are simply watching before forming an opinion. Most change communications are aimed at champions and treat everyone else as a problem. The skeptics, in particular, are often the most valuable people on the team. Their questions, if heard and integrated, tend to sharpen the vision rather than undermine it.

How Should Leaders Prepare Before Starting an Organizational Change Strategy?

Before any structured change work begins, leaders need to do one specific thing: stop trying to fix things and start gathering data.

This sounds simple. It isn't. High-performing operators have strong pattern recognition. They see a problem and they move toward solving it. Pausing to observe, form hypotheses, and resist implementing those hypotheses as if they're conclusions requires real discipline. But the leaders who skip this step tend to arrive at the change process with a solution already in hand, looking for validation rather than clarity. That's a much harder room to work in.

A few signals I've seen indicate that an organization genuinely needs structured change support rather than another internal initiative. A leadership team keeps having the same conversation without resolution. A significant decision has been sitting unmade for months. There's been a major leadership transition that left teams without a clear cultural through-line. Or the organization just completed a 10-year strategic planning exercise and nobody can explain what actually changed as a result.

The other preparation that matters, and this one is uncomfortable to say plainly, is that the leader has to be able to function as a student of the process rather than the author of the answer. If you're bringing in outside expertise to help your organization work through strategic complexity, and you arrive having already decided what the answer is, you're wasting everyone's time. The leaders who get the most out of this kind of work tend to have a specific quality: they hold their perspective clearly, they're not uncertain or directionless, but they genuinely want to hear what's true from the people inside their organization before drawing conclusions.

Self-care for the leader sounds like soft advice in a business context, but it's operational reality. A burned-out leader pulling a change process forward is a constraint on the whole system. Name it directly.

Is Organizational Change Strategy Different From Change Management?

Organizational change strategy and change management are related but they're solving different problems, and conflating them leads to the wrong interventions.

The key distinction is about sustainability. Change management asks: how do we get from here to there? Organizational change strategy asks: how do we build an organization that can work through from here to wherever there turns out to be?

That second question is harder. It requires a different kind of diagnostic process, one that surfaces the actual views held by different people inside the organization, because a common failure mode is leaders assuming everyone shares their perspective. Often they don't. And a conversation needs to happen about the real differences before any strategic direction can be built on top of them.

In my experience working with agencies and services firms, the organizations that struggle most with change are the ones where leaders have been assuming alignment that doesn't actually exist. The change strategy conversation often starts with the fairly uncomfortable realization that a leadership team has been operating on different assumptions about where the organization is headed.

How Do You Build an Organizational Change Strategy That Improves Over Time?

The goal is an organization that actually gets better through change.

This is where it helps to understand the concept of regenerative systems concretely. Extractive systems deplete resources until they're empty and then go find new ones. Sustainable systems maintain what they have over time. Regenerative systems improve. Applied to organizations, a regenerative system is one where people are energized through the work rather than depleted by it, where new ideas can surface and be integrated, and where rest and reflection fuel the next period of growth rather than being treated as inefficiencies.

This isn't idealistic. I've seen what the extractive version looks like inside agencies: high turnover, burned-out senior staff, a culture of urgency that substitutes for actual strategic clarity. It functions for a while. And then it doesn't. The pivot back from that state is expensive and slow.

Building a regenerative organizational system requires a few concrete practices. First, it requires honesty about what's actually happening in the organization, not the official narrative but the real operational and human reality. That starts with a situation analysis that involves talking to people at multiple levels, anonymously if needed, with specific questions designed to surface what's actually true.

Second, it requires tolerance for mess. Expecting clean strategic clarity before beginning to move is a perfectionism trap. You're looking for momentum, and some of the historical mess in the organization can simply be left alone. Leaders often spend enormous energy trying to resolve every prior decision before making the next one. Most of that historical cleanup is unnecessary. Know where you're going, identify what's blocking the path, and move.

Third, it requires that leaders actually practice what gets decided. Ashley and Sarah made a point I've heard from almost every good organizational consultant: the decision-making moment is rarely the hard part. The hard part is building the habit. "Disagree and commit" is a useful principle, and Ray Dalio's Principles articulates this well for organizations trying to build structured decision cultures. But committing publicly and then quietly relitigating the decision in one-on-ones is one of the most corrosive patterns I see in leadership teams.

For B2B services firms in particular, the diagnostic that tends to open the most progress is simple: are the leaders in the organization aligned on what problem the business exists to solve? I've worked with firms that had detailed strategies, clear OKRs, and solid operational processes, but the leadership team had never had a real conversation about that foundational question. Alignment on that question changes everything downstream.

I covered related ideas about how leadership gaps compound over time on The Schmidt List, including how founders in particular tend to avoid exactly the conversations that would move their organizations forward the fastest.

This work also connects directly to simulation training for leadership and the broader challenge of scaling services firms without burning out the people who built it.

If you're a services firm under 10 people still figuring out product-market fit, this kind of structured organizational change work is probably premature. The complexity isn't deep enough yet to warrant it. In that case, a strong business coach focused on go-to-market strategy for agencies is the better immediate investment. But once you're managing multiple teams, working through leadership transitions, or trying to hold strategic alignment across 50-plus people, the diagnostic question underneath every friction point is almost always the same: does the organization have genuine shared clarity about where it's going, or has it been assuming that clarity exists?

The answer, more often than I'd expect after all this time, is the latter.

Key Takeaways

• Most organizational change strategy fails because leaders apply operational solutions to strategic problems. Diagnose the category before reaching for the tool.
• Change fatigue in 2025 runs through every organizational level, from frontline staff to the C-suite. Treating it as an employee morale problem misses the scale of it.
• Before beginning any change process, the leader needs to move from solution mode into observation mode. Form hypotheses; resist treating them as conclusions.
• Organizational change strategy builds adaptive capacity. Change management manages a specific transition. They're different disciplines requiring different approaches.
• Regenerative organizational systems improve over time rather than just sustaining. The difference is built through honesty, tolerance for mess, and consistent practice of what gets decided.
• Alignment on the foundational question of what problem the organization exists to solve is the diagnostic that opens the most downstream progress.

One question to sit with, especially if you're leading a firm that's been through a hard few years: if you surveyed every leader in your organization today about what the business is fundamentally trying to achieve over the next three years, would the answers converge?