Challenge Accepted: Building Critical Mass

I got a national mandate to build a capability. That capability is part of a larger global framework. Instinctually and naturally, I immediately looked at headcount, scope coverage, recruitment velocity. And, quickly, I realized I was playing a game with the wrong metrics in mind.

I started asking the wrong question: "How do we get bigger?"

The real question is different. And it's harder to sit with, because it doesn't have a comforting answer about scale.

The False Problem

Critical mass, for most capabilities, means: large enough to own your full scope independently. Large enough that you're not dependent on other teams. Large enough that you're not 100% billable to client work. Large enough to have slack capacity for thought leadership, experimentation, capability-building.

That makes sense if you're building a capability where resources scale with mandate.

Not always the case.

When given a national mandate to build something that exists within a global framework, the framework often assumes all regional teams would have similar resources. Regional teams often have different starting conditions and resource availability; they may have more or less capacity than others, they may have drastically different configurations and interdependencies with other teams.

The cost of assumptions like this is staffing against benchmarks that were never designed to measure true progress in value creation. When we ask "why are we so small?" instead of "what's actually possible at our size?" we operate in permanent deficit against a baseline nobody validated.

Critical mass, in this context, isn't about becoming big enough to match peer teams in size and capabilities. It's about understanding what critical mass actually looks like when mandate and resources are structurally misaligned.

The Three Fronts

But misalignment doesn't feel like a structural problem when you're living in it. It feels like three separate, simultaneous competitions.

The first is narrative ownership. The global framework outlined what this capability should do. The goal and purpose were so compelling and accurate, that an open community simultaneously and independently formed around a subset of it — same value proposition, fewer governance gates, lower friction. They moved faster. They built visibility faster. By the time we realized they were validating our own mandate, they'd already achieved the kind of momentum that makes them look like the official version of this work. Now we're integrating influence without appearing to control them.

It's damage control dressed as thought leadership.

The second is territory. Our scope overlaps with other capabilities. That's by design — most product work touches multiple dimensions and we don't want to build silos. But when we're understaffed and unclear about our permanent scope, adjacent capabilities start claiming ground that looks like ours. They're not being aggressive; they're moving into ambiguity. The effect is the same: our territory shrinks while we're still defining what territory we actually own.

The third is capacity. We exist because clients need the work. Delivery funds our entire operation. So when client work is heavy, everything else stops: the thought leadership, the community presence, the internal capability-building, the strategic clarity exercises. When the capacity to compete on the first two fronts doesn't exist, control of the narrative goes to the open community and territory goes to adjacent capabilities.

These three feel like separate problems. They're not. They're all manifestations of the same structural reality: executing a national mandate within a global framework with resources don't match peer teams' resources — and until that is named as the operating context, every plan gets written as if it weren't true.

The Constraint Nobody Names

Here's what most global frameworks don't say explicitly, but assume: all regional teams build the same capability with proportional resources.

Here's what's actually true: they don't.

Regions have different key factors: market sizes, organizational structures, talent availability, strategic priorities, and so on. The framework treats this as a deviation from the plan. We're supposed to "catch up."

But catch up to what? A team that started earlier? A team with different constraints? A team operating at a scale that has nothing to do with our actual context?

The cost of leaving this unnamed is enormous. We stay in permanent deficit mode. We staff for capacity we'll never have. We measure success against conditions we don't have. And we read the gap as underperformance when it's actually a measurement error.

The moment we named it — the moment we accepted that our national mandate exists within a global framework but we execute with regional resources — the question changed entirely.

What Critical Mass Actually Means (When Mandate and Resources Misalign)

It's not "large enough to independently own our full scope."

It's: narrow enough to credibly own a defined wedge of that scope, positioned as an essential collaborator to other teams, with enough slack capacity to build our own competencies.

That's three things, not one.

The wedge. We don't always have the luxury of being large enough to own everything our mandate nominally covers. But we can own something specific within it. Something adjacent capabilities don't own. Something that makes us essential to their work rather than redundant with it.

The positioning. We're not building this alone. We're building it within the global framework, explicitly positioned as a national capability that collaborates across borders when the opportunity arises. This isn't a consolation prize; it's structural clarity. We become more valuable when we're clearly bounded and clearly positioned as a partner to adjacent teams than we ever would be defending territory we can't hold.

The slack capacity. This is the real KPI. Not headcount. Not scope coverage. Actual time in our people's schedules that isn't billable to client work. Because without slack, we can't do any of the things that actually build critical mass: thought leadership, community presence, internal upskilling, strategic clarity exercises, attracting the right talent — the people who want to build something, not just deliver something.

The Forcing Functions (What Actually Moves the Needle)

So how do we get there?

Here are four possibilities to test. None of them is "hire more people." I spent a decade in a military community whose founding doctrine is that the right team cannot be mass-produced — where small teams are not a budget compromise, they are the design. Nobody measures a twelve-person team against a battalion and calls it a deficit. The team is built for a different problem, and its value comes from exactly that. And even with that premise wired in, the headcount comparison is a hard instinct to resist.

The capacity trap is real. We need slack to build capability. But capability-building doesn't generate revenue. Client delivery does. So if we're building capability while staying billable enough to fund our existence, we're optimizing for two things that directly compete. The only way out is to acknowledge that some portion of our people's time needs to be invested in capability-building even though it isn't billable. That's different from hoping it happens "in their spare time." It has to be allocated. And it has to be defended when it looks like unused capacity to people outside the team.

The focus wedge matters more than we thought. We want to own everything in our mandate. We can't. Admitting that feels like failure. It isn't — it's clarity. When we narrow our permanent scope to something we can actually defend and own, we become harder to compete with, not easier. We're no longer a threat to adjacent capabilities; we're essential to their work. We're no longer doing everything; we're doing something specific, well. That's attractive to talent. That's defensible against organizational churn.

The visibility game is ongoing. The open community that outpaced us is still moving fast. We're not going to control that, and we shouldn't try to. But we can be central to it. We can shape its direction without appearing to own it. We can claim the narrative space — this is a design challenge, not just a technology adoption challenge — while the community claims the execution space: here's how we're actually doing the work. It's damage control, but it's also the only way to maintain influence when you're smaller than the thing you're trying to shape.

OKRs are a forcing function. Not because they're magic. Because they force us to answer three questions that ambiguity lets everyone avoid: What specifically do we own? What does success actually look like? Who's responsible? Those three answers, written down and committed to, change everything. They defend the wedge against adjacent capabilities. They explain to the open community why we're not trying to control them — because our objectives are different. They recruit talent, because people want clarity about what they're building. They allocate our slack capacity, because we know what we're building toward. Running an OKR iteration might be the most important thing you do in the first year of capability-building.

How these four interact is the puzzle we're still solving. Which sequence gets us to critical mass? Declare capacity first, then focus, then OKRs? Or start with OKRs and use them to defend the capacity allocation? Or something else entirely?

We don't know yet. But we're learning in real time, and that's the point.

The Reframe

Critical mass isn't about becoming the size of other regional teams. It's about becoming indispensable at actual size, within actual constraints, at permanent scope.

If you're a national leader recognizing your own situation in this: you probably have the same constraint. Stop measuring yourself against teams with different starting conditions. The question that matters isn't "how do we get bigger?" It's "what's the narrowest, most defensible scope where we can credibly own this, have the slack capacity to build our competencies, and be essential to the broader organization?"

That's a different game entirely — one measured in the right metrics.