In a new operating model, several legitimate demands compete at once. The useful question is which demand must be protected first and which can wait. The purpose here is helping people orient, decide and act while the situation is moving. Change leadership is the work of helping people understand, test and adopt new behavior while the organization continues operating.
A simple decision tree
If the first signal is multiple initiatives competing for attention: use map stakeholder concerns. If the issue is missing information: use create feedback loops from implementation. If the problem is pressure rather than information: use acknowledge losses as well as benefits. The point is to match the tool to the constraint instead of using the same response every time.
Decision 1: what are you protecting?
Name the outcome in one line. For a new operating model, ask whether the priority is speed, quality, trust, learning, ownership or another constraint. When two priorities conflict, decide which one wins for this attempt and why.
Decision 2: what will make you pause?
Use feedback arriving but not changing the plan as an early warning. A pause is not inactivity; it is a chance to prevent measuring attendance instead of adoption. The pause can be one breath, one written note or one clarifying question.
Decision 3: when do you switch plans?
Plan B begins when the original approach no longer protects the objective. Switch from map stakeholder concerns to identify the few behaviors that must change if the first tool is no longer producing useful information or if the cost of continuing rises.
Language for the decision point
The concern I am hearing is…
We will know adoption is happening when…
Review the branch you actually used
| Attempt | Decision point | Branch used | Evidence | Next rule |
|---|---|---|---|---|
| 1 | multiple initiatives competing for attention | map stakeholder concerns | number of unresolved local workarounds | Change one variable |
| 2 | feedback arriving but not changing the plan | create feedback loops from implementation | feedback-to-decision cycle time | Keep what helped |
| 3 | What became predictable? | Repeat the reliable move | adoption of target behaviors | Increase difficulty only if stable |
A before–during–after protocol
Before: use create feedback loops from implementation and decide what would count as a satisfactory response. During: watch for feedback arriving but not changing the plan and change fatigue expressed as cynicism; when either appears, use track adoption, not just launch activity and the short cue “We will know adoption is happening when…”. After: capture one piece of evidence about quality of stakeholder understanding and one adjustment for next time. The protocol is deliberately short so it remains usable when a new operating model becomes demanding.
How to keep the protocol honest
Do not judge the attempt only by the final result. A good outcome can hide a poor process, and a difficult outcome can still contain a better decision. Review whether the chosen behavior supported helping people orient, decide and act while the situation is moving. If you notice changing too many behaviors at once, treat that as information about the design of the routine, not as proof that you lack the skill.
Use a smaller unit of improvement
Do not try to improve the whole situation at once. Choose one decision point, one sentence, one handoff, one pause, or one review habit. A small unit is easier to rehearse and easier to measure. Once it is reliable, connect it to the next part of the situation. This is slower than collecting many techniques, but it usually produces clearer learning because you can tell which change affected the result. Applied to a new operating model, keep the review tied to change leadership rather than turning it into a broad judgment about ability. Write one observation from the attempt, one decision you would repeat, and one change for the next comparable situation. If you cannot name those three items, the review is probably still too general. The purpose is to leave the situation with a usable next experiment, not a longer explanation of why it was difficult.
Questions people ask
What if I forget the technique in the moment?
Shorten it. Put map stakeholder concerns into the environment before the event and use one sentence such as “The concern I am hearing is…” rather than trying to remember a full framework.
What if another person makes the situation harder?
Keep the boundary between influence and control clear. You can use create feedback loops from implementation, state the relevant constraint, and decide whether to continue, pause, renegotiate or escalate.
How long should I practice before changing the plan?
Run several comparable attempts unless the approach creates a clear problem. Look for a trend in adoption of target behaviors, not a perfect first performance.