MADE · STEP 2 · ASSESS
Three topologies.
Choose your org goal.
A topology is a recognizable pattern of where an organization's units sit on the map. Each one is optimized for something — and pays for it somewhere else. None is “best”. The question is whether it fits your purpose and your environment.
TOPOLOGIES AT A GLANCE
Fit for purpose
FROM 10X ORG · PRINCIPLE 4
No organizational topology is “better” in and of itself. There is “no one best way” to organize; there is only the way that fits your purpose.
Leaders must decide what they are optimizing for. That decision requires accountability, not consensus. It implies consciously accepting what they are not optimizing for. Trade-offs are unavoidable: no organization can optimize for everything at once.
Choosing among the topologies, or deliberately combining them for different goals, is the core practice of organizational design. It determines what kind of performance the organization can reliably produce.
THE KEY QUESTION
Which organizational capabilities will effectively support our strategy?
Are you trying to get better at:
| RESOURCE | DELIVERY | ADAPTIVE | |
|---|---|---|---|
| Maximizes | Resource use, specialization | Output, predictability | Outcome, innovation |
| Dependencies | High | Moderate | Low |
| Best environment | Stable, repeatable demand | Known demand, stable roadmap | Uncertain, fast-changing markets |
- RESOURCE
- Maximizes
- Resource use, specialization
- Dependencies
- High
- Best environment
- Stable, repeatable demand
- DELIVERY
- Maximizes
- Output, predictability
- Dependencies
- Moderate
- Best environment
- Known demand, stable roadmap
- ADAPTIVE
- Maximizes
- Outcome, innovation
- Dependencies
- Low
- Best environment
- Uncertain, fast-changing markets
Different parts of one company can run different topologies — a legacy service in Delivery, a new venture in Adaptive. What matters is that each part's design serves its goal.
SAMPLE MAPPING
01 · DIRECTING + DOING
Resource Topology
Org goal: maximize efficiency of specialized skills under stable demand.
“THE MECHANISTIC SYSTEM” — precision through specialization
Dynamics
Directing units plan, split and dispatch work. Specialists in functional groups each do one part. Specs, hand-offs and coordination connect the pieces; upfront planning and re-planning keep it moving.
At a glance
- Common use case
- PMO resource management of specialists
- Value creation
- Fragmented and reliant on multiple handoffs and coordination
- Dependencies
- High; units depend on coordination across functional silos
- Group structure
- Siloed functional groups with specialized roles
- Empowerment
- Low; constrained to predefined tasks with little autonomy
- Individual contributors
- Complete isolated tasks (defined by coordinators) using specific skills, with minimal ownership
- Strategic AI
- Automates repetitive tasks, optimizes workflows, enhances resource efficiency
- Example
- A movie producer hiring dancers for a scene
Typical contexts: shared services, payroll, compliance, commodity manufacturing, long-lived platforms.
Frameworks that build it: PRINCE2, ITIL and others. Also SAFe: ideally it can build a Delivery Topology, but the implementations we studied lean heavily toward Resource, because cross-team interdependencies are not eliminated, only managed as they are.
With AI: AI automates specialized tasks fast — narrow specialist roles face displacement unless mandates widen.
SAMPLE MAPPING
02 · DIRECTING + DELIVERING
Delivery Topology
Org goal: maximize end-to-end flow of predictable work from demand to delivery.
“THE STRUCTURED NETWORK” — optimized for flow
Dynamics
Complete cross-functional teams deliver within fixed, narrow value boundaries. Discovery stays separate, with directing units deciding what to build. Fast and efficient at outputs — sometimes called a “feature factory”.
At a glance
- Common use case
- Fast delivery of proven worth with minimal change or learning
- Value creation
- Narrowly focused on specific capabilities
- Dependencies
- Moderate; units coordinate across boundaries but less frequently
- Group structure
- Cross-functional and aligned with narrow product or service features
- Empowerment
- Moderate; empowered within a small home unit but dependent on alignment between units, managed by Directing units
- Individual contributors
- Coordinate to deliver features and components within the team’s scope
- Strategic AI
- Integrates data, improves collaboration, aligns team outputs through real-time insights and feedback loops
- Example
- A diner with short-order cooks: the owner decides the menu, the cooks deliver complete plates
Typical contexts: established products with known demand, SaaS in growth or maturity, managed services, customer support.
Frameworks that build it: Team Topologies, Marty Cagan’s Product Operating Model (Empowered Product Teams), the Spotify Model when real teams form, and team-level Scrum.
With AI: AI absorbs execution work faster than teams can adapt their skills and mandates.
SAMPLE MAPPING
03 · DRIVING
Adaptive Topology
Org goal: minimize the cost of learning and reconfiguration in volatile environments.
“THE LIVING ECOSYSTEM” — co-evolving with its environment
Dynamics
Directing, doing and delivering merge into one team-of-teams — people and AI agents — with a broad shared mandate. Work is synchronous and coordinated by those doing it; learning runs across skills and across the scope of work.
At a glance
- Common use case
- Fast delivery of uncertain results, to seek, change, discover and adapt
- Value creation
- Flexible, holistic and novel
- Dependencies
- Low; units work autonomously with minimal dependency on external groups
- Group structure
- Multi-skilled and organized for exploratory outcomes and flexibility
- Empowerment
- High; owns entire processes including inter-unit coordination
- Individual contributors
- Collaborate across boundaries to deliver complete customer solutions, with end-to-end ownership
- Strategic AI
- Drives innovation, predicts customer needs, supports strategic decision-making
- Example
- Units working across the entire solution space (“Uber”) or a partial domain (“Uber Eats”)
Typical contexts: new product development, innovation, platform exploration, consulting, research, emerging services.
Frameworks that build it: LeSS, Nexus, FAST and Creating Agile Organizations (CAO). See all framework mappings.
With AI: AI as teacher and sparring partner lowers the cost of switching domains — and makes this design easier to reach.
THE APPROACH
Change, MADE systemic

