The Model Behind It
The Theoretical Framework
Synthesizing Daniel Pink's Motivation Theory with Spiegler's Agile Maturity Model.
The Core Connection
Daniel Pink provides the "Why" (Human Motivation), while Simone Spiegler provides the "How" (Role Distribution). Together, they form a complete picture of high-performance teams: autonomy is not just a feeling, but a set of specific leadership tasks that must be mastered.
1. Daniel Pink: The Foundation of Motivation
Source: "Drive: The Surprising Truth About What Motivates Us"
To achieve FLOW (the state of optimal performance and engagement), knowledge workers need three intrinsic motivators. However, Pink leaves open how exactly these are achieved in a team context.
Autonomy
The desire to direct our own lives. In teams: self-organization and decision-making power.
Mastery
The urge to get better and better at something that matters. In teams: continuous learning and skill growth.
Purpose
The yearning to do what we do in the service of something larger than ourselves.
2. Simone Spiegler et al.: The Mechanism
Source: "Leadership Gap in Agile Teams"
Spiegler answers Pink's open question: "How is Autonomy actually achieved?"
It is not magic. It is the result of the team mastering 9 specific leadership roles that define Self-Organization.
Pink's Autonomy → Spiegler's 9 Roles
To achieve true Autonomy, the team must take ownership of these functions:
Interpersonal Autonomy
- Coach
- Protector
- Moderator
- Disciplinizer
- Networker
Process Autonomy
- Knowledge Enabler
- Method Champion
- Change Agent
- Helicopter
Pink's Mastery
This is the domain of the Makers & Specialists. The developers and designers bring the technical excellence and craft to the table.
Pink's Purpose
This is the domain of the Product Owner. They provide the 'Why', the vision, and the direction that the team works towards.
The Synthesis
"High performance requires a clear separation of concerns:"
- The PO provides Purpose.
- The Makers ensure Mastery.
- The Team ensures Autonomy via the 9 Roles.