MGMT90227 Chap.3 Organisation Design Choices
Organisation Design Choices
Organisation design aligns roles, relationships and procedures with objectives. This chapter compares management-centric, employee-centric and crowd-centric families while stressing that hybrids are common and no form is universally best.
It explains agile multidisciplinary teams, customer involvement, transparency, iteration and retrospectives, then uses changing critical work to show why a structure that fits one strategy can become a constraint when the venture enters a new product or market. The contingency view rejects a universal best structure.
A design is useful when it fits the organisation's strategy, critical tasks, people, technology, culture and stage. Management-centric forms rely on leader-designed hierarchy and include functional, divisional and matrix arrangements. Employee-centric forms distribute more authority through roles and teams, while crowd-centric forms allow fluid participation around a shared purpose, often through a platform.
Real organisations mix these logics because one dependency may require common standards while another requires rapid local choice. Functional structures concentrate expertise and support development, but can slow work that crosses specialties. Divisions create end-to-end accountability around a product, market or geography, while risking duplication and fragmentation.
A matrix recognises two legitimate dimensions at once, but members may face priority conflict and unclear authority. Flat or self-managed designs can move decisions closer to knowledge, yet depend on capable people, transparent information and visible accountability. Comparison should therefore focus on mechanisms and costs rather than treating an organisation chart as a complete answer.
Agile design combines a structure, way of working and planning approach. Multidisciplinary teams share purpose and end-to-end accountability, involve customers, work iteratively and learn through feedback. Retrospectives make bottlenecks and assumptions discussable after a sprint or phase. This design still needs boundaries, standards and access to scarce expertise.
A team cannot be responsive if every material decision remains outside it, and rapid cycles create little value when customer evidence does not change priorities. Changing strategy can make yesterday's fit become today's constraint. A software venture entering hardware faces fixed specifications, longer planning, specialist supply work and early investment that may conflict with project choice and informal influence.
AI can also redistribute tasks, information and decisions, raising questions about explainability, trust and accountability. Diagnose the new critical work first, compare credible forms, specify decision rights and interfaces, then propose a pilot with evidence. The best answer names what the design improves and the coordination cost it deliberately accepts.
What this chapter covers
- 01
Structure and strategic objectives
- 02
Management-centric organisations
- 03
Employee-centric organisations
- 04
Crowd-centric organisations
- 05
Agile multidisciplinary teams
- 06
Retrospectives and customer feedback
- 07
AI authority and accountability
Worked example · free
Redesign around a new product dependency
- 6Identify how the new critical work differs from software experimentation.
- 6Explain the mismatch between informal project choice and fixed interdependent commitments.
- 6Compare a specialist unit, hybrid or external partnership.
- 7Recommend governance and review evidence suited to the new work.
Key terms
- Organisation design
- The pattern of roles, relationships and procedures aligned with objectives.
- Contingency view
- The claim that design effectiveness depends on fit with organisational context.
- Agile team
- A multidisciplinary team with shared purpose, customer involvement and end-to-end accountability.
- Retrospective
- A participatory review used to learn from a sprint or project phase.
Organisation Design Choices FAQ
Which organisation form is best?
There is no universal winner. A design should fit the venture's strategy, critical work, people, culture, technology and stage. The right exam move is to compare relevant forms and explain the coordination benefits, autonomy and costs each creates in the case.
What makes work agile?
Agile work combines multidisciplinary teams, shared purpose, end-to-end accountability, customer involvement, transparency, iteration and continuous learning. A short cycle alone is not enough if authority remains elsewhere or the team cannot act on feedback.
Can AI flatten an organisation?
AI may help allocate work, monitor information or coordinate across silos, potentially reducing some bottlenecks. It also creates questions about authority, explainability, accountability, data quality and employee trust. Analyse task fit and governance instead of assuming that technology automatically improves design.
Exam move
Build a comparison table for the three broad organisation families and attach one benefit, cost and fit condition to each. Then practise using a design matrix: identify the critical work, test current structure against it, compare alternatives and recommend explicit decision rights. Finish by stating the new coordination cost your choice introduces.
Redesign one venture after a product, market or technology change and mark every dependency that crosses the main structure. Decide whether a functional community, product team, boundary role or shared platform should carry each link. For AI-enabled work, add authority, explanation, review and employee-trust questions rather than treating automation as a structure by itself.
Working through Organisation Design Choices in MGMT90227? Sia is AskSia’s AI Management tutor — ask any MGMT90227 Organisation Design Choices question and get a clear, step-by-step explanation grounded in how MGMT90227 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.