You’ve done the analysis. The flow data tells a clear story — one initiative is choking the system. Cycle time is climbing, aging work is piling up, and three teams are blocked on dependencies that trace back to the same source.
You walk into the leadership meeting with a recommendation: pause it. Redistribute capacity. Let the pipeline recover.
The CTO listens. Nods. Looks at the screen. Then says: “I think we need to look at this differently.”
Every delivery coach, every transformation lead, every person who has ever brought data into a political conversation knows what that sentence means. It means the pushback is about to start. And the pushback has nothing to do with your analysis.
This is the moment that separates coaches who drive change from coaches who present findings.
Pushback Is Information
The first instinct when someone pushes back on sound data is to defend it. Show another chart. Restate the throughput numbers. Make the math louder.
This almost never works. Because the person pushing back already agrees with the math. They’re objecting to something else entirely — the political cost of acting, the personal risk of agreeing in front of peers, or a constraint that lives outside your data set.
When you learn to hear what pushback is actually saying, you stop fighting the wrong battle.
The Three Types of Pushback (and What Each One Means)
After hundreds of these conversations across organizations of every size, I’ve found that pushback in data-driven leadership meetings falls into three patterns. Each one requires a fundamentally different response.
Type 1: “I disagree with the conclusion.”
What it sounds like: “The data might be right, but I think the problem is somewhere else.” Or: “There are factors here you’re not seeing.”
What it means: This person has context your data didn’t capture. A customer commitment. A regulatory deadline. A dependency on another team that shifts the trade-off calculation.
What to do: Listen. Take the new information seriously. Then run the scenario with their constraint included. “If initiative X can’t be paused because of the Q3 commitment, here’s what the throughput picture looks like under that constraint — and here’s what we’d need to adjust instead.”
This type of pushback actually makes your recommendation stronger. Every constraint they surface makes the analysis more complete. The decision gets sharper, the trade-offs become visible, and leadership has a path they can own.
Type 2: “Let’s revisit this next quarter.”
What it sounds like: “Great analysis. Let’s not rush into anything.” Or: “I think we need more data before we act.”
What it means: The cost of acting right now is higher than the cost of waiting — for the person speaking. Something is at stake that has nothing to do with the data quality. Their credibility is tied to the initiative. The timing conflicts with something they’ve already committed to publicly. Or they simply don’t have the political capital to agree in front of this audience.
What to do: Don’t fight the delay directly. Instead, make the cost of waiting concrete. “Absolutely — let’s look at what the next 90 days look like if we continue on the current path.” Show the projected aging work, the downstream impact on other initiatives, the capacity that stays locked.
You’re giving them something to weigh. Delay is always a valid option, but it has a cost, and that cost should be visible.
Type 3: “We need to look at this differently.”
What it sounds like: “I’m not sure this is the right framing.” Or: “I think there’s a bigger picture here we’re missing.”
What it means: This is political pushback. Someone at the table — or someone connected to someone at the table — championed the initiative you’re recommending to pause. Agreeing with your analysis means acknowledging that a visible commitment was wrong. That’s a hard thing to do in front of peers.
What to do: Separate the decision from the audience. This recommendation will not land in this meeting, and forcing it will damage the coalition you need for the next one. Instead, get agreement on process: “Can we run two scenarios — one where we continue and one where we pause — and bring them back to a smaller group next week?”
Now the decision moves to a setting where the political dynamics are different. The person who pushed back has a path to change their position without doing it publicly.
The Physical Mechanics of the Moment
There’s a practical skill here that doesn’t get taught anywhere, and it lives in the three seconds right after the pushback lands.
Pause before you respond. This is counterintuitive. The silence after pushback feels dangerous — like you’re losing ground. You’re not. You’re creating space for the person to add the context they’re holding back. Most people will fill that silence with something closer to the real issue than what they led with.
Acknowledge what you heard. “It sounds like there’s a constraint around this initiative that the numbers aren’t capturing” is a better response than any defense of your data. It signals that you’re reading the conversation beyond the spreadsheet.
Watch the rest of the table. The person who pushed back is not the only person in that conversation. Watch for the head nod from the VP who agrees with your data but won’t say it out loud. Watch for the person taking notes — they’re the one who will follow up privately afterward. These people are your coalition. You’ll need them next week.
When the Recommendation Doesn’t Land
Sometimes it won’t. The data is clear, the pushback is political, and the organization chooses to continue on the current path.
This feels like failure. It isn’t.
The conversation happened. The data is on the record. The projected cost of inaction is documented. The person who chose to delay now owns what happens next quarter.
I’ve watched recommendations that got shelved in one meeting become the approved strategy three months later — same data, same coach, same recommendation. What changed was the cost of inaction becoming visible over time. The coach who planted the seed early is the one leadership trusts when they’re ready to act.
The best coaches treat every hard conversation as a deposit. Some deposits pay out in the same meeting. Some pay out next quarter. The ones that never pay out are the ones that never happened.
The Practice
If you’re walking into a leadership conversation this week with flow data that points to an uncomfortable recommendation, here’s what I want you to think about before you go in:
- Know which type of pushback you’re likely to get. Look at who championed the initiative. Look at who has capital invested. If you can predict the pushback, you can prepare for it.
- Build the counter-scenario before you walk in. If your recommendation is “pause initiative X,” build the scenario where initiative X stays. Show both paths. Let leadership choose between two visible outcomes instead of choosing between your recommendation and the status quo.
- Identify your coalition before the meeting starts. Who already agrees with the data? Who will support you publicly? Who will support you privately after? Your recommendation lands through people.
- Separate the decision from the meeting. If the dynamics in this conversation won’t allow a decision, your goal is to get agreement on the next step.
The coaches who navigate these moments well have learned something important: the data gives you the right answer. The practice is knowing what to do when the right answer meets a room that isn’t ready for it.
And those conversations are a lot harder without clear flow data behind them in the first place. That’s exactly what Nave was built to provide. Learn more at getnave.com
That’s where the real coaching starts.
I’ll see you next week, same time and place for more managerial insights. Bye for now!
