1.2 Scene Setting: External and Internal Factors Shaping Change
Key Takeaways
- External factors include world events, international market conditions, technological trends, industry trends and national culture
- Internal factors include organisational culture, governance structures and style, history of change, change maturity and attitude to risk
- A poor history of change creates cynicism that the next change initiative inherits before it starts
- Change maturity often tracks project and programme maturity and shapes how fast an organisation can absorb change
- Understanding context precedes designing the approach — CM3 puts context first for that reason
The first syllabus area is called Organisational context and approach, and the ordering is deliberate: you understand the context before you design the approach. A technically excellent change plan dropped into a hostile context fails. The same plan in a receptive context looks like genius.
External factors
External factors sit outside the organisation's control and typically create the pressure for change:
- World events — a pandemic, war, or major geopolitical disruption reshapes what organisations must do and how fast
- International market conditions — currency, supply chain, demand shifts, interest rates
- Technological trends — automation, artificial intelligence, cloud migration, platform obsolescence
- Industry trends — competitor moves, consolidation, changing customer expectations, new entrants
- National culture, or cultures plural for multinational enterprises, which shapes how change is received in each territory
The change manager's job with external factors is not to control them but to translate them: to turn "the market has moved" into a message that a warehouse supervisor in Frankfurt understands and believes.
Internal factors
Internal factors determine the organisation's capacity to respond, and they are where most change initiatives are won or lost:
| Internal factor | Why it matters | Question to ask |
|---|---|---|
| Organisational culture(s) | Culture can vary across parts of a single large organisation, even domestically | Is this change compatible with how we actually behave? |
| Governance structures and style | Determines how decisions get made and how fast | Who can say yes, and how long does that take? |
| History of change | A poor history creates problems the next change inherits | What happened last time, and what did people learn from it? |
| Change maturity | Often tracks project and programme maturity — slow and methodical, fast and agile, or somewhere between | Have we done change of this size and type before? |
| Attitude to risk | Shapes appetite for experimental, safe-to-fail approaches | Are we allowed to try something and have it not work? |
History of change deserves special attention
If the last three initiatives were announced with fanfare and quietly abandoned, your stakeholders are not resisting your change — they are responding rationally to a pattern. The Study Guide is explicit that a poor history of change can create many problems for the next change. Practically, this means the change manager should surface that history early rather than pretend it away: run a lessons-learned review, name what went wrong last time in your own communications, and demonstrate concretely what is different now. Silence on the subject reads as either ignorance or evasion, and both cost trust.
Change maturity sets your realistic pace
An organisation with high change maturity has established roles, recognised change practices, leaders who know what sponsorship means and staff who have absorbed change before. An immature organisation has none of these, and a change manager who imports a sophisticated approach into it spends the whole initiative explaining the approach rather than delivering the change. Change maturity often goes hand in hand with project and programme maturity, and it tells you whether to plan for slow and methodical delivery, fast and agile delivery, or something between.
Culture varies inside one organisation
A point CM3 makes explicitly and that catches candidates out: culture can vary across various parts of large organisations even when they are not multinational. The trading floor and the compliance function of one bank, sitting in one building, can hold genuinely different values about risk, speed and hierarchy. A single change approach applied uniformly across both will land very differently in each. Segmenting by culture, not just by department or geography, is part of good context scanning.
Turning context into decisions
Context scanning is only useful if it changes what you do. In practice a context scan should produce answers to three questions:
- How much change can this organisation absorb right now? Change saturation is real. If four initiatives are already competing for the same people, the honest answer may be that yours needs to wait or shrink.
- What approach fits? A high-risk-appetite, change-mature organisation can run experimental, emergent change. A risk-averse, immature one needs planned change with visible structure.
- Where are the cultural landmines? Which parts of this change contradict a deeply held assumption about how we work here, and does senior leadership know?
That third question is the one change managers most often skip and most often regret. If there is a fundamental incompatibility between the proposed change and the underlying culture, it can be extremely hard to make the change successful, and that assessment needs to reach senior leadership early — while the approach can still be adjusted.
Which of the following is an internal factor rather than an external factor in the organisational context of change?
A change manager discovers that the proposed change fundamentally contradicts a deeply held assumption in the organisation's culture. What does CM3 advise?