A program coordinator comes in with a difficulty. A grant reporting requirement has changed and the new format does not fit how the data has been collected all year.
The conversation lasts eleven minutes and is entirely constructive. It ends with the executive director saying she will look at the reporting template over the weekend and get back to him.
The problem walked in belonging to him and walked out belonging to her. Neither person noticed, both feel the meeting went well, and he is now waiting on her before he can proceed.
The transfer happens in one sentence
William Oncken and Donald Wass described this in the Harvard Business Review in 1974 and the mechanism has not changed since. Their point was that the ownership of a task moves at a precisely identifiable moment, and that the moment is nearly always a sentence the manager volunteers.
The sentences are recognisable. Let me look into it. Leave it with me. I will talk to the funder. Let me think about that and come back to you.
Each is generous, each is meant, and each ends the conversation with the next action on your list rather than theirs. That is the entire test, and it can be applied in real time: when this meeting ends, who does the next thing?
Why it happens
It is tempting to read this as somebody offloading work, and occasionally it is. Mostly it is not, and treating it as a character problem produces the wrong correction.
The person bringing the problem is usually doing something rational. They are unsure whether the decision is theirs, and the cost of guessing wrong falls on them. They have observed that this leader takes problems and solves them quickly, which makes bringing problems an efficient move. Nothing in their environment has told them otherwise.
The leader is also doing something rational in the moment. Solving is faster than coaching, it is satisfying in a way that most of their day is not, and they usually can solve it faster. The whole exchange is two people optimising locally and producing a result neither wants, which is a leader carrying twenty problems that belong to eleven other people.
The sentences that send it back
Refusal does not require being unhelpful, and the useful versions are short.
What do you think we should do? Asked early, before you have engaged with the substance. Most people arrive with a view and have not been asked for it. A surprising share of these conversations end there.
Come back with two options and a recommendation. This converts an open problem into a defined piece of work that remains theirs, and it is the correct response when they genuinely need your decision. You are not refusing to decide. You are refusing to do the analysis.
That one is yours. What would help? The second half matters. Support without ownership is a real offer, and it distinguishes returning the problem from abandoning the person.
Before we finish, who has the next step? The single most useful habit available here. Said at the end of any problem conversation, out loud, it catches nearly every unintended transfer, because the answer is either their name or yours and both parties hear it.
When you should take it
Three cases, and outside them the answer is generally no.
The decision genuinely sits above their authority, in which case taking it is not upward delegation but correct routing, and the useful addition is to say why so the boundary becomes clearer for next time. The problem requires information they cannot access, such as something a board discussed in closed session. Or the person is genuinely overloaded, in which case taking it is humane and should be said aloud as temporary: I am taking this one because your week is impossible, and it comes back to you in October.
Naming it as temporary is what preserves the underlying arrangement. A silent rescue is indistinguishable from a permanent transfer.
Read the pattern before correcting it
One person doing this repeatedly is information, and the correction depends entirely on which of three things is happening.
They may not have the authority the work requires, in which case the upward flow is not a failing but an accurate report on an arrangement you set up. They may have the authority and lack the confidence, which is developmental and resolves with a named level and a few decisions you let stand. Or they may be avoiding the exposure of deciding, which is a different conversation and should be had directly rather than through a series of returned problems.
Applying the third correction to someone in the first situation is a common and expensive error, and the person on the receiving end will find it bewildering, because from where they sit they have been asking permission for exactly the things they were told to ask permission for.
Edited by Patrick J. Wolf, PhD