Companies mistakenly bundle management with authority, forcing top performers onto a management track to gain influence. Separate them. Define management's role as coordination and context-sharing, allowing senior individual contributors to drive decisions without managing people.

By strictly limiting team size, a company is forced to hire only the “best in the world” for each role. This avoids the dilution of talent and communication overhead that plagues growing organizations, aiming to perpetually maintain the high-productivity “mind meld” of a founding team.

Johnson's model demanded lean interfaces with the military and intelligence customers, sometimes limiting their team to just six people. This ensured quick decisions and minimal correspondence, making the entire project ecosystem faster, not just his internal team.

Leaders focus on increasing reports because headcount is an objective metric for promotion, unlike subjective assessments of business impact. This creates an incentive for managers to accumulate people, even if it's not the most impactful business decision.

Robinhood intentionally decouples compensation from an employee's org size. This counters the typical corporate incentive for 'empire building.' By disproportionately rewarding people who achieve high impact with the smallest possible team, they foster a culture of lean efficiency and focus.

Kelly Johnson viewed reporting, approvals, and meetings as operational "drag." He systematically pared away anything that used time without advancing the project, treating organizational design as a performance-critical system to be engineered for speed.

Beyond hiding projects from adversaries, secrecy served a critical internal function: it insulated the team from corporate bureaucracy and distractions. This allowed a compact, focused group to maintain high velocity without interference from the larger organization.

Johnson didn't just prefer small teams; he enforced it "in an almost vicious manner." This ruthless commitment to talent density over headcount was a key operational principle, ensuring only the most capable people were involved in any given project.

To avoid bureaucratic bloat, organize the company into small, self-sufficient "pods" of no more than 10 people. Each pod owns a specific problem and includes all necessary roles. Performance is judged solely on the pod's impact, mimicking an early-stage startup's focus.