Skip to main content

The New Logic: Change Should Be Co-Created, Not Commanded

The New Logic: Change Should Be Co-Created, Not Commanded graphic on co-created change

Chuck Those Ol’ Change Logic Approaches: Why Traditional Change Approaches are Failing

For decades, organizations have relied on a familiar formula for change:

  • Executives decide
  • A rollout plan is built
  • Communications begin
  • Resistance is “managed”
  • Compliance is monitored

It is neat. It is structured. It is comfortable. It is also the opposite of co-created change.

And in today’s world, it increasingly fails.

Not because leaders are lazy. Not because employees are “resistant.” Not because the communication team missed a few messages.

It fails because the logic underneath it is outdated.

This is Industrial Era change logic—built for organizations designed like machines: centralized, hierarchical, predictable, and optimized for control.

That model made sense when change was occasional.

But in today’s environment—where organizations are dispersed, work is digital, complexity is constant, and adaptation must happen in real time—that same logic often creates the very friction it claims to solve.

Traditional change is not failing because people are hard to convince. It is failing because the system is built on the wrong assumptions.

As Built to Adapt argues, organizations must stop treating change as an episodic event to be managed and start embedding adaptation into daily operations as a continuous capability.

The Real Problem: You’re Treating an Operating System Issue Like a Communication Issue

Here is the uncomfortable truth many leaders still avoid:

Most failed change efforts are not communication failures. They are operating model failures.

When leaders say:

  • “People don’t get it”
  • “We need stronger messaging”
  • “We need a better change plan”
  • “Managers need to reinforce the narrative”

…they are often misdiagnosing the issue.

Because if people closest to the work were not involved in:

  • defining the problem,
  • making sense of what is changing,
  • exploring options,
  • shaping the solution,
  • and testing what will actually work,

then no amount of messaging will fix the gap.

That gap is not awareness. It is ownership.

That is the central reframe in Built to Adapt: move from change-as-persuasion to change-as-co-creation. Instead of broadcasting decisions and managing resistance after the fact, adaptive organizations involve people in shaping the systems they work in—making resistance less something to “manage” and more something to prevent through participation.

Why Traditional Change Logic Backfires in Dispersed Organizations

In distributed and dispersed organizations, old change logic becomes even more fragile.

Why?

Because distance amplifies everything:

  • Misunderstanding spreads faster
  • Context gets lost
  • Local realities differ
  • Trust is harder to maintain
  • Central assumptions break more easily
  • Managers become bottlenecks
  • Employees feel change is being imposed from far away

In this environment, top-down change often produces predictable side effects:

  • False alignment

Leaders mistake message distribution for shared understanding.

  • Surface compliance

People comply enough to stay safe—but do not commit enough to improve the system.

  • Local workarounds

Teams quietly adapt the change to reality because the design did not reflect actual work.

  • “Resistance” that is actually useful feedback

What gets labeled as resistance is often expertise trying to protect the organization from a bad design.

  • Change fatigue

Not because there is too much change—but because too much change is imposed without meaningful involvement.

This is exactly why the New Era shift matters: organizations must move from episodic, expert-led interventions toward continuous, participatory adaptation embedded in everyday work.

Let’s Be Honest: “Managing Resistance” Is Often a Symptom of Poor Design

One of the most outdated phrases in change management is:

“We need to manage resistance.”

That phrase carries an Industrial Era assumption: That the right answer has already been decided, and the remaining job is to get people on board.

But what if the resistance is not irrational?

What if it’s NOT the people that is the problem?

What if it is telling you:

  • The problem was defined too narrowly
  • The design ignored operational reality
  • Decision-makers are too far from the work
  • Risk was underestimated
  • Local conditions were not considered
  • Trust is low because participation was absent

In that case, resistance is not the enemy.

It is intelligence.

Built to Adapt makes this point powerfully in its manifesto: “Design for change, not resistance.” That means building organizations and processes that make routine adaptation normal, instead of relying on specialists to push people through episodic, top-down change.

That is a major shift in posture:

  • From controlling reactions → to improving design quality
  • From selling the answer → to co-creating the path
  • From reducing pushback → to increasing participation

The New Logic: Change Should Be Co-Created, Not Commanded

The principle is simple:

People support what they help design. They resist what feels done to them.

That is not just a humanistic statement.

It is an organizational performance principle.

Why?

Because co-created change produces:

  • Better diagnosis of the real problem
  • Faster detection of unintended consequences
  • Higher-quality decisions through frontline insight
  • Greater ownership and accountability
  • Less rework after launch
  • Stronger trust across functions
  • Better adoption because the solution already reflects reality

This is why the Org-Change Manifesto for the New Era explicitly states:

  • Everyone owns the change
  • Change is co-created, not commanded
  • Change leadership is everywhere
  • Shared understanding before deciding

