MGMT10002 Chap.8 Organisational Structure and Coordination
Organisational Structure and Coordination
Organisational structure divides work and reconnects it through authority, information and coordination. Specialisation can deepen expertise and efficiency while increasing hand-offs. Departmental grouping, hierarchy, span of control, centralisation and formalisation influence how decisions travel and where accountability sits.
Structure should fit strategy, task interdependence, environment, capability and risk.
Functional, divisional, matrix, team and network arrangements solve different coordination problems and create different tensions. Centralisation can protect consistency and scarce expertise; decentralisation can improve local response and learning. Neither works without adequate information, capability, escalation and accountability.
Strong analysis begins with the flow and required decisions rather than choosing a fashionable chart.
What this chapter covers
- 01
Division of labour and the need for integration
- 02
Departmental grouping and organisational boundaries
- 03
Hierarchy, span of control and delegation
- 04
Centralisation, decentralisation and decision rights
- 05
Formalisation, standardisation and discretion
- 06
Functional, divisional, matrix and team forms
- 07
Interdependence and coordination mechanisms
- 08
Networks, hybrid work and structural adaptation
AskSia-authored practice weighting (not an official mark scheme): redesign an overloaded approval hierarchy
- +2Define the coordination need: protect consistent risk boundaries while enabling timely context-sensitive response.
- +2Diagnose centralised decision overload, information distance and added vertical differentiation.
- +2Separate standard cases, local discretion and exceptions requiring escalation.
- +2Provide shared information, capability, thresholds, audit and clear accountability for delegated decisions.
- +2Evaluate consistency, speed, control and the risk that decentralisation transfers unsupported responsibility.
Key terms
- Specialisation
- Concentration of tasks or expertise that can improve depth while increasing dependence and hand-offs.
- Centralisation
- Concentration of decision authority at higher or common organisational levels.
- Formalisation
- Use of written rules, procedures and standards to guide behaviour and reduce variation.
- Span of control
- The number and complexity of direct reporting relationships managed by one role.
- Matrix structure
- An arrangement combining two authority or grouping dimensions, increasing integration and potential role conflict.
- Interdependence
- The degree to which tasks or units rely on one another's inputs, timing, knowledge or outcomes.
Organisational Structure and Coordination FAQ
Is a flatter structure always more agile?
Fewer layers can shorten communication, but wider spans may overload managers and weaken support. Agility depends on decision rights, information, capability and coordination, not layer count alone.
When should decisions be centralised?
Centralisation can fit high-consequence consistency, scarce expertise or system-wide coordination. It becomes costly when local information and speed matter. Hybrid designs often centralise boundaries while decentralising responsive choices.
What is the main matrix problem?
Dual authority can integrate function and product or project knowledge, but it creates priority and accountability ambiguity. Clear escalation, shared goals, conflict capability and resource rules are essential.
How do I diagnose a structural case?
Trace the work and decision flow. Mark hand-offs, information loss, delay, duplicated authority and unresolved interdependence. Then select a structure and coordination mechanism whose benefits address those causes.
How can managers decentralise decisions without losing responsible consistency?
Separate the decisions that require a common boundary from those that benefit from local knowledge. Headquarters can define safety, legal, ethical or brand standards while trained local roles decide ordinary exceptions within explicit thresholds. Delegation must include information, capability, resources and accountability; otherwise it transfers blame rather than authority.
Create a shared record so local decisions produce organisational learning, and specify the condition that triggers escalation. Audit outcomes across sites for recurrence and unequal stakeholder effects rather than demanding identical choices in different contexts. If one location repeatedly exceeds the boundary, investigate workload, interpretation and incentive before automatically recentralising everything.
Central teams should also review whether their standard remains workable. A hybrid design succeeds when local response and system-wide learning reinforce each other. Measure speed, quality and consistency together, because a faster decision can still be irresponsible and a uniform decision can still be poorly fitted. Review the allocation of authority when capability, technology or consequence changes.
What coordination mechanism fits different forms of interdependence?
Pooled work may be coordinated through common standards and resource rules; sequential work needs reliable schedules, specifications and hand-offs; reciprocal work needs richer mutual adjustment and rapid feedback. Complex expert work may require integrator roles, cross-functional teams or shared problem-solving rather than additional hierarchy. Begin with the actual dependency and uncertainty, then choose the mechanism.
Adding meetings to independent work wastes attention, while a static procedure may fail where tasks continually reshape one another. Define the owner, information, cadence and escalation, and evaluate both coordination benefit and burden.
Exam move
Redraw the same fictional organisation as functional, divisional, matrix and team-based forms. For each, state the coordination benefit, new conflict and condition for success. Then map a single customer or service journey through the current structure. Identify where information waits, authority is distant or roles overlap.
Practise separating strategic policy, routine decisions and high-risk exceptions; assign each to an appropriate level with data and escalation. Contrast centralisation with standardisation, because common rules do not always require every decision to travel upward. Add a contingency lens: environment, strategy, task interdependence, capability and risk.
A complete response includes structural design, an integrating mechanism, implementation support and outcome evidence. Use current assessment requirements for any organisation-chart or case format.
Working through Organisational Structure and Coordination in MGMT10002? Sia is AskSia’s AI Management tutor — ask any MGMT10002 Organisational Structure and Coordination question and get a clear, step-by-step explanation grounded in how MGMT10002 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
