org-design

name	org-design
description	Design organizational structures, operating models, and role frameworks. Use when restructuring organizations, defining reporting relationships, designing job architectures, aligning org design with strategy, planning spans of control, or building transition roadmaps for new organizational models.

Organizational Design

Structure organizations to execute their strategy through operating models, reporting structures, role frameworks, and transition plans. Org design is a people-affecting discipline that requires connecting structure to strategy and careful change management.

---

The Org Design Process

Step 1: Assess Strategic Requirements

Before drawing boxes and lines, define what the organization must do to execute its strategy. Structure follows strategy, not the other way around.

Strategic alignment analysis:

• Strategic priorities: What 3-5 things must the organization do well to win?
• Capability requirements: What capabilities does each priority demand?
• Critical success factors: What must go right for each capability to work?

Operating model choices (the big decisions that shape everything downstream):

Dimension	Question to Answer
Vertical integration	What do we do ourselves vs. outsource?
Centralization	What decisions sit at the center vs. the edge?
Geographic structure	How do we organize across locations?
Product/service alignment	Do we organize around what we sell or who we sell to?
Customer segmentation	Do customer segments warrant separate structures?
Agility model	Traditional hierarchy, agile pods, or hybrid?

Business model analysis:

• How does the organization create value?
• What are the major cost drivers? Which are structural vs. operational?
• What key partnerships or ecosystem relationships constrain or enable structural choices?

Capability gap assessment:

For each required capability, assess current maturity (1-5) against target maturity. The biggest gaps become the structural priorities. A capability gap that sits at 2 today but needs to be at 5 is a structural problem, not a training problem.

Step 2: Analyze Current State

Document and diagnose the existing organization honestly. Most redesigns fail because they don't understand what's actually happening (vs. what the org chart says).

Structural baseline:

• Structure type: Functional, matrix, divisional, network, hybrid
• Number of layers from CEO to front line
• Average span of control by level
• Total headcount by function/division

