miss is the hardest competency in Resolve — harder than hold, harder than power — because it asks you to do something that feels socially dangerous: name your own failure, in public, before anyone extracts it from you.
the competency is not about being humble. it is not about performing accountability. it is about precision: identifying the exact call you made, exactly where your read was wrong, exactly what you'd do differently. one sentence. no narrative gymnastics.
what distinguishes a clean miss from the alternatives isn't the emotional weight of the admission — anyone can manufacture that. what distinguishes it is the specificity. "i made the wrong call when i scoped the Q3 bet to desktop only; the mobile-first research existed, i discounted it, that was my read, not the team's." that sentence does something. it names the decision, names the disconfirming evidence, names who made it. it closes the door on reinterpretation. it is, structurally, unfalsifiable accountability.
what most people confuse this with: the post-mortem participation. attending the retrospective, nodding at the blameless process, adding to the "what we learned" column. that is not miss. miss is what you say before the post-mortem is called — or the sentence you lead with when it is. "i was the strongest voice for the approach that didn't work. here is the read i missed."
the wrong takes beginners bring to this: they think miss is about emotional bravery. it isn't. it's about intellectual precision. the fear that stops people from a clean miss is usually not fear of punishment — it's the cognitive discomfort of naming yourself as the causal agent without the buffer of system complexity. "it was a hard problem" is almost always true and almost never the point.
citation
PL Standard v3.1 · Resolve · Miss
Markdown form: [PL Standard v3.1 · Resolve · Miss](https://pragmaticleaders.io/framework/competencies/miss)
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
admits a miss only when pressed, then adds context that shifts blame before the acknowledgment lands.
you'll see this when…
they participate constructively in retrospectives but lead with "we" — the sentence has collective subject even when the call was individually theirs
when pressed on what specifically went wrong, they pivot to process ("the data wasn't there") rather than judgment ("i read the data wrong")
they treat a miss as something to survive and move past, not something to name clearly and then move past
common failure mode: the passive blame — sentences that grammatically imply collective ownership of a call that was individually made. "the team decided," "we didn't have visibility," "the signals weren't clear" — each technically true, each structurally evasive.
L2Competent
admits the miss directly when prompted, names what went wrong without blaming data gaps or timing, but waits for a postmortem or 1:1 rather than flagging it in the moment.
you'll see this when…
they name the miss when directly asked, with reasonable specificity, and without the "but here's what we learned" pivot happening faster than the acknowledgment
they've started to separate the factual account (what call, what evidence, what outcome) from the emotional processing of it
they can say "i got this wrong" without either over-flagellating or immediately neutralizing it with a silver lining
common failure mode: the rebuild reframe — they name the miss, then immediately pivot to "what we built from it." the pivot arrives so fast it functions as an escape. the miss gets acknowledged in the headline and buried in the follow-on. the room moves to lessons learned before the original call has been properly held.
L3Proficient
spots recurring miss conditions in a new situation and flags them before the outcome repeats. coaches teammates to name their misses directly, without softening the cause.
you'll see this when…
they volunteer the miss before the room asks — in a planning review, a quarterly, a 1:1 — without theater or self-punishment, just precision
the miss statement is structurally complete: the call, the evidence they had, the read they made, what they'd read differently now
they've built a habit of separating "what I should have seen" from "what I now know in hindsight" — they don't claim they had more information than they did; they claim responsibility for reading the information they had
common failure mode: the org-level hide — at proficiency, the traps are subtler. they'll own personal execution misses cleanly, but when the miss involved a judgment call they made that contradicted organizational consensus or exec direction, they'll reach for org-design narratives. "the incentives weren't aligned" is often an honest structural critique — and also sometimes a way to defuse individual accountability for the judgment call inside the structure.
L4Expert
names the miss publicly, explains what broke in the thinking, and reframes how the team should evaluate similar calls going forward.
you'll see this when…
the miss statement raises the bar in the room — not by drama, but because its precision makes everyone else's framing feel soft by comparison
they model the level publicly and consistently: in all-hands, in quarterly reviews, in PRs on their own decisions, with their own directs watching
they've learned to hold a miss without it becoming a running narrative — they name it cleanly, integrate the lesson, and don't keep re-litigating it as proof of their self-awareness
common failure mode: ritualized miss-owning — the L4 trap is performing miss as a power move. "i take full responsibility" delivered from a position of safety, where the actual consequences have already been absorbed by others. the sentence is grammatically correct and structurally hollow. what gives it away: they name the failure category (the bet was too big, the timing was wrong) but not the specific call they made that they wouldn't make again. the form of accountability is present; the substance is missing. at L4, this reads as sophisticated deflection dressed as humility.
how to develop it
the hardest development move here isn't cognitive — you probably already know what you got wrong. it's structural: building the habit of saying it before you're asked, and in a form specific enough to be unfalsifiable. start small. after your next decision that didn't land as planned, write one sentence privately: "i made the wrong call when I [specific decision]; what I should have read differently was [specific evidence read]." don't share it yet. just practice the form. notice where your instinct is to hedge — "the data suggested," "given what we knew" — and strip the hedge. the sentence should stand without caveats.
Read. [The Miss Chapter in Resolve — Manual](/manual/resolve-miss) — the canon on what separates clean accountability from performed accountability; [Post-Mortem or Judgment Call? — Manual](/manual/post-mortem-vs-judgment)
Practice. Scenarios: [Quarterly Miss Statement — Practice](/practice/quarterly-miss-statement) — write the actual miss statement for a real call you've made in the last 90 days; [The Blameless Retro That Wasn't](/practice/blameless-retro-accountability) — you ran a "blameless" process but the individual judgment call is still unowned
Write. Brief prompt: "Describe the last significant product call you made that turned out to be wrong. What was the call, what evidence did you have, what did you read incorrectly, and what would you read differently now? Write this as you would open a quarterly review." The Brief evaluates specificity, absence of hedge, and whether the structure is complete.
Coach yourself. After any post-mortem or retrospective, ask: did I name the call, or did I name the situation? if the sentence could apply equally well to anyone in the room, it isn't a miss yet.
how to spot it in others
in a quarterly review or all-hands, do they volunteer the miss before the Q&A, or wait to be asked?
when the miss statement arrives, does it include a specific call, or does it stay at the level of "the bet didn't land"?
does the sentence have a subject? is that subject "i" or "we"?
when you probe ("what specifically would you read differently?"), do they go more specific, or does the answer get vaguer?
watch what happens after the miss statement. do they move to lessons immediately, or do they hold the acknowledgment for a beat before moving on? the pause is evidence. the instant pivot to "what we learned" is evidence the other way.
in 1:1s, do they bring their own misses, or do they only surface them when you raise the outcome directly?
three failure modes we see often
the passive blame. the sentence is collectively addressed when the call was individually made. "we didn't prioritize it," "the team moved fast," "the roadmap didn't have room" — each framing is technically defensible, and each is a way of distributing the weight of an individual judgment call across a group that didn't actually make it. this isn't dishonesty in the usual sense; it's a learned social habit. product teams that celebrate "no heroes, no villains" retrospective cultures produce this at scale. the individual read — which is exactly what MARK is measuring — disappears into the org narrative. the cost: the actual learning never lands, because the person who made the call never claims it.
the rebuild reframe. they acknowledge the miss, then pivot to lessons so quickly the acknowledgment functions as a preamble to the win. "we got this wrong, but here's what we built from it — and honestly, the failure led us to a much better place." structurally, this is the miss being used as setup for a comeback narrative. it's emotionally compelling and informationally useless. the question isn't whether anything good came after the miss; of course it might have. the question is whether the original call was examined with enough precision to prevent the same read error next time. the rebuild reframe closes that examination before it opens.
the org-level hide. a more senior failure mode. individual judgment errors get absorbed into structural narratives: "the incentives weren't set up for this," "the org wasn't structured to see it," "the data infrastructure didn't support the call we needed to make." these claims are often partly true — and often deployed to replace a simpler, harder sentence: "i had enough signal to make a different call and i didn't." the tell: the org critique is specific and well-articulated; the individual judgment error inside it is never named. someone who owns a clean miss can make the structural critique AND name their specific read error. the hide version only does the first.
hold is the skill of maintaining a position under pressure while the outcome is still open. miss is what comes after the outcome is known and it was wrong. hold asks: can you stay with the call when it's contested? miss asks: can you own the call when it's confirmed wrong? they're sequential: good hold requires being willing to name a miss if you turn out to be wrong. but they're not the same competency — someone can hold well and still deflect when it lands badly.
kill is the skill of ending your own idea while it's still in flight — before the market or the outcome settles the question. miss is owning the call after it has settled wrong. the temporal gap matters: kill requires killing something you still believe in (or used to). miss requires owning something you got wrong after the evidence is in. the failure modes are different: kill resists sunk cost; miss resists ego protection. a person who's strong at kill may still be poor at miss — the will to cut early doesn't guarantee the precision to name what you should have read differently.
what good looks like in the wild
it was a quarterly business review — the kind that's attended by the board observer, the head of growth, and about fifteen people who are all quietly calibrating who handles heat well.
the director opened with a slide. not the one about what they learned. the one about what went wrong. "the Q2 platform bet was wrong. i was the strongest voice for it in planning. here's the specific read i missed: we assumed mobile usage was a long-tail adoption problem when we had three signals in the March cohort data that it was a primary use case, not a secondary one. i discounted those signals because they contradicted the pattern we'd seen the prior two quarters. that was my read. it cost us six weeks of build time and the Q2 retention target."
no theater. no over-flagellation. the sentence structure was clean: the call, the evidence, the read error, the cost. the director moved on in about ninety seconds.
what happened in the room was interesting. the board observer, who had been asking gentle questions about the platform decision for two quarters, stopped asking them. not because the issue went away — because the issue had been actually owned, with enough precision that there was nothing left to probe. the question had an answer.
the more consequential thing: the PMs on the director's team started doing the same thing in their own reviews. not because they were told to. because the bar moved. they'd seen what a clean miss looked like, and now "we didn't prioritize it" felt like exactly what it was — a way of not saying the thing.
“
that's the downstream effect of miss done well. it doesn't just close the current accountability loop. it raises what counts as accountability for everyone watching.