Beyond transformation: build organisations that evolve by design

For much of the twentieth century, organisations were designed for stability. Strategy was set, structures aligned, and work proceeded until a disruption demanded a deliberate transformation effort. Change was something to be planned, implemented, and completed.

That model has become increasingly misaligned with reality. Markets shift rapidly, technology evolves continuously, workforce expectations change, and geopolitical and environmental uncertainty now shape everyday decisions. In this context, change is no longer episodic; it is ongoing and cumulative. The challenge for leaders is not how to manage change projects more effectively, but how to design organisations that can operate productively while continually changing.

Karl Weick and Robert Quinn’s (1999) distinction between episodic and continuous change provides a useful lens. Episodic change is infrequent, intentional, and disruptive: restructures, major system implementations, or strategic resets. It aligns with Lewin’s unfreeze–change–refreeze sequence and with project-based transformation.

By contrast, continuous change is constant, evolving, and emergent. It consists of small adjustments that accumulate over time: shifts in routines, decision rules, team boundaries, and ways of working. Rather than restoring equilibrium, continuous change treats instability as the normal condition. The organisation is not “refrozen” but continually rebalanced.

A helpful metaphor is the difference between a dam and a flowing stream. Episodic change builds pressure until a dramatic release is required. Continuous change allows pressure to move through the system in smaller, ongoing ways. Modern organisations increasingly resemble the stream rather than the dam.

Purpose and core capability as anchors for change

Continuous change raises a fundamental question: what should this organisation truly be responsible for? Without clarity of purpose and core competence, adaptation risks becoming reactive rather than strategic.

Research on core competencies (Prahalad & Hamel, 1990) and more recent work on purpose-driven organisations (Gulati, 2020) converge on the idea that not all work should be treated equally. Leaders must distinguish between:

• what is mission‑critical
• what differentiates the organisation
• what can be sourced, partnered, or automated

Real‑world examples illustrate this shift:

Unilever, under former CEO Paul Polman, clarified its purpose around sustainable living and divested non-core brands while investing heavily in capabilities related to sustainability, supply chain resilience, and consumer insight.

Large healthcare providers increasingly partner with analytics firms for data infrastructure while retaining clinical decision-making and patient relationships as core.

Global retailers have outsourced commodity IT hosting and back-office functions while retaining strategic capability in data, customer experience, and digital service design.

Purpose and core competence act as stabilising reference points. They help leaders decide not only how to change, but where to invest attention and where to simplify.

From change programmes to organisational design

Much leadership and management practice still assumes that change can be separated from “normal operations.” Transformation initiatives are launched alongside business‑as‑usual activity, often with dedicated programmes and temporary governance structures.

However, when change is continuous, this separation becomes artificial. Organisational design, meaning the way teams, roles, and processes are structured, becomes the primary mechanism through which change is absorbed and enacted.

A large metropolitan hospital provides an instructive example. Rather than running discrete “digital transformation” programmes, it restructured clinical and administrative staff into multidisciplinary service lines responsible for patient pathways (for example, emergency care or chronic disease management). Technology improvement became part of day‑to‑day work, not a parallel initiative.

Other examples include:

• Spotify’s squad–tribe model, which embeds continuous improvement into autonomous product teams rather than centralised transformation offices.
• Airlines that redesigned operating models during the COVID-19 crisis to integrate digital, customer, and operational teams, enabling rapid adaptation to demand fluctuations.
• Toyota’s production system, which treats improvement as part of everyday work through kaizen rather than episodic change programmes.

This shifts attention from managing transitions to designing adaptive systems.

Principle 1: Design for learning, not just efficiency

Traditional organisational design prioritises efficiency, standardisation, and predictability. While these remain important, they are insufficient in environments where assumptions must be regularly revised.

From a psychological and coaching perspective, adaptive capacity depends on sensemaking: the ability of individuals and groups to notice changes, interpret their meaning, and adjust behaviour accordingly (Weick, 1995).

Technology firms operationalise this through rapid feedback loops between users and developers. Companies such as Microsoft, Netflix, and Atlassian have moved from fixed annual release cycles to continuous deployment models supported by product teams who own learning as well as delivery.

Structurally, this implies:

• Short feedback loops between action and outcome
• Decision‑making close to the point of information
• Time and space for reflection, not just execution
• Norms that legitimise experimentation and course correction

In investment decision‑making, similar logic appears in staged funding models. Venture capital portfolios assume uncertainty and adapt allocations based on evidence rather than original plans. Learning becomes a strategic input rather than a by‑product of failure.

Principle 2: Shift from control to coherence

In stable environments, coordination is achieved through detailed plans and hierarchical control. In conditions of continuous change, these mechanisms become brittle.

Management consulting literature increasingly emphasises coherence: aligning purpose, priorities, and decision principles so that autonomous action remains directionally consistent.

Netflix offers a well-known example. Rather than detailed rules and approvals, Netflix emphasises “freedom and responsibility” and “context, not control,” trusting high-talent teams to make decisions within a clear strategic frame.

Other examples include:

• Haier’s RenDanHeYi model, which decentralises authority to micro‑enterprises aligned by shared purpose and customer value.
• Amazon’s “two‑pizza teams”, which operate autonomously but are guided by clear leadership principles and customer‑obsessed metrics.
• Spotify’s squad–tribe model, where small, cross‑functional squads are granted significant autonomy over how they deliver, while alignment comes from shared missions and lightweight leadership structures.