7S assessment (McKinsey's framework, useful because it forces you beyond just structure):

Element	What to Assess
Strategy	Is the strategy clear and understood?
Structure	Does the reporting structure support strategy execution?
Systems	Do processes, tools, and IT support the work?
Shared values	Is there alignment on culture and purpose?
Style	How do leaders actually lead?
Staff	Do we have the right people in the right roles?
Skills	Do we have the capabilities we need?

Rate each 1-5 for alignment. The misaligned elements are your design targets.

Pain point diagnosis:

Identify the actual problems people experience, not just the structural aesthetics you'd prefer. Common symptoms of structural misalignment:

• Slow decision-making (too many layers, unclear authority)
• Duplication of effort (overlapping mandates)
• Silos preventing collaboration (wrong integration mechanisms)
• Key work falling between the cracks (structural white space)
• Talent bottlenecks (wrong spans, missing career paths)

Process overlay:

Map how work actually flows across the current structure. Where are the handoffs? Where do things slow down? Where do workarounds exist? The informal organization often matters more than the formal one.

Step 3: Design the Future State

Start with design principles, then evaluate structural options, then detail the selected design.

Design principles (5-7 rules that guide every structural decision):

Good design principles are specific enough to resolve trade-offs. "Customer-centric" is too vague. "Customer segment leaders have P&L authority and direct control over product, sales, and service for their segment" resolves actual decisions.

Examples of principles that actually do work:

• Decisions are made at the lowest level with adequate information
• No more than 6 layers from CEO to front line
• Every role has a clear single point of accountability
• Shared services consolidate where scale matters; embed where speed matters
• Digital and technology capability is built into value streams, not bolted on

Structural options to evaluate:

Structure Type	Best When	Watch Out For
Functional	Single product/service, scale matters, expertise depth needed	Silos, slow cross-functional work
Divisional (product)	Multiple distinct products, end-to-end accountability needed	Duplication, sub-scale functions
Divisional (geographic)	Local market differences matter, regulatory variation	Inconsistency, duplication
Divisional (customer)	Distinct customer segments with different needs	Complexity if segments overlap
Matrix	Two dimensions equally important (e.g., product AND geography)	Dual reporting confusion, slow decisions, conflict
Network/agile	Fast-moving markets, innovation priority, knowledge work	Coordination cost, governance gaps, career path ambiguity
Platform + value streams	Digital businesses, shared infrastructure with diverse products	Platform team becomes bottleneck

For each viable option, assess:

• How well it supports each strategic priority
• Implementation complexity and transition risk
• Cultural fit (how far is this from how people work today?)

Detailing the selected design:

Once a structure is selected, define:

• Top-level architecture: Major units, their mandates, and reporting lines
• Structural dimensions: Target layers, spans of control, authority distribution
• Integration mechanisms: How units coordinate (cross-functional teams, shared processes, liaison roles, communities of practice)
• Governance: Decision rights, escalation paths, committee structures
• Work model: Hybrid, remote-first, or co-located, and how this interacts with structure

Step 4: Define Roles and Job Architecture

Structure without clear roles is just boxes on paper. This is where design becomes operational.

Key role definitions (for every role that matters structurally):

• Purpose: Why this role exists (one sentence)
• Key accountabilities: The 5-7 things this role is responsible for delivering
• Decision authority: What decisions this role makes independently vs. escalates
• Relationships: Reports to, peers with, manages, key stakeholders
• Span of control: Direct reports (target range)

Span of control guidance:

Work Type	Typical Span	Rationale
Routine, standardized work	10-15 direct reports	Work is predictable, less supervision needed
Knowledge work, moderate complexity	6-10 direct reports	Balance of coaching and autonomy
Complex, varied, senior work	4-7 direct reports	High interaction needed
Highly creative, R&D, transformation	3-5 direct reports	Intensive collaboration required

Spans outside these ranges usually signal a problem: too narrow means unnecessary layers; too wide means insufficient oversight or development.

Job family framework:

Group roles into job families with consistent leveling:

• Level definitions: What scope, complexity, and autonomy look like at each level
• Competency expectations: What skills and behaviors are required at each level
• Career pathways: Vertical progression, lateral moves, diagonal (cross-functional) moves

Career pathways matter for retention. If the new structure eliminates career paths people were counting on, you'll lose people you didn't intend to.

Grading framework:

Grade Band	Typical Scope	% of Organization
Executive	Enterprise/division-wide accountability	1-3%
Senior management	Function or large team leadership	5-10%
Middle management	Team leadership, project ownership	15-20%
Professional/specialist	Individual contributor, expertise-driven	30-40%
Operational	Execution-focused, defined processes	30-40%

Step 5: Plan the Transition

The best org design fails if the transition is botched. People experience restructuring as personal, not organizational.

Phased implementation:

Phase 1: Foundation (Weeks 1-4)

• Finalize design and get leadership sign-off
• Develop detailed role profiles
• Assess current incumbents against new roles
• Identify people implications (moves, redundancies, new hires)

Phase 2: Communication (Weeks 5-8)

• Align leadership team first (they must be advocates, not passengers)
• Train managers on the rationale, the "why," and how to have conversations
• Communicate to all employees with clarity and honesty
• Run Q&A sessions; don't hide from hard questions

Phase 3: Implementation (Weeks 9-16)

• Match people to roles (selection processes where needed)
• Execute transitions in coordinated waves
• Launch new teams with clear charters
• Update processes, systems, and governance

Phase 4: Stabilization (Weeks 17-24)

• Monitor for emerging issues
• Provide development support for people in stretched roles
• Fine-tune based on reality vs. design intent
• Measure against success metrics

Risk mitigation:

Common transition risks and how to handle them:

Risk	Mitigation
Key talent leaving during uncertainty	Early, honest communication; retention arrangements for critical roles
Productivity dip during transition	Phase the change; don't reorganize everything simultaneously
Manager resistance to reduced scope	Involve them in design; provide alternative career paths
Cultural clash in merged teams	Invest in team-building; don't assume culture just happens
Loss of institutional knowledge	Document critical processes; use overlap periods for knowledge transfer

Success metrics:

Measure whether the redesign is working:

• Role clarity scores (survey-based, within 3 months)
• Decision speed (time from request to decision, before and after)
• Employee engagement (within 6 months)
• Cross-functional collaboration effectiveness
• Process efficiency improvements
• Leadership effectiveness ratings

Step 6: Establish Governance

The new organization needs governance to operate, not just an org chart.

Decision rights framework:

For key decision categories, define who:

• Decides: Has final authority
• Approves: Must sign off before execution
• Recommends: Provides input that shapes the decision
• Informs: Needs to know the outcome
• Executes: Carries out the decision

(This is RAPID or RACI by another name. The framework matters less than actually clarifying who does what.)

Governance cadence:

Forum	Purpose	Frequency	Participants
Executive committee	Strategic decisions, resource allocation	Weekly/biweekly	C-suite
Operating review	Performance tracking, issue resolution	Monthly	Leaders + 1
Cross-functional sync	Coordination across units	Weekly	Working level leads
Portfolio review	Investment prioritization	Quarterly	Senior leadership

Review and adaptation:

Org design is not a one-time event. Build in structural review checkpoints:

• 90-day post-implementation review
• 6-month effectiveness assessment
• Annual strategic alignment check

---

Key Principles

• Structure follows strategy. If the strategy changes, the structure probably needs to change too.
• Every structural choice is a trade-off. Centralizing gains efficiency but loses responsiveness. Decentralizing gains speed but risks inconsistency. Name the trade-off explicitly.
• Org design is about work, not people. Design the structure for the work that needs to happen, then fit people to roles.
• Spans of control should be driven by the nature of work, not by status or seniority.
• The informal organization is as real as the formal one. Design with awareness of how work actually flows.
• Org design affects people deeply. Communicate honestly, treat people with respect, and don't pretend difficult changes are painless.
• Simple structures outperform complex ones. If you need a 20-page document to explain how the matrix works, the matrix doesn't work.
• Design for the next 3-5 years, not for today's problems. But don't design for a future that may never arrive.
• Build in mechanisms for adaptation. The organization that can restructure quickly beats the one with the perfect structure.