Catching the Shrapnel: The Art of Saying "Not Right Now"
We have all been there.
The squad finishes a sprint planning meeting. The goals are clear, with a solid hypothesis and a reasonable path forward. The team is locked in.
Then, two days into the iteration, the shrapnel starts flying from three different directions at once:
- An executive pops by with a "quick request" that needs immediate attention.
- A competitor goes to market with a flash sale, causing a sudden, reactive shift in your own marketing plans.
- An upstream or downstream partner team realizes they need a "last-minute" piece from your squad—even though their own sprint was supposed to be completely planned out.
In an instant, your team's precious focus is shattered.
The "Middle Manager’s Vise" Reopened
I’ve talked before about how Scope Churn is the silent killer of team efficiency. It erratically injects unplanned work into a fixed period of time, stalling your predictability and putting your original customer promises at risk.
This is that incredibly uncomfortable, high-pressure space where Product Owners and Crew Leaders are caught in the middle. From one angle, they are squeezed by changing business landscape realities and immediate stakeholder needs. From another angle, they are trying to shield their squad members—especially those shared experts who split time across multiple squads—from being torn in half by competing priorities.
If you are a PO or Crew Leader caught in this vise, your natural instinct might be to become a human shield. You want to protect the team, so you simply dig your heels in and yell, "No! We committed to a plan!" But simply shouting "no" without context doesn't work. It creates organizational friction and makes you look like a blocker rather than a business partner. To avoid this squeeze, we have to change how we guard the gate.
Moving From Gatekeeper to Business Partner
When an unexpected request hits your desk, it often comes from a real business need. A competitor's sudden pricing shift is important. A partner team's last-minute blocker does impact the broader organization.
Instead of treating the request like an attack on your plan, treat it like an invitation to collaborate. This is where we look to industry best practices to help guide our behavior.
In modern product development, we rely heavily on the concepts of Capacity Management and Cost of Delay. Author and product flow pioneer Don Reinertsen highlights a concept in his work The Principles of Product Development Flow:
"We cannot manage capacity effectively if we treat queue capacity as infinite. When you inject a new, urgent item into a full queue, something else must drop out, or the entire system experiences a massive bottleneck."
When a leader or downstream partner brings you a disruptive request, they are often suffering from an "illusion of infinite capacity." They think they are just adding a tiny drop to the bucket. Your job as a Value Mastermind isn't to say an arbitrary "no," it is to make the true trade-offs highly visible.
The Data-Driven Pivot: "Yes, And..."
How do we do this practically? We change the conversation from an emotional argument about "agile rules" to a transparent discussion about outcomes and metrics.
When the next "urgent" request hits the vise, try utilizing a three-step approach:
- Acknowledge the Reality: Validate the request. "I see exactly why reacting to this competitor pricing change is critical, and we need to handle it."
- Expose the Invisible Cost: Articulate the current Sprint Goals. Show the system constraints, especially for your shared team members. Size the cost of the "ask". "Our current sprint goals include features that will improve call containment by XX%, which will save the company $75k annually."
- Co-Create the Trade-Off: Put the decision back onto the organization. "We have exactly zero unallocated capacity this sprint. To add this executive request or partner dependency to this sprint, we need to pause Hypothesis A or delay Feature B. Which of those trade-offs makes the most sense for our broader business goals right now?"
When you shift from a defensive "We can't" to a collaborative "Which should we drop?", you stop being a gatekeeper. You become a partner in strategic prioritization. You are no longer just protecting the effort; you are guarding the ROI of the organization.
While the "Yes, And..." might save your current iteration, long-term survival requires turning that recurring shrapnel into strategic data. By monitoring scope-changes and calculating its tax on the velocity during sprint retrospectives, you transform invisible friction into a visible ledger. Bringing this aggregate data to quarterly planning changes the conversation with leadership from an emotional complaint to an ROI-driven case, shifting the organization from short-term firefighting to structural, capacity-driven change.
📋 Coach’s Challenge for Product Owners and Crew Leaders
The next time an "unplanned" request drops into your room mid-iteration, do not accept it quietly, and do not fight it blindly. Try this instead:
- Acknowledge the Source: Capture the request, and the reason behind the request, transparently. Is it an executive "quick favor," a market shift, or an upstream team's last-minute gap?
- Review the Queue: Open your current sprint board with the requester and share the Sprint Goals. Show them exactly what the squad (and your shared team members) are actively working on right now.
- Ask the Trade-Off Question: Ask them: "To make room to solve this problem today, which of our current committed outcomes are we collectively agreeing to delay or drop?"
Observe how the conversation changes when you focus on trade-offs rather than boundaries. Does it reduce the friction? Does it help your partners see the invisible shrapnel you've been catching?
📋 Coach’s Challenge for Shared Team Members
If you are a specialist splitting your time across multiple squads, you probably feel like you are catching shrapnel from every direction. When change happens, you are often the one expected to just "absorb" the extra workload. Next Sprint, try:
- Make Your Split Visible: Don’t let your capacity be a mystery. Make sure every squad you support knows exactly what percentage of your time they own this iteration (e.g., 50/50, 60/40).
- Expose the Vise: The moment an unexpected request or mid-sprint shift from Squad A threatens to bleed into the time you promised to Squad B, do not try to work nights to fix it. Instantly raise your hand.
- Force the Alignment: Bring the Product Owners of both teams into a quick chat and say: "Squad A just had a critical shift that requires an extra 10 hours of my time this week. That means I cannot deliver Feature X for Squad B on time. Please connect and agree on which team takes the hit before I pivot my focus."
Remember, you are an expert, not infinite capacity. If you don't make your capacity limits transparent, the organization will continue to treat your queue as endless.
📋 Coach’s Challenge for Senior Leaders and Executives
Take 10 minutes this week and consider the teams under your care.
- Are You Providing Air Cover? Do your Product Owners and Crew Leaders have the explicit "air cover" to ask stakeholders hard trade-off questions?
- Are You Squeezing the Vise? When you pass down an urgent request from a partner or superior, do you automatically ask your leaders what current efforts they need to drop or delay to make room for it?
If your leaders and shared team members don't feel safe raising their voices to highlight capacity constraints, they will eventually crush within the vise. We must give our protectors the permission to protect the focus of the team. That focus is the actual engine of our delivery.
Everyone needs to help dispel that illusion of infinite capacity! What's stopping you from protecting the team's focus this sprint?
We all win together!
Coach Dan
Comments
Post a Comment