Six Performance Circles¶
Definition¶
The Six Performance Circles form the core structure of the Agile Performance Holarchy. Each circle encapsulates a discrete set of behaviors, actions, and outcomes essential to adopting and sustaining agility at scale. They work interdependently rather than sequentially: Leading establishes values and vision; Providing builds enabling infrastructure and partnerships; Envisioning clarifies customer needs and product roadmaps; Crafting executes with discipline and craftsmanship; Affirming measures and observes performance; Teaming grows people and governs the culture.
In the Book¶
Dalton presents the six circles as the primary organizational structure for agile transformation, distinct from linear phase-gate processes. Leading is the largest and most critical circle—agile organizations must be led by agile leaders who demonstrate values, remove impediments, and create vision. Providing ensures infrastructure (tools, training, partnerships, best practices) supports teams without controlling them. Envisioning is the product owner domain—creating vision, roadmaps, backlogs, and clarifying customer needs into stories. Crafting is the execution domain—teams commit to sprints, develop with discipline (TDD, pair programming), deliver incrementally, and reflect on quality. Affirming observes and measures whether agile is actually working through metrics, retrospectives, and Gemba Walks. Teaming develops people through training and mentoring, establishes team agreements, promotes self-organization, and aligns governance with agile values. The book details 18 holons distributed across these six circles, with each holon having adopting, transforming, and mastering outcome levels.
Why It Matters¶
By organizing agile adoption into six interdependent behavioral domains rather than a linear checklist, the model reflects how agile actually works. No single circle operates in isolation; a failure in Leading (unclear values) cascades into Crafting (teams don't know what quality means) and Affirming (metrics don't measure what matters). The circles also distribute responsibility across roles and functions—product owners, engineers, coaches, and leaders each have clear behavioral expectations within their circles. This prevents the common pattern where "agile is the development team's problem" while other functions continue unchanged.