Building agile ecosystems where business and technology work as one for a fast flow of ideas and value.
A framework-agnostic, scalable approach for digital product development and beyond.
Org Topologies™
Learn from the Creators
Why Org Topologies™?
Some say: "Agile is dead!" Is it? Or has it been downgraded to mean team-level agility?
Today’s solutions create tomorrow’s problems. By focusing on team-level agility, organizations have created the need for scaling. Scaling is a problem. It is not a solution. It is a self-inflicted issue caused by a lack of system thinking.
Others say: "Business agility is the new path!" But is there "another agility"? Hasn't agility always been for the benefit of everyone: developers, customers, and managers? For the whole business? The fact that we need something like business agility is a symptom of failure.
At Org Topologies™, we don’t believe that agile is dead or that business agility is the new focus.
We believe there is a need to revive the agile revolution: Ride the second wave! We shall focus on both in-team and inter-team collaboration, independence of the individual teams, and interdependence of them working together.
We need to embrace value-creating ecosystems by looking from the outside in, organizing around value, and creating strong cohesion with teams of teams.
Org Topologies™ is a thinking tool that makes it easier to see where your organization is on the transformation journey. And from there, discuss where you want to be.
This helps organizations discover, own and monitor their journey toward perfection without relying on "agile" frameworks.
Expert Product and Agile Coach at Sixt
"It was so much easier to describe the FlixBus agile journey using Org Topologies™, which otherwise would need much more explanation and reasoning. Mapping product depth and team skills dimensions bridges the gap between applying frameworks and discovering ways to organize teams. Thank you for the elegant system to visualize organizational growth."
Org. development I Executive coaching
"Last fall I was introduced to the very interesting work by Alexey Krivitsky and Roland Flemm. They have aggregated their enormous base of experiences into a reality-oriented thinking tool. It can help us all create a common language and share a mental map... I tested their very early version on the management in a mid-sized fintech in Europe last fall (approx 15 teams). It was so inspiring to see how it immediately increased the quality of the conversations and their own reasoning on what they were optimizing for."
So, what is Org Topologies™?
Agile transformation is a highly contextual journey. We believe one essential meta objective of every business is to stay resilient for as long as possible in the face of competition and market landscape changes.
This means applying an org design that maximizes innovation and adaptivity to keep discovering constantly changing market demands. And also simultaneously keep delivering the value that is known to be needed.
Structurally, this requires investing in improvements along two essential axes of org development:
-
Invest in engineering autonomy – by deepening cross-functionality to deliver value fast.
-
Invest in shared product ownership – by broadening understanding of the problem space.
Org Topologies™ enables change agents to choose an org design that allows them to grow their organization along these two axes and embrace holistic product development with high adaptivity, innovation, and resilience.
Organizations that maximize org development at both axes create strong inter-team cohesion.
If this approach sounds more like the Agile Fluency ® Model approach, you might want to learn more about the similarities and differences between the two.
Growing Engineering Autonomy
For many organizations we know, "agile transformation" means creating "agile teams". This is indeed a step in the right direction. However, it is impossible to get to a higher state of adaptivity by relying on individualistic work.
Jelled groups of people organized in teams are better at adapting to changing environments than individuals. Teams absorb the complexity of uncertainty, acquire new skills, and discover and deliver at the same time.
Organizational improvements along this dimension increase the capabilities of teams to work across the entire technology stack, delivering results faster and in a constant flow. This dimension is closely related to what Scrum people call the "Definition of Done" and the DevOps call techniques of "Continuous Delivery".
Mastering this dimension allows teams to work on customer problems end-to-end. "End-to-end" means that teams don't have blocking dependencies between each other - i.e. no queues, no waiting, no hand-offs, no victimization or unclarity of responsibility. Lean production requires multi-trained individuals in cross-functional teams to improve delivery and learning. We see organizations tend to focus most on this dimension: Creating better teams.
Yet, from our experience of years of consulting, focusing only on improving the performance of individual teams is not enough. When each team focuses on a specific aspect of a product (such as a certain feature or a product capability, e.g. the product catalogue search) the joint result of all the teams will unlikely provide a seamless and joyful customer experience (e.g. finding and buying a product at minimal clicks). The product might look like a Frankenstein to its customers, lacking holistic design.
Growing Product-Centric Alignment
As we mentioned above, improving performance of individual teams is not enough to provide good customer experience. And also, when teams are driven by narrow focus and local interests, this creates a fragmented and conflicting view of reality, jeopardizing the organization's general ability to foresee upcoming changes and adapt at the customer level.
So organizations also need to focus on a second dimension we call "Value Consolidation". It means how broadly and holistically do teams, departments and the entire organization understand the value they deliver to their customers.
Value consolidation implies enabling teams to work together with broader focus and wider responsibilities. Not only cross-functionally, but also product-wide thinking of integrated user journeys and holistic customer experiences.
In practice, such organizations have fewer backlogs, fewer roles, and less bureaucracy. There are fewer steering wheels to be turned when the organization needs to adjust its course. This is a better fit for adaptivity.
High Adaptivity as a Target
Organizational transformation is not a project with a fixed end date. It is an ongoing learning effort to get closer to the ideal state, making incremental changes over time.
And what is this ideal state worth pursuing?
We believe it is an organizational ability (of all the employees, teams and departments) to re-focus and keep doing what's most important and most valuable at any given moment. This is a state of high organizational adaptivity. And your organization can get better at it, continuously improving its fit for adaptivity .
We discovered that both dimensions need to be developed and matched on the journey of making your organization more adaptive.
What Is Org Topologies™ Good For?
Org Topologies is an org design mapping technique that helps you:
-
Assess the current org design of your product development organization.
-
Define your target operating model.
-
Determine your roadmap towards organizational perfection – higher adaptivity, innovation, and resilience.
Such a DIY approach increases shared understanding and ownership of the organizational transformation.
To simplify the assessment and determination of the target state and the path, the Org Topologies™ map consists of recognizable org archetypes, among which are these essential seven organizational archetypes. They are positioned on the map in relation to their structure along both axes and proximity to the perfection vision of high adaptability.
Download a PDF
