Organisational Structures and Design

TL;DR

Organisational structure defines how work is divided, grouped, and coordinated. Good design helps achieve goals by improving efficiency and communication. Your choice of structure impacts everything from decision-making to employee morale.

1. The Mental Model

Think of an organisation's structure as its skeleton. Just like your skeleton supports your body, an organisational structure supports its activities. A well-designed skeleton helps you move efficiently; a poorly designed one leads to awkwardness and pain.

2. The Core Material

Organisational structure is essentially how tasks are formally divided, grouped, and coordinated. Organisational design is the process of choosing and implementing this structure. It's about making deliberate choices to align the structure with your organisation's strategy and environment.

Key Elements of Organisational Structure

Photo by Jan van der Wolf on Pexels

When you design an organisation, you're making decisions about these six key elements:

1. Work Specialisation: How much are tasks divided into separate jobs? High specialisation means people become experts in narrow tasks (e.g., assembly line). Low specialisation means people do a wider range of tasks.
2. Departmentalisation: How are jobs grouped together? Common ways include by function (e.g., marketing, finance), product (e.g., laptops, smartphones), geography (e.g., North America, Europe), or customer (e.g., retail clients, corporate clients).
3. Chain of Command: Who reports to whom? This clarifies authority and reporting lines. It used to be very strict but is less emphasised in many modern organisations.
4. Span of Control: How many subordinates can a manager effectively direct? A narrow span means more managers and closer supervision. A wide span means fewer managers and more autonomy for employees.
5. Centralisation and Decentralisation: Where does decision-making authority lie? In centralised organisations, top management makes most decisions. In decentralised ones, lower-level managers and employees have more input.
6. Formalisation: How much are jobs standardised, and how many rules and procedures guide employee behaviour? Highly formalised organisations have explicit job descriptions and lots of policies.

Common Organisational Structures

Photo by DS stories on Pexels

Different structures suit different purposes. Here are a few common ones:

• Simple Structure: Low departmentalisation, wide spans of control, centralised authority, little formalisation. Often found in small businesses where the owner manages everything. It's fast and flexible but can be risky as it depends heavily on one person.
• Bureaucracy (or Functional Structure): High specialisation, formal rules and regulations, tasks grouped by function, centralised authority, narrow spans of control, and a clear chain of command. Efficient for standardised tasks but can be slow and rigid.
• Divisional Structure (or Multi-Divisional Structure): Groups activities by product, service, customer, or geography. Each division often operates as a relatively autonomous unit with its own functional departments. Good for large organisations with diverse offerings or markets.
• Matrix Structure: Combines functional and product/project departmentalisation. Employees have two managers: a functional manager and a product/project manager. It can improve coordination and communication but can also create confusion and power struggles.
• Team Structure: The entire organisation is made up of work teams that perform the organisation's tasks. Breaks down departmental barriers and decentralises decision-making.

Here's how some of these structures compare:

graph TD
    A["Simple Structure"] --> B["Owner/Manager makes all decisions"]
    B --> C["Few rules, fast decisions"]

    D["Functional Structure"] --> E["Departments by specialisation (e.g., Marketing, HR)"]
    E --> F["Clear reporting, efficient within functions"]

    G["Divisional Structure"] --> H["Divisions by product/region/customer"]
    H --> I["Each division acts like a mini-company"]

    J["Matrix Structure"] --> K["Employees report to functional & project managers"]
    K --> L["Combines functional efficiency with project flexibility"]

Organisational Design Considerations

Photo by Jakub Zerdzicki on Pexels

When you're designing or redesigning a structure, consider:

• Strategy: Does your structure support your goals? (e.g., innovation often needs a flexible, decentralised structure).
• Size: As organisations grow, they tend to become more complex and formalised.
• Technology: Routine technology often suits a more mechanistic (formal, centralised) structure. Non-routine technology often suits an organic (flexible, decentralised) structure.
• Environment: Stable environments can tolerate more rigid structures. Dynamic, uncertain environments require more organic, adaptable structures.

3. Worked Example

Imagine you're the CEO of "EcoBikes," a small startup that designs and sells custom electric bicycles. You have 15 employees. Currently, everyone reports directly to you, and you handle most of the decision-making. This is a simple structure.

However, EcoBikes is growing fast. You're starting to feel overwhelmed, and decisions are slowing down because everything needs your approval. You've also noticed that the sales team isn't communicating effectively with the design team, leading to some misunderstandings about customer needs.

You decide to redesign the structure. You think:

1. Departmentalisation: Group people by their main function.
2. Span of Control: Create a few managers to oversee smaller teams.
3. Centralisation: Decentralise some decisions to these new managers.

Your new structure might look like this:

• You (CEO)
  • Head of Design & Engineering (manages 4 designers/engineers)
  • Head of Sales & Marketing (manages 5 sales/marketing specialists)
  • Head of Operations & Customer Service (manages 4 assembly/customer service staff)
  • One administrative assistant still reports directly to you.

This moves you towards a functional structure. Now, the Head of Sales & Marketing can make daily sales decisions without your direct input, and the Head of Design can manage project timelines for the design team. This offloads work from you, clarifies reporting, and hopefully improves communication within functions. It's a more scalable structure for your growing company.

4. Key Takeaways

• Organisational structure is about how tasks are divided, grouped, and coordinated.
• Key elements include work specialisation, departmentalisation, chain of command, span of control, centralisation, and formalisation.
• Different structures (simple, functional, divisional, matrix, team) suit different organisational needs.
• Match your structure to your strategy, size, technology, and environment for optimal performance.
• A well-designed structure improves efficiency, communication, and decision-making.
• Organisational design is an ongoing process, not a one-time event.

Common Mistakes to Avoid

Photo by KATRIN BOLOVTSOVA on Pexels

• Sticking to a structure that no longer fits: As an organisation grows or its environment changes, its structure needs to evolve.
• Ignoring informal structures: People often create their own ways of working; formal structure should support, not stifle, this.
• Too much formalisation too soon: Over-formalising a small, agile team can kill innovation and flexibility.
• Copying another company's structure directly: What works for one organisation might not work for yours due to unique circumstances.

5. Now Try It

Think about a team or small organisation you're currently a part of (e.g., a club, a project team, a small business you know).

1. Identify its current structure: How is work divided? Who reports to whom? Where are decisions made? Is it more centralised or decentralised?
2. Propose one change: Based on what you've learned, suggest one specific change to its structure that you believe would improve its efficiency, communication, or ability to achieve its goals. For example, "Decentralise decision-making for X tasks to Y people."

What success looks like: You can clearly describe the existing structure and articulate a logical reason why your proposed change would be beneficial, linking it back to one or two of the core elements of organisational design.