MGMT90010 Chap.6 Agile and Self-Managing Structures
Agile and Self-Managing Structures
Agile and self-managing designs move selected decisions closer to interdependent work. This chapter explains why shared purpose, meaningful authority, information, governance and review are necessary for agility.
It also examines the HR practices that must change when work no longer fits fixed jobs, one manager and an annual individual cycle, including multi-source feedback, coaching, team outcomes and capability-based careers. Flexible labels alone do not create adaptability. A squad that owns an outcome but lacks access to information or permission to alter the workflow remains dependent on the old hierarchy.
Conversely, autonomy without purpose, escalation or transparent career rules can produce inconsistency and hidden status. The chapter treats agility as a disciplined learning loop and shows how a bounded pilot can preserve reversibility when evidence about the new design remains uncertain.
What this chapter covers
- 01
Team interdependence
- 02
Decision authority near work
- 03
Self-management governance
- 04
Continuous and multi-source feedback
- 05
Team outcomes and capability careers
Worked example · free
Align evaluation with squad work
- 1Show how individual functional targets pull effort away from reciprocal team work.
- 2Add product outcome evidence and multi-source feedback while preserving capability review.
- 1Balance team results with transparent individual contribution.
- 1Monitor delivery, learning, free-riding and popularity bias.
Key terms
- Agile Team
- An agile team is an interdependent group able to adapt roles and decisions around a shared purpose.
- Self-Management
- Self-management distributes selected authority to roles or teams while retaining explicit governance.
- Multi-Source Feedback
- Multi-source feedback draws performance evidence from several people who observe interdependent contribution.
- Role Proliferation
- Role proliferation is the growth of flexible roles until coordination and ownership become unnecessarily complex.
Agile and Self-Managing Structures FAQ
What makes a group an interdependent team?
Members need one another's knowledge, decisions or work to produce the result. A shared label or meeting schedule is not enough if everyone still completes separate tasks independently.
Does self-management remove leadership?
No. Purpose, priorities, coaching, conflict resolution and boundary decisions remain. The design redistributes where leadership activities and authority sit and makes their governance explicit for everyone involved.
Why must HR practices change with agile work?
Fixed individual jobs and annual supervisor ratings may contradict team-based, changing work. Feedback, reward, development and careers should follow interdependence while preserving fair individual evidence and professional standards.
Why should an agile redesign begin with a bounded pilot?
A bounded pilot makes the decision scope, affected team and review date visible before the design spreads. Leaders can test whether faster decisions improve delivery without allowing coordination costs, workload or role ambiguity to become an organisation-wide commitment.
How can self-managing teams avoid hidden status systems?
Publish how roles are allocated, how contribution is reviewed and how pay or career decisions are made. Transparent criteria do not remove disagreement, but they prevent informal influence and popularity from silently replacing the hierarchy that the redesign claimed to remove.
Which decisions should remain outside an agile team?
Keep decisions central when enterprise risk, legal obligations, scarce expertise or shared platforms require consistency. The team can still own local workflow choices, provided the boundary and escalation route are explicit enough to support both speed and system reliability.
How should an agile team review its own design?
Examine delivery outcomes alongside decision delays, coordination effort, workload and employee voice. The review should identify whether the authority boundary helped learning or merely transferred unresolved dependencies into the team.
Exam move
Use the agility loop to test purpose, composition, authority, information, review and reconfiguration. Diagnose cases where responsibility moves but permission does not. Practise redesigning feedback and reward for interdependent work without removing individual accountability. Add identity, status and career consequences to the analysis, then recommend a bounded experiment with expansion, modification and stop conditions.
Compare a real team with a group of people who merely report under one label. Write the interdependence explicitly: whose knowledge or decision is needed by whom, and at what point in the work? Next, list the decisions the team can make without approval and the constraints that remain enterprise-wide. This makes ceremonial agility easy to spot.
Build an HR-fit table covering feedback source, reward unit, career home, learning, selection and conflict resolution. For each item, explain why the work requires the change. Practise one case where tighter governance is the correct answer because risk or role proliferation has become excessive.
Close every pilot recommendation with the scope, evidence, review date and outcome that would justify expansion, modification or termination. That structure demonstrates learning without assuming that every flexible design should spread.
Working through Agile and Self-Managing Structures in MGMT90010? Sia is AskSia’s AI Management tutor — ask any MGMT90010 Agile and Self-Managing Structures question and get a clear, step-by-step explanation grounded in how MGMT90010 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
