Imposed vs Chosen: Why Most Transformations Are Theater

Your company announced an AI strategy. Not because anyone inside the org identified a use case — because a competitor shipped something that made the board nervous.

Six months later, the initiative has executive sponsorship, a program manager, a Confluence space with 200 pages nobody reads, and a weekly steering committee. It also has almost no adoption. The teams who are supposed to integrate LLMs into their workflows don’t see how it applies. The engineers who do see how it applies weren’t consulted on the architecture.

Meanwhile, a team in a corner of the org has been using Claude to automate their code review triage for eight months. No executive sponsorship. No program manager. Just engineers who got tired of a broken process and built something better. Their tool handles 60% of initial reviews, catches real bugs, and saves each developer four hours a week. Nobody in leadership knows it exists.

One of these changes has a budget. The other has momentum. They almost never have both.

Every organizational change has a source. Either the pressure comes from outside the organization or it originates from within.

Exogenous change is triggered externally. A competitor launches a product. A regulation takes effect. A technology shift makes your approach obsolete. The market moves, and leadership responds.

Endogenous change is triggered internally. An engineer prototypes a better workflow using new tools. A team adopts a practice that spreads organically. Someone writes an internal doc that changes how people think about a problem.

Exogenous:
  Source:       Outside the organization
  Trigger:      Threat, regulation, market shift
  Motivation:   Survival, competitive pressure
  Sponsor:      Leadership (top-down)
  Funding:      Easy (fear is persuasive)
  Adoption:     Hard (imposed, not chosen)
  Knowledge:    Low (decision-makers far from the work)

Endogenous:
  Source:       Inside the organization
  Trigger:      Pain, curiosity, better idea
  Motivation:   Craft, efficiency, frustration
  Sponsor:      Individual contributors (bottom-up)
  Funding:      Hard (no burning platform)
  Adoption:     Easy (built by users, for users)
  Knowledge:    High (creators are practitioners)

Both are real. Both are necessary. But organizations systematically overweight one and underweight the other.

Exogenous change has a built-in sales pitch: fear.

Board meeting, Q1:
  "Our competitor just shipped an AI-powered feature.
   We need an AI strategy."

  Budget approved:     $5M
  Timeline:            12 months
  Headcount:           25 engineers
  Executive sponsor:   CTO
  Slack channel:       #project-atlas

  Time from threat to funding: 3 weeks

Compare this to an endogenous proposal:

Staff engineer, Q1:
  "I've been using LLMs to automate our review triage.
   It saves each dev 4 hours a week and catches real bugs.
   I need 2 engineers for 6 months to productionize it."

  Response:            "Write a proposal"
  Then:                "Get director approval"
  Then:                "Present to the architecture review board"
  Then:                "Align with the AI platform roadmap"
  Then:                "We'll consider it next planning cycle"

  Time from idea to funding: 6-9 months (if ever)

The exogenous proposal had less evidence and more money. The endogenous proposal had a working prototype and couldn’t get two engineers.

This isn’t irrational. It’s asymmetric risk perception. Leadership is far more afraid of being disrupted than of missing an internal improvement. The cost of ignoring an external threat is visible — lost market share, board scrutiny, bad press. The cost of ignoring an internal innovation is invisible — slightly worse developer experience, marginally slower processes, one more frustrated senior engineer who quietly updates their resume.

Here’s the problem: exogenous change is easy to fund and hard to execute. The urgency comes from outside, but the work happens inside — and inside, nobody feels the urgency the same way.

Leadership:
  "The market is shifting. We must integrate AI across the org."

Engineering:
  "Integrate it into what? My workflow is fine."

Leadership:
  "We're building an AI platform. Every team ships an AI feature by Q4."

Engineering:
  "We weren't consulted on this. Our use cases don't fit.
   But sure, we'll check the box."

The result is what organizational theorists call decoupling — the formal structure changes (new tools, new processes, new org chart) while the actual work stays the same. Teams register on the AI platform to satisfy the mandate and keep doing their work the old way. The adoption dashboard shows 80% complete. Actual usage is 30%.

Exogenous change lifecycle:

Phase 1 — Alarm
  External trigger creates urgency
  Leadership announces transformation
  Budget and headcount approved quickly

Phase 2 — Theater
  Program stands up
  Weekly status meetings begin
  Dashboards track "progress" (activity, not adoption)
  Teams comply minimally

