# Design: choose the org goal your organization optimizes for

> The Design step of MADE, in the words of 10X ORG: choose one primary org goal, fit the topology to it, and make the org goal win.

URL: https://www.orgtopologies.com/design

## Design.

MADE · STEP 3 · DESIGN

The Design step starts with the question: What should this organization be optimizing for, and which strategic capabilities does it need to develop in order to better serve its future?

From 10X ORG · Principle 5: Change Through a Learning Loop

## Redesigning from a Messy State

FROM 10X ORG · PRINCIPLE 5: CHANGE THROUGH A LEARNING LOOP

Strategy needs a vehicle to translate intent into performance—and that vehicle is the organization.

Thinking of an organization as a vehicle helps. When choosing a car, we clarify what matters most: speed, capacity, safety, or flexibility. A sports car, a freight truck, and an SUV are all well-designed, but for different purposes. No single vehicle excels at everything.

The metaphor breaks down, however, because in real organizational design work, we almost never get a clean showroom choice. Leaders redesign while already in motion—from a messy state.

They inherit structures, people, habits, customers, commitments, codebases, budgets, and policies—and must refactor while the business continues to run. In this reality, change rarely follows a straight line from objectives to design choices to performance gains.

When leaders do try to design more strategically, they often reach for off-the-shelf models. But what worked elsewhere rarely fits this organization’s constraints, history, and work, even within the same industry.

Organizational redesign is not about drawing an ideal diagram on a blank whiteboard.

## Desired Org Goal

FROM 10X ORG · CHAPTER 7: DESIGN FOR THE FUTURE

After the group reviewed the business landscape, the consultant invited them to identify what they wanted strengthened in the organization to increase the likelihood of success. He displayed ten potential “organizational goals”—as he called them—on the screen:

Output Predictability

delivering consistently and reliably.

Lead Times & Throughput

reducing waste, delays, improving flow.

Specialist Expertise

maintaining deep skill and craft where it counts.

Customer Value

delivering outcomes that truly matter to users.

Adaptiveness

responding flexibly to change.

Employee Engagement

sustaining motivation and satisfaction.

Operational Reliability

ensuring stable day-to-day operations.

Ideation and Innovation

generating and testing new ideas.

Organizational Learning

continuously learning and improving.

Resource Efficiency

using resources wisely, without excess.

10X ORG · CHAPTER 7 · QUESTIONS FOR SLOW THINKING

If you were to reimagine your organization based on what it needs to become to be the best version of itself and to drive the strategy well, which one or two organizational goals would you pick from the list?

## Learn the Org Topologies approach

ACADEMY

Practitioner (C-OTP) and Consultant (C-OTC) classes, live online and in person.

Visit the Academy →

## Make the Org Goal Win

FROM 10X ORG · PRINCIPLE 7: MAKE THE ORG GOAL WIN

“Organizations are implicitly optimized to avoid changing the status quo of middle- and first-level manager and ‘specialist’ positions & power structures.”

Craig Larman, “Laws of Organizational Behavior”

The root cause behind failed organizational change is rarely motivation or competence; it is misalignment. It is surprisingly rare for an organization to clearly declare a single primary optimizing goal. Without that clarity, different parts of the organization pull in different directions, each optimizing for what their local system rewards.

False Choices

Consider a shift toward greater customer centricity as an example of a carefully chosen organizational goal.

Top-down, the case looks solid: executives and consultants, viewing the organization as a whole, can clearly see how closer customer proximity would improve outcomes, learning, and long-term performance.

“Yes, I value customer centricity, but if we let developers talk to customers, they’ll have less time to do what they were hired for—development. That would be inefficient.”

Formulating these options as a choice creates a false dilemma. It makes them seem to sit at opposite ends of a spectrum. And as if choosing one necessarily requires sacrificing the other.

Middle managers and specialists are not resisting change out of stubbornness; they are responding rationally to the system they operate in.

We all optimize within the scope of what we own—the scope by which our performance is judged. And we don’t want to fail. What is interesting is that we might not even be aware of the false choices we create.

Context Is King

But what is being efficient, really?

When we look at the three Org Topologies side by side, the difference becomes explicit:

“Efficiency” means maximum productive utilization of specialized skills with minimal idle capacity.

“Efficiency” means fast, reliable end-to-end flow of known work from demand to delivery.

