Building capability without creating dependency
Help can solve a problem today and develop the ability to handle tomorrow’s problem. The way we provide it determines how much of each happens.
A person asks for help with a difficult task. We solve it, and they move forward. Later, they return with another version of the same difficulty. The immediate result was useful, but the understanding required to produce it has not necessarily travelled with them.
I recognise this tension in conversations about careers, learning and getting things done. People often arrive with a result they need. A document. An answer. A decision. When the need is pressing, the process can seem like an inconvenience.
The helper faces a choice about how much of the reasoning to reveal and how much of the work to leave with the person. Giving the complete answer can be efficient. It can also leave the person dependent on access to someone else’s judgement.
That does not make the immediate help wrong. A beginner may need a worked example. Someone facing a deadline may need direct intervention. A person can face barriers that require continuing support. The useful question is what should happen after that first result.
Capability involves more than having seen the answer. The person needs to understand what mattered, make an attempt and receive feedback. They need opportunities to recognise a familiar pattern when its appearance changes.
Consider career support. A strong CV can help someone apply for a role. If every section has been produced for them without explanation, they may struggle to describe the evidence in an interview or adapt it to the next opportunity. The document is useful, but the person’s ability to interpret and communicate their own experience still needs work.
An approach that develops capability would involve asking the person to identify the problem they addressed, the decisions they made and the evidence of their contribution. The helper can improve the structure and language while explaining why a particular example is relevant. The next attempt gives the person more responsibility.
The same issue appears in organisations. A consultant can produce a recommendation that is accepted but remains difficult for the team to use. If the reasoning, trade-offs and ownership are unclear, the organisation may need another intervention when circumstances change.
A useful engagement leaves people able to make decisions with the work. That may require explaining the assumptions, involving them in the analysis and making the limits visible. A handover matters because the context will continue to develop after the adviser leaves.
There is a balance to find. Withdrawing support too early can become abandonment. Holding every decision indefinitely can prevent development. The balance depends on the person’s current capability, the risk of the task and the quality of the feedback available.
I find three questions helpful. What can the person do now? What should they become able to do? What part of the next attempt can they reasonably own?
Those questions turn a general desire for independence into a practical development path. They also reveal whether the person has the authority and resources required. Responsibility without the means to act can look like an invitation to grow while actually creating frustration.
When I help someone, I want to pay attention to what they carry away. The immediate answer may be necessary. The understanding behind it creates the possibility of meeting a future problem with greater confidence and less dependence.