profile

The Weekly Gist

How to Lead When the Plan Changes


Helping you learn practical, straightforward methods to boost your soft skills and enhance your career as a software engineer.


Weekly Newsletter

March 17th, 2026

How to Lead When the Plan Changes

I'm writing this from an airport after a blizzard disrupted my travel plans.

My original flight was delayed and eventually rebooked onto an option that would have put me at my destination roughly 30 hours later than planned. I still have a meeting to get to.

At this point, the situation required a quick reset. The itinerary has changed, but the goal has not. The work becomes figuring out the best path forward.

This means staying calm enough to think clearly, communicate with the people who were expecting me, and work through the available options.

This is the same kind of moment teams run into all the time.

A hotfix appears in the middle of planned work. A deadline moves because priorities shift. A dependency falls through. Another part of the business raises the urgency of something that suddenly matters more.

The specifics differ, but the pattern remains the same. The plan changes, and the team has to decide how it will move forward.

Start by Resetting the Situation

When the plan changes, the first challenge is not solving the problem. It's resetting how you think about the situation.

The original plan is usually what people stay attached to. They try to force it to work or spend time wishing it hadn't changed.

That reaction is understandable, but it rarely helps the team move forward.

In my case, I started to figure out how I could make my connecting flight in Chicago, desperately trying to find an alternative flight.

At some point, the focus has to shift from the plan to the outcome. In my case, the itinerary stopped being the thing to optimize. The meeting was.

Once that shift happens, the work becomes clearer. You start asking better questions.

  • What options do we have from here?
  • What constraints actually matter?
  • What tradeoffs are acceptable?

Teams run into the same moment all the time. The work stops being about preserving the original plan and starts becoming about finding the best path forward.

How to Refocus Your Efforts

When plans shift, the situation usually becomes uncomfortable for a team. Work that was planned suddenly has to move. Priorities get reshuffled. People feel pressure to respond quickly.

What matters in those moments is not avoiding the disruption. It is how the team responds once the change is clear.

Strong teams tend to focus on a few practical behaviors.

1. Communicate early

The first step is making sure everyone understands what changed.

When issues show up, the instinct is often to wait until you have the full answer before saying anything. In practice, that usually slows things down. Teams make better decisions when they have the right information early.

Research supports this. Project management data shows communication breakdowns are a major contributor to failed projects and missed goals.

Communication also needs to match the situation. Sometimes that means a quick message to let people know something changed. Other times, it means bringing the right people together to talk through the options.

Communicating with clarity and context helps teams move forward faster. It's the same idea I wrote about in The Hidden Communication Skill That Will 10x Your Impact, where adjusting how you communicate based on the situation keeps teams aligned when things get uncertain.

2. Re-anchor on the outcome

When the original plan changes, teams can lose time trying to preserve it.

A better approach is to pause and ask a simpler question: what outcome are we still trying to achieve?

The answer often clarifies the next move. The hotfix may need a smaller scope. The deadline may require a tradeoff. A feature can be postponed so the team can focus on the issue that matters most right now.

When the team focuses on the outcome rather than the original plan, it becomes easier to work through those decisions.

This becomes even more important when you consider how many interconnected systems teams operate within. I wrote more about this in Understanding All the Systems You Work With. The more systems and dependencies involved, the more likely it is that something outside your control will change your plan.

3. Work the path forward together

Once the situation is clear and the goal is understood, the next step is working through the available options.

That might involve identifying what work can move forward immediately, deciding which tradeoffs make sense, clarifying ownership, and aligning the team on the updated direction.

Teams that do this well treat problem-solving as a shared responsibility rather than something that sits on one person's shoulders.

You see the same pattern in operational disciplines like Site Reliability Engineering. During incidents, teams are encouraged to declare issues early and organize a clear response so work can continue while information is still coming in.

Those small behaviors add up. Consistently communicating clearly, helping others move forward, and working through challenges together builds trust over time.

That's the same idea behind How to Win in the Margins. Small, consistent actions are what build credibility.

Where can AI save you time?

My friends at Big Creek Growth put together a quick survey to spot the repetitive work you can hand off to automation.

How to Lead your Team

When plans change, the work often becomes less structured. People are trying to understand what happened, what it means for the work, and what to do next. Those moments create a gap between the problem and the path forward.

Leaders tend to step into that gap.

Sometimes that means communicating what is known and what is still unclear. Sometimes it means helping the team refocus on the outcome rather than the original plan. Other times, it is simply helping people think through the options so the group can decide on the next move.

None of those actions requires a title. They require awareness, judgment, and a willingness to help the team work through the situation.

Over time, those patterns shape how others see you. The person who helps the team stay steady, communicate clearly, and move forward becomes someone people naturally look to when the next challenge shows up.


Problems rarely show up at a convenient time.

They interrupt the plan, create pressure, and force teams to adjust faster than they would like. That part is normal. It is part of working in complex environments with changing priorities, dependencies, and real business pressure.

The teams that handle these moments well usually do the same few things. They communicate early. They stay focused on the outcome. They talk through the path forward. They keep moving.

That is true whether you are sitting in an airport trying to make it to a meeting, working through a hotfix, or rethinking a deadline that no longer fits the work in front of you.

The plan will change. The opportunity is in how you respond when it does.


David Ziemann

Founder of MoreThanCoders.com
david@morethancoders.com

Related Articles

5 Tips to Improve Your Communication

3 Easy Critical Thinking Exercises


Follow MoreThanCoders

Was this forwarded to you? Sign up here.


600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246

You're receiving this email because you signed up for the MoreThanCoders Newsletter. If you prefer to not receive these messages anymore, feel free to unsubscribe or update your preferences.

The Weekly Gist

Learn practical, straightforward methods to boost your soft skills and enhance your career as a software engineer because you are so much more than a developer.

Share this page