“Efficiency” means lowering the cost of learning, reconfiguration, and redirection.

So when someone argues for making things “efficient,” or uses words like “faster,” “slower,” “cheaper,” or “more expensive” to justify what should be optimized, be cautious.

Ask what they mean, really—local or global speed? Short-term or long-term costs? Efficient for whom? Against which goal?

In too many cases, these questions are not asked, hiding unspoken assumptions.

Secondary Concerns

#1: How do we optimize for customer centricity with its promising business benefits, #2: while also allowing our engineers to work with flow and have enough focused time?

Notice the two parts of this exploratory, open-ended question.

The first part of the question is our primary concern—we want to optimize it for some greater good. This is usually the chosen organizational goal with a broad and positive global impact.

The second part of the question is the secondary concern—something that we value, do not want to lose, diminish, or jeopardize during the change process. We will do our best to work on it, but only to the extent that it does not undermine our primary concern.

So, first things first.

This reframing allows us to find a dozen new, vivid solutions we couldn’t see before when the choice was viewed in black and white. They only become visible once we start asking better questions.

The field of possibilities is endless when you go from “either-or” to “both-and”.

Winning Change

Without an explicit primary goal, everyone fills in the blanks themselves. Each manager and employee defines “efficiency” for themselves from their local perspective and then acts accordingly.

When the org goal is unclear or weakly embedded, “efficiency” becomes a battlefield, and local optimization quietly defeats the intended direction.

Making the org goal win requires explicitly choosing a primary organizational goal, accepting the trade-offs that come with it, and embedding that choice into structure, mandates, incentives, and decisions.

Therefore:

Principle: Make the Org Goal Win.

## Fit Is All You Need

FROM 10X ORG · PRINCIPLE 4: FIT FOR PURPOSE

We must repeat: no organizational topology is “better” in and of itself. As Structural Contingency Theory established decades ago, there is "no one best way" to organize; there is only the way that fits your purpose.

PRIMARY ORG GOAL

SYSTEM METAPHOR

—

resource

Resource

Doing + Directing

Maximize efficiency of specialized skills under stable demand.

“The Mechanistic System”: precision through specialization.

delivery

Delivery

Delivering + Directing

Maximize end-to-end flow of predictable work from demand to delivery.

“The Structured Network”: optimized for flow.

adaptive

Adaptive

Driving

Minimize the cost of learning and reconfiguration in volatile environments.

“The Living Ecosystem”: co-evolving with its environment.

## “Waterfall”

FROM 10X ORG · PRINCIPLE 4: FIT FOR PURPOSE

When applied to Product R&D, the forces behind Resource Topology often lead to rigid ownership of subsystems by individual teams. This pattern is well studied and documented under the names: Component Development or more specifically Component Teams Dynamic.

This approach comes from a traditional way of organizing the work of large software product groups, where developer teams form around architectural modules. Customer-facing features are then decomposed so that each team delivers only the piece related to its component.

Moreover—and this is fascinating—the teams might even think they have no dependencies on each other. How come? Whatever work they see has already been prefiltered to match their skill and work scope.

But that’s a very local lens. Performance has to be judged at the outcome level—on what customers value and what the business needs—not on how neatly each unit works within its silo.

When work is split into components and ownership is fragmented, progress naturally becomes sequential. Each team optimizes its part, hands work over to the next, and waits. Feedback arrives late, learning is delayed, and iteration collapses into a rigid stage-gate process.

To improve global performance, R&D teams must be unpinned from owning components large and small: applications, subsystems, services, and modules. Their mandates have to shift to delivering end-to-end customer features.

Waterfall is not a mindset problem; it is a structural outcome.

## When Fast Feels Last, and Flow Runs Slow

FROM 10X ORG · PRINCIPLE 4: FIT FOR PURPOSE

Delivering value fast and with flow sounds like honey to most executives’ ears. But “fast” and “flow” mean very different things depending on the nature of work.

If some work—service delivery or product development—can truly be done by a single team with good flow, there is little else to wish for. Provided, of course, that the direction of the team’s fast running is right.

The problems begin when the work is truly larger than any team’s scope.

This is the trade-off built into the heart of Delivery Topology. It is optimized for local speed and local flow, because it promises speed and flow only in isolation—by splitting a whole into parts and assigning those parts to teams. The moment an outcome requires coordinated change across many parts, local speed and flow do not translate into global speed and flow.

