I watched two coaches present to the same company last quarter. Different divisions, same tool, same AI-generated investigation. The findings were nearly identical: a testing stage holding 63% of all work in progress, arrivals outpacing departures by 40%, seven items aging past the 85th percentile, a batch of related work dragging through three stages like an anchor.
Both coaches understood the data. Both had years of experience. Both walked into their leadership meetings prepared.
One walked out with a commitment to reduce WIP and reassign capacity to clear the bottleneck. The other walked out with “thanks, we’ll take this under advisement.”
I used to think these different outcomes came down to analytical skill. One coach sees the pattern faster. One reads the scatterplot more fluently. One catches the batch dependency that the other misses.
That’s not what happened here. The investigation was identical. The evidence was identical. The starting line was the same.
So whatever created the gap had nothing to do with data.
She Connected Evidence to Commitments They Already Owned
The first coach did something before she ever opened the dashboard. She spent ten minutes reading the initiative roadmap for that division. She found three items from the investigation that were tied directly to the VP of Engineering’s Q3 release commitment.
When she presented the bottleneck, she didn’t lead with the bottleneck. She led with this: “Three items tied to your Q3 commitment haven’t moved in eleven days. The stage they’re sitting in is getting worse.”
She brought two scenarios. Clear the bottleneck by pausing new arrivals into testing and reassigning two engineers for a sprint — the Q3 items ship in two weeks. Do nothing — the Q3 items ship in six weeks, assuming the accumulation doesn’t accelerate.
She named the trade-off using language that already lived in that leadership team’s vocabulary. Revenue at risk. Customer commitments. Board-level visibility.
The VP pushed back. “We can’t pull engineers off feature work right now.”
She didn’t argue. She asked one question: “What’s the cost of missing Q3 by a month?”
She let the silence sit.
The second coach presented the same findings. Testing bottleneck. WIP concentration. Aging items. Capacity gap. His recommendation was clear and correct: reduce WIP, clear the oldest items first.
Leadership agreed with his analysis. They thanked him. They moved to the next agenda item.
His recommendation was accurate. It was also general enough that no one felt compelled to act on it today.
The Analytical Edge Disappeared. This One Replaced It.
Here’s the thing. A year ago, the quality of that analysis would have been the differentiator. The coach who could build the picture faster, trace the causal chain more accurately, spot the batch pattern that others missed — that coach had an advantage.
That advantage is gone. The picture builds itself now.
What separated these two outcomes was everything that happened around the data. Reading the politics of the organization. Knowing which finding would create urgency for this specific leadership team. Connecting evidence to commitments they had already made publicly. Building scenarios that turned a recommendation into a decision point. Handling the pushback with a question that made the cost of inaction visible.
That’s change work. It’s the skill that sits between the dashboard and the decision.
AI made the analytical capability available to everyone. The investigation is there. The causal chain is traced. The aging work is flagged. The capacity gap is quantified. Every coach reading this has access to the same evidence base.
The gap lives in what happens between opening the dashboard and walking into the meeting.
The Preparation That Creates Movement
Let me make this concrete. Here’s what the first coach actually did that the second one skipped.
She mapped findings to specific business commitments. She didn’t present a bottleneck. She presented a risk to Q3 revenue that leadership had already committed to publicly.
She built scenarios with specific timelines. Two weeks versus six weeks. Leadership could see two futures side by side. That framing made deferral feel expensive.
She read the political landscape. She knew which executive needed the risk framed as revenue impact and which one needed it framed as reputation risk. She adjusted her language accordingly.
She prepared for pushback. When the VP said “we can’t pull engineers,” she already had the follow-up question ready. She didn’t defend her recommendation. She made the cost of the alternative visible.
Every one of these moves is learnable. None of them require years of political instinct. They require preparation. Ten minutes with the roadmap. A few questions about what commitments matter most this quarter. A second scenario built before the meeting starts.
The coaches who are building this muscle right now are pulling ahead in ways that will be difficult to close later. The data is the same for everyone. The investigation is the same for everyone. What you do with it is the entire differentiator.
Your Move
Pick one leadership meeting you have coming up this month. Before you open the dashboard, answer three questions:
- Which findings from the investigation connect to a commitment this leadership team has already made?
- What are two scenarios you can present — one where they act, one where they don’t — with specific timelines?
- What’s the most likely pushback, and what question would make the cost of inaction visible?
If you can answer those three questions before you walk in, you’re doing change work. If you can’t, the data will land and nothing will move.
You can try the investigation yourself at getnave.com. It takes seconds to connect your board and see what your data is already telling you. What you build around that investigation is what makes the difference.
The data leveled the playing field. What you do with it is the entire game now.
I’ll see you next week, same time and place. Bye for now!
