I need to explain why we missed the target.

What to do when you have to explain why you missed the target

Los Angeles, late October two thousand and twenty. Meg Whitman and Jeffrey Katzenberg have just announced the shutdown of Quibi.

The pitch had been straightforward when she signed on in August two thousand and eighteen. One-point-seven-five billion dollars in pre-launch capital. A library of original content from top Hollywood studios. A clean proposition — five-to-ten-minute premium episodes designed for mobile-only viewing.

Quibi launched on the sixth of April two thousand and twenty. Two weeks into the US covid lockdowns. By September two thousand and twenty it was clear the subscriber trajectory was not recoverable. On the twenty-first of October, Whitman and Katzenberg published an open letter announcing the shutdown.

The day after the announcement is the part of the story that matters for this scenario.

The early post-mortem framing — given by Katzenberg in a May two thousand and twenty New York Times interview — had attributed everything that had gone wrong to coronavirus. The pandemic explanation was legible, defensible, and emotionally easy to deliver. It was also not the whole truth.

In the joint CNBC and Deadline interviews on the twenty-second of October, Whitman holds a different position. Quibi has run three pricing experiments over the summer — a payment-less trial, a ninety-day free trial, a fourteen-day free trial. None had moved the subscriber numbers materially. Whitman tells Deadline: we tried a lot of different things over the summer. The product, she allows, had asked people to pay for it before they had understood what it was. In the joint interview, Katzenberg concedes that his earlier covid-only framing had been, by his own characterisation, flippant.

Why the honest explanation is rarely the one the environment offers

When you need to explain why you missed the target, the honest explanation is almost never the one the environment offers you.

Macroenvironmental explanations — pandemic, recession, supply chain — are legible, defensible, and almost always partially true. They are also almost always incomplete, because something about the product, the pricing, or the distribution would have been a problem without the macro.

Whitman's move, across her post-mortem interviews, was to hold both things at once. The pandemic was real. So was the product gap. The lesson is not that missed targets have real causes. It is that the temptation to reach for the one cause that will be forgiven is strongest precisely when the real cause is the one that won't be.

So let's go to the office and work through it.

Start by reading whether the team missed or the target did

"I need to explain why we missed the target."

The feeling is defensive.

The number didn't land. The room is going to ask. And the gap between what would be true if you said it and what would be defensible if you said it is the gap your credibility is going to have to walk through in the next conversation.

Two choices. They look like the same explanation problem. Different fundamental causes.

When the team missed

Choice one: the team missed. The plan was reasonable, the conditions held, and the work simply didn't happen the way it should have.

If that's the read, present the variance honestly and take the hit before anyone else takes it for you. Not a performance of humility. A specific, factual account of what was supposed to happen, what did happen, and where the gap is.

Elliot Aronson's research on the pratfall effect names the dynamic that makes this work. People trust a description of their own failure more than a defence of it, and the room's instinct to attack is disarmed by the absence of anything to attack. The audience is going to form an opinion about your credibility in the first two minutes; the single most effective way to protect your credibility is to name the failure more accurately than anyone else in the room could.

When the target missed the world

Choice two: the target missed the world. The plan was built for conditions that have since changed. The gap between the target and reality isn't a performance failure, it's a strategic one.

If that's the read, do not defend the miss. Reframe the conversation entirely: explain what changed in the environment since the target was set, and why the original goal no longer matches the business you are now in.

Karl Weick's sensemaking writing names this move structurally. The real job in the room isn't defending the existing frame. It's building a better one out loud. You're not excusing the miss; you're pointing out that continuing to measure against the original target is itself the mistake, and the useful conversation is about what the new target should be. The move is hard because it requires naming, out loud, that the original target was wrong — which is uncomfortable if you set it. The discomfort is exactly what makes the reframe work when it does work.

Team missed, or target missed the world. Same explanation problem. Two different first moves.

How to make the miss legible before the room fills it in

Three tools. The discipline is to make the miss structurally legible before the room fills in its own interpretation. All three were unpacked earlier in the toolkit; here, they combine.

The first is

Lead with the variance before the meeting

Status Reporting.

We unpacked Status Reporting at scenario twenty-six — the PMI-and-defence project-communications tradition, applied with the discipline of leading with variance rather than achievements, in plain language, distributed visibly.

The reason Status Reporting matters here is that the report itself is doing two things at once. It establishes that you understand what happened. And it removes the possibility that anyone will ask the questions you haven't already answered. Variance, facts, dates, no softening language — the report shape is the discipline that protects credibility before the meeting begins.

The team that went into the meeting having already published a status report covering the miss honestly walks into a different conversation than the team that has been trying to absorb the miss internally and is now caught explaining it under pressure. The report is the difference between we knew this and we are dealing with it and we are scrambling now.

