The warning signals came through fast.
Oxygen pressure dropping. Power disappearing. Systems reading abnormal across the board. Apollo 13 was still moving - still intact, as far as anyone could tell - but nobody in the room had a clean picture of what had actually failed.
For a moment, it could have been almost anything.
A bad sensor reading. An electrical fault. A tank problem. A leak somewhere in the system. One component failing and pulling others down with it. Something physical escaping the craft. An instrumentation issue that only looked catastrophic but wasn't.
Every possibility pointed to a different response. Apply the wrong one and the situation gets worse. Apply the right one to the wrong problem and you have lost time you may not have - at the minimum.
It was clear the spacecraft was in trouble. But "the spacecraft is in trouble" was not a problem anyone could fix.
Before they could fix it, they had to understand what kind of problem they had.
The pressure is familiar enough to recognise.
"We're growing, but everyone is stretched - should I hire more people or fix how the work gets done first?"
"Revenue has plateaued and the team is at 100% capacity - do I hire to unlock growth, or force efficiencies first?"
"We're profitable but thinly staffed - is staying lean smart, or are we slowly burning out the team?"
"Everyone is stretched - do I add headcount, change how the team works, or automate more?"
"Before I hire again, could better processes or automation solve the capacity problem first?"
These sound close. They are not the same decision.
"Everyone is stretched" is the symptom, not the diagnosis.
Hiring might be the right answer. In some businesses, demand has genuinely grown past what the current team can handle and adding capacity is exactly what is needed.
Staying lean might be the right answer. Not every pressure to hire is a signal to hire - and not every business is in a position to add headcount even if it wanted to. Some are better served by tightening what they do than by growing the team.
Automation might be the right answer. In others, the same repetitive work is absorbing hours every week that a well-configured system could handle in seconds.
Redesigning how the work is organised might be the right answer. The work exists, the capacity exists, but how work moves through the business is creating friction, duplication, or delay.
Outsourcing might be the right answer. Or stopping certain work entirely. Or clarifying ownership so that decisions stop stacking up at one person.
The problem is that choosing between these options before understanding the cause is how businesses end up solving the wrong problem at real cost.
Some causes worth examining:
The responses point in different directions. Hiring addresses the first. Reorganising the work addresses the second. Stopping the work addresses the third. Delegation and structure address the fourth. Fixing the upstream issue addresses the fifth. Capability investment addresses the sixth. Systems investment addresses the seventh. Process repair addresses the eighth.
Pick the wrong one and the stretch continues - sometimes with more headcount, more overhead, and more complexity on top.
It is not only that different businesses face different causes.
The same business can have several running at once.
One part of the operation may genuinely need more capacity. Another may have a routing problem. A third may be compensating for a system that was never properly set up. And so forth.
That is why the question cannot be answered from the surface symptom alone.
Hire. Automate. Redesign the work. Outsource. Stay lean. Stop doing some work. Clarify ownership. Fix the workflow. Add a capability. Remove the avoidable rework.
None of these is wrong if the diagnosis is right. Each of them is costly if it's wrong.
Hiring when the problem is workflow adds cost without fixing the friction. Automating when the work should not exist creates a faster process for the wrong output. Staying lean when capacity is genuinely the constraint burns out the people carrying it.
"Spacecraft in trouble" was never the problem they solved.
Once the team understood what had actually happened, they were dealing with several distinct problems - each with its own response, its own urgency, and its own constraints. Some could wait. Some could not. The sequence mattered as much as the solutions.
They did not fix one big thing. They worked out what had failed, what was still functioning, and which problem had to come first.
Occasionally it is one of these clearly. More often it is a combination - and within the same business, different parts of the operation are stretched for different reasons.
Before deciding whether to hire, automate, stay lean, or restructure how the work gets done - find out what the symptoms are coming from.
Find out what the stretch is really showing you.
If this feels familiar, start here:
👉 Run the Second Look Decision Diagnostic to see what’s missing before you decide
👉See related business decision
👉 📖 Read more on Second Look blog
You can continue with making the decision afterwwards.