Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / The Hidden Cost of Overhiring Your Team
Transcript
- Lucas: There is a specific kind of silence that falls over a conference room when a company realizes it has hired too many people too fast. It isn't the panic of layoffs, which is loud and chaotic. It is the quiet friction of misaligned incentives, duplicated work, and meetings that exist only to coordinate with other teams that shouldn't need coordinating in the first place. Luna: Right, because suddenly everyone is busy, but nothing is getting shipped. The overhead cost of simply being in each other's way exceeds the output of any individual contributor. Lucas: Exactly. And we have seen this pattern repeat across multiple sectors this year. Tech giants announced significant workforce reductions not just because revenue slowed, but because their internal complexity had become unmanageable. They were paying for seats that didn't solve problems; they were paying for coordination tax. Luna: So the issue isn't just the salary line item. It is the cognitive load placed on the remaining high performers who end up doing double duty. Lucas: Precisely. Let us look at the concept of span of control. In lean operations, a manager might oversee six to eight direct reports effectively. Once you push past ten or twelve, the quality of one-on-ones degrades. The manager stops coaching and starts managing status updates. That is where productivity leaks happen. Luna: And if you keep adding managers to manage the managers, you create layers that add zero value to the actual product or service delivery. Lucas: That is the pyramid problem. You start with a flat structure when you are small. Then you hire ten people, then twenty. Suddenly you need a director, then three vice presidents, then a chief operating officer. Each layer adds cost without necessarily adding strategic clarity. Luna: It feels like a game of musical chairs where the music never stops until someone finally sits down, or in this case, gets let go. Lucas: A perfect analogy. The tragedy is that these roles are often filled by competent people. They are good employees. But they are in the wrong environment. Their skills are being wasted on internal politics rather than external growth. Luna: So how do leaders identify this before it becomes a crisis? Is there a leading indicator beyond just the burn rate? Lucas: Yes, and it is counterintuitive. Look at meeting attendance. If your average employee is spending more than twenty percent of their week in meetings, you likely have overstaffing or poor process definition. Those hours should be spent on deep work. Luna: Twenty percent is a hard threshold. Most knowledge workers probably spend closer to thirty-five percent right now. Lucas: Often more. And here is the kicker: those meetings are rarely about decision making. They are about alignment. Alignment is a symptom of unclear ownership. When you have too many people, boundaries blur. Everyone assumes someone else is handling it, so no one handles it. Luna: Which leads to the paralysis by analysis. We see it constantly in marketing teams where five people approve every single campaign asset. Lucas: Five approvals for one email blast. By the time it goes out, the news cycle has moved twice. The cost of that delay is invisible on the P&L, but it is real. It is lost market share. Luna: It makes me wonder if the solution is actually firing people. Or is it just reorganizing the existing talent into tighter squads? Lucas: Reorganization is painful, but it is often cheaper than attrition. However, you cannot reorganize your way out of a culture that rewards presence over output. If your promotion criteria are based on how many people report to you, you will always overhire. Luna: So you have to change the incentive structure first. Make smaller, denser teams the gold standard, not the exception. Lucas: Correct. Amazon talks about two-pizza teams. You should be able to feed the entire team with two pizzas. If you need a catering truck, you have too many people. It sounds simplistic, but it forces a conversation about scope. Luna: I love that visual. Two pizzas. Simple, tangible, and impossible to argue with in a budget meeting. Lucas: But let us be clear. Cutting headcount is not just about saving money. It is about restoring velocity. When you remove the noise, the signal gets louder. Good employees stay because they can actually do their jobs again. Luna: And bad fits leave, which is usually a net positive for team health, even if it hurts short-term. Lucas: Absolutely. The goal is not to minimize headcount for its own sake. The goal is to maximize impact per dollar spent. That requires ruthless prioritization of who stays and who goes. Luna: Before we go deeper into the mechanics of restructuring, I want to pause here. We deliberately don't run ads on these episodes because we believe in keeping the content pure and uninterrupted. Lucas: If this conversation has helped you think differently about your own team dynamics, consider supporting the show directly. It keeps us independent and allows us to keep digging into these topics. Luna: You can find the link to support us at buy me a coffee dot com slash fexingo. Thank you for helping us keep this network ad-free. Lucas: Now, back to the data. Let us talk about the specific metric that tells you when you are overextended. It is called revenue per employee, but that number alone is misleading if you do not adjust for department. Luna: Because sales teams naturally generate more revenue than engineering or HR. Comparing them directly skews the picture. Lucas: Right. You need to look at profit per employee within functional silos. If your engineering team's profitability drops while headcount rises, you are building complexity, not capability. You are creating technical debt and managerial debt simultaneously. Luna: So the warning sign is a divergence. Revenue goes up, but profit per person goes down. That is the death spiral of bloat. Lucas: Exactly. And the fix is rarely immediate. You have to stop hiring first. Freeze new positions. Then audit existing roles. Ask every manager: what would happen if this role disappeared tomorrow? If the answer is 'nothing,' you have your candidate for reduction. Luna: That is a brutal question. What would happen if this role disappeared tomorrow? Most managers will struggle to answer honestly. Lucas: They will defend their turf. But you have to push. Because if the role is truly redundant, keeping it is costing the company more than letting it go. The severance package is a one-time hit. The salary is a recurring wound. Luna: And the emotional toll on the team watching someone get cut is real. How do you handle that transition without destroying morale? Lucas: Transparency is key. Explain why the decision was made. Frame it around the business needs, not personal failure. And ensure the remaining team members have clear next steps. Uncertainty is far more damaging than the layoff itself. Luna: So you turn a negative event into a clarity event. Show them the path forward, not just the door out. Lucas: Yes. And often, after the dust settles, productivity spikes. The survivors realize they have more autonomy. They stop waiting for approvals that never came. They start executing. Luna: It is a paradox. Sometimes you have to shrink to grow. To get big again, you first have to get lean. Lucas: That is the lesson. Growth without discipline is just expense. And in today's market, expense is the enemy of resilience. We will continue tracking these trends as we move through the rest of the quarter.