Agile Adaptive Organizations

I don’t hide that AO took a lot of NextGen. The initial AO-Method focused strictly on expending an agile way of working. It did not consider target models.
While I was working at SAP Headquarters, the Global Finance Admin team requested my support. They wanted help with their Digital Finance Initiative as an Agile Organization. They already selected one approach, NextGen.
This was a starting point.

Is that the same? Is AO just rebranding?

Let’s go deeper.

The Stern Stewart NextGen (often called “NextGenCorp”) model is an organizational and leadership design. It tries to combine high stability with high flexibility in one coherent operating model.

Core idea

NextGenCorp separates the company into two different “worlds” and then reconnects them via a central entrepreneurial governance layer.

• A highly standardized, efficient platform for repeatable tasks.
• A flexible, entrepreneurial project swarm for non‑standard, innovation and change work.
• An entrepreneurial plexus that steers both towards shared goals, capital allocation, and strategy.

The goal is to avoid the usual trade‑off “either stable OR agile”. Instead, we should design for both at the same time.

The three main components

1. Platform (stability engine)
   • Bundles all routine, high‑volume, standardized work (e.g. payroll, logistics, basic customer service, standard go‑to‑market activities).
   • Organizations are strictly arranged along end‑to‑end processes. They are heavily digitized with extensive use of automation. AI is utilized to exploit economies of scale, scope, and skills.
   • Clear governance, efficiency metrics, and lean structures; humans gradually move away from transactional work as digitalization advances.
2. Project swarm (flexibility engine)
   • Houses all non‑standard, temporary, exploratory work organized as projects (innovation, transformation, customer‑specific solutions, complex improvements).
   • Built on principles of self‑organization, team‑based decisions, acceptance of failure, and rapid learning loops.
   • Capacity is actively managed by competencies. It is not managed by rigid headcount. People can move from platform roles into swarm roles. This happens as processes get automated.
3. Entrepreneurial plexus (governance & integration)
   • The “brain and heartbeat” that connects platform and swarm and aligns them to strategy and value creation.
   • Defines business models and priorities. Sets the common target system. Manages resource allocation between platform and swarm. Ensures fast, principle‑based decisions instead of slow matrix compromises.
   • Restores entrepreneurial freedom. It assigns P&L‑like responsibility to leaders. Leaders can draw on the platform for efficiency. They can also draw on the swarm for innovation.

Leadership and culture implications

• The platform and swarm require different leadership models. The platform needs more classical, process‑ and KPI‑driven leadership. The swarm requires much more enabling, coaching, and boundary‑setting leadership.
• Overall culture is meant to be more entrepreneurial. It includes decentral decision-making and openness to experimentation. Reinforcement systems should reward initiative and value creation rather than mere compliance.
• They link this to other “NextGen” lenses. These include “NextGen Digital” and “Idea‑to‑Solution”. These lenses extend the same logic to digital strategy and innovation funnels.

Why Stern Stewart positions this as “NextGen”

• Traditional functional or multi‑dimensional matrix organizations are seen as too slow and bureaucratic for digital markets.
• NextGenCorp is proposed as a holistic target picture. Its plan is to redesign structure, processes, leadership, and culture together. This approach avoids running isolated “agile” or “digital” initiatives.
• It is explicitly framed as a “next generation” governance and operating model. This model can cope with volatility. It handles digitalization and the need for continuous innovation at scale.

---

NextGenCorp and the AO‑method are trying to solve the same problem (stable efficiency + adaptive agility). However, they start from different angles. NextGen approaches this from structural/operating‑model design. AO begins with systemic interaction rules and emergent agility.

High‑level intent

• NextGen (Stern Stewart): Design a target operating model with three building blocks. These are platform, project swarm, and entrepreneurial plexus. The model combines scale efficiencies with extreme entrepreneurial flexibility.
• AO‑method: Treat the organization as a social system and use simple interaction rules (coherence, cohesion, separation, avoidance, etc.) so agility emerges from how people interact, not from fixed frameworks.

Structural view: platform, swarm, plexus vs. AO container