That is not a “soft culture” statement.

It is a direct challenge to the Industrial Era assumption that a small group should diagnose, decide, and deploy while everyone else adjusts.

Co-Creation Is Not Soft. It Is Strategic.

Let’s kill another myth while we’re here:

Co-creation is not a kumbaya workshop.

It is not endless consensus-building. It is not democracy without accountability. It is not letting everyone vote on everything.

That misunderstanding keeps many executives trapped in outdated models.

Co-creation, done well, is disciplined.

It means:

  • Involving the right people early
  • Bringing frontline knowledge into the design
  • Making constraints visible
  • Testing assumptions before scaling
  • Clarifying decision rights
  • Allowing local adaptation inside shared guardrails
  • Building shared understanding before locking decisions

In other words:

It improves the quality of the change before you ask people to live with it.

That is exactly aligned with the New Era principle of distributed decision-making and leadership as facilitation, where authority moves closer to the source of impact and leaders create conditions for better decisions instead of trying to control every move.

What Leaders Must Stop Doing Immediately

If you want better change outcomes, stop defaulting to these five habits:

  • Stop treating change as a rollout

A rollout is the tail end of a process. If you begin there, you are already late.

  • Stop using communication as the primary lever

Communication matters. But communication should support shared sensemaking—not compensate for exclusion.

  • Stop calling dissent “resistance” too quickly

Pushback may be the most valuable data in the room.

  • Stop assuming executives can fully design the future from a conference room

Distance from the work creates design defects.

  • Stop measuring success as compliance

Compliance tells you whether people followed instructions. It does not tell you whether the system became more adaptive, effective, or resilient.

What New Era Leaders Must Start Doing Instead

Here is the shift:

  • Start with shared sensemaking

Before solutions, create shared understanding of the problem.

  • Involve people closest to the work

The people living the system often understand it better than the people governing it.

  • Design with, not for

Co-design the change with those who will implement and sustain it.

  • Use pilots and iteration

Don’t “launch and pray.” Test, learn, refine, scale.

  • Shift managers from controllers to facilitators

Silvia Calleja’s work reinforces this: the manager’s future role is less “problem solver” and more coach/facilitator—helping teams think, decide, and learn rather than rescuing them from every challenge.

  • Build adaptation into the work itself

If change only exists as a special project, the organization is still operating with old logic.

This Is Bigger Than Change Management—It’s About Organization Design

Here is the deeper point many change professionals still miss:

You cannot fix outdated change practices without redesigning how the organization works.

Why?

Because change behavior is downstream from organization design.

If your organization is built around:

  • centralized authority,
  • slow approvals,
  • siloed functions,
  • manager dependency,
  • low trust,
  • and risk avoidance,

then your change approach will naturally become:

  • top-down,
  • delayed,
  • overly planned,
  • communication-heavy,
  • and resistant to local adaptation.

That is why Change leaders worth their salt keep tying together organization design and change.

Final Thought

You do not create adaptive change inside a fundamentally non-adaptive system. You can't. You must redesign the conditions for adaptation:

  • clearer purpose,
  • better local decision rights,
  • tighter feedback loops,
  • more transparency,
  • fewer layers,
  • stronger facilitation capability,
  • and more participatory problem-solving.

Or said bluntly:

If your operating model still assumes control, your change model will keep producing compliance theater.

Do you want to continue to act in Change and Compliance Theater, or do you want to dig deeper and really help the folks inside these organizations struggling within the Systems (ways of working)?

It's a choice.

Written by: Dana Houston Jackson, Owner of Change – With a Coach Approach, LLC

Quick Answers

Why do traditional change approaches fail?

They run on Industrial Era logic: executives decide, a rollout plan is built, communication begins and resistance gets managed. Most failed changes aren’t communication failures. They’re operating model failures, because the people closest to the work never helped define the problem or shape the solution.

What does co-created change mean?

People closest to the work help define the problem, make sense of what’s changing, explore options, shape the solution and test what works. People support what they help design and resist what feels done to them.

Why does co-creation improve performance?

It produces a better diagnosis of the real problem and designs that fit actual work, and it builds ownership instead of surface compliance. What gets labeled resistance is often expertise trying to protect the organization from a bad design.

Originally published on LinkedIn on March 13, 2026. Read it on LinkedIn.

Dana Houston Jackson

Dana Houston Jackson is the founder of Change With A Coach Approach, LLC and the author of The AI Adoption Traps. She started in manufacturing, spent 10 years in construction, taught K-12 and university students, and ran technology projects as a scrum master and project manager. As a consultant she has stood up project management and change management offices and trained clients across industries, including work with the Department of Energy. She’s a speaker, advisor and executive coach with 30 years in the work, now focused on helping leaders turn AI activity into lasting capability.

    Comments are closed