When "Just One More Thing" Breaks the System

The cup was full before the last drop landed.

It never feels like a big ask.

An executive pulls a product leader aside before a sprint kicks off. There is a customer who needs a specific feature. A sales deal that hinges on one small addition. A request that seems reasonable given the circumstances.

“Just one more thing.”

The product leader says yes. The team is already at capacity but the feature is not that large. The relationship is worth protecting. It seems like the right call in the moment.

But one more thing added to a full sprint is not a small decision. It is a tradeoff that someone just made without calling it one.

How Unplanned Work Actually Arrives

Unplanned work does not announce itself as a problem. It arrives as a favor.

An executive with a legitimate need and real organizational authority makes a request that is hard to refuse. The ask is framed as small. The urgency feels real. And the product leader, caught between protecting the team and responding to someone with more authority, says yes.

When the addition happens before the sprint starts, the team can at least attempt to reprioritize. Something gets pushed out to make room. The plan bends but does not break.

When it happens mid-sprint, the consequences are more serious. Work that is already in flight gets interrupted. Context switches multiply. The team that was focused and moving now has to absorb something new without the time or space to do it well. In a well-run sprint the work does not go long. It ends incomplete, with unfinished items returning to the backlog and the team closing a sprint they were set up not to finish.

Either way the team pays the price for a decision they did not make.

The Product Leader Who Cannot Hold the Line

When a product leader cannot push back on unplanned work, the team absorbs the consequences silently. Priorities blur. The sprint that was designed around a clear set of outcomes becomes something nobody fully committed to. And the team, which was set up to succeed, finds itself set up to fall short.

The product leader who always says yes is not being responsive. They are being reactive. And over time the team stops believing the plan will hold, because it never does.

Holding the line is not about refusing legitimate needs. It is about making the cost of unplanned additions visible before the answer is yes.

When an executive brings a new request mid-sprint, the honest response is not a flat no. It is: "Here is what we would need to remove or delay to absorb this, and here is what that costs." That conversation gives the executive something real to weigh rather than an abstract pushback. And it puts the tradeoff decision where it belongs, with the person making the request.

Executives Are Not Off the Hook

But the product leader is not the only one with skin in this game.

A mature executive understands that adding work to a sprint is not a neutral act. Every addition displaces something, disrupts focus, or forces a tradeoff that the team has to absorb. Executives who consistently push unplanned work into sprints without understanding that context are not just creating delivery problems. They are undermining the planning process that makes reliable execution possible.

That does not mean executives should never make urgent requests. It means they should make them with an understanding of what they are asking for and a willingness to have an honest conversation about the tradeoff.

When that conversation does not happen, the product leader has to create it.

What Unplanned Work Actually Costs

The cost is rarely visible when the addition is made. It shows up later.

It shows up when the sprint ends incomplete and the team has to explain why. When the feature that was supposed to ship this quarter gets pushed to the next one. When the work that does ship carries the marks of being rushed.

It shows up in quality. Work done under the pressure of an overloaded sprint is rarely the team's best work. The focus that produces something great gets diluted by the volume of things competing for attention.

And it shows up in trust. Teams that are repeatedly asked to absorb more than they committed to stop believing in the planning process. They stop trusting that what gets agreed to in sprint planning will actually hold. When that trust erodes, execution suffers in ways that are hard to recover from quickly.

Closing Thought

Unplanned work does not break teams all at once. It arrives one reasonable request at a time, from people with legitimate needs and real authority.

Executives in a product organization have a responsibility to understand what they are asking for when they make those requests. And product leaders have a responsibility to make the cost visible when they do.

Just one more thing is never just one more thing. The teams that stay healthy are the ones where both sides of that equation understand it.