Execution discipline

When the Founder Keeps Changing Priorities

When new work becomes urgent, decide what happens to the work already promised. A team needs to know what takes priority, what moves, and who will explain the change to anyone affected.

By Scott Smith ·

You agree on the week's work. People begin. Then a customer conversation produces a new request. A product idea needs attention. Something the founder noticed yesterday becomes the most important thing today.

Each request may have a sound reason behind it. Together, they can leave the team carrying commitments that no longer fit.

By Friday, the new work has moved forward and the original work is late. The founder wonders why the team cannot finish what it starts. The team wonders which promise it was supposed to break.

Before calling that an execution problem, look at how priorities changed.

Establish what actually changed

A growing business needs to respond to new information. A customer may face a real deadline. A delivery problem may threaten an important relationship. Something the company planned last week may no longer be worth doing.

Changing direction can be the right decision. The responsibility is to carry that decision through to the work.

What changed in the business? What result now matters more? Why does it need attention before the current commitments are complete?

Those questions help distinguish a necessary change from a new idea that deserves consideration later. They also give the team enough context to make sensible choices when you are unavailable.

If you are unsure whether changing priorities is the real problem, start by finding the constraint in the work.

Make clear whether you are exploring or assigning

A founder can be thinking aloud while an employee hears an instruction.

“We should look at this” might mean save the idea, investigate it, or stop the current assignment and begin immediately. If people have learned that your suggestions often become urgent, they may act before you intended them to.

Be clear about the request. Are you asking someone to record an idea, answer a question, or produce a result?

An investigation needs a limit too. Asking whether something is possible can turn into several days of development if nobody agrees on what evidence is enough to answer the question.

For example, you might ask for a brief assessment of the options before deciding whether to commit delivery time. State how much effort that assessment deserves and when you will decide what follows.

This lets you remain curious without accidentally commissioning every idea you mention.

Name the commitment that will move

When the new work really does take priority, examine the work it interrupts with the person responsible for delivery.

What is already promised? Which people are needed for both assignments? What is the cost of stopping work now? Who else depends on the original result?

Then make a decision. You may move a date, narrow the new request, pause another assignment, add suitable help, or decline the new work. Sometimes the team has enough room to absorb it. Check that rather than assuming it.

An illustrative conversation might sound like this:

“I understand why the customer needs this by Thursday. The same person is finishing the onboarding guide we agreed for Friday. We can deliver the customer work first and move the guide to Tuesday, or reduce the customer request and protect Friday. Which commitment should change?”

The dates and assignments here are hypothetical. The useful part is making the choice visible before either commitment is missed.

If the answer is that both dates must hold, establish what makes that possible. Is there available capacity? Can the work be reduced? Can another qualified person contribute without creating more review work than they remove?

Repeatedly catching up at night should prompt a closer look at what the business is committing to.

Keep the delivery owner in the conversation

A founder may have a good reason to speak directly with anyone in the business. But a direct request can change a person's workload without the person coordinating delivery knowing about it.

That leaves a manager accountable for a plan that has already changed elsewhere.

You do not need to put a manager into every conversation. You do need a clear way to make changes visible. When a request affects an agreed commitment, include the delivery owner in the decision about timing, scope, and consequences.

Give employees language they can use without feeling that they are refusing the founder:

“I can help with that. Let me confirm what needs to move with the person coordinating this work.”

Then support them when they use it. If asking about the tradeoff is treated as resistance, people may agree to everything and leave the conflict unresolved.

The broader question of usable authority is covered in why managers keep bringing decisions back to the founder.

Update the people who depend on the original promise

An internal change can affect a customer, another team, or someone preparing the next stage of the work.

Agreeing privately that an assignment can wait does not tell those people what to expect. Name who will communicate the revised commitment and when.

A short record is enough for many teams: the new priority, the work displaced, the revised scope or date, the owner, and anyone who needs to be told. Update the place people actually use to coordinate work. A separate document nobody checks adds little.

Be especially careful with work that is paused. Record where it stopped and what must be true before it restarts. Otherwise, an assignment can remain on everyone's list while nobody knows whether it is still expected.

Handle emergencies, then examine the pattern

Some situations require action before there is time for a full discussion. Protect people, customers, and the business as the circumstances require.

Once the immediate issue is contained, reset the affected commitments. Do not leave the team working from dates that the emergency made unrealistic.

If urgent requests repeatedly displace the same important work, examine what is happening. Is the team learning about problems too late? Are customer promises being made without checking delivery? Is a recurring responsibility missing from the plan? Are interesting ideas being treated as emergencies?

The answer should guide the correction. A longer priority list will not resolve a habit of accepting work without deciding what it replaces.

Judge delivery against the agreement that remained

Reliable execution requires accountability. That includes accountability for the changes leaders make.

When reviewing a missed deadline, reconstruct the sequence. What was originally agreed? What changed? Who approved the change? Was a revised commitment communicated? Did the person then meet it?

An employee remains responsible for raising a conflict they can see. A leader remains responsible for deciding a tradeoff that sits outside the employee's authority.

When the commitment was clear and workable but delivery still fell short, address that directly. The guide on repeated missed deadlines can help prepare that conversation.

Start with the next request

You do not need a new planning system to begin. Use the next request that conflicts with work already underway.

Explain why the new result matters. Ask the delivery owner what it affects. Decide what will move, shrink, or stop. Tell the people affected, then review whether the revised commitment held.

The founder can change direction. The team needs a clear decision about what that change asks them to deliver.

Let's talk about the work that keeps getting displaced

If your team is busy but important work keeps slipping when priorities change, let's have a conversation about what is happening. We can examine the commitments, decisions, and capacity involved and work out what needs to change.

Let's talk about your situation