Issue 03 : The 50-Employee Inflection

Overview

The challenges that surface around 50 employees are different from the 25 employees that show up earlier, which makes it more dangerous.

At 25 employees, the coordination gaps are visible.

Two people are working on the same project, unaware of the other. A decision gets made without authority. Everyone in the company can see what's broken.

At 50 employees, the gaps are systemic.

Teams start working towards different priorities without realizing it. People become unclear about who actually owns a decision. New hires experience the company differently from the people who were there from the beginning.

Systemic failures are invisible until they start to become visible.

Anchor Growth Partners gave us the right setting for this issue because Marcus Webb's first-month assessment documented three specific systemic failures:

1) The overlapping strategic initiatives

2) The informal authority confusion

3) The culture drift

None of these three issues had produced a dramatic failure event. They were accumulating slowly, in the background of a company that looked like it was scaling successfully.

What Didn't Make The Final Cut

A section on the CEO's communication architecture at 50 employees.

We originally included a section on how a CEO's communication style needs to change as a company grows from 20 to 50 employees.

The reason we removed it was because it moved the issue into a different area. This issue was about what an operations leader needs to build. How a CEO communicates is something the CEO needs to develop.

We also removed a section on what happens when groups of early employees start acting like an unofficial leadership team. It's a real challenge in growing companies and can create a lot of confusion around decision-making and influence.

We removed it because we felt it belonged in another issue that is more focused on culture and organisational design rather than this one.

What We Were Thinking

The planning session was the moment that shaped this issue entirely. It revealed three overlapping initiatives in the first 30 minutes.

The OKR document didn't create alignment. It created the context in which misalignment became visible.

The distinction mattered. The company already had the problem.

The planning process just gave everyone a way to see it.

Terms

• Decision Rights
• Management Infrastructure
• Operating Cadence
• Organization Inflection Point
• The 25-Employee Problem
• The 50-Employee Problem

Learn

• Issue 03 - The 50-Employee Inflection