Saying no to power — telling the exec the call is wrong.
what we mean by this
Power is not about being right. Plenty of people are right and silent. Plenty are loud and wrong. Power is the specific act of telling the truth upward — to the person with the authority to overrule you — when that truth is unwelcome, when the room will go quiet when you say it, when silence is the path of least resistance and saying it costs something real.
Most of the time in product work, your judgment stays at peer level. You disagree with a designer, you push back on an engineer's scope estimate, you debate a roadmap call with another PM. Those conversations have friction, but they're lateral — no one in the room can end your career. Power is different. Power is the conversation where the status gradient runs against you: the CEO is presenting the new pricing plan at the all-hands and the math is wrong, the VP is about to commit the team to a timeline that will kill quality, the board is excited about a direction and you're the only one in the room who has read the data. What you do in that moment is what Power measures.
Two traps that look like Power but aren't: performing dissent — saying no to authority because it signals independence, not because you've done the work — and complaining laterally, where you're absolutely clear-eyed with your peers about why the exec is wrong, and absolutely silent in the room where it matters. The first is contrarianism. The second is the most common failure mode we see at experienced PMs — people who have excellent judgment and no nerve.
The thing that makes Power rare isn't intelligence. It's that the skill only gets exercised when the cost is real. You can rehearse it in low-stakes conversations, but Power itself is only visible under pressure. That also makes it compound: every time you do it cleanly — evidenced, direct, no theatrics — you earn access to the rooms where it matters. Executives who don't hear honest reads stop getting them. They end up surrounded by confirmation. The PM who told the CEO the pricing plan would lose 40% of SMB revenue, with the math, in front of 200 people — and the CEO changed the plan that week — has a relationship now that no amount of good work without that moment would have produced.
citation
PL Standard v3.1 · Resolve · Power
Markdown form: [PL Standard v3.1 · Resolve · Power](https://pragmaticleaders.io/framework/competencies/power)
the four levels
Anchored at every rung. The blockquote at each level is panel-authored and pulled live from the rubric — edit anchors via the panel tooling and they appear here.
L1Developing
agrees with the exec in the room, then surfaces concerns only in private or after the call.
you'll see this when…
The PM agrees in the room and complains in the hallway — accurate reads, zero upward delivery.
Disagreement surfaces only after the decision is made, in a post-mortem or a Slack message, never in the moment.
When challenged by someone senior, the PM immediately hedges, adds qualifiers, or abandons the position — not because new evidence arrived, but because the status pressure landed.
common failure mode: Email courage — the PM sends a well-reasoned concern over async after the meeting ends, when it could have changed nothing, and calls that speaking up.
L2Competent
names a disagreement with the exec when evidence is clear; backs down when the exec pushes back without new argument.
you'll see this when…
The PM raises the concern in the room, but softens it so thoroughly that the executive doesn't register it as disagreement — six caveats wrapped around the one sentence that matters, with the hope that the recipient reads between the lines.
Pushback happens in 1:1s or pre-meetings with the exec's deputy, not directly with the decision-maker — effectively using a proxy to carry the risk.
The PM can hold a position under mild pressure ("are you sure about that?") but folds when the pressure escalates beyond a single challenge.
common failure mode: The wrap-around — the PM technically said the thing, but buried it in so much hedging and framing that the message was absorbed as noise rather than signal.
L3Proficient
holds the position under direct pushback from senior stakeholders, names the cost of the wrong call in concrete terms, and does it in the room — not in a follow-up note.
you'll see this when…
The PM delivers the disagreement directly to the decision-maker, in the room where the decision is being made, with the evidence in hand — not as a performance, not as a hedge, but as a clean read.
The framing is calibrated: enough context to land, no unnecessary friction. Not combative; not deferential. The tone says "I think you have this wrong, here's why" without requiring the exec to save face before they can engage.
When the exec pushes back, the PM distinguishes between new evidence (which updates the position) and status pressure (which doesn't). The position holds until the evidence moves it.
common failure mode: The timing error — the PM has the nerve and the evidence, but delivers it after the window closes: after the announcement, after the commitment, after the room has moved on. Right read, wrong moment.
L4Expert
reframes the stakes before the exec decides, not after — making the cost of the wrong call visible in terms leadership can't dismiss.
you'll see this when…
The PM has built the kind of track record where saying the uncomfortable thing upward is not a courageous act — it's a known pattern that executives seek out. "Ask them before we commit" is how the room uses this person.
Delivery is so clean that even when the exec disagrees, they don't experience it as a threat. The PM has learned to separate the call from the person making the call, and the exec feels that separation.
The PM coaches others on this — specifically on the distinction between evidence-based pushback and status-driven noise, and on the moments where silence is a choice with consequences.
common failure mode: Contrarianism — Power as performance. The L4 trap is that saying no to authority gets rewarded, and the reward warps the incentive. The PM starts pushing back not because the evidence calls for it but because the identity of "the one who speaks truth to power" has become a feature they're protecting. Contrarianism dressed as honesty is exactly as damaging as silence.
how to develop it
The most leveraged move here is almost never technical — it's practice with the specific conditions that erode Power. Prepare your read before the meeting, not in the meeting. Know what the evidence says. Know what you're willing to say and in what room. The failure modes at every level below L3 are about preparation and nerve, not about intelligence.
Read. The Manual chapters on managing up, disagreement, and organizational dynamics — /manual/managing-up, /manual/decision-room, /manual/influence-without-authority. These aren't about being liked; they're about being heard.
Practice. The /practice/strategic-alignment and /practice/executive-pressure scenarios put you in rooms where the senior leader is steering toward a visibly wrong call. Practice the delivery, not just the analysis.
Write. A Brief prompt that tests it: "The CPO has announced a direction. You have data that directly contradicts the core assumption. Write what you say in the next planning meeting — who's in the room, what you lead with, and how you hold the position if pushed." The Brief is graded on clarity of delivery, not just correctness of the call.
Coach yourself. After every meeting where you disagreed and stayed silent: ask why. What specifically stopped you? Status? Preparation? Uncertainty about whether you were right? Name it. The gap between what you thought in the room and what you said is the precise gap this competency is measuring.
how to spot it in others
Watch what they do when the most senior person in the room states a position confidently. Do they probe it, or does their body language close?
Listen for their post-meeting commentary. If their private read is consistently sharper and more accurate than what they said in the room, you're watching Power in deficit.
Notice how they respond to being challenged. Do they update on evidence or do they update on status? A person with Power can hold the same position across five challenges if the evidence hasn't moved, and they can drop it mid-sentence if new information arrives.
Look for the moment when they could have said something and chose not to — and whether they know they made a choice. Self-awareness about the silence is a precursor to the behavior changing.
In interviews: ask them about a time they pushed back on a call from someone above them. Listen for whether they describe the actual moment of delivery, with the actual stakes and the actual outcome — or whether they describe a safer version where the disagreement was welcomed, the timing was right, and no one's face went tight.
three failure modes we see often
Email courage. The PM has the read, produces the evidence, and delivers it — in writing, after the decision, via a message no one will have time to act on. This is not Power; it's a way of feeling like you spoke while avoiding the moment where speaking actually costs something. The tell is that the communication happens downstream of the window — after the meeting, after the commitment, after the ask. Email courage often comes with a genuine belief that the PM "said something." They did. They said it too late and in a medium that couldn't change anything.
The deputy proxy. Rather than delivering the disagreement directly, the PM routes it through the exec's chief of staff, a trusted peer who has the exec's ear, or a pre-meeting with a more junior stakeholder who "might surface it." The read is accurate and the concern is real — but the PM has outsourced the nerve part to someone else. When the exec doesn't hear it, or hears a softened version, the PM feels they've done what they could. The failure here is structural: Power only counts if it's delivered to the person who can act on it.
The wrap-around. The PM says the thing — technically. But it's wrapped in so much preamble, qualification, and hedging that the disagreement disappears into the context. "I think this is a really strong direction, and I know the team has put a lot of work into it, and there are so many dimensions here, and I don't have all the context you have, but one small thing I might flag is…" By the time the actual concern surfaces, the recipient has classified the speaker as a supporter and isn't listening for a challenge. The wrap-around is usually an attempt to manage the exec's reaction before the message lands. It almost always backfires — the concern isn't heard, and the PM has now signaled that they'll absorb the discomfort of disagreement alone rather than naming it.
Both live in Resolve, both require conviction under pressure. The distinction is directional. Hold is lateral or downward pressure: your team is wavering, the market is noisy, a peer is pushing you to flip — you hold the position because the evidence hasn't moved. Power is upward pressure: the person with authority over you is wrong, and you say so. Hold is about not folding. Power is about speaking first.
Also in Resolve, also about absorbing costs cleanly. Miss is about owning a wrong call you made; it's retrospective accountability. Power is prospective — you're trying to prevent the wrong call from being made. A PM can be excellent at Miss (taking accountability after the fact with no deflection) while being poor at Power (never surfacing the disagreement before the call was locked). They look similar from outside — both involve discomfort, both involve not hiding — but the timing and the direction are entirely different.
what good looks like in the wild
A PM on a mid-size SaaS team — roughly 200 people, Series C, scaling fast — is sitting in an all-hands when the CEO unveils the new pricing strategy. The plan is to restructure the SMB tier: eliminate the lower-priced entry plan, move all new SMB customers to a higher-priced tier with more seats. The logic the CEO is selling is that SMB customers are undermonetized, the new tier is still affordable, and the team should be proud of what they built.
The PM has spent the last two weeks building the retention model for exactly this cohort. The data is unambiguous: at the proposed price point, roughly 40% of the SMB segment — mostly teams of two to four — will not convert on renewal. The math on the new tier assumes a conversion rate that the model says won't hold.
In the room are 200 people, the leadership team, and the CEO mid-presentation. The PM raises her hand. Not after the presentation, not in the Q&A that never happens, not in a Slack message three hours later. She raises her hand in the middle of the slide. "I want to flag something on the SMB numbers before we go further. I've been building the retention model for this cohort — can I share what the data shows?"
The CEO pauses. The room goes quiet. This is the moment. She shares three numbers. Not a deck, not a lengthy preamble — three numbers that show where the model says conversion will land at the proposed price point, and what the annual revenue impact is if the model is right. The tone is clean: evidenced, direct, no theatrics. She's not challenging the CEO's competence; she's challenging the assumption. The CEO asks two questions. She answers both. He asks a third: "How confident are you in this model?" She says: "Confident enough to flag it in this room."
“
The plan was modified that week. The lower entry tier stayed. The conversion assumption was revised. Six months later, when the company is designing the pricing strategy for the enterprise tier, the CEO sends her a message: "I want you in that meeting." That's the compound. Power, exercised cleanly, doesn't just change the call. It changes who gets access to the next call.