Org Topologies™ and Doing Better Scrum

Last month, I did something a bit unusual.  Instead of being the instructor, I was a student and attended an Org Topologies™ Practitioner course.  The things I learned there resonated with me because they helped me answer this question, “Why do so many organizations struggle to #DoBetterScrum?” 

When done well, Scrum (and other Agile processes) will create change.  But many Scrum and Agile adoptions are short-lived or superficial.  They do not touch upon the other elements of organizational design - strategy, structure, rewards and people.  IME, if you do not adjust these other elements of the system, the organizational design will reject the new processes because they are inconsistent with how the business truly operates.  For me, the Org Topologies course gave me a light that I can shine onto an organizational design to discover if it is fit for purpose.

How Is Success Defined with Org Topologies?

In their model, Krivitsky and Flemm place the highest performing units in a location they call “C3 [WHOLE-3]”.   When a small business is operating as a start-up, it would be considered a C3 [WHOLE-3] unit.  A C3 [WHOLE-3] unit has the following characteristics:

• It is a cross-functional team that can deliver a complete slice of value to its customers quickly and efficiently, with a minimal amount of waste.
• The team has direct interaction with customers and is adaptive to a changing business environment.
• As a result of its direct interaction with both customers and the competitive landscape, the team will learn whatever is needed in order to generate a win for both the customer and the business.

As the business scales, the various responsibilities that were contained within the initial C3 [WHOLE-3] unit, the start-up, are now divided across multiple units that map to lower archetypes, such as Y0 [TASKS-1], Y3 [TASKS-3], A0 [CAPS-1] or A1 [CAPS-1].  Unfortunately, the lower archetype work units lack self-sufficiency, so they need coordinating units from the higher archetypes to deliver end-to-end value to the customer.  By definition, the entire organization must be C3 [WHOLE-3], or it would fail as a business. 

How Does Org Topologies Help You #DoBetterScrum?

There are a couple of reasons why I think this mental model will be helpful for teams and organizations who want to do better Scrum.

1. Evolutionary: with its scales of zero to three and Y to C, practitioners and other leaders can chart their growth along multiple horizons based upon the destination they desire.
2. Diagnostic: it helps practitioners and other leaders identify where they are today, where they can expect to encounter resistance, from whom, and offers some reasons why they might be resisting change.
3. Holistic: to achieve higher levels of performance, practitioners and business leaders must look beyond the adoption of new (Agile) processes and consider additional elevating practices that impact strategy, structure, rewards and people.

What I like about this model is that its creators are (mostly) neutral on what is the final destination.  While both have a preference to help organizations to grow in the direction of C3 [WHOLE-3], one of their main motivations was to publish a model that gave practitioners a clear and specific language when talking about organizational design.

For instance, if a business completes an Org Topologies mapping and discovers its current organizational design enables it to achieve its strategic objectives, then nothing needs to be changed.  However, if the mapping reveals the organizational design is not fit for purpose, there are a number of elevating structures they could adopt to shift right, or up, in the Org Topologies map.