the PM shape
Most PMs arrive at the role through analysis — case interviews, product sense questions, competitive teardowns. They earn their seat by being the smartest reader of a problem. Acuity lands early and lands strong. Worth follows because scoping work is the job description. That’s the reliable double.
What doesn’t land early is Resolve. PMs don’t own a budget line, don’t write performance reviews, and don’t have a team reporting to them. Their authority is entirely relational — earned through credibility, not title. That means the one skill where the environment gives you the least practice is the one you need most when it counts: holding a call under pressure from an exec, a peer, or a customer escalation.
Ken splits by seniority. Junior PMs are often L1 on Room — they’ve studied the product, haven’t learned the org. Senior PMs usually close the Room gap, but then let User drift. Three years in, you start building for the internal mental model of your customer, not the actual one. You stop going to the source because you think you already know what they’ll say.
On the radar, the average senior PM shape lights up Acuity and starts thinning as it crosses into Resolve.
the three competencies that decide the year
Hold — Resolve
Why this one: PMs fold under cross-functional pressure more than any other MARK failure we score. Not because they lack the right answer — because they haven’t trained the behavior of holding it when engineering says “too complex,” design says “not enough time,” or the CPO says “I thought we agreed.”
L4 signal: When someone with more organizational power challenges their call, they name the disagreement explicitly, state what evidence would change their position, and don’t move until that evidence appears — not out of stubbornness, but because they’ve shown their working and the challenge hasn’t engaged with it.
Failure mode: The polished PM version — they don’t fold loudly. They “take it offline,” “align on priorities,” or “incorporate the feedback.” Three days later, the original call is quietly gone and no one can point to the moment it died.
Room — Ken
Why this one: Cross-functional throughput is almost entirely a Room problem. The PM who can read what the engineering lead actually means by “it’ll be tricky” — vs. the PM who hears “it might take a few extra days” — operates in a different league. Speed, trust, and org health are downstream of this read.
L4 signal: In a planning review, they name the subtext out loud — not to embarrass, but to surface it: “I think the concern under this is that we keep changing scope. Let me address that directly before we move on.” The room relaxes. The call gets made faster.
Failure mode: Over-indexing on the explicit signal. PM reads the slide, not the body language, not the history, not the question that wasn’t asked. Leaves the meeting thinking they got alignment. Discovers three weeks later they didn’t.
Worth — Map
Why this one: PMs rarely get to decide unilaterally. Most Worth calls happen in a negotiation — between competing bets, between a stakeholder who wants it now and data that says it’s low-value, between what leadership asked for and what the customer actually needs. When the PM finally does get the call, this is the test.
L4 signal: They can articulate exactly what they’re not building and why — including the thing they personally wanted to build. The trade-off is explicit in the document, not buried. The decision can be audited in six months.
Failure mode: The “yes to everything” trap. Because Worth requires saying no, and PMs in collaborative cultures have been rewarded for accommodation, the L2 PM builds a roadmap that feels inclusive but is actually indecisive — three priorities that are actually seven, all P1.
what to do this week
Pick the last cross-functional meeting where you folded — where you left the room with a direction you didn’t believe in and didn’t say so. Write the version where you held: the exact sentences you would have said, the evidence you would have cited, the question you would have asked back. Bring it to your next 1:1 with your manager and read it out loud. The discomfort in that conversation is the gap.
read this next
MARK for 1:1s and managing up — because Hold, Room, and managing borrowed authority are all conversations that happen one-on-one first; this essay gives you the language to surface your MARK gaps with your manager before the next big call, not after.
avoid these traps
The polished fold. You don’t disagree openly — you “take it as input,” update the doc without saying what changed, and let the original call die quietly. It reads as collaborative. It is actually the highest-cost Hold failure because nobody can name the moment the decision broke.
Acuity as armor. When under pressure, defaulting to more analysis — another survey, another data pull, another framework — instead of holding the call the existing evidence already supports. Sharp analysis is a strength; using it to delay commitment is an Acuity-flavored Resolve gap.
The stale user model. Senior PMs are at highest risk. You’ve talked to customers for three years and you’ve built an internal model that feels like evidence. When Room and User diverge from that model, you discount the signal instead of questioning the model. The year you stop going to the source is the year Worth calls quietly go wrong.
citation
PL Standard v3.1 · MARK for PMs