Phase 3 — Fatigue
  Urgency fades (the competitor's product wasn't that good)
  Teams resist because the solution doesn't fit their needs
  Leadership attention moves to the next crisis

Phase 4 — Abandonment
  Initiative quietly deprioritized
  Platform team reduced
  Teams revert to old practices
  $5M spent. Little changed.

This cycle repeats. Each time, it makes the next transformation harder because the organization learns that it can wait out any initiative.

Endogenous change has the opposite problem: hard to fund, easy to execute.

When an engineer builds an LLM-powered tool because their existing process drives them crazy, the motivation is intrinsic. They understand the problem because they live it. The solution fits because the builder is the user. Adoption happens because colleagues see something that works and ask to use it.

Endogenous change lifecycle:

Phase 1 — Frustration
  Practitioner hits a pain point repeatedly
  Existing solutions don't work or don't exist

Phase 2 — Prototype
  Built on slack time, hack days, or "skunkworks"
  No formal approval, no budget
  Works for the builder's team

Phase 3 — Organic Spread
  Neighboring teams notice
  "How is your team triaging reviews that fast?"
  Word of mouth adoption

Phase 4 — Legitimacy Crisis
  Too many teams depend on an unsupported tool
  Leadership discovers it exists
  Fork in the road:
    a) Fund it and formalize it
    b) Kill it and force migration to the "official" solution

Option (b) is depressingly common. Leadership kills the thing that works and mandates adoption of the thing that doesn’t — because the official solution went through the proper process, has a program manager, and exists on someone’s roadmap.

The endogenous innovation, discovered by leadership:

  VP: "Who approved this?"
  Director: "Nobody. The team just built it."
  VP: "It's not on the roadmap."
  Director: "No, but 8 teams use it daily."
  VP: "It hasn't been through security review."
  Director: "It's been running for 8 months with zero incidents."
  VP: "Shut it down. We have an AI platform team for this."

  The AI platform team's solution:
    In development for 14 months
    0 teams in production
    3 teams in "beta"
    Last meaningful update: 6 weeks ago

The endorsed solution has legitimacy. The grassroots solution has users. Organizations that consistently choose legitimacy over adoption train their best engineers to stop trying.

In evolutionary biology, punctuated equilibrium describes a pattern where species remain stable for long periods, then change rapidly in response to environmental disruption. Organizational theorists Tushman and Romanelli applied the same model to companies.

Organizational punctuated equilibrium:

  Stability ─────────────────── Disruption ── Rapid change ── New stability
  (5-10 years)                  (external)    (1-2 years)     (repeat)

  During stability:
    - Processes ossify
    - Culture solidifies
    - Internal innovation suppressed
    - "If it ain't broke, don't fix it"

  During disruption:
    - Panic
    - Top-down transformation mandated
    - Everything changes at once
    - High cost, high chaos, uncertain outcomes

This is the default pattern for large organizations. Long periods of exogenous-resistant stability punctuated by frantic, exogenous-driven transformation.

The cost of this pattern is enormous. During the stable period, endogenous improvements are blocked — exploration is cut in favor of exploitation. During the disruption, the organization over-corrects, launching massive transformations without the institutional knowledge of what actually needs to change.

Continuous endogenous change would eliminate the need for most exogenous-driven transformations. But continuous change requires continuous investment in slack, experimentation, and autonomy — exactly the things that get cut during stable periods.

The best leaders are bilingual — they speak finite to leadership and infinite to their teams. The exogenous/endogenous split requires a similar translation skill: converting bottom-up insight into top-down language.

What the engineer knows:
  "I built an LLM tool that automates review triage.
   8 teams use it. It saves 4 hours per dev per week."

What leadership needs to hear:
  "We have an engineering efficiency opportunity worth $1.2M/year.
   A proof-of-concept serving 8 teams has demonstrated 93% accuracy
   and measurable time savings. I'm proposing we formalize this
   as a Q3 initiative with 2 engineers and a $200K budget."

Same change. Different language.

The engineer who can make this translation gets their innovation funded. The one who can’t watches it get killed.

This is a structural failure, not a personal one. Organizations should have mechanisms for endogenous innovation to surface without requiring every engineer to also be a business case writer. Most don’t.

If endogenous change is higher quality but lower funded, the fix is structural: create pathways for bottom-up innovation to get resources without requiring an external crisis.

