Skip to the end of this post for today’s roundup of insights from earnings calls. You can follow me on X for more: @TheAmericanCEO.
What is a CEO’s first impulse when a major project falls behind?
Add more people!
It makes sense intuitively. Get more hands on deck. Send in the cavalry. Everyone pitch in to take it across the finish line.
Unfortunately, the body-count solution is too simplistic for most projects within the modern organization. In fact, it often backfires: Adding people can slow things down further and even degrade the quality of the final product.
If a CEO wants to drive consistent execution, they must understand this counterintuitive dynamic.
I recently read the book Recoding America by Code for America founder Jennifer Pahlka. In 2020, Pahlka was appointed to a strike team to help bail out California’s desperately backlogged unemployment system. The department’s staff had been overwhelmed by an explosion in claims in the first months of COVID. What was the department’s response?
Add more people!
Over five thousand new staff had been hired to tackle the backlog. But Pahlka’s engineering mind saw the problem with productivity-by-addition:
More people equals more productivity equals fewer backlogged claims, the logic went. But what the politicians didn’t know was that these brand-new employees, with their days or weeks of training by Zoom, could not do the work that would reduce the backlog. Only highly experienced claims processors could do that. In fact, new employees could do almost none of the work assigned to them.
And that wasn’t all. Not only were the thousands of new staffers unable to do the work—they were also eating up the time of those who could.
Pretty much every staff member with tenure and knowledge of how the arcane and complex systems worked . . . all had inboxes full of requests from new employees, representing hundreds of hours of work just to read and respond to them. It was clear that the new employees couldn’t help with recomps, the part of the system that was causing the backlog; it would be years before they were either competent or authorized to do so. But if the people who could help with it, the old-timers, were busy training the new employees, who was processing the claims?
And thus we see that the heroic effort to flood California’s unemployment system with new employees paradoxically made the problem worse.
We shouldn’t kid ourselves that this only happens in government. Fred Brooks, longtime software engineer at IBM, is best remembered today for his succinct statement of this truth: “Adding manpower to a late software project makes it later." His book of essays, The Mythical Man-Month, elaborates this idea, making the memorable statement that:
The bearing of a child takes nine months, no matter how many women are assigned.
So, let’s say that you, a CEO, are facing a stalled project that your customers, shareholders, and board are all waiting impatiently for. When does adding more people help, and when does it hurt?
Adding people helps when:
Tasks are easily divisible and self-contained. When a project consists of independent tasks that can be worked on concurrently, adding more people often results in faster progress. This was an assumption in all those high school algebra problems. If one person can dig a hole in x hours, how long will it take three people to do it? Some work is like that—though knowledge work tends to not be.
Time to reach minimum competency is short. If the tasks to be done can be learned quickly while pulling minimum time from existing resources, adding more people may make sense.
You’re selectively bringing in someone with expertise you need. If the project has a roadblock that can be overcome by specialized talent—i.e., someone with a “very particular set of skills”—adding that person can help the team make progress.
But adding people hurts when:
The output is creative or visionary. If you have a brilliant, top 1%, out-of-the-box-thinking engineer who is behind on delivering a new product, trying to speed them up by hiring ten new engineers isn’t going to work. This is analogous to trying to make the woman have her baby faster by adding more women. Not going to happen.
Roles are complex and require training. As with Pahlka’s example, if you try to get a bunch of new people onboarded into roles that may take months or even a year or more to become fully competent in, you’re going to drastically slow down productivity for the foreseeable future.
If throwing more bodies at a delayed project usually doesn’t work, what are you supposed to do then?
That answer varies widely based on the context, but some general principles:
Focus on communication with project stakeholders. Become like an investigator and understand, from the mouths of the responsible employees themselves, what’s going on. Ask smart questions and listen closely to what you hear. What do they think can get the project back on schedule?
Train employees on prediction. If you’ve read my work, you know that one of my biggest themes is the importance of employees predicting their outcomes. As CEO, it has always been a priority for my employees to be able to tell me with some degree of accuracy when their goals will be met. This is indispensable to planning and coordination at the company level. When a project has fallen behind, you need to train intensively on prediction, asking the responsible employee(s) to forecast when the next deliverable will be done. They must feel able to tell you the real truth rather than what they think you want to hear. Only then can you get a true picture of where things stand and support them with resources that make sense.
Coach toward simplicity. When projects lag, it’s often due to a fixation on details that may not be mission-critical. Again working in close communication with the responsible employees, talk through what roadblocks could be sidestepped through simplification. Often you can get to something sleeker and more efficient, much as SpaceX simplified its rocket engines over time:
Every CEO wishes their team could work faster at times. And when a project is falling behind, it’s natural to want to throw all the resources you can at it.
But it’s also crucial to stop, consider the added complexity, administrative burden, and bottlenecks that an influx of “help” can cause, and ask yourself if it’s actually worth it.
Earnings Call Insights
I recently started posting earnings call summaries to capture “What CEOs are Saying.” Here are some snippets from calls I found interesting from last week:
Union Pacific: Over 200 track construction projects in progress with $1.5B potential revenue
Texas Instruments: Analog segment returned to growth (+2% YoY) after eight quarters of decline
Steel Dynamics: Customer inventories remain historically lean
Intuitive Surgical: Bariatric procedures declined due to GLP-1 impacts
HCA Healthcare: Depressed respiratory season in Q4 affected volumes
Freeport-McMoRan: Potential 10% U.S. tax credit if copper classified as critical mineral
Elevance Health: Current Medicaid rates not fully reflecting cost trends
United Airlines: Accelerating Starlink installation across fleet
Charles Schwab: Planning spot crypto trading launch pending regulations
Prologis: Leasing activity accelerated post-U.S. election with pipeline up 17% YoY. Southern California rents down 25% in 2024
Netflix: NFL games achieved record streaming viewership (30-31M viewers). Acquired FIFA Women's World Cup rights for 2027 and 2031
Halliburton: Expects natural gas demand to increase due to power shortage and AI-driven electricity needs
D.R. Horton: Housing inventory down 15% YoY





