This chapter sets the foundation for the entire playbook. It explains what organizational design really means in practice, how it differs from related concepts like strategy and operating model, and why structure still matters for performance. You’ll also see how the rest of the book is organized and how to use it as a step-by-step guide for a live org design project.
1.1 What Organizational Design Is (and Is Not)
Organizational design is the discipline of shaping how work, decisions, and people are structured so the organization can deliver its strategy reliably and at scale. At its core, it is about making deliberate, coherent choices on who does what, who decides what, and how the pieces fit together day to day.
A practical way to think about organizational design is through four questions:
- What work needs to be done to deliver our strategy and promises to customers?
- How should that work be grouped into units, teams, and roles?
- How will decisions be made and coordinated across those units
- Who will be accountable for what outcomes?
If you can answer these questions clearly and consistently, you are doing organizational design.
Organizational design is:
- The definition of the macro-structure: business units, functions, regions, and how they relate.
- The creation of clear mandates and accountabilities for each unit and role.
- The design of decision rights and governance so that critical decisions are made at the right level, with the right speed and quality.
- The shaping of interfaces and ways of working between units to avoid fragmentation and friction.
- The alignment of roles, capabilities, and talent with the organization’s most critical activities.
Organizational design is not:
- Simply drawing an org chart. The picture of boxes and lines is an output, not the design itself.
- A headcount reduction exercise. Cost can be an outcome of design, but if cost-cutting is the sole objective, you are doing restructuring, not design.
- A cosmetic title change. Renaming roles and functions without changing underlying work and decisions is re-labeling, not design.
- An HR-only activity. HR is a critical partner, but org design is a top-management responsibility because it shapes how the business competes and performs.
- A one-time event. The first design is a hypothesis; organizations need periodic adjustments as strategy and context evolve.
It is also important to distinguish organizational design from adjacent concepts:
- Strategy defines where and how you will compete. Organizational design defines how you will organize to execute that strategy.
- Operating model is broader: it encompasses structure, processes, technology, data, and culture. Organizational design is the structural and human side of the operating model.
- Culture and leadership are enablers of performance, but changing culture alone will not fix structural bottlenecks, and vice versa. The best designs take culture and leadership realities into account.
You will see throughout this playbook that effective organizational design is less about a “perfect” model and more about coherent, explicit choices. Many different designs can work; very few incoherent designs do.
1.2 When Structure Actually Matters for Performance
Executives often swing between two extremes. On one end: “Our problem is structure; we need a reorg.” On the other: “Structure doesn’t matter; it’s all about people and culture.” Both positions are incomplete.
Structure matters when it systematically makes it easier or harder for people to do the right work well. In practice, structure has material impact in at least five domains:
- Speed and quality of decisions
When decision rights are unclear, duplicated, or concentrated in the wrong places, decisions become slow, political, or low quality. Typical symptoms:- The same topic is debated repeatedly in multiple forums.
- Teams “shop” decisions around the organization until they get the answer they want.
- Senior leaders spend disproportionate time arbitrating cross-unit conflicts.
- In these situations, structural choices about where P&L responsibility sits, how governance forums are set up, and how cross-functional teams are formed can materially improve decision speed and clarity.
- Customer experience and growth
Structure influences how easy or hard it is to deliver a coherent experience to customers. Common issues:- Customers in the same segment are served by different units with inconsistent pricing and service.
- No one owns the end-to-end customer journey; handoffs are frequent and clumsy.
- Sales, delivery, and service are fragmented across functions with weak coordination.
- Shifting to a more segment-, product-, or journey-oriented structure, or clearly defining “accountable owners” across units, can unlock growth and customer satisfaction.
- Accountability and performance management
When accountabilities are diluted across multiple leaders, performance suffers:- Outcomes are jointly owned by three or four units, with none truly in charge.
- Metrics are misaligned; one unit is rewarded for volume, another for margin, another for customer satisfaction, leading to conflicting behaviors.
- Structural clarity—who owns what outcome, what each unit is mandated to deliver—enables a sharper performance dialogue and better resource allocation.
- Scalability and efficiency
As organizations grow, structures designed for a smaller, simpler business can become strained:- Too many layers between the front line and the CEO.
- Duplicate functions across business units with no standardization.
- A headquarters that has accumulated activities but not been deliberately designed.
- Redesigning spans and layers, consolidating duplicative activities into shared services or centers of excellence, and clarifying corporate vs business unit roles can unlock material productivity.
- Risk, control, and compliance
In regulated or complex environments, unclear structural accountability for risk and control leads to:- Gaps where no one owns key risks.
- Overlaps where multiple functions attempt to control the same risk in different ways.
- Confusion between “second line” and “first line” responsibilities.
- Thoughtful design of risk, compliance, and control roles—and how they interface with the business—matters directly for regulatory outcomes and reputational risk.
At the same time, not every performance issue is a structural one. Many “we need a reorg” conversations are, in fact, about:
- Weak or misaligned leadership.
- Poorly defined priorities and too many initiatives.
- Capability gaps in critical roles.
- Broken processes or systems.
A useful quick test before launching into org design is to ask:
- If we kept the current structure but dramatically improved leadership quality and clarity of priorities, would performance materially improve?
- Are the problems we see localized to a few leaders or teams, or systematic across units and processes?
- Do we repeatedly see the same structural issues (e.g., accountabilities unclear, customers falling between cracks) despite changing people?
If the issues are systematic and repeat across leaders, structure is likely a material part of the problem and worth addressing deliberately. If the issues are localized and strongly linked to individual behaviors, a full-blown redesign may be unnecessary and distracting.
A short checklist you can use:
Signals you may have a structural problem
- Important decisions are regularly escalated because it is unclear who owns them.
- Customers or partners frequently complain about being “handed around” the organization.
- Multiple units perform similar activities with different standards and tools.
- Senior leaders spend a lot of time resolving turf conflicts rather than growing the business.
- P&L responsibility does not line up with the levers leaders actually control.
- The number of management layers has grown over time without deliberate design.
If three or more of these statements describe your organization, this playbook is likely directly relevant to your current challenges.
1.3 The Role of the Organizational Design Playbook
This playbook exists for a simple reason: most organizations still approach org design as a one-off “reorg” event rather than a disciplined management capability. The goal here is to give you a practical, end-to-end approach you can apply to real projects, not a theoretical treatment of organizational forms.
This book is designed for:
- CEOs and general managers who must sponsor and make decisions on structure.
- CHROs and HR leaders who are responsible for driving the design process.
- Business unit and functional leaders asked to redesign their parts of the organization.
- Strategy and transformation leaders who need to connect org design to broader change.
It assumes you are busy, under pressure to deliver results, and need clear guidance on the “how”, not generalities about being agile or customer-centric.
You can expect the playbook to provide:
- A clear project sequence: from clarifying the problem and mandate, through diagnosis and design, to implementation and sustainment.
- Frameworks and lenses to structure your thinking: how to choose a grouping logic, how to balance centralization and decentralization, how to think about spans and layers.
- Checklists and templates where they genuinely help you not miss critical steps: for design principles, decision rights, role charters, and implementation plans.
- Typical pitfalls and patterns from hundreds of real projects: where designs usually fail, what to watch out for in governance, how to avoid common history-repeating mistakes.
The playbook will not:
- Tell you there is one “best” organizational model. Different strategies and contexts need different designs.
- Attempt to cover every theoretical variant of structure. You will see repeated emphasis on a small number of practical choices that matter most in real life.
- Replace the need for judgment. Organizational design is an exercise in trade-offs; no framework can remove the need for leadership decision-making.
You can use this book in three ways:
- As a step-by-step guide for a live org design project.
- As a reference for specific questions (e.g., “How should we think about decision rights?”).
- As a capability-building tool for your leadership team and HR function, to establish a shared language and method.
Subsequent chapters will follow the rough sequence of a well-run design effort: why to redesign, how to frame the effort, diagnose, design, and implement; and how to use external advisors well when you need them.
1.4 How to Use This Book in a Live Project
The most powerful way to use this playbook is alongside a real organizational design effort. This section offers a concrete way to do that.
Think of a design project as moving through five broad phases:
- Frame and mandate – Clarify why you are redesigning and what success looks like.
- Diagnose – Understand how the current organization is working and where it is failing.
- Design – Develop and test macro- and micro-structure options, decision rights, and roles.
- Plan implementation – Translate the design into a sequenced, practical implementation plan.
- Implement and sustain – Execute the change and build mechanisms to keep the organization healthy.
The chapters in this playbook map to those phases. A practical way to use it is as follows.
Before you start the project
- Read Chapters 1–3 to align your leadership team on:
- What organizational design is.
- Why you might be redesigning now.
- The main frameworks and options you will be choosing among.
- Use Chapter 2 to articulate the triggers for your redesign and to test whether structure is really the issue.
- Use Chapter 5 (Shaping the Org Design Program) to clarify scope, governance, roles, and the overall workplan. Treat it as a template for your project charter.
During diagnosis
- Use Chapters 4, 6, and 7 to:
- Translate strategy into clear design objectives and principles.
- Structure your diagnostic fact base: what data to collect, who to interview, which pain points to probe.
- Synthesize the diagnosis into a set of design hypotheses you will test in the next phase.
- Treat the diagnostic checklists as “do not forget” guides, not rigid questionnaires. Adapt them to your business.
During design
- Use Chapters 8–12 and 14–15 as your primary references:
- Chapter 8 for macro-structure options and trade-offs.
- Chapter 9 for designing teams and roles.
- Chapter 10 for decision rights and governance.
- Chapter 11 for spans and layers.
- Chapter 12 for interfaces and collaboration.
- Chapter 14 for footprint and sourcing choices.
- Chapter 15 for quantifying impact and building the business case.
- Before each design workshop, identify which specific choices you expect to make (e.g., “Should we organize around products or regions?”) and revisit the relevant sections to structure the discussion:
- Use the frameworks to prepare 2–3 clear structural options.
- Use the design principles you agreed earlier as tests for those options.
- Use the checklists to ensure each option addresses accountabilities, governance, and interfaces—not just the org chart.
During implementation planning
- Use Chapter 16 to:
- Decide on overall implementation phasing (big bang vs phased).
- Identify key risks (e.g., loss of critical talent, disruption to customers) and mitigation actions.
- Structure your communication plan and change story.
- Apply the templates for implementation roadmaps and risk registers as starting points, not final answers. Every organization’s constraints are different.
During implementation and beyond
- Use Chapter 17 to design:
- The metrics and feedback loops that will tell you whether the new design is working.
- The review cadence for adjusting roles, interfaces, and governance without triggering a full redesign every year.
- Return periodically to earlier chapters to remind yourself:
- Why did you make the design choices you did?
- Which trade-offs you consciously accepted.
- Which risks you expected and how you planned to address them.
A simple way to embed the playbook into your project rhythm
You can institutionalize the use of this book with a straightforward routine:
- Pre-meeting preparation
For each steering committee or design session, the project lead identifies the relevant chapter sections (e.g., “8.1–8.3” for a macro-structure workshop) and circulates a short reading list with 2–3 key questions the group must answer. - In-session reference
Keep the relevant frameworks and checklists visible in the room (printed or summarized in your deck). Use them actively:- When stuck in debate, go back to the design principles.
- When considering an option, explicitly test it against the criteria and pitfalls outlined in the book.
- Post-session documentation
After each major design decision, document:- The decision made and the rejected alternatives.
- The rationale in terms of strategy and design principles.
- Any assumptions or risks associated with the choice.
- Over time this becomes your org design log—a record that prevents you from relitigating the same debates and helps future leaders understand why the organization is structured as it is.
- Capability building alongside delivery
Use selected chapters as material for short leadership and HR learning sessions:- For example, a 60-minute lunch session on decision rights (Chapter 10) with live examples from your business.
- Or a working session on spans and layers (Chapter 11) using your actual org data.
- This accelerates not just the current project, but your organization’s ability to manage structure as an ongoing discipline.
You do not need to read the entire book before acting. The minimal viable approach is:
- Align on why you are redesigning and what you want to achieve (Chapters 1–2).
- Set up the project and governance properly (Chapter 5).
- Then move through the remaining chapters as the project unfolds, pulling in what you need at each step.
If you treat this playbook as a living reference and integrate it into the rhythm of your project, it will help you move from episodic reorgs to a more deliberate, repeatable practice of organizational design.
