🧠 Knowledge Base

Institutional Isomorphism: Why Organisations End Up Looking Alike

Focus
Category
Lens
Latest blog posts
Focus
Category
Lens
Institutional Isomorphism explains why organisations within the same field start to resemble one another, not because it makes them more effective, but because it makes them appear legitimate in the eyes of stakeholders.
Explanation
What it is

Institutional Isomorphism describes the process by which organisations within the same field become increasingly similar over time. Instead of purely competing on efficiency or innovation, organisations conform to shared norms, pressures, and expectations.

This convergence is driven by the pursuit of legitimacy — appearing credible, modern, or trustworthy in the eyes of regulators, funders, peers, and the public.

When to use it
  • When analysing why reforms across different institutions produce near-identical outcomes.
  • When evaluating the role of external pressures (regulation, accreditation, funding) in shaping organisational behaviour.
  • When diagnosing cultural or structural sameness that limits innovation or differentiation.
Why it matters

Understanding Institutional Isomorphism helps reveal why surface-level reforms so often look alike but fail to address deeper dysfunction. By recognising these conformity pressures, leaders and observers can better distinguish between genuine redesign and performative change, improving clarity, legitimacy, and long-term alignment.

Definitions

Institutional Isomorphism

The process by which organisations within a field converge in structure, practice, and appearance to maintain legitimacy.

Coercive Isomorphism

Similarity driven by external pressures such as regulations, laws, or funding requirements.

Mimetic Isomorphism

Similarity that emerges when organisations copy others in conditions of uncertainty, adopting practices perceived as successful.

Normative Isomorphism

Similarity resulting from professional standards, education, and shared cultural expectations within a field.

Notes & Caveats
  • Isomorphism is not inherently negative; it can enable interoperability and shared standards.
  • Misread: assuming similarity always signals efficiency or quality; in reality, it often reflects conformity for legitimacy.
  • Critique: excessive isomorphism can stifle innovation and entrench systemic dysfunction, reinforcing the Dustpan Delusion dynamic.
Objective

Identify whether organisational similarity is a sign of healthy alignment or a symptom of conformity that reinforces dysfunction.

Steps
  1. Map organisational practices
    Compare structures, policies, or technologies across peers in the same field.
  2. Classify drivers
    Determine whether similarities stem from coercive (regulatory), mimetic (copying), or normative (professional) pressures.
  3. Assess legitimacy vs. effectiveness
    Record whether conformity improves actual outcomes or merely optics.
  4. Document findings
    Verify by linking observed patterns to external pressures, not just internal choices.
Tips
  • Use a simple table to log observed similarities and their likely driver type (coercive, mimetic, normative).
  • Cross-check reforms against user outcomes: if sameness doesn’t improve speed, quality, or trust, it may be isomorphic theatre.

Pitfalls

Assuming similarity equals best practice

Always ask if the change improves outcomes or just legitimacy.

Over-generalising all conformity as negative

Recognise that shared standards can sometimes improve interoperability.

Acceptance criteria
  • A clear list of observed similarities mapped to isomorphism type.
  • Record of whether changes improve outcomes (not just appearances).
  • Stakeholder agreement on whether the pattern reflects reform or conformity.
Scenario

A national healthcare provider adopts a new AI-powered triage chatbot after regulators signal support for “digital-first” innovation. Competing hospitals quickly follow, fearing reputational risk if they appear behind.

Walkthrough

Decision Point

Leadership teams must decide whether to adopt the chatbot. The pressure isn’t clinical evidence but the perception that “everyone else is doing it.”

Input/Output

Input: regulatory endorsement, peer adoption, and media narratives about “modernisation.”

Output: procurement brief and rollout plan, mirroring peers.

Action

Procurement teams implement the same vendor solution with minimal customisation. The outcome is institutional conformity rather than tailored redesign.

Error handling

When the chatbot struggles with complex cases, organisations double down (“patch with FAQs”) rather than reassess whether the adoption solved root problems.

Closure

The cycle ends with most providers offering nearly identical systems — not because they work better, but because divergence feels too risky.

Result
  • Before → After: Perceived modernisation increases trust optics, but clinical quality and patient outcomes remain unchanged.
  • Artefact snapshot: Vendor contract + identical chatbot workflows across multiple institutions.
Variations
  • If regulatory pressure eases, adoption rates slow and diversity of approaches re-emerges.
  • If larger institutions push back (e.g. citing patient safety evidence), smaller players may mimic them instead, shifting the mimetic anchor.