Organizational Evolution

Read and redesign the system.

Performance emerges from the relationship between strategy, structure, work, decisions, technology and the human conditions in which people operate.

Organizational Evolution helps make that system visible, understand the patterns within it, and redesign the ways of working that shape performance.

02When the context changes

Sometimes the organization has changed. But the way the work happens has not.

  • The strategy is clear, but local decisions remain inconsistent.
  • The organization chart has changed, but the same friction remains.
  • New technologies have been introduced without fundamentally changing the work.
  • Decisions are slow because ownership and approval paths have accumulated.
  • Teams coordinate constantly across interfaces that no longer make sense.
  • Transformation programmes multiply while the underlying way of working remains unchanged.
  • AI adoption is increasing, but human workload, accountability or decision rights remain unclear.
  • The organization is working harder without becoming more adaptive.

What is the organization currently designed to do?

And what is it actually asking people to do?

03See

From redesigning the boxes to redesigning the system.

Redesigning the structure
  • New org chart
  • New roles
  • New governance
  • New processes
  • New programmes
  • New technology
Redesigning the system
  • Value flows
  • Workflows
  • Decision rights
  • Ownership
  • Interfaces
  • Meetings
  • Learning
  • Human + AI work

An organization is not only the structure on paper. It is the system of relationships, decisions, workflows and practices through which work actually happens.

The design target is therefore not simply structure.

It is the operating system.

Before redesigning the organization, understand how it actually works.

Organizational System Map
  • Value flow

    Where is value created, slowed or lost?

  • Decision flow

    Where are decisions made, delayed or revisited?

  • Ownership

    Who decides? Who is accountable?

  • Interfaces

    Where does coordination become friction?

  • Meetings

    Where does coordination create value — and where does it substitute for action?

  • Learning

    Where does experience become organizational capability?

  • Technology

    Where does technology change how work is performed?

  • Human + AI work

    Where are people and AI assisting, deciding, checking, coordinating or executing?

The aim is not to map everything.

It is to identify the patterns that matter most to the current organizational situation.

04Understand

Performance emerges from the conditions in which the system operates.

  • Purpose

    Does the organization know what matters, where value is created and what should receive attention?

  • Passion

    Does the system create the energy, meaning and trust required to contribute?

  • Progress

    Does the organization convert experience into capability and adaptation?

  • Productivity

    Does the operating model turn effort, technology and capability into meaningful value?

  • Perspective

    Can the organization notice changing realities, challenge assumptions and adapt?

Five conditions. One living system.

The Five Conditions are interconnected. Their relationships often explain more than any single condition.

What keeps happening?

  1. Observation

    What do we notice?

  2. →Pattern

    What keeps happening?

  3. →Condition

    What allows the pattern to persist?

  4. →Developmental tension

    What legitimate need might the pattern be serving?

The goal is not to diagnose the organization.

It is to understand the pattern well enough to change it.

05Design

The operating system is the way the organization actually works.

  • Leadership

    How does leadership create or weaken the conditions?

  • Decisions

    How do decisions shape outcomes and future capability?

  • Meetings

    How does meeting architecture shape attention, culture and execution?

  • Ownership

    Where do authority, contribution and accountability need clarification?

  • Trust

    Can disagreement become learning?

  • Learning

    How does experience become capability?

  • Collaboration

    Where do interfaces need redesign rather than more coordination?

The real organization is revealed in how work moves.

An operating model becomes real through everyday work.

The question is not only: “What roles should exist?”

It is: “How should work, decisions, capabilities and accountability be designed so that the system can create value and adapt?”

Work Design is the bridge

Leadership creates conditions.

Work Design embeds those conditions into everyday organizational life.

Evolution Experiments prevent ways of working from becoming static.

Outcome→Work→Roles→Decisions→Interfaces→Technology→Learning→Accountability

Organizational Evolution redesigns work before adding programmes.

06When technology changes the work

AI does not sit outside the operating model.