So next time you promise speed and flow to stakeholders—or if you are a stakeholder being promised that—slow down and go one level deeper: are we talking about local speed or global speed, short-term flow or long-term flow?

## Combining Topologies

FROM 10X ORG · PRINCIPLE 4: FIT FOR PURPOSE

There is something deeply attractive about the idea of a single topology spanning the entire organization. Perfect alignment. One logic. One rhythm. One way of working.

In reality, that level of uniformity is not always feasible. Sometimes the organization is too large. Sometimes it is improving incrementally, constrained by history, contracts, or risk. And sometimes different parts of the business are doing fundamentally different kinds of work. In those cases, multiple topologies will have to coexist.

That is what purposeful organizational design looks like in practice. Leaders must be explicit about what each part of the organization is optimizing for—and accept that different kinds of work call for different topologies.

Making multiple topologies coexist in a synergistic way requires clear guidelines. One key rule is self-sufficiency. For a topology to optimize what it is meant to optimize, it must stand largely on its own—a business within the business.

Clear accountability matters. Each topology needs ownership of outcomes. In practice, this means treating topologies as profit centers wherever possible—containing the relevant costs, investments, and trade-offs within the same structural boundary. Only then can they optimize coherently, without pushing complexity onto the rest of the system.

Multi-topology setups must not be static. As strategy or the environment shifts, topologies must evolve with them. Freezing a topology turns today’s fit into tomorrow’s constraint.

## Serious Redesigns

FROM THE CASE STUDIES

CASE STUDY · 10 MIN READ

roland-flemm

CASE STUDY · 45 MIN READ

andrii-sabaiev

CASE STUDY · 2 MIN READ

denis-salnikov

All case studies →