This requires:

• Clear strategic intent rather than exhaustive roadmaps
• Shared criteria for prioritisation
• Transparent trade‑offs between speed, risk, and quality
• Distributed authority within agreed limits

Leaders become designers of conditions rather than controllers of outcomes.

Principle 3: Treat change as a portfolio, not a project

Continuous change challenges the logic of one‑off transformation initiatives. Instead of discrete programmes, organisations face overlapping waves of improvement, innovation, and compliance‑driven adjustment.

Investment logic provides a useful parallel. Portfolios balance risk, return, and timing. They are reviewed regularly and adjusted based on performance and context.

Examples include:

• Maersk, which maintains a rolling portfolio of digital, logistics, and automation initiatives rather than a single enterprise transformation.
• ANZ Bank, which adopted an agile portfolio model, enabling staged investment and reallocation based on customer outcomes.
• Google X, which treats innovation as a portfolio of “moonshots” with staged continuation based on evidence of value.

Applied to organisational change, this implies:

• Visibility across multiple initiatives
• Explicit balancing of operational stability and innovation
• Staged commitments rather than full upfront investment
• Willingness to reallocate resources as conditions evolve

Purpose again provides a filter: initiatives aligned with core capability and mission are protected; peripheral activity is deprioritised.

Principle 4: Build teams around work, not hierarchy

Organisations designed for continuous change favour team‑based structures aligned to enduring problems rather than temporary projects.

Examples include:

• Kaiser Permanente in the US, which organises around patient journeys rather than functional silos.
• ING Bank, which reorganised into cross‑functional squads aligned to customer journeys, reducing handoffs and increasing accountability.

Such designs feature:

• Cross‑functional teams with clear outcome ownership
• Fluid task allocation within stable role boundaries
• Reduced dependency on escalation chains
• Integration between strategy and delivery

Change becomes embedded in everyday work rather than delegated to transformation offices.

Principle 5: Attend to the human experience of continuous change

Continuous change is also a psychological condition. It places sustained demands on attention, identity, and emotional regulation.

Studies in organisational psychology show that prolonged ambiguity can generate fatigue and defensiveness if not well supported (Kahn, 1990; Maitlis & Sonenshein, 2010). Leaders therefore face a dual task: enabling adaptation while maintaining coherence and meaning.

Examples include:

• Satya Nadella’s cultural reset at Microsoft, which emphasised growth mindset, empathy, and learning as antidotes to defensiveness and siloed behaviour.
• Airbnb’s crisis leadership during COVID‑19, where CEO Brian Chesky communicated transparently, acknowledged emotional impact, and reinforced purpose even while making difficult decisions.

This involves:

• Helping people interpret what is changing and why
• Distinguishing experimentation from instability
• Normalising uncertainty without minimising it
• Supporting reflection on habits and assumptions

Here, coaching‑oriented leadership becomes critical. Resistance becomes information rather than obstruction.

Principle 6: Strengthen system awareness and boundary-spanning

Continuous change requires leaders who can see patterns across the system rather than optimise isolated parts.

Examples include:

• Procter & Gamble’s “Connect + Develop” model, which integrates external innovation into internal R&D.

This principle emphasises:

• Cross‑boundary collaboration
• System mapping and pattern recognition
• Shared intelligence across teams and partners
• Awareness of second‑order effects

Principle 7: Build rhythms and rituals for rebalancing

Continuous change requires deliberate rhythms that create temporary stability — enough to act, but not enough to stagnate.

Examples include:

• Agile cadences (sprints, retrospectives, demos) that create predictable cycles of reflection and adjustment.
• Netflix’s quarterly “context not control” reviews, which align teams without imposing rigid plans.
• Te Ao Māori practices such as pōwhiri, whakawhanaungatanga, and wānanga, which create relational grounding and collective sensemaking.

This principle emphasises:

• Regular reflection cycles
• Rituals that reinforce purpose and connection
• Temporary stabilisation points
• Collective sensemaking

From managing change to practising change

The implications of continuous change are not merely operational. They alter what it means to lead and manage.

Leadership becomes less about driving transitions and more about sustaining movement. Management becomes less about enforcing plans and more about shaping patterns of work.

Accountability shifts from compliance with predefined tasks to stewardship of evolving outcomes.

Weick and Quinn’s insight that continuous change follows a “freeze–rebalance–unfreeze” pattern is instructive. Stability is not eliminated but made temporary and functional: enough structure to act, enough looseness to adjust.

Rather than oscillating between chaos and control, effective organisations cultivate dynamic equilibrium through many small recalibrations rather than periodic upheavals.

Conclusion

The central challenge facing modern organisations is no longer how to implement change, but how to operate when change is ongoing. This requires a shift in mindset from transformation to design, from programmes to systems, and from control to learning.

Frameworks from project management, investment theory, consulting, psychology, and leadership development converge on a common insight: adaptability must be built into structure, not bolted on through initiatives.

Purpose and core competence provide the necessary anchors. They help leaders decide what must be protected, what can be adapted, and what can be sourced externally. Without this clarity, continuous change risks becoming directionless.

In this context, leadership is less about certainty and more about coherence; less about solving and more about framing; and less about directing movement than enabling it. Managing and leading become inseparable from changing.

Continuous change, then, is not a problem to be solved, but a reality to be practiced.