• NextGen explicitly splits the organization into:
  • Platform for standardized, end‑to‑end processes, heavily digitized and optimized.
  • Project swarm for temporary, non‑standard, exploratory work (innovation, transformation, complex solutions).
  • Entrepreneurial plexus as the governance “nerve system” that aligns both to strategy and value.
• AO distinguishes between structure as container (fail‑safe boundaries, roles, domains) and organization as experiments (fail‑safe swarming, exploration, adaptive practices).
  • AO can host platforms, swarms, and plexus-like governance. It treats these as patterns that can be tuned. This approach differs from a fixed 3-part blueprint.

Governance and decision‑making

• NextGen’s plexus defines business models and strategies. It allocates resources between platform and swarm. It restores entrepreneurial P&L‑like responsibility in a clear, principle‑driven way.
• AO focuses on systemic decision‑making. Leaders operate as stewards of the social system. They are guided by simple rules. They also follow the five experience loops: enterprise, organization, people, customer, and system. They prioritize these over mainly financial/efficiency KPIs.
• In practice, a NextGen plexus can be interpreted as AO’s “system head” (strategy/coordination). However, AO will insist that its behavior emerges from interaction rules and feedback. It does not come merely from a formal governance organ.

Culture, agility and “swarming”

• NextGen describes a project swarm that dissolves classic matrix hierarchies and is built on self‑organization, experimentation and lived entrepreneurship.
• AO also uses swarming language at the method level. Projects start in swarming. Product owners work on needs, not requirements. Swarming is explicitly used to limit WIP at the portfolio level.
• AO defines agility as “the nature of interactions of agents within a system”. Flocking-like rules (alignment, cohesion, separation, avoidance) shape behavior.
  • NextGen prescribes a structural swarm. AO provides you with the interaction grammar of swarming. You can apply this grammar inside any structure, including a NextGen-style swarm.

Scope: operating model vs. systemic method

• NextGen is positioned as a holistic target operating model for digital corporations. It covers the value chain, go‑to‑market strategies, and admin functions. Leadership is addressed in a “NextGen” context (NextGenCorp, NextGen Digital, NextGen Idea‑to‑Solution).
• AO is a meta‑method for designing agile organizations, independent of specific operating‑model templates.
  • It offers patterns, principles, and an adoption path. These elements can generate many target designs. This includes something that looks very close to NextGenCorp if context demands it.

Summary in table form

Aspect	NextGenCorp (Stern Stewart)	AO‑method (Agile Organization)
Primary lens	Target operating model for digital/NextGen corporation	Systemic method for emergent agility in social systems
Core building blocks	Platform, project swarm, entrepreneurial plexus	Container (structure), experiments (organization), simple rules, swarming
Stability engine	Digitized, process‑oriented platform	Any stable container; AO guides how to design it for coherence & cohesion
Flexibility engine	Project swarm with self‑organization and entrepreneurship	Swarming, adaptive experiments, context‑specific “agiles”
Governance “head”	Entrepreneurial plexus (strategy, capital allocation, mandates)	Systemic leadership guided by experiences and interaction rules
Agility definition	Structural/operating‑model property combining scale + entrepreneurship	Emergent dynamic of interactions between agents in the system
Usage	Prescriptive target picture for large corporates	Design and transformation method, can generate various target models (incl. NextGen‑like)
Digitalization stance	Strong emphasis on platform digitization and AI in processes	Digital as one context factor, not the center; focus on human‑system dynamics
Transformation path	Roadmap to move from classic matrix to platform+swarm+plexus	Phased transformation using AO principles and five experience loops

Example of how you would frame a NextGenCorp transformation using AO phases and language for a Swiss mid‑market client

For a Swiss mid-market client, I’d position NextGenCorp as the target picture. AO serves as the transformation and governance method that guides them there step by step.

1. Positioning and framing (before Phase 1)

• Context: Swiss mid‑market, high pressure on digitalization and AI investment, cautious about big‑bang transformations and heavy consulting overhead.
• Frame: “We use AO to design and steer your journey towards a NextGen‑style operating model. This model includes platform, swarm, and plexus. We tailor it to a speed and risk level that fits your capital and culture.”

