Managing Inertia in Wardley Mapping
Inertia is resistance to change. In Wardley Mapping it usually comes from past success: the capital, relationships, skills, and practices built around how things work today. When a component evolves, for example from Product to Commodity, that investment pushes back. This guide covers the 16 forms of inertia Simon Wardley describes, in four groups, with a counter for each, and shows you how to spot inertia on a map before it stalls a change.
Where Inertia Comes From
Every component on a map evolves through supply and demand competition, from Genesis through Custom-Built and Product (+rental) to Commodity (+utility). Each stage rewards different investments: the hardware you bought, the supplier contracts you negotiated, the skills your people built, and the processes that hold it all together. When the component moves on, those investments become reasons not to move with it. Wardley captures this in the climatic pattern "Success breeds inertia", and two related patterns explain why it matters: "Inertia increases the more successful the past model is" and "Inertia can kill an organisation". Inertia is not stupidity. The people resisting usually have something real to lose, and their objections are often partly true. Treat inertia as something to anticipate and plan for, not as a character flaw.
How to Spot Inertia on a Map
The doctrine "Manage inertia" asks you to use a map to anticipate inertia before you meet it, and to prepare your answers in advance. Mapping with the people affected also lets them discover their own inertia, which is more persuasive than being told about it. The same steps work on competitors: inertia you can see in a rival is an opportunity.
Map the Landscape and Its Movement
Start from user needs, map the value chain, and position each component by how evolved it is. Then mark where components are heading. Pay most attention to those about to cross from Product to Commodity, where change tends to be fast.
Find the Investment
For each component that is moving, ask what the organisation has invested in its current form: assets, contracts, skills, processes, reputations, and revenue. Wherever the investment is large, expect resistance.
Draw the Barrier
Mark inertia on the map as a bar across the component's path of evolution. Note which of the 16 forms below you expect, and who holds it.
Prepare the Counter
Choose the tactic and the argument for each form before you start the change, not after the first meeting goes badly.
Disruption of Past Norms
The first group covers what the organisation already has and stands to lose: relationships, assets, influence, and protection from competitors. Each form below is followed by Wardley's tactic for countering it and the argument that goes with it.
Change of Business Relationship
People have spent years building relationships with current suppliers and partners, and the change puts that social capital at risk. Counter with vendor management: the current arrangement was right for its time, but the market has moved on. Point to other departments that have already changed, and invite people to lead the change rather than follow it.
Loss of Existing Financial or Physical Capital
Money has gone into assets such as data centres, licences, or equipment that the change will make redundant. Counter with future planning: plan the write-down, consider running the asset down before you dispose of it or sell it on, and compare the cost of change with the rising running costs of the legacy.
Loss of Political Capital
The people who championed the current way of working may read the change as a verdict that they got it wrong. Counter with modernisation: present the change as building for the future, focus on future agility and efficiency, and make the wider business aware of why it is happening, so nobody's earlier decision is put on trial.
Threats to Barriers to Entry
The organisation relies on high costs or scarce capability to keep competitors out, and the change will lower those barriers. Counter by treating it as unavoidable change: it is already happening in the market, and the barriers will fall whether or not you take part.
Transition to the New
Even when people accept that change is coming, moving to the new way of working costs money, time, and effort. These forms of inertia are about that cost.
Investment in Knowledge Capital
People need to learn new skills, and somebody has to pay for it. Counter with training: hiring the skills from outside will often cost more than developing your own people, and training shows staff that the change includes them.
Cost of Acquiring New Skill Sets
Some of the skills the change needs do not exist in the organisation at all. Counter with organisational development: build the capability in-house through hack days, conferences, and centres of gravity where people with the new skills can gather and teach others.
Investment in New Business Relationships
The new way of working needs new suppliers, and finding and vetting them takes effort. Counter with vendor management: invest early in understanding the market and building relationships with the right suppliers.
Changes to Governance, Management, and Practices
Processes, controls, and management habits were designed for the old way of working. Counter with awareness of co-evolution: practices adapt as activities evolve, as they have before. Point to past examples, such as DevOps emerging as computing infrastructure became a utility.
Agency of the New
The new thing itself attracts objections. Is it ready? Can you depend on it? Who will control it? These forms of inertia are about the change, not about what you already have.
Suitability
A common objection to anything new is "it isn't suitable for us" or "it isn't ready yet". Often that is inertia talking. Counter with weak signals and prior identification: test the claim against evolution by asking how widespread (ubiquitous) the component is becoming and how well understood (certain) it is. If both are rising, it is moving towards Commodity and the objection will not hold for long. Watch for the weak signals that come before that shift, so you can act early rather than be forced to.
Lack of Second Sourcing Options
With only one supplier of the new thing, people fear being locked in. Counter with supply chain management: use and help develop standards, choose open source options where they exist, limit your use of features that only one supplier offers, and put an abstraction layer between you and the supplier.
Lack of Pricing Competition
With few suppliers, people fear being overcharged. Counter with market analysis: find out whether there are one or several vendors, examine what switching would cost, and consider using a broker.
Loss of Strategic Control
Handing a component to an outside provider feels like giving away control of something important. Counter with strategic planning: examine the buyer and supplier relationship in detail, and check whether the market is commoditising. If it is, running the component yourself means competing with providers who operate at far greater volume.
Business Model
The deepest inertia comes from how the organisation makes money, and from the people and markets that reward it for doing so.
Declining Unit Value
As a component evolves, the value of each unit falls, and a business that sold it at a high margin sees its revenue at risk. Counter with awareness of evolution: defending the old margin can become a death spiral as customers move to cheaper options. Look for alternative opportunities instead, such as building an ecosystem on top of the commodity.
Data for Past Success Counteracts
The figures that justified the current model argue against changing it, because they measure what worked before. Counter with portfolio management: treat the change as risk mitigation, run new work as separate bets judged on their own measures, and consider disposing of or spinning off parts of the business.
Resistance from Rewards and Culture
Bonuses, targets, promotion criteria, and culture all reward the existing way of working. Counter through human resources: offer higher rewards for adapting, educate people about why the change is happening, and promote situational awareness so they can see the landscape for themselves.
External Financial Markets Reinforce Existing Models
Investors and analysts value the business on its current model and may punish a change that dents short-term results. Counter with analyst relationships: tell a clear, credible story about where the market is heading and why the change positions you for it. If you are a listed company, do this within your disclosure obligations.
Working with Resistance
The counters above give you arguments. Arguments alone rarely move people who have something to lose, so pair them with ways of working that lower the stakes and build trust.
Start with a Pilot
A small, time-boxed pilot lowers the perceived risk of a large change. It gives sceptics evidence from their own organisation, and it lets you refine the approach before you scale it up.
Listen Before You Argue
Ask people what they stand to lose and which of their concerns are true. Some will be. Fixing those builds more trust than any counter argument, and the conversation tells you which forms of inertia you are really facing.
Work Through Respected Colleagues
Find the people whose opinion others trust, involve them early, and let them make the case to their peers. A change explained by a respected colleague is easier to accept than one announced from the top.
Map the Change Together
Build the map with the people affected rather than presenting them with a finished one. When people see for themselves that their component is about to evolve, the argument becomes theirs rather than yours.
Match Methods to Evolution
A common response to inertia is to roll out one method everywhere, such as Agile across the whole organisation. That swaps one form of inertia for another. Wardley's doctrine "Use appropriate methods" and the climatic pattern "No single method fits all" both make the same point: components at different stages of evolution need different approaches.
Genesis and Custom-Built
You are still discovering what is needed, and the requirements will change. Agile methods suit this work because they are built for learning and change.
Product (+rental)
The component is better understood, and the aim is to improve it and remove waste. Lean methods suit this stage.
Commodity (+utility)
The component is well defined, and the aim is to remove variation and run it efficiently. Six Sigma suits this stage, as does buying it as a utility rather than building it.
Related
Sources
- Adapted from Simon Wardley, A pet favourite - Inertia, licensed under CC BY-SA 3.0.
- Adapted from Simon Wardley, Wardley Maps, licensed under CC BY-SA 4.0.
Material adapted from these sources is shared under CC BY-SA 4.0.