Instead of:
  "Who approved this?"

Try:
  "This has 8 teams using it with zero incidents?
   Let's fund it properly."

Create an explicit path from prototype to product. Hack days produce prototypes. What happens next? In most orgs, nothing — the prototype dies when sprint work resumes. Build a lightweight process: demo → review → small funding → pilot → scale.

Don’t wait for a crisis to fund change. Allocate a standing budget for internal innovation — not a massive “transformation fund,” but a modest, renewable pool for 2-4 person experiments.

Exogenous funding model:
  Crisis → $5M → 25 engineers → 12-month program
  Hit rate: Low (solution designed far from the problem)

Endogenous funding model:
  Standing allocation → $500K/year → 5 small bets
  Hit rate: Higher (solutions built by practitioners)
  Cost of failure: Low (small bets, not big programs)

This is option value thinking — you’re buying cheap options on future improvements.

Exogenous change tracks compliance: “200/200 teams registered on the AI platform.” Endogenous change tracks adoption: “How many teams are actually using it daily?”

Compliance metric:
  "Platform registration: 85% complete"
  (Doesn't tell you if anyone is actually using it)

Adoption metric:
  "Daily active teams: 60% of eligible"
  (Tells you the solution is solving a real problem)

If teams aren’t voluntarily adopting, the solution doesn’t fit — regardless of what the registration dashboard says.

The most common way endogenous innovation dies: a top-down mandate replaces it with the “official” solution.

Before mandate:
  Team A: Custom LLM review tool (works great)
  Team B: Custom AI test generator (works great)
  Team C: Waiting for official AI platform

After mandate:
  All teams: Official AI platform (works for Team C)
  Team A: Lost their review tool, worse off
  Team B: Lost their test generator, worse off
  Team C: Slightly better off, but at 3x the cost

Smart organizations incorporate endogenous innovations into the official platform rather than competing with them. The team that built the better tool should be consulted — or hired onto the platform team — not overridden.

The healthiest organizations don’t rely on either source alone. They use exogenous pressure to create urgency and endogenous knowledge to direct the response.

Pure exogenous:
  Urgency: High
  Direction: Wrong (designed by people far from the work)
  Adoption: Low (imposed)
  Outcome: Expensive theater

Pure endogenous:
  Urgency: Low (no burning platform)
  Direction: Right (designed by practitioners)
  Adoption: High (chosen)
  Outcome: Never gets funded

Combined:
  Urgency: High (exogenous trigger)
  Direction: Right (endogenous practitioners shape the solution)
  Adoption: High (solution fits real needs)
  Outcome: Actual transformation

The pattern: leadership sets the strategic direction (we need to integrate AI into our workflows). Practitioners shape the solution (here’s what we’ve already built that works). Funding flows to proven prototypes, not PowerPoint architectures.

This requires leadership to do something uncomfortable: admit that the people closest to the problem know more about the solution than the people approving the budget. It requires practitioners to do something equally uncomfortable: learn to package their innovations in language that secures resources.

Dimension Exogenous Change Endogenous Change
Source Market, regulation, competitor Practitioner pain, curiosity, craft
Trigger Threat Frustration
Funding Easy (fear sells) Hard (no crisis to point to)
Knowledge Low (far from the work) High (built by practitioners)
Adoption Low (imposed) High (chosen)
Speed to budget Weeks Months (if ever)
Quality of solution Variable (often poor fit) High (built from real needs)
Failure mode Expensive theater Dies in obscurity

The pattern in most large organizations:

  1. Endogenous innovation is suppressed during stable periods
  2. Exogenous shock triggers panic-driven transformation
  3. Transformation is designed top-down, far from the work
  4. Adoption is low because the solution doesn’t fit
  5. Initiative fades. Organization returns to stability
  6. Repeat

The fix:

  • Fund small endogenous bets continuously, not big exogenous programs episodically
  • When exogenous pressure creates urgency, channel it through endogenous expertise
  • Measure adoption, not compliance
  • Create pathways for bottom-up innovation to surface and get resourced
  • Stop killing grassroots solutions in favor of official ones that don’t work

The organizations that transform well aren’t the ones that react fastest to external threats. They’re the ones that were already changing from within — and use external pressure to accelerate what was already working.

Change that’s imposed is tolerated. Change that’s chosen is adopted. The difference between transformation theater and actual transformation is which kind you’re funding.