A BA I worked with told me about a meeting that broke her. The company’s COO had walked into a backlog review and casually said, “We need to add SSO before the end of the quarter.” She had been hired to interrogate requirements, not approve them. She started to ask the questions. The COO interrupted her with: “I’ve already decided. Let’s not waste time.”
The team watched. Her manager was in the room and said nothing. She said okay. The team built SSO in eight weeks. It was used by three customers in the next two quarters.
She told me later she knew at that moment the requirement was wrong. She just couldn’t find a version of “actually, can we step back” that wouldn’t have ended her credibility in that meeting.
Most stakeholder management advice quietly assumes you’re operating between peers. The reality for BAs and POs in services firms, in junior product roles, in any org where the senior people make the calls, is different. You’re often three to six levels below the person who needs questioning. The five-question framework I’ve written about doesn’t survive contact with that asymmetry unless you change how you use it.
This piece is about that.
Why standard advice doesn’t work when they outrank you
The standard advice — “ask clarifying questions,” “make it about the work, not about the person,” “earn the right to push back through trust” — assumes a relationship where pushback is permitted by default. With a senior stakeholder, pushback is the exception that needs to be earned, framed, and timed carefully. The default is: do what they said.
Trying to apply peer-level tactics to senior stakeholders produces three failure modes:
The visible interrogation. You ask the five questions in a meeting where the stakeholder didn’t expect them. They feel ambushed. They escalate, dismiss you, or just route around you next time. You’ve burned the relationship.
The quiet build. You internally disagree but ship the thing anyway, telling yourself you “raised concerns.” You didn’t. You expressed mild discomfort. The senior stakeholder thinks you’re aligned. When the thing fails, you have no defensible record of having opposed it.
The career-limiting move. You go to the meeting with a strongly-worded one-pager arguing against their proposal, hand it to them in front of others, and watch your manager’s face go grey. The argument might be right. The career move was wrong. You’ve made the senior stakeholder look uninformed in public, which is the one thing no senior stakeholder forgives.
The version of pushback that works is none of these. It’s something quieter and more deliberate.
The pre-meeting move
The single highest-leverage moment for pushing back on a senior stakeholder is before the meeting where the decision gets ratified. After is too late. During is too public.
Concretely: when you hear a senior person is about to commit to a feature or direction, get fifteen minutes with them or their chief of staff or your manager BEFORE the decision is announced. In those fifteen minutes, you don’t ask the five questions verbally. You bring a one-page artifact you already wrote, with your best-guess answers, and you ask: “I drafted this in case it’s useful. The thing I’d flag is X. If that doesn’t change your direction, I’ll get on with it.”
Three things matter about that move:
You’ve already done the work. The senior person doesn’t have to think on the spot, which is the thing they hate most because it makes them feel exposed.
You’ve named one specific concern, not five. Five concerns reads as “I disagree with you.” One specific concern reads as “I want this to succeed.”
You’ve given them the exit. “If that doesn’t change your direction, I’ll get on with it” tells them you’re not blocking. They retain authority. You’ve made the point. What they do with it is theirs.
About sixty percent of the time, in my experience, the senior person says some version of “actually, that’s a good point, let me think.” About thirty percent, they say “we considered that, the answer is Y,” and now you have a real reason rather than a vibe. The remaining ten percent, they brush it off — at which point you have two choices, which the rest of this piece is about.
When the senior person ignores your concern
If you raised the concern early and privately, and they brushed it off, you’ve already done more than most BAs would. You don’t owe them a second push in the moment. But you owe yourself a paper trail.
The artifact you produced before the meeting now becomes the record. Save it. Don’t email it as a hostile follow-up. Just keep it in your own files, dated, with the concern stated clearly. If the project fails for the reason you flagged, you have evidence that you saw it. That evidence isn’t for blame — it’s for trust. The next time you flag a concern, the senior person remembers (or your manager reminds them) that you called this one. Your credit accumulates.
This sounds slow. It is. Building credibility with senior stakeholders in environments where you start with none takes one to two years. There is no shortcut. The BAs who try to take the shortcut — by being loudly contrarian, by making one big stand in a meeting, by escalating publicly — usually leave the company within six months. The ones who play the long game become the BA the senior people ask for by name.
The escalation that actually works
There’s one situation where the long game isn’t enough. Sometimes the senior stakeholder’s decision is going to cause material harm to the company — a regulatory miss, a customer-trust break, a security risk. In those cases, you need to escalate, and the escalation path matters.
The wrong way: go around the senior stakeholder to their boss. This terminates your career at this company within a quarter, regardless of whether you were right.
The right way: go to your own manager first, with a written brief explaining the risk in business terms (not requirements terms). Ask them to escalate or to grant you permission to escalate. If they refuse, that itself is information about the company. If they agree, the escalation goes up through proper channels with named accountability.
Critically: you escalate the risk, not the disagreement. “I think this decision is wrong” is a disagreement. “Shipping this would put us in non-compliance with X regulation” is a risk. Senior leadership escalations only run on risk language. Disagreement gets routed back down with a polite “work it out among yourselves.”
What this looks like in practice
A senior BA I respect has built a reputation over five years for being the person you bring difficult decisions to. She has overruled VPs three times in those five years. Two of those overrules turned out to be correct; one turned out to be wrong. The wrong one, importantly, did not damage her — because she’d made the point in writing, in advance, with a recommendation that included an explicit “I could be wrong; here’s how we’d know within ninety days.” When she was wrong, the system caught it on schedule and adjusted. She got credit for the framework even though the call was off.
That’s the pattern that works. You don’t win by being right. You win by being calibrated. Calibrated BAs make senior stakeholders feel safer making decisions, because they know they’ll hear honest assessments instead of either rubber-stamping or aggressive pushback.
The five-question framework is a tool for calibration. When you use it against a senior stakeholder, you’re not interrogating them. You’re showing them you’ve done the work of thinking through the proposal seriously, you’ve identified the specific weak point, and you respect their authority to decide what to do with that information.
The career math
Most BAs who plateau at mid-level do so because they’ve optimised for being right in meetings. The ones who advance optimise for being calibrated over years. The two are not the same. The calibrated BA might raise fewer concerns and miss a few real issues. The right-in-meetings BA raises many concerns, half of which turn out to be noise, and acquires a reputation for being difficult.
If you’re a BA or PO working under senior people who don’t take pushback well, the long-game move is to build a track record that earns you the right to be heard. Every prediction you make in writing, dated, accumulates over time. The senior people who initially brush you off will, within eighteen months, start asking for your read before they decide.
You will not get this from one good meeting. You will get this from forty quiet ones where you said the careful version of what you thought, in writing, and let the work speak.
The next piece in this series tackles the specific case of how to write the one-page artifact mentioned above — the format, the order of sections, and the rhetorical moves that make it land instead of feel adversarial. Subscribe below to get it.