The collapse nobody should be surprised by Spirit Airlines shut down this week. Thirty-four years of operations, gone. The company had been in talks with the Trump administration about a $500m bailout, but those conversations collapsed. The headlines focus on the failed rescue. I focus on something else: how did an airline that survived decades end up needing government intervention to stay alive? The answer is almost never one thing. It is a chain of decisions, missed signals, and problems that compounded because nobody stopped to ask why they kept happening. This is not just an airline story. I have seen the same pattern in businesses with five people and businesses with fifty. By the time you are looking for someone to rescue you, the real damage happened months or years earlier. Why most post-mortems happen too late People tend to analyse failure after the fact. The business closes, the project collapses, the client leaves. Then everyone sits around asking what went wrong. That is backwards. The problems that kill businesses rarely appear suddenly. They build. A cash flow issue that gets patched. A team member who keeps missing deadlines. A product line that underperforms quarter after quarter. Each one gets addressed at the surface level, and the underlying cause stays untouched. I worked with someone last year whose business was bleeding about £4,000 a month in operational waste. Not from one big leak, but from dozens of small inefficiencies that had accumulated over three years. Nobody had ever asked why those inefficiencies existed. They just kept working around them. By the time we traced the root causes, we found that 60% of the waste came from a single decision made in 2021 about how they structured client onboarding. One decision. Three years of compound damage. The 5 Whys method, explained without the jargon The 5 Whys is a diagnostic technique developed at Toyota in the 1930s. It works like this: when you identify a problem, you ask why it happened. Then you ask why that happened. You keep going until you reach something you can actually fix. Most people stop at the first or second why. That is where you find symptoms. The root cause usually sits at the fourth or fifth. Here is a real example from a client: Problem: We keep missing project deadlines. Why? Because the team runs out of time at the end of each phase. Why? Because scope keeps expanding mid-project. Why? Because clients add requests after we have started work. Why? Because the initial brief does not capture everything they actually need. Why? Because our discovery process is a single 30-minute call with no structured questions. The surface problem was missed deadlines. The root cause was a weak discovery process. Fixing the deadlines directly would have meant pushing the team harder, adding buffer time, or constantly renegotiating. Fixing the discovery process meant fewer scope changes in the first place. One solution treats symptoms. The other treats the disease. When to run this exercise Do not wait for crisis. The best time to use 5 Whys is when you notice a pattern. Something that keeps going wrong. A frustration that keeps returning. A number that keeps moving in the wrong direction. I recommend running it quarterly on your three most persistent operational problems. Not your biggest fires, but your most repetitive ones. The things you keep solving but never seem to stay solved. At alira.london, we built a 5 Whys tool specifically for this. It walks you through the questioning process and helps you document each layer so you do not lose the thread halfway through. It takes about fifteen minutes and forces you to go deeper than you would on your own. The difference between a root cause and an excuse One thing I see people get wrong: they use 5 Whys to arrive at something they cannot control, then stop there. "Why did we lose that client?" leads to "Because the economy is bad" or "Because competitors undercut us on price." Those might be true. They are not useful. If your 5 Whys ends at something external, you went in the wrong direction. The question is not "what happened to us." The question is "what did we do, or fail to do, that made us vulnerable to what happened." Spirit Airlines faced rising fuel costs from geopolitical instability. So did every other airline. Some are still flying. The external pressure exposed internal weaknesses. Those weaknesses are what 5 Whys is designed to find. Structure prevents the need for rescue I run ALIRA. as a system consultancy. What that means, in practice, is that I help people install structure into their operations before they need rescuing. The businesses that survive external shocks are not the ones with the best luck. They are the ones with the clearest understanding of how their operation actually works, where the weak points are, and what needs attention before it becomes urgent. This is not about predicting the future. It is about building a business that can absorb impact without collapsing. The Real Greek got rescued this week by the Karali group. Spirit Airlines did not. The difference is rarely about the severity of the problem. It is about what state the business was in when the problem hit. What to do this week First: Identify one recurring problem in your business. Something that has happened at least three times in the past six months. Write it down in one sentence. Second: Run 5 Whys on it. Use the tool at alira.london if you want structure, or do it on paper. Either way, do not stop before the fifth why. If you hit an external factor, redirect: ask what internal condition made that external factor hurt you. Third: Take whatever you find at the fifth why and write one concrete action you can take in the next fourteen days to address it. Not a plan to make a plan. An actual thing you will do.