Org design sits between strategy and performance. MADE is the loop that keeps it fit, named after its four moves: Map, Assess, Design, Elevate. First study the design you have, then improve toward the design you need.
Studythe design you have
- 01MapPlace every unit by skills and work mandate
- 02AssessName the topology you have — and whether it fits
Improvethe design you need
- 03DesignImagine the organization you need, without today’s limits
- 04ElevateGet the change going with Elevating Katas
ELEVATE · STEP 4 OF MADE
Elevating Katas
Elevating is a deliberate move right and up on the map. The katas are the moves: small, repeatable routines that change how the organization works. A menu, not a sequence: start with the few that match your most pressing constraint.
The katas are grouped by the five elements of Jay Galbraith’s Star Model™: change one element and the others must follow.
- 1Strategy Direction and Goals6 katas
- 2Structure Power, Authority, Organization7 katas
- 3Processes Information and Decision Flows9 katas
- 4Rewards Incentives and Motivation3 katas
- 5People Skills, Mindsets, Capabilities2 katas
Case studies rich in katas
All case studies with katas →LeSS Transformation in Wartime Ukraine: Building an Adaptive Organization at DIM.RIA
DIM.RIA's 50-person product organization replaced component teams and many manager backlogs with one Product Backlog and three cross-functional feature teams, cutting cycle time by about 80%.
Katas applied proposed
Elevating an EV Scale-up with Org Topologies
A scale-up flipped its 50-person R&D from component teams to three product areas in two days, then hit local-optimization pain and moved toward a single backlog.
Katas applied proposed
ACADEMY
Learn the Org Topologies approach
All upcoming events
Community
TALK TO THE AUTHORS LIVE
Learn with community
Practitioners share maps, and the authors join the conversation live in Slack.
Join Slack


