Ask Savannah
Closing the gap between what you mean, what you say, and what actually lands.
Start soon, because the conversation isn't on pause while you avoid it — both people are already adjusting to the unspoken issue, and every week it goes unaddressed makes the eventual version harder, not easier. Name the specific issue plainly and early, before it accumulates into something bigger than it started as.
Lead with genuine curiosity about what happened rather than visible disappointment — the same standard, delivered through irritation versus through interest, produces very different willingness to actually hear it. People deflect feedback that feels like a verdict on them; they absorb feedback that feels like a real question about what happened.
Silence and nodding in the room are rarely confirmation — they're often just the lowest-cost response when disagreeing with someone who holds real authority carries real risk. Test understanding directly, by asking someone to restate the decision in their own words, rather than treating an open "any questions?" as sufficient.
Ask a specific person what they'd do differently on their team starting Monday — that reveals whether the reasoning actually transferred, in a way a general silence never will. Understanding surfaces in application, not in the moment right after you explained something.
Say no to the specific request while being explicit about what you do agree with and why — a clear, reasoned no is read very differently than a vague or defensive one. Relationships are damaged far more by an unexplained no, or a reluctant yes that later fails, than by honest, well-reasoned pushback.
Separate what you genuinely know from what you don't, and speak plainly about both — "here's what I know, here's what I don't, here's how we'll get clarity" reads as more confident than manufactured certainty ever does. Confidence comes from honesty about the gap, not from hiding it.
Notice the moment you're already forming your response while someone's still talking — that's the exact signal that you've stopped listening and started waiting. Deliberately withhold the response you already have and ask one more question aimed at what your fast read might be missing.
Ask directly, specifically, and without judgment about what you're sensing — "something about this seems unresolved, what am I missing" — rather than pressing on the surface topic harder. People withhold when the perceived cost of speaking exceeds the perceived benefit; your job is to lower that cost visibly.
Find out, specifically, what they'd actually lose if they said yes — a real concern, a political cost, a past experience this resembles — before you present your case at all. A stronger version of the same argument rarely converts a no; addressing the actual, unstated reason behind it often does.
Separate what you don't know from what you do — the outcome may be uncertain, but you likely know the process, the timeline, and the principles that will guide the decision regardless of how it lands. That's usually enough to give people real footing, even without a resolved answer.
Lead with understanding their actual incentives and constraints before you lead with your case — influence without authority runs on genuine alignment of interests, not on the strength of your argument alone. People who don't report to you are evaluating what's in it for their own priorities, not just whether your idea is good.
Frame it as making sure your boss has what they need to make good decisions and to represent your work accurately — that's not politics, that's just closing an information gap that exists in any hierarchy. It only feels political when it's about managing perception instead of managing information.
Have a question of your own?