Managing failure for growth
There is a kind of help that looks generous in the moment but quietly weakens people over time.
You see someone heading toward a mistake. You know how the story ends. You can already feel the awkward conversation, the broken plan, the rework, the avoidable mess. So you step in. You correct the path. You save the outcome.
Sometimes that is exactly the right thing to do. Some failures are too expensive, too harmful, or too pointless to allow. Letting someone walk into a wood chipper for the sake of “learning” is not wisdom. It is negligence with a beard.
But not every failure is a wood chipper. Some failures are small, survivable, and deeply useful. When we prevent all of them, we may protect short-term performance, but we also steal the feedback loops people need to build judgement.
Advice is not experience
People rarely learn deeply from advice alone. Advice can help, of course. It can prepare someone, warn them, give them a map, or make the lesson easier to recognise later. But advice often remains theoretical until reality lands the punch. There are things people only understand once they have felt the consequence themselves.
You can explain a trade-off ten times. You can describe why an approach is fragile. You can warn that a plan depends on too many assumptions. But until the thing bends, cracks, or becomes awkward in their own hands, the lesson often stays abstract.
This is frustrating when you can see the mistake coming. It is especially frustrating when you have already paid for the same lesson yourself and would quite like to save someone else the bill. But saving someone from every bill is not the same as helping them become competent. Sometimes it only teaches them that someone else will catch the falling plate.
Intervention has a cost
Intervention improves immediate performance, but it can damage long-term performance.
A senior engineer who constantly steps in may keep the work moving, but they may also prevent someone else from building judgement. The task gets done, the delivery risk drops, the meeting goes more smoothly, and everyone feels like the right decision was made. Maybe it was. But there is still a trade-off.
The person who was rescued did not get to experience the consequence of their decision. They did not have to debug the assumption. They did not have to recover the situation. They did not have to sit with the gap between what they thought would happen and what actually happened.
That gap is where judgement forms.
If we close that gap too quickly, we create dependence. People learn to wait for correction, approval, or rescue. They become good at operating inside someone else’s judgement instead of developing their own. This is one of the quieter costs of micromanagement. It does not only waste the manager’s time or frustrate the person being managed. It interrupts the learning loop.
The goal is not abandonment
None of this means we should let people fail blindly. There is a lazy version of “let people learn” that is really just neglect wearing a philosophical hat. That is not the point.
The job of a senior person is not to disappear. It is to design the conditions where people can encounter reality without being destroyed by it. That means setting context, clarifying constraints, making risks visible, and managing the blast radius.
Let the small things break so the big things do not.
That might mean letting someone own a technical decision, but keeping the scope small. It might mean allowing an awkward design review, but not allowing a production incident. It might mean letting someone present an imperfect proposal, but making sure the room is safe enough for them to learn rather than be humiliated.
The distinction matters. Preventing every mistake creates fragility. Allowing unlimited damage creates chaos. The useful path is deliberate exposure to recoverable failure.
Failure should be visible
There is another reason to let some failures play out: other people learn from them too.
In healthy engineering cultures, failure is not hidden away like a family curse. It is examined. Not theatrically. Not with blame. But openly enough that the team can learn from what happened.
This is especially important for senior engineers. Senior people set the tone for what is allowed to be visible. If they hide every mistake, every bad assumption, and every moment of uncertainty, they teach everyone else to perform competence instead of build it.
That performance is toxic.
Junior engineers start believing that strong engineers are always certain. Less technical managers start judging people against an unrealistic image of effortless expertise. Teams stop asking questions because nobody wants to look like the only confused person in the room.
But real competence is not clean. It involves wrong turns, bad assumptions, incomplete context, debugging, recovery, revision, and occasionally staring at a terminal with the hollow expression of someone reconsidering several life choices. People need to see that. They need to see strong engineers misunderstand something, correct themselves, ask for help, change their mind, and recover.
Not because failure is glamorous. Because it is normal. Hiding it creates a fantasy model of competence, and fantasy models are terrible operating systems.
Cultures that hide failure become brittle
An organisation where people hide failure is as unhealthy as an organisation where people hoard knowledge. Both create the same underlying problem: learning gets trapped.
When knowledge is hoarded, people cannot build on what others know. When failure is hidden, people cannot build on what others learned. In both cases, the organisation becomes dumber than the sum of its people.
Failure that is never discussed becomes private tuition. The individual pays the price, maybe learns something, and the wider system gains nothing. That is waste.
A team should not need every person to step on the same rake independently. The first person to take the handle to the face should be able to make the rake visible for everyone else.
This requires psychological safety, but psychological safety is often misunderstood. It does not mean low standards. It does not mean everyone gets wrapped in emotional bubble wrap. It means people can expose uncertainty, mistakes, and incomplete thinking without being punished for the act of learning in public.
High standards and visible failure are not opposites. In serious engineering cultures, they depend on each other.
Some people still will not learn
There is an uncomfortable edge to all of this: failure only teaches people who are willing and able to reflect.
Some people do not learn from advice. Some do not learn from failure either. They repeat the same pattern, pay the same price, blame the same external forces, and somehow emerge with the same conclusion they started with. At that point, failure is no longer a feedback loop. It is just a recurring subscription.
This matters because “let people fail” is not a magic growth strategy. Exposure alone is not enough. The learning comes from reflection, ownership, and adjustment.
If someone repeatedly fails in the same way and refuses to engage with the lesson, the answer is not infinite patience disguised as empowerment. The answer may be clearer boundaries, different responsibilities, direct feedback, or removal from a context where their failure damages others.
Recoverable failure is useful. Repeated unexamined failure is a signal.
Support is better than rescue
The better alternative to over-intervention is not passivity. It is support.
Rescue says, “I will prevent this from going wrong.”
Support says, “I will help you understand the terrain, make the risk visible, and stay close enough that the failure remains useful.”
Rescue takes ownership away. Support leaves ownership in place while improving the conditions around it. That is the difference between micromanagement and leadership. Micromanagement tries to control the outcome by controlling the person. Leadership improves the environment so the person can grow into better judgement.
A useful senior person knows when to intervene, when to warn, when to ask a question, when to let the decision stand, and when to quietly reduce the blast radius. That is harder than simply stepping in. It requires patience, trust, and tolerance for some mess in the system, because all capability is built through contact with reality.
The job is to manage the blast radius
The job of a senior person is not to prevent every mistake. It is to know which mistakes are survivable, which ones are dangerous, and which ones are necessary.
Do not let people walk into the wood chipper. Do not let avoidable damage hit customers, patients, production systems, security boundaries, or people’s dignity just because you enjoy the rugged aesthetic of “learning by doing.”
But do not wrap every sharp edge in foam either.
Let the small things break. Let people feel reality. Let the team see recovery in public. Let people build scar tissue while the stakes are still low enough for scar tissue to be useful rather than catastrophic.
That is how judgement forms. That is how engineering cultures mature. That is how people become strong enough to not need rescuing.