Treat a change that requires new behavior, not just new tools as a repeatable performance situation: prepare a cue, run the attempt, capture evidence and change one variable next time. 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.
Design one experiment
Do not try to fix every part of a change that requires new behavior, not just new tools at once. Change only identify the few behaviors that must change. Keep the rest of the situation as normal as practical.
Write the prediction
Predict what should change: perhaps time to resolve implementation blockers improves or feedback arriving but not changing the plan appears later. A prediction forces you to be specific about what the tool is supposed to do.
Run the attempt
Use “We will know adoption is happening when…” as the cue. If the attempt becomes difficult, use separate what is decided from what is still open instead of adding several new techniques.
Compare prediction with outcome
If the outcome differs, do not call the experiment a failure automatically. Ask whether the tool was used, whether the constraint changed, and whether communicating only the benefits interfered.
Choose the next experiment
Keep the tool if it improves time to resolve implementation blockers without harming quality of stakeholder understanding. Otherwise change one variable: timing, wording, difficulty or environment.
| Attempt | Prediction | Behavior | Observed result | Next test |
|---|---|---|---|---|
| 1 | feedback arriving but not changing the plan | identify the few behaviors that must change | time to resolve implementation blockers | Change one variable |
| 2 | change fatigue expressed as cynicism | separate what is decided from what is still open | quality of stakeholder understanding | Keep what helped |
| 3 | What became predictable? | Repeat the reliable move | number of unresolved local workarounds | Increase difficulty only if stable |
Use the next attempt as data
Treat the next instance of a change that requires new behavior, not just new tools as an experiment rather than a verdict on your ability. Predict what will happen if you use separate what is decided from what is still open, then test it. If change fatigue expressed as cynicism appears, note when it appeared and whether create feedback loops from implementation changed the sequence.
Change one variable
After the attempt, compare the prediction with adoption of target behaviors and time to resolve implementation blockers. If the result was weaker than expected, change timing, wording, difficulty or environment—but only one at a time. This creates information you can use instead of a cycle of trying many things and learning little.
Review one trade-off explicitly
Most professional situations contain a trade-off: speed versus accuracy, candor versus harmony, autonomy versus control, short-term relief versus long-term learning, or detail versus clarity. Name the trade-off before acting. Afterward, ask whether the balance you chose still makes sense. This creates a more useful review than asking only whether the situation felt comfortable or whether everybody was pleased. Applied to a change that requires new behavior, not just new tools, 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 another person makes the situation harder?
Keep the boundary between influence and control clear. You can use separate what is decided from what is still open, 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 number of unresolved local workarounds, not a perfect first performance.
What is the earliest sign I should watch for in a change that requires new behavior, not just new tools?
Use an observable signal rather than a mood label. For this article, start with feedback arriving but not changing the plan. It appears early enough to support a different choice.