For this scenario, the discipline tightens. The report has to land before the conversation about the miss, not during it. The audience reads the report; the audience comes to the meeting having already absorbed the variance. The conversation can move past the explanation to what to do next.

The second is

Trace the miss up to the outcome that matters

Product Metrics Hierarchy.

We unpacked it at scenario twenty-three — the Kaplan-and-Norton balanced-scorecard tradition, applied with the discipline of tracing every input metric back through the chain to the business outcome leadership actually cares about.

The reason the hierarchy matters here is that most missed targets are disconnected from the outcome at the strategic level. The team hit the output metric and missed the outcome metric. Or hit the outcome metric and missed the output one. The hierarchy makes the disconnect visible.

If you missed an activation target but the retention number is healthier than expected, the hierarchy explains why. If you missed a revenue target but the leading-indicator metrics are pointing the other way, the hierarchy explains why. The conversation about the miss becomes structural — this metric missed; here's where it sits in the hierarchy; here's what the outcome metric is doing — rather than reduced to we missed.

The hierarchy is the artefact you walk into the room with. The audience can see what missed and what didn't, in a structure that makes the conversation about which level matters, not about whether you are competent.

The third is

Turn a team failure into a portfolio decision

Product Council.

We unpacked the Product Council at scenario twenty-six — the Marty Cagan and Silicon Valley Product Group governance pattern, applied with the discipline that the council is the structural mechanism for portfolio-level decisions.

The reason the Council matters here is that most missed targets are treated as team failures when they are actually portfolio failures. The team missed because the strategic investment was wrong, or because the resourcing was wrong, or because the priority-setting was wrong — and those decisions live above the team, not inside it.

Escalating the missed target to the Council is what turns team failure into portfolio decision. The team's pain becomes the Council's information. The conversation moves to whether the strategic investment itself needs adjusting, not just the delivery team's velocity.

For this scenario, the discipline is to do the escalation deliberately, not as a defence. We missed. Here's why. Here's what the hierarchy says about whether the miss matters at the outcome level. The Council needs to decide whether the original investment thesis still holds. The escalation reframes the meeting from explanation-of-failure to portfolio-decision-required.

That's the toolkit. One more story before we close.

The Whitman story we opened with showed the discipline of refusing the easy explanation that would let her off the hook — holding the macro and the specific causes simultaneously. The story we close with is a different cut at the same move — a founder who chose immediate, full transparency about a security breach before anyone in the room could ask for it.

A precedent: spending credibility fast under threat

The twenty-sixth of October two thousand and thirteen. Saturday morning at Buffer. Attackers have compromised the company's infrastructure and are using OAuth tokens to post weight-loss spam from tens of thousands of customer accounts, mostly to Twitter and Facebook. The breach route — later confirmed — is a backdoor through MongoHQ, Buffer's database service, whose own employee-password compromise has given the attackers access to Buffer's user token store.

Founder and CEO Joel Gascoigne, with CTO Leo Widrich, has the choice every breached company has in the first few hours.

Minimise. Wait for legal sign-off. Issue a carefully hedged statement the following day. Or publish everything immediately and absorb the reputational damage.

They choose immediate publication.

Gascoigne's first customer-facing post goes up within about two hours of discovery, with a headline that names the breach directly rather than euphemising it. Subsequent updates — numbered, in sequence, appended to the same post — follow every few hours as the team learns more. The posts are in Gascoigne's normal voice, not press-release English. An apology for ruining customers' weekends. A working description of what is known and what isn't. A commitment to the timeline for the next update.

By the time the team has identified the MongoHQ vector and closed the vulnerability, ten numbered updates have been published openly across the weekend. No lawyer has vetted the content. Customers can see the team working in real time, rather than a communications function drip-feeding a sanitised version of events.

Buffer loses some users. The team sees a spike in downgrades from paid plans that evens out within days. What the team also sees, and describes in retrospectives afterwards, is almost record numbers of signups during the same window — new customers arriving not despite the breach but because of the way it was being handled.

So.

Whitman at Quibi refused the macro-only explanation that would have let everyone off the hook, and held both the pandemic and the product gap in the same conversation. Gascoigne at Buffer refused the slower-vetted explanation the legal calculus would have produced, and published everything immediately. Two inversions of the same move — the honest explanation, delivered the way it has to be delivered, costs something; the dishonest or delayed one costs more.

The lesson is not that transparency is always the right play. Some crises involve third-party data in ways that change the legal calculus, and some breaches require a slower, carefully worded response.

The lesson is that when the only asset still under direct threat is credibility, spending it slowly is the same as losing it.

So. Your Next Move from this playbook.

Trace the metric your team missed up to the outcome leadership cares about — and if the line breaks somewhere in the middle, why is anyone still chasing the bottom one?