- [Case Study: Using Org Topologies™ to Analyze the Agile Transformation Journey at a Large Dutch Bank](https://www.orgtopologies.com/post/org-topologies-to-assess-the-agile-transformation-journey-at-a-large-dutch-bank)
- [LeSS Transformation in Wartime Ukraine: Building an Adaptive Organization at DIM.RIA](https://www.orgtopologies.com/post/less-transformation-in-wartime-ukraine-building-an-adaptive-organization-at-dim-ria)
- [How Much Adaptivity Is Enough? PandaDoc's Journey with Large-Scale Scrum (LeSS)](https://www.orgtopologies.com/post/how-much-adaptivity-is-enough-pandadoc-s-journey-with-large-scale-scrum-less-by-denis-salnikov-an)

## Organizational Design

FROM 10X ORG · PRINCIPLE 2: DRIVE PERFORMANCE WITH ORG DESIGN

Jay Galbraith’s Star Model™ offers the most valuable lens. It teaches us that an organization is not just its org chart or sum of all policies, but a system of interconnected design choices that must be made deliberately and kept in sync.

This model represents the core organizational design elements that must be aligned for the organization to deliver on its strategy:

The outcomes the organization is designed to achieve are derived from the strategy and are used as the benchmark for all design choices.

How power and authority are distributed: roles, units, reporting lines, and the basic architecture of who reports to whom.

How work and information flow: governance routines, planning and budgeting cycles, and decision-making processes.

How people are motivated and steered: compensation, promotions, recognition, and other formal and informal incentives.

The skills, mindsets, and capacities needed: how the organization recruits, develops, and grows people to match its strategic needs.

When they are aligned and reinforce one another, performance becomes more reliable and less accidental.

## Complete Means Independent

FROM 10X ORG · PRINCIPLE 3: SHAPE INTELLIGENCE WITH MANDATES

In the OT language, every organizational unit carries a mandate: a bundle of authority and responsibility to decide, explore, act, and deliver results within a defined scope.

Imagine a service-desk team in a large service organization. They answer calls, log issues, and forward requests to other departments. But can they resolve a customer’s billing problem end-to-end? Not really. They are incomplete by design; they do not have the mandate to deliver a full resolution.

Now, picture a full-service team that owns the entire customer experience. They can investigate the issue, update the billing record, adjust the contract when needed, and confirm with the customer that everything is resolved. They have the tools, the data, and the authority to act. That team is complete.

Incomplete doesn’t mean “bad.” But it does mean insufficient and interdependent, as seen through the customer’s eyes.

Incomplete units can serve a purpose: tightening security, enforcing control, reducing costs, or preserving rare specialization. They can also preserve long-standing, outdated organizational habits.

This distinction is crucial because most dependencies are structural and can’t be solved by an extra “alignment meeting” or a “big room” planning session.

In your organization, which units are intentionally incomplete?

What trade-offs made that design acceptable?

What are you protecting by keeping them there?

What are you willing to give up to let these units start moving rightward on the map?

## Follow the Value

FROM 10X ORG · PRINCIPLE 6: FOLLOW THE VALUE—LEARN AND DELIVER

The industry is full of best practices for slicing organizations into parts.

Each unit combines fewer skills and owns a smaller slice of work. The promise is clear accountability within well-defined boundaries for speed: less to care about, less to learn, and fewer distractions. And locally, this works. Teams become very good at executing their part.

But how long does that fit last?

But in a dynamic environment, the narrower the team’s scope, the higher the likelihood that the design will drift out of fit. As work shifts, narrowly scoped teams struggle to respond. Employees and managers might see what needs to be done, but are structurally prevented from acting on it.

The root cause of repeated reorganizations is the inability of organizational units to remain relevant as work shifts. In Resource and Delivery topologies, work is analyzed, decomposed into smaller pieces (streams, features, or tasks), and assigned to organizational units designed to execute that specific type of work. In such setups, work follows workers.

We propose reversing that logic.

When organizations are designed with broader mandates, individuals and teams can take responsibility for larger, unsliced outcomes. Following the value then means learning and delivering what matters most.

This ability to follow value into the unknown, learn there, and still deliver is what creates true adaptive capability. It allows the organization to respond, recombine, and evolve as conditions change—without repeatedly reshuffling its structure to catch up.

Principle: Follow the Value—Learn and Deliver.

## 10X ORG

THE BOOK · POWERED BY ORG TOPOLOGIES

10X is not more activity. It is a tenfold increase in the organization's capability to learn, evolve, create value and stay strategically aligned.

A business novel with a working method inside. The CEO wants fewer hires and more AI. Hanna, head of HR, looks through the Org Topologies lens — and finds an org design misfit no tool can fix. Principles, maps and real case studies along the way.

ALEXEY KRIVITSKY · CRAIG LARMAN · ROLAND FLEMM

More About the Book →

Amazon.com

Amazon.de

Amazon.fr

Amazon.nl

Leanpub

PDF, EPUB and web

“10X is a vote for humanity in an era obsessed with mechanical efficiency.”

WHAT REVIEWERS AND READERS SAY

“You might be surprised how disconnected your organization’s structure is from what you are trying to achieve with it. This book describes a practical approach to organizational redesign, offering a blueprint for success.”

Dave West

CEO of Scrum.org (2015–2026)

“Org Topologies forces an honest look at how the organization truly works, not how the slide decks pretend it works. … What follows is the real magic: defensiveness drops, curiosity kicks in, and the conversation switches from protecting the past to shaping a structure that actually makes sense for the future. OT does what a thousand slide decks never will: it forces clarity, fast. … Most management books add complexity. This one strips it away.”

jurgen-de-smet

Your Chief Simplification Officer (Belgium)

★★★★★ on Goodreads

“Absolutely one of the best books in recent years—and certainly the best at explaining how to get the maximum possible value out of AI. … We purchased the book for our entire executive team, along with 10 additional copies to circulate among others.”

Taru Vasenius

“The book’s core insight is clear: true 10X growth requires rethinking organisational structure—not just adding technology to existing silos. If you want real organisational improvement—not just theatre—read it to understand why fluid scaling and self-organisation are the key building blocks for 10X change.”

quinton-quartel

Creator of FAST Agile (USA)

“Despite being written for the context of 2026, the book is a heavyweight packed with timeless organizational wisdom. My highlighter literally ran out of ink trying to mark all the nuggets for future educational use.”

steinar-haldorsen

Strategic Executive Partner (Norway)

“A rare book that actually changes how you see organizations. … If you've ever sat through a reorg that solved nothing, or watched an 'AI transformation' stall because nobody addressed the underlying structure — this book names what you were feeling and gives you a vocabulary to act on it.”

Tomasz Zelezny

“As someone who lives in the world of Flow, Kanban Strategy, TameFlow, and Org Design, this is the book I've been waiting for.”

jose-coignard

ProKanban Trainer (France)

“The core contribution of the book is simple but powerful: performance is structural. … What I appreciate most in the book is that it treats organizational design not as a consultant deliverable, but as a leadership responsibility!”

Jens Thiemann

“For me, the Org Topologies concept brought new light and joy into scaling conversations, and I would highly recommend it for any organization, no matter how far they are on their agile journey.”

Zuzi Šochová

Certified Scrum Trainer; author of The Great ScrumMaster (Czech Republic)

“In a way, reading 10xOrg feels like revisiting Peter Senge's The Fifth Discipline in the Age of AI.”

Ilja Vi

“Packed with practical tips that help me reflect and act in my role as a leader. This is a book you should always have in your back pocket!”

joris-verheij

Director Anti-Financial Crime Operations, ASN Bank (Netherlands)

“10X Org is one of the few org/design books I've read that genuinely integrates systems thinking, orgl design and AI leverage in a coherent way.”

alena-hlekava

“The characters feel so real that I kept thinking: "Yep, I've worked with this person." … For me, the storyline made the ideas stick.”

Zdenek

“OT gave me the insight that growing companies suffer from a growing need for coordination … The Team-of-Teams, guided by a common vision and goal, requires less top-down coordination.”

michiel-de-van-der-schueren

Digital transformation lead, public sector, Rapid Circle (Netherlands)

“With all the hype around AI, I was getting anxious about my future as a developer. This book helped me change my perspective and understand how to steer my career to remain productive and valuable in my organization.”

Mike Maikovych

★★★★★ on Amazon.com

“As someone who has worked for years with organizational design and large-scale agile transformations, I rarely get genuinely excited about a management book. 10x Org is one of those rare exceptions.”

Robert Briese

★★★★★ on Amazon.de

Executive Agile Coach, Certified LeSS Trainer (Germany)

“I particularly liked the “Ferrari Effect” metaphor: AI can make individuals faster, but if the organisation still has traffic jams and roadblocks, overall performance will not improve.”

Natalia

“For me, Org Topologies™ has become the missing piece of the puzzle that connects agility, frameworks, switching costs, transaction costs, learning costs, to organizational design.”

koen-siegers

“This book goes straight to the heart of the issue: the real bottleneck is rarely the technology — it’s the organizational design.”

Pelzl

“Good managers understand the relationship between organisational performance and how work and skills are structured. Great managers apply this in practice.”

Viktor

★★★★★ on Amazon.nl

“A dialogue-based book that you finish thinking "okay, now I see it." A really necessary book for managers.”

Francois

★★★★★ on Amazon.fr

“A powerful and practical guide for modern leaders. Clear thinking, actionable frameworks, and a compelling vision for combining people and AI to elevate performance. Highly recommended.”

Alexandra

“The exchange between novel and narrative, and explanation of how they helped organisations based on real life experience and examples, is a refreshing way of storytelling as well as educating. A pleasant yet educative read!”

Chiel

“If you’re wondering what your organization is actually optimizing for, read the book!”

julius-alexander-friedrich

on LinkedIn

A manager’s guide to elevating business performance with people and AI

by Alexey Krivitsky, Craig Larman and Roland Flemm

in Business Management, Management Science and Strategic Management

Paperback on Amazon.com ↗

eBook on Leanpub ↗

More shops

Paperback & hardcover

bol.com

Thalia

buecher.de

Kobo

Barnes & Noble

AbeBooks

Libristo

Wristers

Boekenbestellen

Buscalibre

eBook

Kindle

Ex Libris

Google Play

eBooks.com

364 pages

ISBN

Released

Editions

10xorg.com, the book’s home page ↗

Paperback

9789083670409

978-90-836704-0-9

wristers.nl (Bindwijze paperback, 364 blz.), checked 2026-11-18

364 pp

Hardcover

9789083670416

978-90-836704-1-6

buscalibre (Tapa Dura, 376 páginas), checked 2026-11-18

376 pp

EBook

9789083670423

978-90-836704-2-3

exlibris (E-Book epub, 374 Seiten), checked 2026-11-18

EPUB

2026-11-18

2026-02-23

launch newsletter 2026-02-23 (newsletters/2026-02-10x-org-book: “Feb 23, 2026 · 10X ORG BOOK IS OUT”)
