Issue 03 : The 50-Employee Inflection

In this section, we are talking about the editorial position, including what the team actually thinks, stated without hedging, with specific reasoning on the topic on the Hard Question in each issue.

Hard Question

Three weeks after Anchor Growth Partners implements its first company-wide OKR document and bi-weekly leadership coordination meeting, Marcus Webb discovers that one of his VPs has been actively pursuing a genuinely important initiative that was never tied to any objective in the new document because that VP wasn't in the room when priorities were set for the quarter.

The VP's frustration is legitimate. The work matters, it was already underway, and exclusion from the planning conversation wasn't a judgment on its value.

However, the OKR document is only three weeks old, and it already has an unplanned exception sitting outside it.

Should Marcus add the initiative into this quarter's OKRs mid-cycle or hold it for the next planning round?

Hard Question Verdict

Context

This is the predictable cost of any company's first real OKR cycle after years of informal, founder-or-leadership-proximity-driven prioritization. A person who is used to having an automatic seat at the table loses it the moment priorities get written down in one place, and the new document's credibility gets tested in week three rather than month six.

It is both earlier and more dangerous than most leadership teams expect. The instinct to fix it immediately by simply adding the initiative is understandable.

The VP is right, the work is real, and refusing to act on a legitimate complaint feels like bureaucracy for its own sake. That instinct is also exactly how a brand-new prioritization document loses its authority before it has had a chance to earn any.

Our Position

Hold the initiative for the next planning cycle, but treat the planning exclusion as the real failure, fix that immediately and visibly, and be explicit with the VP that the decision is about process integrity, not about the initiative's value.

The OKR document's only function is to be the place where everyone agrees, in advance, on what matters this quarter. The moment it becomes negotiable under sufficiently forceful pushback, it stops being that place and becomes a list that strong-willed leaders can talk their way around.

It means every other VP who didn't push back just learned that the document doesn't actually bind anyone equally.

Marcus is not protecting a piece of paper here. He is protecting the only mechanism Anchor Growth Partners has over 50 employees for ensuring two teams don't independently duplicate six weeks of work on the same problem, which is exactly the failure this document was built to prevent in the first place.

The distinction Marcus needs to hold onto under pressure is that there is a real difference between "this initiative should be added because it's important" and "this initiative should have been included because the planning process failed to include its owner."

Only the second claim is true here, and only the second claim deserves an immediate fix.

The first claim that importance alone earns a mid-quarter exception is the version of this argument every future leader will make the next time they want to go around the document, and granting it once means Marcus has no principled basis for declining it the next four times.

Operational Implication

Marcus tells the VP directly, this week, that the exclusion was a planning failure on his side, not a verdict on the work, and he means it.

He commits the VP to a defined role in the next quarter's planning session, with enough lead time that it's a real commitment rather than a placation.

If the initiative is genuinely time-sensitive that a full quarter's delay would cause measurable harm, not just frustration but a missed window or a compounding cost, then the urgency gets evaluated through the same above-authority escalation path any other out-of-cycle resource request would use, with the VP making the case on the initiative's merits to whoever has standing to grant a genuine exception.

What doesn't happen is a quiet, informal addition to the document because the conversation got uncomfortable. That path feels like the kind thing to do in the room.

It is the most expensive possible way to handle the first stress test of a system Anchor needs to survive for the next year, not just this quarter.