Deep Battle Cards A–G
A — Change vs Transition
Definition: change is the external new state; transition is the psychological process of coming to terms with it.
Purpose: prevent launch dates from being treated as completed human transition.
Users: change leaders, managers, Change Agents, affected stakeholders.
Inputs: new role/system/process plus perceptions, losses and prior experience.
Outputs: state change vs Ending/Neutral Zone/New Beginning experience.
When: choose Bridges when loss, ambiguity or becoming comfortable with the new state is decisive.
Nearest confusion: rollout phases can sound similar, but Bridges is about people.
Scenario pair: system went live yesterday → change; staff grieve roles and mix old/new practices → transition.
Deciding clue: state/event vs psychological journey.
Changed fact: if the stem asks which transformation step leaders should execute, Kotter may become more relevant.
Trap: every implementation phase is not a Bridges phase.
Memory: New state outside; transition inside.
Source: 542–545.
B — Urgency vs Anxiety
Definition: urgency is focused motivation to leave status quo; anxiety/fear can cause overload, defensiveness and retreat.
Purpose: create movement without chaotic resistance.
Inputs: dissatisfaction evidence, triggers, communication and competing demands.
Outputs: focused case for action vs alarm/firefighting.
When: urgency is required in Kotter; anxiety is what urgency can become when mishandled.
Scenario pair: coherent regulatory case → urgency; five conflicting emergencies → anxiety.
Deciding clue: focused mobilization vs fear-driven overload.
Changed fact: consolidate competing initiatives under one coherent priority and anxiety may become productive urgency.
Trap: more fear ≠ more urgency.
Memory: Urgency moves; anxiety freezes or scatters.
Source: 545–546, 550–553.
C — Sponsor vs Guiding Coalition
Definition: sponsor = one influential backer; coalition = powerful cross-org team with position power, expertise, credibility and leadership.
Purpose: separate executive support from system-wide guiding capacity.
Inputs: authority, stakeholder map, expertise, trust, leadership.
Outputs: champion support vs broad guiding capacity.
When: coalition is needed when change crosses functions and behavior systems.
Scenario pair: CFO secures funding → sponsor; CFO + BU leaders + SMEs guide transformation → coalition.
Deciding clue: one champion vs system-influencing team.
Changed fact: if the only problem is lack of one influential executive to protect/fund the effort, sponsor becomes more direct.
Trap: more attendees ≠ coalition.
Memory: Champion backs; coalition guides.
Source: 546, 553–557.
D — Guiding Coalition vs Steering Committee
Definition: coalition is a transformation-leadership team; steering committee is a decision/oversight forum that may be narrower.
Purpose: do not treat any committee as the change engine.
Inputs: influence/trust/common goal vs scope/budget/issues/decisions.
Outputs: transformation influence vs oversight decisions.
When: a steering group can function like a coalition only if composition/behavior actually satisfy coalition needs.
Scenario pair: monthly budget/risk forum → steering; respected cross-functional leaders modeling change → coalition.
Deciding clue: what it does, not what it is called.
Changed fact: broaden the steering group and make it actively lead behavior change with power/expertise/credibility/leadership, and it can become the coalition.
Trap: committee label ≠ coalition quality.
Memory: Oversight forum vs change engine.
Source: 553–557, 569–571.
E — Leadership vs Management
Definition: leadership creates vision/strategy and mobilizes movement; management provides planning, budgeting and control.
Purpose: balance both disciplines in major change.
Outputs: direction/movement vs order/coordination.
Scenario pair: mobilize around future state → leadership; build schedule/budget/control → management.
Deciding clue: change direction vs execution control.
Changed fact: when the stem shifts to controlling delivery against plan, management becomes primary.
Trap: neither is universally superior.
Memory: Lead change; manage complexity.
Source: 553–560.
F — Vision vs Plan/Charter
Definition: vision is a compelling statement of where change is leading; plan/charter is execution detail.
Purpose: keep meaning/motivation separate from work breakdown.
Inputs: current problem + desired future vs tasks/milestones/owners/budget.
Outputs: compelling direction vs execution roadmap.
Scenario pair: trusted timely reporting → vision; deploy System X by Q1 → plan/goal.
Deciding clue: where/why vs what/when/how.
Changed fact: if vision is agreed and the question asks milestones/resources, plan/strategy becomes relevant.
Trap: specificity does not automatically make something visionary.
Memory: Vision gives meaning; plan gives mechanics.
Source: 546–547, 557–560.
G — Short-Term Win vs Declaring Victory
Definition: win = visible evidence that fuels change; victory = early progress incorrectly treated as completion.
Purpose: use evidence without losing momentum.
Inputs: early results, skepticism and remaining deeper work.
Outputs: momentum/evidence vs premature closure.
When: wins support stages 6–7; cultural anchoring comes later.
Scenario pair: pilot cuts errors → win; leaders disband program because pilot worked → early victory.
Deciding clue: fuel vs finish line.
Changed fact: if practices/culture are genuinely anchored and no longer need special effort, completion becomes more defensible.
Trap: success ≠ automatically done.
Memory: Celebrate, then continue.
Source: 548–550.