Basics of Organisation Design — Structures & Culture
Executive Readiness Lens
Structure is the operating system of the firm. It determines who decides what, who talks to whom, and where information flows fast or gets stuck. Culture determines what people do when the chart does not tell them what to do. Good leaders do not treat structure and culture as soft backdrop; they treat them as design variables that shape execution speed, accountability, and learning.
Canonical Grounding
- Chandler: structure follows strategy.
- Schein: culture has visible artefacts, stated values, and hidden assumptions.
- Bernstein & Nohria: the informal network often determines who actually gets things done.
- Design principle: a structure should make the right decision easy and the wrong decision costly.
Working Heuristic
Use this five-point stack when designing or diagnosing organisational structure:
- Fit to strategy. Confirm the structure matches the strategy phase.
- Owner clarity. Give each important process one accountable owner.
- Role simplicity. Make decision rights easy to state.
- Map the informal. Identify who people actually call for help and influence.
- Culture signals. Look at promotions, firings, and crisis response to infer the real culture.
When to use this framework
- Before restructuring, team redesign, or function integration.
- When strategy changes and execution quality declines.
- When cross-functional handoffs produce repeated errors or delays.
Key leadership principle
If you want to change how work gets done, change who decides what — not just who reports to whom.
Corporate Reality Check
Run this reality check before designing a new structure or diagnosing why execution quality is declining. Most failures are design failures first, people failures second.
Common failure patterns:
- Structure designed around current leaders rather than strategy.
- Matrix structures created without a primary reporting line.
- Culture defined in values statements but not reinforced in promotions or crisis response.
Failure signals:
- Cross-functional decisions are repeatedly delayed or escalated.
- High performers complain about unclear decision rights.
- Formal org chart and informal influence map diverge on key decisions.
What to do instead: map both the formal structure and the informal influence network before redesigning.
Case Lens
Spotify is a useful example of a structure designed for product speed. Squads own features end to end, tribes coordinate related squads, and chapters preserve functional excellence. The broader lesson is not the labels; it is the logic. Structure should fit the decision flow the strategy requires.
Lesson: structure creates operating advantage when it is deliberately designed for the strategy.
Full Case Walkthrough
Click here to read full case study
1. Case Context
Spotify competes in a category where experimentation, deployment speed, and engineering quality matter. Traditional functional structures would have slowed decisions and created bottlenecks.
2. Decision Trigger
Three conditions forced the redesign: coordination bottlenecks, scaling information flow problems, and the need to combine speed with functional depth.
3. Timeline (Simplified)
| Phase | What Happened | Management Relevance |
|---|---|---|
| Startup phase | Small flat team with informal coordination | Fast decisions but not scalable |
| Growth challenge | More headcount created coordination bottlenecks | Traditional functional structure was insufficient |
| Squad model design | Squads, tribes, chapters, and guilds introduced | Speed and quality were designed together |
| Scale phase | Model adapted through thousands of employees | Structure evolved while preserving core logic |
4. Options Considered (Managerial Framing)
Three options were considered: a functional hierarchy, a pure product organisation, or a hybrid model. The hybrid approach preserved speed and functional depth while reducing decision gridlock.
5. Execution Moves
The key moves were clear accountability through squads, coordination through tribes, functional development through chapters, and informal learning through guilds.
6. Outcomes and Evidence
What improved: decision speed and engineering velocity remained strong at scale. What remained challenging: transferability to more hierarchical or compliance-heavy environments.
7. What to Transfer to Managerial Practice
What to copy:
- Make the primary unit of accountability explicit and give it end-to-end ownership.
- Separate decision-making structures from knowledge-sharing structures.
- Map informal coordination before redesigning the formal structure.
What to adapt:
- The squad/tribe/chapter model is most appropriate for product and technology contexts.
- Spans of control and autonomy should reflect team maturity and decision risk.
What to avoid:
- Copying the labels without the governance logic.
- Implementing a matrix without a primary reporting line and escalation path.
8. What We Know vs What Is Inferred
| Category | Statement Type |
|---|---|
| What we know (documented) | Spotify publicly described the squad/tribe/chapter/guild model in engineering culture materials. |
| What is inferred (managerial synthesis) | Transferability depends on trust, autonomy, and psychological safety. |
9. Discussion Questions
- Where do your formal and informal structures diverge most?
- Which cross-functional process fails most often in your organisation?
- Where do Schein’s three culture levels conflict in your team?
- What governance decisions are needed before introducing a matrix?
- How would a squad model look in a non-tech business?
Monday Morning Playbook
30-minute prep
- Map one cross-functional process that is currently underperforming.
- Review the last three significant decisions made in your team.
- Identify one informal leader with influence outside their title.
60-minute structure and culture review
- Review cross-functional handoff failures and trace them to a structural root cause.
- Check whether the last three promotions reinforced the desired culture.
- Identify one accountability gap and assign it.
- Name one structure element that should be changed or removed.
7-day follow-through
- Draw the real org chart for one key process and share it with the owner.
- Redesign ownership and decision rights for one failed cross-functional process.
- Use Schein’s three-level audit in a leadership conversation.
Role-Based Activation
- People Manager: formalise decision rights that are currently implicit.
- Functional Leader: assign one owner to one cross-functional process.
- BU Leader: compare espoused culture with what promotions actually reward.
- Strategy/Founder Office: map the informal network before restructuring.
KPI and Evidence Block
Track leading, lagging, and risk indicators in one evidence view.
| Metric Type | Suggested Metric | Review Cadence |
|---|---|---|
| Leading | % cross-functional processes with a single named owner and defined review cadence | Weekly |
| Leading | Decision latency for the top 5 operating decisions | Weekly |
| Lagging | Employee clarity score on decision rights and role expectations | Quarterly |
| Lagging | Cross-functional handoff failure rate | Monthly |
| Risk | Number of processes with no accountable owner | Monthly |
Tools Pack
Tool 1: Formal vs Informal Org Map
Map both networks for key decisions before any structural redesign.
| Key Decision | Formal Authority (who should decide) | Informal Reality (who actually decides) | Gap Implication | Action |
|---|---|---|---|---|
| Decision 1 | ||||
| Decision 2 | ||||
| Decision 3 | ||||
| Decision 4 | ||||
| Decision 5 |
Tool 2: Schein Culture Audit
Diagnose all three levels before any culture-change initiative.
Level 1 — Artefacts (visible): What does the office, onboarding, dress code, and meeting format signal about what is valued?
Answer: _______________
Level 2 — Espoused Values (stated): What does the website, values poster, and leadership communication say the organisation values?
Answer: _______________
Level 3 — Basic Assumptions (actual): What does promotion history, crisis response, and informal conversation reveal about what is actually rewarded?
Answer: _______________
Gap Analysis: Where do levels 1, 2, and 3 conflict, and what behaviour does that conflict produce?
Practice MCQs
Chandler's thesis 'structure follows strategy' implies that:
- A. Strategy should be designed to fit the existing structure
- B. Organisational structure should be redesigned when strategy changes
- C. Structure and strategy are independent
- D. Culture determines strategy
Which organisation structure is most prone to decision gridlock?
- A. Functional
- B. Flat
- C. Matrix
- D. Divisional
Edgar Schein's deepest level of organisational culture — the hardest to change — is:
- A. Artifacts (office layout, symbols)
- B. Espoused values (mission statements)
- C. Basic underlying assumptions (unconscious beliefs)
- D. HR policies
A firm with multiple product lines serving different customer segments with different needs should typically adopt:
- A. A functional structure
- B. A divisional structure organised by product or customer
- C. A flat structure
- D. No formal structure
'Culture eats strategy for breakfast' means:
- A. Culture is irrelevant to strategy
- B. Even a well-designed strategy will fail if the culture does not support its execution
- C. Breakfast meetings improve culture
- D. Strategy should be designed by the culture team
What is the 'span of control' in organisational design?
- A. The number of projects a manager controls
- B. The number of direct reports a manager has
- C. The geographic spread of a firm’s operations
- D. The number of layers in a hierarchy
Which of the following is the fastest lever to change organisational culture?
- A. Revising the company values statement
- B. Changing who gets promoted (the behaviour culture actually rewards)
- C. Redesigning the office layout
- D. Hosting culture workshops
Spotify's 'Squad' model is an example of which structural innovation?
- A. Traditional functional structure
- B. Divisional structure by geography
- C. Network/agile structure with cross-functional autonomous teams
- D. Pure hierarchical structure
Informal organisational networks are important because:
- A. They replace formal structure entirely
- B. Critical information and influence flow through informal networks, often faster and more accurately than formal channels
- C. They are only relevant in small organisations
- D. They exist only in dysfunctional organisations
A 'flat' organisational structure is best suited to:
- A. Safety-critical operations requiring close supervision (nuclear plants, hospitals)
- B. Fast-moving, innovative environments requiring quick local decisions
- C. Large conglomerates with many product lines
- D. Heavily regulated industries
Flashcards
Click the card to flip
Continue Learning
References
- Chandler, A. D. (1962). Strategy and structure. MIT Press.
- Schein, E. H. (2010). Organizational culture and leadership (4th ed.). Jossey-Bass.
- Spotify Engineering. (2014). Spotify engineering culture. https://engineering.atspotify.com/2014/03/spotify-engineering-culture-part-1/
- Tuckman, B. W. (1965). Developmental sequence in small groups. Psychological Bulletin, 63(6), 384-399. https://doi.org/10.1037/h0022100
If you want to change how work gets done, change who decides what — not just who reports to whom.