Before You Launch Another Transformation: A Diagnostic Checklist for Leadership Teams

Five readiness questions to ask before committing resources to a new initiative

• The Question That Rarely Gets Asked
• Why Readiness Matters More Than Design
• The Five Diagnostic Questions
• Question 1: Does This Initiative Depend on People Articulating Things They Currently Do Not Say?
• Question 2: Does This Initiative Require Ideas to Stabilise Into Shared Form?
• Question 3: Is the Receiving Environment Configured to Absorb What This Initiative Will Produce?
• Question 4: Do the People Whose Behaviour Needs to Change Have a Rational Incentive to Change It?
• Question 5: Is There an Orchestration Function Maintaining the Conditions Across Stages?
• What to Do With the Answers
• Conclusion
• References

The Question That Rarely Gets Asked

Most transformation initiatives begin the same way. A leadership team identifies a strategic challenge: new technology, changing markets, operational pressure, regulatory shift, competitive threat. A programme is designed. Budget is allocated. Communication is planned. Workshops are scheduled. The initiative launches.

And in a significant percentage of cases — the number varies by industry but is consistently high — the initiative produces activity without producing the intended change.

The explanation usually given is execution risk. The strategy was correct, but something went wrong during implementation. The Bridgium research, based on 28 in-depth interviews with innovation leaders across Nordic and European enterprises, suggests a different explanation. In most cases, the failure of a transformation initiative is not an execution failure. It is a readiness failure — a structural condition that existed before the initiative launched and that the initiative did not address.

The question that rarely gets asked, but that determines the outcome more than almost any design decision, is this: can the existing organisational flow absorb what this initiative will produce?

Why Readiness Matters More Than Design

In the Bridgium research, the organisations that consistently moved transformation initiatives successfully were not the ones with the most sophisticated programme designs. They were the ones whose underlying Innovation Flow — the structural capacity to move new ideas and practices through articulation, stabilisation, and adoption — was functioning well enough to absorb what the initiative produced.

“Before launching another initiative, diagnose where movement actually breaks.”
— Bridgium Research Framework

This is the core diagnostic principle. It is not a call to avoid transformation. It is a call to understand the existing conditions before committing resources, so that the initiative is either adjusted to work with the current architecture or accompanied by the structural interventions needed to make absorption possible.

The Five Diagnostic Questions

The Bridgium framework suggests that most readiness failures can be anticipated by asking five questions before the initiative launches. Each question corresponds to a specific condition in the Innovation Flow that determines whether new initiatives can actually move through the organisation.

These questions are not designed to produce a pass/fail verdict. They are designed to make specific risks visible, so that the leadership team can decide what to do about them before the initiative is committed.

Question 1: Does This Initiative Depend on People Articulating Things They Currently Do Not Say?

Most transformation initiatives assume a level of open dialogue that does not necessarily exist. They assume that when problems arise, people will raise them. When opportunities appear, people will surface them. When the initiative encounters friction, that friction will be visible to leadership.

The Bridgium research shows that in most large enterprises, articulation is structurally constrained. People observe problems they do not voice, because the architecture does not make voicing rational. If the new initiative depends on that articulation suddenly happening — without any change to the conditions that have kept it silent — the initiative is importing a Stage 1 risk that the framework calls the Silence Tax.

The readiness question is specific: what exactly needs to be articulated for this initiative to work, who needs to articulate it, and does the current architecture make that articulation possible?

Question 2: Does This Initiative Require Ideas to Stabilise Into Shared Form?

Transformation rarely succeeds through a single decision. It requires collective sensemaking — the process through which abstract intentions become shared understanding, and shared understanding becomes concrete action. In the Bridgium framework, this is Stage 2: Objectivation.

The risk at this stage is fragmentation. Ideas are discussed but never stabilise into shared concepts that others can carry. Workshops produce enthusiasm that evaporates before the next meeting. Slide decks circulate without producing alignment. The initiative appears to be moving, but the movement is surface-level.

The readiness question here is about protected space. Does the initiative have room for ideas to develop before they are measured? Are there follow-up loops that allow sensemaking to continue across meetings? Is there an Innovation Memory system — a shared artefact, document, or pipeline — where the evolving understanding can accumulate?

Question 3: Is the Receiving Environment Configured to Absorb What This Initiative Will Produce?

This is the most commonly skipped readiness question, and the one that accounts for the largest share of transformation failures. It is the question about Stage 3: Internalization, and the Adoption Gap.

Every transformation initiative produces something: new processes, new tools, new practices, new decisions. Those outputs then need to be absorbed into an operational environment that was designed for different practices. If the receiving environment has not been reconfigured — if KPIs still reward the old behaviour, if ownership has not been explicitly transferred, if frontline teams were not involved in development — the new practice arrives as an external imposition on a routine that already works.