I would explicitly say that NextGenCorp is one possible AO‑compatible target, not the method itself.

2. AO Phase 1 – See the system, not the org chart

• Use AO’s systemic lens and five experience loops. These loops include enterprise, organization, people, customer, and system. Diagnose where the “pain” and constraints are today.
• Map existing operations roughly into “platform‑like” (stable, repetitive) and “swarm‑like” (project/innovation/change) work, but without yet changing structure.
• Clarify stereotypes/archetypes (e.g. “industrial matrix with agile pockets”) using AO language, and test whether a NextGen target (platform + swarm + plexus) is realistic given size and context.

Deliverable to client: AO‑style systemic map with “proto‑platform”, “proto‑swarm” and “head” functions highlighted, plus experience tensions (e.g. customer vs. people).

3. AO Phase 2 – Design the container: a light‑weight NextGen

• Use AO’s container concept to shape a minimal viable platform and minimal viable swarm, not the full Stern Stewart blueprint.
  • MVP platform: select 1–2 end‑to‑end processes (e.g. order‑to‑cash, service ticketing) to treat explicitly as platform candidates for digitization and AI readiness.
  • MVP swarm: choose a small portfolio of strategic projects (e.g. new digital service, key account solutions) and place them into an explicit project swarm with AO swarming rules (limit WIP, pull‑based staffing, visible options).
• Design an entrepreneurial plexus in AO terms. It should be a cross-functional “system head” that steers enterprise priorities. This system head allocates capacity between platform and swarm. It works with AO decision rules instead of classic steering committees.

For a Swiss mid‑market firm, this plexus might consist of 3–5 people. These could include the CEO, COO, Head of Sales, and Head of Digital. It is not a big corporate center.

4. AO Phase 3 – Define interaction rules and swarming behavior

• Apply AO’s simple rules (alignment, cohesion, separation, avoidance) explicitly inside the new container:
  • Platform: rules for standardization, reuse, and escalation; clear “avoidance” of custom work in the platform.
  • Swarm: rules for team formation, time‑boxing, decision rights, and customer contact; “cohesion” around value streams rather than functions.
• Implement AO’s swarming and portfolio principles. Start with a visual portfolio board and incorporate option thinking. Set explicit WIP limits and manage dynamic capacity allocation between swarm initiatives.
• Teach leaders to use experience feedback. Focus particularly on customer and people experience as steering signals. The plexus balances this with enterprise and system experience.

This keeps NextGen’s entrepreneurial swarm from degenerating into chaos by giving it an AO‑style interaction grammar.

5. AO Phase 4 – Iterative scaling and digitalization of the platform

• Emphasize NextGen’s proactive digitalization and AI in the platform. Scale it based on AO’s “continuous adaptation” principle. Avoid a big‑bang rollout.
• Every time a process chunk stabilizes in the swarm (e.g. a new digital service), AO guides when to “harden” parts into the platform container, with explicit feedback from people/customer/system loops.
• The plexus regularly revisits structure. It decides which activities stay exploratory in the swarm. It also determines which activities migrate to the platform and which get killed. AO provides the cadence and decision rules for these evolutionary steps.

In a Swiss mid‑market setting, this might mean quarterly AO/plexus reviews instead of annual planning. This should be done with capital discipline that CFOs are comfortable with.

6. AO Phase 5 – Stabilize “NextGen as habit”, not project

• Move from “NextGen transformation program” to “how we run the company.” AO treats structures as evolving. NextGenCorp becomes the current best container. It is not a frozen end‑state.
• Embed AO‑style leadership coaching for middle managers. Teach them to operate as entrepreneurs within the plexus logic. Encourage the conscious use of both platform and swarm. Discourage them from falling back to functional silos.
• Over time, refine the model using experience metrics and adjust the proportions of platform vs. swarm with the plexus acting as a permanent system function, not a temporary project steering committee.

For many Swiss mid‑market firms, this final step is where the competitive advantage appears. They maintain the capital discipline, quality, and reliability of a Swiss SME. However, they operate with a visibly more entrepreneurial, NextGen‑like model.