Organizational design including structure optimization, spans and layers analysis, role clarity, and transition planning. USE THIS SKILL when the user asks about org structure, reorganization, restructuring the organization, spans of control, reporting lines, organizational effectiveness, operating model design, RACI matrix, decision rights, role clarity, headcount optimization, or "how should we organize." Also trigger when asked to assess organizational health, evaluate structural options, plan a reorg, or design a new operating model aligned to strategy.
Calculate average and median spans of control at each organizational level.
Industry benchmarks by function and level:
| Function | Frontline Manager | Mid-Manager | Senior Leader | Executive | |---|---|---|---|---| | Sales | 8-12 | 6-8 | 5-7 | 5-8 | | Operations / Manufacturing | 15-25 | 8-12 | 5-8 | 5-7 | | Customer Service / Call Center | 12-20 | 8-10 | 5-7 | 5-7 | | Engineering / R&D | 6-10 | 5-8 | 4-6 | 4-6 | | Finance / Accounting | 5-8 | 5-7 | 4-6 | 4-6 | | HR / Legal / Admin | 5-8 | 5-7 | 4-6 | 4-6 | | IT / Technology | 6-10 | 5-8 | 4-6 | 4-6 | | Marketing | 5-8 | 5-7 | 4-6 | 4-6 | | General Management | N/A | 5-8 | 5-7 | 5-10 |
Red flags in spans of control:
Count organizational layers from CEO to frontline. Benchmark against:
| Organization Size (Headcount) | Typical Layers | Best-in-Class | |---|---|---| | < 100 | 3-4 | 3 | | 100-500 | 4-5 | 4 | | 500-2,000 | 5-6 | 5 | | 2,000-10,000 | 6-8 | 6 | | 10,000-50,000 | 7-9 | 7 | | > 50,000 | 8-11 | 8 |
Symptoms of excess layers:
Map decision rights for 8-12 critical business processes using RAPID framework:
| Decision | Recommend | Agree | Perform | Input | Decide | |---|---|---|---|---|---| | Pricing changes | [Role] | [Role] | [Role] | [Role] | [Role] | | New product launch | [Role] | [Role] | [Role] | [Role] | [Role] | | Hiring (backfill) | [Role] | [Role] | [Role] | [Role] | [Role] | | Hiring (new role) | [Role] | [Role] | [Role] | [Role] | [Role] | | Capital expenditure >$X | [Role] | [Role] | [Role] | [Role] | [Role] | | Vendor selection >$X | [Role] | [Role] | [Role] | [Role] | [Role] | | Customer escalation | [Role] | [Role] | [Role] | [Role] | [Role] | | Strategic partnership | [Role] | [Role] | [Role] | [Role] | [Role] |
Decision rights red flags:
For each major role, assess:
Define 4-6 design principles that link the future structure to the business strategy. Each principle must be specific enough to resolve a design trade-off.
Framework for writing design principles:
| Strategic Priority | Design Principle | Structural Implication | |---|---|---| | Customer centricity | "Organize around customer segments, not internal functions" | Segment-based P&L units; customer-facing teams empowered to make decisions | | Speed to market | "Minimize approval layers; max 2 approvals for decisions below $[X]" | Flatten hierarchy; push authority to frontline; co-locate product teams | | Cost efficiency | "Consolidate shared services; eliminate duplication across regions" | Shared services center for finance, HR, IT; standardized processes | | Innovation | "Create dedicated innovation units shielded from operational demands" | Separate innovation team; ring-fenced budget; different governance | | Integration (post-M&A) | "One leadership team per function within 90 days; no dual roles" | Clear integration timeline; role selection process; single reporting line | | Global consistency | "Global process ownership with regional execution flexibility" | Global COEs set standards; regional teams adapt within guardrails |
Test each principle: Does it help resolve a real design disagreement? If everyone would agree with it regardless, it is too vague.
Evaluate which archetype best fits the strategy and design principles.
| Archetype | Structure | Best When | Watch Out For | |---|---|---|---| | Functional | Organized by function (Sales, Ops, Finance, HR, IT) | Single business/product line; efficiency and expertise matter most; stable environment | Silos between functions; slow cross-functional coordination; CEO becomes bottleneck | | Divisional | Organized by product, geography, or customer segment; each division has its own functions | Multiple distinct businesses; speed and autonomy matter; divisional P&L accountability needed | Duplication of functions across divisions; loss of scale economies; inconsistent practices | | Matrix | Dual reporting — typically function + business/region | Need both functional excellence and business responsiveness; complex global operations | Role confusion; power struggles between matrix dimensions; slow decisions if not well-governed | | Network / Platform | Small core with ecosystem of partners, contractors, and internal product teams | Highly dynamic environment; need for speed and flexibility; platform-based business model | Coordination complexity; culture dilution; dependency on partner quality |
Hybrid approaches: Most real-world designs are hybrids. A common pattern is Divisional at the top with Functional shared services. Document which archetype applies to which part of the organization and why.
Develop minimum 3 distinct structural options. Each option must be a genuinely different design, not a cosmetic variation.
Per option, document:
| Attribute | Option A | Option B | Option C | |---|---|---|---| | Name / Label | [Descriptive name] | [Descriptive name] | [Descriptive name] | | Archetype | [Functional / Divisional / Matrix / Network / Hybrid] | | | | Top-level structure | [Description of L1/L2 reporting] | | | | Spans of control (avg) | [Target spans by level] | | | | Layers (CEO to frontline) | [Target layers] | | | | Headcount impact | [Net change: +/- X FTEs] | | | | Key roles created | [New roles required] | | | | Key roles eliminated | [Roles no longer needed] | | | | Annual cost impact | [$X savings or cost] | | | | Implementation complexity | [Low / Medium / High] | | | | Time to implement | [X months] | | | | Alignment to design principles | [Score each principle: Strong / Partial / Weak] | | | | Primary risk | [Biggest risk of this design] | | |
For the recommended option, build a full RACI matrix for the top 10-15 business processes.
| Process | Role A | Role B | Role C | Role D | Role E | |---|---|---|---|---|---| | Strategic planning | A | C | R | I | C | | Annual budgeting | C | A | R | I | C | | Product development | I | C | A | R | C | | Sales (enterprise) | I | I | C | C | A/R | | Customer onboarding | I | I | R | A | C | | Talent acquisition | C | A | I | R | I | | Performance management | C | A | I | R | I | | Vendor management | I | C | A | R | I | | Regulatory compliance | C | I | I | I | A/R | | Capital allocation | A | C | I | I | C |
R = Responsible (does the work), A = Accountable (owns the outcome), C = Consulted, I = Informed.
RACI rules: Every process must have exactly one "A." If a process has more than 3 "C" roles, simplify.
| Category | Current FTEs | Option A | Option B | Option C | |---|---|---|---|---| | Executive / C-Suite | | | | | | Senior Management | | | | | | Middle Management | | | | | | Professional / Individual Contributor | | | | | | Frontline / Operational | | | | | | Shared Services | | | | | | Contractors / Contingent | | | | | | Total | | | | | | Net Change from Current | — | +/- X | +/- X | +/- X | | Annual Salary Impact | — | $___M | $___M | $___M | | One-Time Restructuring Cost | — | $___M | $___M | $___M |
One-time costs include: severance (typically 1-4 weeks per year of service), outplacement, retention bonuses for critical talent, recruitment for new roles, relocation, and systems/process changes.
Phased approach with clear milestones:
| Phase | Timeline | Activities | Milestones | |---|---|---|---| | 1. Design Finalization | Weeks 1-4 | Detailed org chart; role definitions; RACI; selection criteria for contested roles | Board/ExCo approval of final design | | 2. Leadership Appointments | Weeks 3-6 | L1 and L2 role selection; announcement preparation; retention offers for critical talent | All leadership roles filled and announced | | 3. Organization Announcement | Week 6-7 | All-hands communication; manager talking points; FAQ document; HR support desk activated | Announcement completed; feedback channels open | | 4. Detailed Slotting | Weeks 7-12 | L3+ role assignments; team composition; 1:1 conversations with every affected employee | All employees know their role, manager, and team | | 5. Operational Cutover | Weeks 10-16 | Systems updated (HRIS, org chart, access); processes transitioned; governance activated | New structure operational in systems and processes | | 6. Stabilization | Weeks 12-26 | Monitor for issues; adjust spans/roles as needed; pulse surveys; coaching for new managers | Stabilization metrics green; pulse survey scores acceptable |
| Change Type | Typical Impact Level | Key Change Actions | |---|---|---| | Layer removal (delayering) | High — affected managers lose role or status | Early engagement with affected managers; redeployment support; outplacement; survivor engagement | | Function consolidation (shared services) | Medium-High — roles relocate or are eliminated | Clear service-level agreements; location strategy; reskilling; knowledge transfer plan | | Matrix introduction | Medium — new dual reporting creates confusion | Matrix operating norms document; escalation protocols; training on "working in a matrix" | | Divisional split | Medium — teams separate; shared resources divide | Fair allocation of shared resources; clean data/system separation; new identity building | | Merger integration | Very High — role duplication; cultural clash | Selection process design; cultural integration plan; quick wins to build shared identity | | Geographic reorganization | High — physical moves; timezone challenges | Relocation packages; remote work policy; timezone overlap requirements |
| Audience | Message | Channel | Timing | Owner | |---|---|---|---|---| | Board / ExCo | Strategic rationale; options considered; recommendation; financial impact | Board memo + presentation | Before any other audience | CEO / CHRO | | Senior Leaders (L1-L2) | Design rationale; their specific role; expectations of them as change agents | 1:1 meetings | Day 1 of announcement wave | CEO / CHRO | | Middle Managers | What is changing; impact on their team; talking points for their reports; support available | Town hall + manager toolkit | Day 1-2 of announcement | CHRO / Transformation Lead | | All Employees | What is changing and why; what stays the same; timeline; how to get answers | All-hands (live or video) + written FAQ | Day 2-3 of announcement | CEO | | External (customers, partners) | Relevant changes to their contacts or service model only | Account manager briefing + letter | After internal announcement | CCO / Head of Partnerships | | Union / Works Council (if applicable) | Full plan per legal requirements; consultation period | Formal consultation process | Per legal requirement (often before announcement) | CHRO / Legal |
## Organizational Design: [Organization / Business Unit Name]
**Date**: [Date] | **Headcount**: [N] FTEs | **Revenue**: $[X]M
### Executive Summary
[Organization] requires a structural redesign to support its strategy of [strategy summary].
The current structure has [X] layers, an average span of control of [X], and exhibits
[key pain points]. We evaluated [N] structural options and recommend [Option Name], which
[key changes]. This will result in a net headcount change of [+/- X] FTEs, annual savings
of $[X]M, and one-time restructuring costs of $[X]M. Implementation will take [X] months.
### Current State Diagnostic
**Spans of Control**
| Level | Current Avg Span | Benchmark | Gap | Assessment |
|---|---|---|---|---|
| Executive | X | X-X | [Narrow/On target/Wide] | [Commentary] |
| Senior Manager | X | X-X | [Narrow/On target/Wide] | [Commentary] |
| Mid-Manager | X | X-X | [Narrow/On target/Wide] | [Commentary] |
| Frontline Manager | X | X-X | [Narrow/On target/Wide] | [Commentary] |
**Layers Analysis**
- Current layers (CEO to frontline): [X]
- Benchmark for organization of this size: [X-X]
- Assessment: [Over-layered / Appropriate / Under-layered]
**Decision Rights Issues**
| Decision | Current Issue | Impact |
|---|---|---|
| [Decision] | [Issue] | [Business impact] |
### Design Principles
| # | Principle | Strategic Link | Structural Implication |
|---|---|---|---|
| 1 | [Principle] | [Strategy element] | [What it means for the design] |
| 2 | [Principle] | [Strategy element] | [What it means for the design] |
| 3 | [Principle] | [Strategy element] | [What it means for the design] |
| 4 | [Principle] | [Strategy element] | [What it means for the design] |
### Structural Options
| Attribute | Option A: [Name] | Option B: [Name] | Option C: [Name] |
|---|---|---|---|
| Archetype | | | |
| Layers | | | |
| Avg span of control | | | |
| Headcount impact | | | |
| Annual cost impact | | | |
| Implementation time | | | |
| Complexity | | | |
| Alignment to principles | | | |
| Primary risk | | | |
### Recommendation: [Option Name]
[Rationale for selection — why this option best supports the strategy and design principles.]
**Org Chart (Top 3 Levels)**
[CEO] ├── [L1 Role A] │ ├── [L2 Role] │ ├── [L2 Role] │ └── [L2 Role] ├── [L1 Role B] │ ├── [L2 Role] │ └── [L2 Role] └── [L1 Role C] ├── [L2 Role] └── [L2 Role]
### RACI Matrix (Key Processes)
| Process | [Role A] | [Role B] | [Role C] | [Role D] |
|---|---|---|---|---|
| [Process 1] | A | R | C | I |
| [Process 2] | C | A | R | I |
### Headcount Impact
| Category | Current | Future | Change | Savings / Cost |
|---|---|---|---|---|
| [Category] | X | X | +/- X | $___M |
| **Total** | **X** | **X** | **+/- X** | **$___M** |
| One-time restructuring cost | | | | $___M |
### Transition Plan
| Phase | Timeline | Key Activities | Milestone |
|---|---|---|---|
| Design Finalization | Weeks 1-4 | [Activities] | [Milestone] |
| Leadership Appointments | Weeks 3-6 | [Activities] | [Milestone] |
| Organization Announcement | Weeks 6-7 | [Activities] | [Milestone] |
| Detailed Slotting | Weeks 7-12 | [Activities] | [Milestone] |
| Operational Cutover | Weeks 10-16 | [Activities] | [Milestone] |
| Stabilization | Weeks 12-26 | [Activities] | [Milestone] |
### Communication Plan
| Audience | Message Theme | Channel | Timing |
|---|---|---|---|
| [Audience] | [Theme] | [Channel] | [When] |
### Change Management Risks
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Key talent attrition during transition | [H/M/L] | [H/M/L] | [Action] |
| Manager resistance to span increases | [H/M/L] | [H/M/L] | [Action] |
| Productivity dip during transition | [H/M/L] | [H/M/L] | [Action] |
Category:business