Articulating the consequences of inaction is one of the most powerful tools available to change leaders seeking to build awareness and desire for change. When stakeholders understand—in concrete, credible terms—what will happen if the change does not occur or is not adopted, complacency is replaced with a genuine sense of necessity. The question 'What will happen if we don't change?' complements the case for change by grounding it in risk and consequence.
Definition and Distinction
Consequences of inaction refers to the documented, evidence-based description of the organisational and individual outcomes that will occur if the change is not implemented or if adoption is insufficient. This is distinct from: the case for change (which describes why change is desirable); the urgency narrative (which addresses why change must happen now); and risk management (which identifies project delivery risks). Consequences of inaction specifically describes what life will look like for stakeholders if the change does not happen.
Effective consequence statements are specific and evidence-based, not hypothetical or catastrophic. They describe realistic, near-term outcomes that stakeholders can relate to their own experience of the current state.
Why Articulating Consequences of Inaction Matters
Effective change is driven by the perceived gap between the current and future states (Bridges, 2009). Where the current state remains comfortable or familiar, stakeholders require a clear understanding of the alternative to engage. Articulating the consequences of inaction is therefore critical to making the cost of maintaining the status quo both tangible and relevant. This technique is particularly effective for stakeholders in the 'wait and see' category—those who are not actively resistant but who are insufficiently motivated to invest in change. For these individuals, understanding the specific consequences of inaction can shift the cost-benefit calculus in favour of engagement.
Developing and Documenting Consequences of Inaction
Consequences of inaction should be developed by the change manager in collaboration with the project sponsor, subject matter experts, and where possible, representatives from the impacted population. They should be grounded in evidence—current performance data, regulatory requirements, vendor communications, or industry benchmarks—rather than speculation.
Example of a well-articulated consequences statement:
'If we do not migrate to the new system before the vendor support deadline of 31 December 2025: our financial data will be processed on an unsupported platform, exposing us to regulatory sanction under our financial services licence; manual processing errors—which averaged 2.3% last year—will continue to create financial restatement risk; and our finance team will continue to spend an average of 60 hours per month on manual reconciliation tasks, limiting their capacity for higher-value analysis. The cost of continued inaction is estimated at $1.2 million per year in rework, risk management, and opportunity cost.'
Common Pitfalls and How to Avoid Them
Using fear as the primary motivator without a compelling vision of the future state: Consequence-based messaging alone creates anxiety, not commitment. Balance of consequences of inaction with an inspiring description of what the future state will enable.
Overstating consequences to the point of incredibility: If stakeholders perceive the consequences as exaggerated or unfalsifiable, the message will be dismissed. Ensure all consequence statements are grounded in evidence and presented with appropriate qualifications.
Applying the same consequence narrative to all stakeholder groups: Different stakeholder groups face different consequences of inaction. Customise the consequence narrative to reflect the specific impacts on each group.
Not revisiting the consequences narrative as the project progresses: The consequences of inaction may change over time—for example, as a regulatory deadline approaches or as a competitor's advantage becomes more evident. Keep the consequences narrative current and credible.
References
Bridges, W. (2009). Managing Transitions. Da Capo Press. https://wmbridges.com/books/managing-transitions
Kotter, J. P. (1996). Leading Change. Harvard Business Review Press. https://hbr.org/books/kotter
Prosci. (2023). Building the Case for Change. https://www.prosci.com/resources/articles/building-the-case-for-change