Examine How Last Minute Changes Affect a Leadership Team

A leadership team can absorb one late change without much cost. The trouble starts when late changes become a pattern, when plans get rebuilt overnight and people learn to expect the ground to shift under them. As an executive coach, your job is not to tell the leader to stop changing course. Real conditions change, and leaders who never adjust plans are usually the ones ignoring new information. Your job is to help the leader see what a late change actually costs the team, and to build a habit that keeps the cost low even when the decision itself is sound.

Why This Conversation Goes Wrong

Most coaches open this topic the wrong way. They ask the leader to explain why they changed the plan, and the leader gives a perfectly reasonable answer about budget, a client request, or new data. The conversation stalls there because the reasoning was never the problem. The problem is what happened between the decision and the moment the team found out.

Leaders also hear "late change" as a criticism of their judgment, so they get defensive fast. If you frame the conversation around whether the decision was right, you will get a justification, not a behavior you can change. The useful question is different. It asks what information arrived late, who felt the disruption, and how much notice they actually got. That question does not challenge the leader's judgment. It challenges the gap between when the leader knew and when the team knew, and that gap is something a leader can actually fix.

How to Prepare Before You Sit Down With the Leader

Do not walk into this conversation cold. Ask the leader in advance to bring two recent examples of a plan that changed close to the deadline. For each one, you want four pieces of information. First, what the original decision was. Second, what new fact triggered the change. Third, who was affected and had to react. Fourth, how much notice those people received before the change landed on them.

This preparation step matters because it turns a vague complaint, "my team feels whiplashed," into a specific pattern you can examine together. Once you have two real examples, you can ask which part actually created the disruption. Sometimes it is the timing of the decision itself, made later than it needed to be. Sometimes it is the communication route, where the leader tells one person who is supposed to relay it and the message gets lost or delayed. Sometimes there was never a real deadline in the first place, so the decision just happened whenever it happened, and the team had no way to anticipate it. Naming which of these it is changes what the leader practices next.

What to Say When You Walk Through a Reversal

Start with the specific instance, not the general pattern. A coach named Priya sat down with a leader named Marcus after his team spent a weekend reworking a product launch sequence. She asked, "What did Friday's change actually require from your team?" Marcus said, "They rebuilt the whole agenda overnight and had to tell their own teams by Saturday morning." Priya asked, "Walk me back further. When did you actually know the sequence had to change?" Marcus paused and said, "Wednesday, honestly. I was still waiting on the budget number before I wanted to say anything."

Priya asked, "What would have helped your team prepare, even without the final answer?" Marcus thought about it and said, "I could have told them Wednesday that a change was likely, named Friday noon as the point I'd know for sure, and flagged that the budget input was still open." Priya asked him to practice saying that out loud, as if Monday's meeting were happening right now. Marcus said, "I changed the launch sequence after the budget review came back late. I know the short notice created a weekend of rework, and that's on me. Going forward, when a decision is still open, I'll tell you the date I expect to close it, what input I'm still waiting on, and who to check with if that date slips."

Notice what that practiced statement does. It names the change without over explaining the reasoning. It acknowledges the cost to the team in plain terms instead of defending the decision. And it commits to a specific behavior, not a general promise to communicate better.

Mistakes to Avoid

Coaches and leaders both trip on a few things here. The first mistake is treating every late change as evidence of poor planning. Some changes are genuinely unavoidable, and a leader who apologizes for every one starts to sound like they have no judgment of their own. The second mistake is stopping at the apology. "Sorry for the short notice" without a stated change in behavior teaches the team nothing about what to expect next time.

The third mistake is putting the fix entirely on communication style. A leader can get warmer and more personable in how they deliver news and still deliver it too late to matter. The real fix usually lives earlier, in when the decision gets made and when a tentative signal goes out, not in how the final announcement is worded. The fourth mistake is skipping the follow up. A single good conversation about one reversal does not change a habit. The leader needs a way to track this over more than one cycle, and you need a way to check it with them.

Practice the Conversation and Score It

This is exactly the kind of conversation that benefits from rehearsal before it happens for real, which is the idea behind DealSpeak. You can run the leader through a practice exchange with an AI counterpart playing a frustrated team member, then score how the leader handled it. Did they name the decision plainly. Did they acknowledge the cost without over explaining. Did they commit to a specific, checkable behavior instead of a vague promise. Those three questions work as a simple scorecard you can reuse after every practice run.

Outside of rehearsal, ask the leader to keep a decision log for two weeks. For each significant decision, they record the date they expected to decide, the date they actually decided, what new information caused any gap, who was affected, and when those people were told. Review one entry together in your next session. Ask which signal, if shared earlier, would have let the team start preparing sooner, and ask what the leader will change in the next cycle. If the leader manages a chief of staff or project lead, that person can help track the log, but the leader stays accountable for the actual communication. A related pattern worth checking is whether the leader is genuinely asking the team for input on these signals or just narrating decisions out loud. If that sounds familiar, our post on how to Help a Leader Stop Answering Their Own Questions covers a closely related habit. If you are also coaching someone through a pilot program and need the team to agree on what evidence counts as success, Agree on Evaluation Evidence Before a Learning Pilot Begins walks through a similar structured conversation.

Where This Leaves You

Late changes are not the real problem, and you do too your coaching no favors by pretending they can be eliminated. The real problem is the gap between what a leader knows and when the team learns it, and that gap is trainable. Practice the specific language for naming a change, owning its cost, and committing to a decision date, and you give the leader something to use the very next time conditions shift. For more scenarios like this one, browse our HR and Leadership practice conversations.