How to Let Your Team Struggle Without Abandoning Them
Development requires room to struggle, but that room needs boundaries.
Leaders often feel caught between two uncomfortable choices.
Step in and solve the problem, or leave the person alone to figure it out.
The first choice can create dependency. The second can feel careless.
But those aren't the only options.
Between rescuing someone and abandoning them is a more demanding form of leadership: staying close enough to provide safety, context and support while leaving enough room for the person to think.
That space is where judgment develops.
The moment restraint became real
Years ago, a leader on my team hired a new employee.
She was highly capable, conscientious and quick to help. When she understood how something should be done, sharing the answer came naturally. She wanted people to succeed, the work to be completed properly and problems to be resolved.
Those were genuine strengths.
They also made restraint difficult.
I had spoken with her about a distinction that becomes increasingly important as someone moves into leadership:
Knowing how to do the work doesn't mean you should do it.
Just because you can doesn't mean you should.
A leader's competence can become a shortcut through every difficulty. The leader sees the problem, recognizes the answer and supplies it before the other person has worked through the uncertainty.
The work moves forward.
The person may not.
One day, this leader came into my office and dropped heavily into a chair. She told me how difficult it was to know what someone should do, resist explaining it and then watch the person struggle toward the answer.
I found the moment quietly amusing, but I was also proud of her.
The employee was learning through the work.
The leader was learning through restraint.
She was beginning to understand that developing someone can feel less helpful than rescuing them. It sometimes requires watching a capable person move more slowly, consider imperfect options and reach an answer the leader could have supplied immediately.
Years later, she speaks with genuine pride about the strength of her team.
That capability wasn't built because she stopped supporting people. It was built partly because she learned how to remain supportive without becoming the solution.
Struggle is part of learning
Leaders often treat struggle as evidence that something has gone wrong.
Sometimes it is.
A person may lack essential information. The expectations may be unclear. They may not have the authority required to complete the work. The consequences may be too serious to leave room for experimentation.
But struggle can also be evidence that learning is taking place.
Someone is comparing options.
They're discovering which information matters.
They're testing their understanding against the situation.
They're learning how much uncertainty they can carry before seeking help.
They're forming judgment.
When a leader removes that struggle too quickly, the immediate discomfort disappears. So does part of the learning.
The goal isn't to make work unnecessarily difficult. It's to recognize that capability isn't created only through instruction. It's also created through experience, uncertainty, correction and recovery.
People need opportunities to make decisions while the consequences are still manageable.
What makes struggle safe?
Safe struggle is not the same as telling someone to figure it out.
Leaving a person without context, authority or support isn't empowerment. It's abandonment.
A productive struggle has several conditions.
The outcome is clear
The person needs to understand what the work is meant to accomplish.
Leaders sometimes delegate a task while keeping the standard inside their own head. The employee is left trying to discover what good looks like by interpreting the leader's reactions.
That isn't useful struggle. It's hidden criteria.
Clarify the outcome, the important constraints and what must be protected. Leave room for the person to determine how to get there.
Responsibility and authority are aligned
Someone can't meaningfully own a decision if they need permission for every significant step.
Before stepping back, make clear what the person can decide, what requires consultation and what must be escalated.
Without that clarity, hesitation may be entirely reasonable.
The consequences are recoverable
Not every situation is suitable for independent experimentation.
A delayed internal document may be recoverable. A serious safety decision may not be. A modest purchasing choice and a major contractual commitment don't carry the same consequences.
The leader needs to understand what could happen if the person gets the decision wrong.
If the result can be corrected without serious harm, the situation may offer useful room for judgment to develop.
Support remains available
Stepping back doesn't mean disappearing.
The person should know when and how to seek help. They should also know that asking for support won't automatically cause the leader to take the work away.
The leader's role is to help the person carry the decision, not make help contingent on surrendering it.
The experience is examined afterward
Experience doesn't automatically produce learning.
After the decision, discuss what the person noticed, what they considered, what worked and what they would change.
A short debrief can transfer more judgment than a long explanation given before the person has experienced the problem.
When leaders should intervene
Restraint isn't an absolute rule.
There are situations where a leader needs to step in early and clearly:
- Safety is at risk
- A legal or ethical boundary may be crossed
- The consequences are serious and difficult to reverse
- The person lacks information they couldn't reasonably obtain
- The decision exceeds their formal authority
- The situation has changed beyond the boundaries originally established
- Continuing would harm another person, the organization or the public
Intervention in these situations isn't a failure of development. It's part of responsible leadership.
The mistake is treating every discomfort as though it carries the same level of risk.
A person taking longer than you would isn't necessarily a reason to intervene.
A person choosing a different method isn't necessarily a reason to intervene.
An incomplete first recommendation isn't necessarily a reason to intervene.
Feeling uncomfortable while someone else works through a problem isn't, by itself, a reason to intervene.
Sometimes the leader's discomfort is the thing that needs to be managed.
Support should change as capability grows
People don't need the same amount of support forever.
A new employee may initially need direct instruction. They may need to see the work demonstrated and understand the reasoning behind it.
The next time, the leader might complete the work alongside them.
After that, the employee may take the lead while the leader observes.
Eventually, the employee should be able to make the decision independently and explain the reasoning afterward.
The progression might look like this:
- I'll show you how and explain why.
- We'll work through this together.
- You lead, and I'll remain available.
- You decide within these boundaries.
- You act independently and tell me what you learned.
Development becomes difficult when support never changes.
If the leader continues providing answers long after the person is capable of reasoning through the problem, the relationship remains fixed at an earlier stage.
If the leader withdraws support before the person has enough context or experience, responsibility moves faster than capability.
The work is to adjust support deliberately.
Ask for thinking before giving an answer
When someone brings a problem, the leader doesn't need to begin with a solution.
A few questions can reveal whether the person needs instruction, context, permission or simply more room to think:
- What decision are you trying to make?
- What do you know so far?
- What have you already considered?
- What options do you see?
- Which option do you recommend?
- What risks concern you?
- What support do you need from me?
These questions shouldn't become a ritual for withholding help.
Their purpose is to make the person's thinking visible.
Sometimes the conversation will reveal that they genuinely need direction. Sometimes it will show that they already know what to do but lack confidence or clarity about their authority.
In that case, the most useful response may not be an answer.
It may be permission.
The leader is developing too
Safe struggle isn't only difficult for the employee.
It asks something of the leader.
Many leaders were promoted because they were good at solving problems. Their competence created credibility, recognition and opportunity.
Then leadership changes the nature of their contribution.
They're no longer responsible only for producing good answers. They're responsible for developing people who can produce good answers without them.
That requires a different way of experiencing usefulness.
The leader may know the answer and choose not to begin with it.
They may watch someone take a longer route.
They may accept a reasonable decision that isn't the decision they would have made.
They may allow a manageable mistake and then help the person learn from it.
None of this means becoming indifferent to quality.
It means recognizing that today's outcome isn't the only outcome being created.
The person's future capability matters too.
A practical test before stepping in
When you feel the urge to take over, pause long enough to ask:
- Is there an immediate safety, legal, ethical or irreversible risk?
- Does the person understand the required outcome?
- Do they have the authority and information needed to proceed?
- Is the possible mistake recoverable?
- Have I asked for their reasoning or recommendation?
- Would stepping in develop their judgment, or replace it?
- Am I responding to the actual risk, or to my own discomfort?
If the conditions are clear and the consequences are manageable, the best form of help may be to remain available while allowing the person to continue.
The longer view
Strong teams aren't built by leaving people alone.
They're also not built by preventing people from experiencing difficulty.
They're built when leaders create clear boundaries, provide appropriate support and allow people to carry increasingly meaningful judgment.
That process can be slower than supplying the answer.
It can feel uncomfortable.
It can produce decisions that look different from the ones the leader would have made.
But over time, it creates something more valuable than immediate efficiency.
It creates capability.
The leader who sat in my office that day stayed close enough to support the work while leaving enough room for someone else to grow.
That is the balance.
Sometimes the most useful thing a leader can do is not remove the struggle, but make it safe enough to learn from.