When AI changes who or what performs work, it also changes decisions, ownership, capabilities, learning, interfaces and accountability.

  • Workflows

    How does the end-to-end work change?

  • Roles

    Which tasks disappear, combine or become more valuable?

  • Decisions

    What may AI recommend or trigger — and what remains human-owned?

  • Human–AI teaming

    Where does AI assist, collaborate, delegate or execute?

  • Governance

    What boundaries, controls and escalation paths are required?

  • Learning

    How does the organization learn from outcomes, errors and exceptions?

The question is not where to add AI.

It is how the distribution of work should change.

07How the work unfolds

Read the system. Understand the pattern. Redesign what matters.

  1. 01
    See

    What is happening in the system?

    Organizational System Map
  2. 02
    Understand

    What pattern and conditions are shaping performance?

    Organizational Evolution Profile
  3. 03
    Design

    What should evolve next?

    Operating Model / Work Design Leverage Map
  4. 04
    Activate

    How does the organization change the work itself?

    Evolution Experiment
  5. 05
    Evolve

    What changed and what did the system learn?

    90-Day Evolution Rhythm

The process is structured.

The target is discovered with the organization.

08Activate

Organizational Evolution happens in everyday work.

  • One conversation

    Create a recurring conversation focused on learning, direction or future capability.

  • One meeting

    Redesign one leadership or cross-functional meeting around decisions, ownership or learning.

  • One experiment

    Test one new decision path, workflow, interface or human–AI collaboration model.

The objective is not to add more work.

It is to change how existing work is done.

09What can change

The change becomes visible in how the system works.

  • Clearer priorities

    Strategic priorities translate more consistently into local decisions and work.

  • Clearer ownership

    Roles, decisions and accountability reinforce one another.

  • Better flow

    Unnecessary coordination and friction decline.

  • Better decisions

    Decisions become clearer, more timely and closer to the work where appropriate.

  • More learning

    Experience and experiments become reusable organizational capability.

  • Better adaptation

    The organization notices changing conditions and challenges assumptions earlier.

  • Human + AI clarity

    Where AI contributes, human judgment and accountability remain visible.

These are examples of observable evidence, not guaranteed outcomes.

10Organizational Evolution may be relevant when…

The context is changing faster than the operating model can comfortably absorb.

  • Operating model change

    The current way of working no longer supports the strategy.

  • Organization redesign

    Structure is changing, but the underlying work and decision patterns also need attention.

  • AI-enabled work

    AI is entering workflows and changing who does what, while accountability and decision rights remain unclear.

  • Transformation fatigue

    Multiple initiatives are underway, but capability and learning are not keeping pace.

  • Performance under pressure

    The organization needs to improve value flow without creating more unnecessary friction or depletion.

  • Cross-functional transformation

    Functions depend on one another in ways the current interfaces no longer support.

  • Scaling

    Informal capability needs to become organizational capability.

  • Ways of working

    The organization wants to evolve through the actual design of work rather than another culture programme.

You do not need to arrive with a target operating model.

We begin by understanding the system you already have.

11How the work is configured

The work is shaped around the system you actually have.

Organizational Evolution is not a standard transformation programme. The engagement is configured around the system, context and leverage points that matter most.

Depending on the situation, the work may include system mapping, workflow exploration, decision and ownership design, human–AI work design or focused evolution experiments.

12Where a first engagement can begin

Read before redesigning.

A first engagement is not an exercise in producing a new organization chart. It is an opportunity to understand how the system currently works — and where meaningful leverage may exist.

  1. 01What is changing right now?
  2. 02Where does the current operating model create friction?
  3. 03What keeps happening despite repeated interventions?
  4. 04Where are decisions, ownership or interfaces unclear?
  5. 05What would need to be observably different in the next 90 days?

Organizations evolve when they become able to redesign how work actually happens.

A clearer view of the system you already have — and a place to experiment with what could work differently.

Human-Centered Evolution™

The future of performance is human.