Organisation Design: Structuring Teams for Growth and Clarity

Organisation design is the process of defining roles, reporting structures, and team architecture to support strategic objectives. Done well, it provides clarity and scalability. Done poorly, it creates confusion, conflict, and bottlenecks.

Why Organisation Design Matters

Without Clear Design:

• Role ambiguity and overlap
• Unclear accountability
• Reporting confusion
• Decision-making bottlenecks
• Cultural friction

With Good Design:

• Clear roles and accountability
• Efficient decision-making
• Scalable structures
• Reduced conflict
• Better execution

When to Engage Organisation Design

Key Inflection Points:

1. Pre-fundraising (Series A, B, C) – Investors expect clear structures
2. Rapid scaling (e.g. 30 → 100 people in 12 months)
3. Adding C-suite roles (CFO, COO, CTO)
4. Role conflict or ambiguity causing friction
5. Restructuring after acquisitions or strategic pivots

Core Principles of Good Organisation Design

1. Strategy First, Structure Second

Organisation design should support your strategy, not dictate it.

Questions to ask:

• What are our strategic objectives for the next 12-24 months?
• What capabilities do we need to achieve them?
• What structure best supports these objectives?

2. Clear Accountability

Every outcome should have one clear owner.

Avoid: Joint accountability or ambiguous ownership
Prefer: Single-threaded leadership with defined decision rights

3. Simple Reporting Lines

Minimise matrix reporting and dual accountability. Complex structures slow decision-making and create confusion.

Prefer:

• Clear, direct reporting lines
• Minimal layers (ideally 3-5 from CEO to front line)

4. Balanced Spans of Control

Too narrow: (e.g. 2-3 direct reports) → Micromanagement, bureaucracy
Too wide: (e.g. 15+ direct reports) → Lack of support, overwhelm

Sweet spot: 5-8 direct reports for most leadership roles

5. Scalable Design

Design for where you'll be in 12-18 months, not where you are today.

Common Organisation Design Models

1. Functional Structure

Structure: Teams organised by function (Engineering, Product, Sales, Marketing, Finance, etc.)

Best for:

• Small to mid-size companies (< 150 people)
• Single product or service line
• Efficiency and functional depth

Pros:

• Clear functional ownership
• Deep expertise in each function
• Efficient resource use

Cons:

• Can create silos
• Cross-functional coordination required

2. Product-Led Structure

Structure: Teams organised around products or product lines

Best for:

• Multi-product companies
• Product-focused organisations
• Scaling product development

Pros:

• Product ownership and accountability
• Fast decision-making within product teams
• Customer-centric

Cons:

• Duplication of functions across products
• Coordination complexity

3. Matrix Structure

Structure: Dual reporting (e.g. functional + product or regional)

Best for:

• Large, complex organisations
• Multi-regional or multi-product companies

Pros:

• Flexible resource allocation
• Balances functional depth with product/regional focus

Cons:

• Complex and slow decision-making
• Ambiguous accountability
• High coordination overhead

Recommendation: Avoid matrix structures in growth-stage companies (< 300 people). Stick to functional or product-led models.

4. Hybrid Structure

Structure: Functional at the top, product-led within Engineering/Product

Best for:

• Mid-stage companies (100-300 people)
• Multi-product with shared functions (Finance, Legal, People)

Example:

• Functional: CFO, General Counsel, VP People, VP Sales, VP Marketing
• Product-led: Engineering and Product organised into product squads

Defining Roles and Reporting Lines

Step 1: Map Current State

Document:

• Current roles and titles
• Reporting lines
• Accountabilities and responsibilities
• Gaps, overlaps, and ambiguities

Step 2: Define Future State

Design:

• Desired roles and structure
• Clear reporting lines
• Defined accountabilities
• Decision rights (who decides what?)

Step 3: Identify Gaps

Where do you need new roles or leadership?

Step 4: Communicate and Implement

Roll out the new structure with:

• Clear communication to all staff
• 1-on-1s with those whose roles change
• Documentation (org chart, role profiles)

Case Study: Restructuring at Series B

Company: Series B SaaS, 70 people, scaling to 150

Problem:

• Engineering and Product both reported to CEO (bottleneck)
• Finance, Ops, and People all managed by one "Head of Finance & Ops" (stretched thin)
• Sales and Marketing led by founder (founder stretched, no specialist leadership)

Solution:

New C-suite:

• CEO
• CTO (owns Engineering)
• CPO (owns Product)
• CFO (owns Finance)
• COO (owns Operations, People, Legal)
• VP Sales
• VP Marketing

Reporting structure:

• CTO, CPO, CFO, COO, VP Sales, VP Marketing → CEO
• Engineering teams → CTO
• Product teams → CPO
• Finance, Ops, People → CFO/COO (split responsibilities)

Outcome:

• Reduced CEO bottleneck
• Clear functional ownership
• Scalable to 150+ people

Common Pitfalls

1. Over-Engineering Too Early

Don't create enterprise-style structures at 30 people. Scale gradually.

2. Under-Designing Too Late

Waiting until role confusion causes attrition is costly. Design proactively.

3. Copying Competitors

Your org design should reflect your strategy and culture, not mimic others.

4. Ignoring Cultural Fit

Structure must align with your culture. Hierarchical structures won't work in flat, collaborative cultures.

Practical Tips

1. Involve Leadership in Design

Don't design in isolation. Engage C-suite and functional leads.

2. Test and Iterate

Org design is never "done." Review and refine every 6-12 months.

3. Communicate Clearly

Ambiguity creates anxiety. Over-communicate the new structure, roles, and rationale.

4. Document Everything

Publish org chart, role profiles, and decision rights. Make them accessible.

Conclusion

Organisation design provides clarity, accountability, and scalability. As you grow, invest time in defining roles, reporting lines, and team structures that support your strategy and culture. The effort pays dividends in execution speed, decision quality, and team morale.