The rational response of the receiving environment is not resistance. It is passive non-integration: formally acknowledging the change, practically continuing as before, until the change quietly disappears.

Question 4: Do the People Whose Behaviour Needs to Change Have a Rational Incentive to Change It?

This is a question about alignment between the initiative and the performance system. The Bridgium research references Steven Kerr’s foundational 1975 analysis, “On the Folly of Rewarding A, While Hoping for B,” which documented the systematic disconnect between what organisations claim to value and what their reward systems actually reinforce.

Most transformation initiatives implicitly assume that the behaviours they require will be adopted because they are important. But in a large enterprise, behaviour is not driven by importance — it is driven by the performance system. If the initiative asks people to do something that is not recognised, measured, or rewarded by the system that determines their standing in the organisation, adoption is structurally unlikely.

The readiness question is about incentive architecture. What specific behaviours does this initiative require? Are those behaviours visible in any performance metric? If the answer is that the initiative expects people to voluntarily adopt uncompensated work, the initiative is fighting the incentive architecture — and the incentive architecture usually wins.

Question 5: Is There an Orchestration Function Maintaining the Conditions Across Stages?

Orchestration is the coordinating capacity that guides ideas across departmental and stage boundaries. In the Bridgium framework, it is the function that keeps legitimacy, predictability, and connectivity aligned throughout the flow. When orchestration is absent, initiatives move well within functional silos but stall at the interfaces between them.

The readiness question is whether someone — explicitly, with authority and resources — is responsible for orchestration across the full arc of the initiative. Not the sponsor, who champions the work. Not the project manager, who coordinates within scope. Not the innovation director, who leads a function. Someone whose specific role is to maintain the transitions.

What to Do With the Answers

These five questions are unlikely to produce uniformly positive answers. Most leadership teams, applying them honestly to a specific initiative, will find that one or two conditions are clearly in place, two or three are partially in place, and at least one is structurally absent.

This is not a reason to abandon the initiative. It is information about what needs to accompany the initiative for it to succeed. Three practical responses are available:

1. Adjust the initiative. If the diagnostic reveals that a specific stage is structurally weak, the initiative can be redesigned to work with that constraint rather than against it. For example, if Stage 1 articulation is constrained, the initiative can include structured listening mechanisms that do not depend on spontaneous voicing.
2. Strengthen the architecture first. In some cases, the readiness gap is large enough that launching the initiative would produce predictable failure. The productive response is to invest first in the structural conditions — building protected sensemaking space, defining handover protocols, clarifying orchestration — before committing resources to the initiative itself.
3. Proceed with open eyes. In some cases, strategic urgency makes delay impossible, and the leadership team decides to proceed despite the diagnostic findings. The value of having done the diagnostic is that the team now knows where the risks are concentrated and can monitor those specific transitions.

Conclusion

Most transformation failures are not design failures. They are readiness failures — structural conditions that existed before the initiative launched and that the initiative did not address. The Bridgium Innovation Flow framework provides a diagnostic lens for making those conditions visible: five questions that translate the research findings into a practical readiness check for leadership teams.

The point is not to discourage transformation. It is to make transformation more likely to succeed by ensuring that the existing flow can absorb what the initiative will produce — or by surfacing, in advance, the structural interventions that need to accompany it.

For leadership teams that want to work through this diagnostic systematically, the Bridgium Innovation Flow Checklist is available here: bridgium-research.eu/innovation-checklist-2026/. The full research report provides the underlying framework: bridgium-research.eu/innovation-report-2026/.

For organisations that want to go beyond self-assessment and map the specific conditions of their own Innovation Flow — the transitions, the bottlenecks, the structural gaps — the Bridgium team runs structured Innovation Flow Diagnostic sessions with leadership teams.

References

1. Berger, P.L. & Luckmann, T., The Social Construction of Reality, Doubleday (1966)
2. Kerr, S., “On the Folly of Rewarding A, While Hoping for B,” Academy of Management Journal (1975)
3. Kotter, J.P., Leading Change, Harvard Business School Press (1996)
4. Cohen, W.M. & Levinthal, D.A., “Absorptive Capacity: A New Perspective on Learning and Innovation,” Administrative Science Quarterly (1990)
5. Burt, R.S., Structural Holes: The Social Structure of Competition, Harvard University Press (1992)
6. Amabile, T.M., Creativity in Context, Westview Press (1996)
7. Weick, K.E., Sensemaking in Organizations, Sage Publications (1995)
8. Schein, E.H., Organizational Culture and Leadership (4th ed.), Jossey-Bass (2010)
9. Beer, M. & Nohria, N., “Cracking the Code of Change,” Harvard Business Review (2000)