Do not bring me problems. Bring me solutions.

Managers repeat it to each other like wisdom. It is bad advice.

What reaches your desk is the residue. Your people solve things all day and you hear about almost none of it, because a solved problem is not news. It surfaces later, in a status report, or a performance review, or when somebody wants to share a win. If they could have solved it, it would not be on your desk.

So the rule taxes exactly the conversations you most need to have, and the tax gets paid two ways. Some people stop coming. The problem does not pause while you are not hearing about it. It matures, and you find out a quarter later, when it is expensive and the week-one options are gone. The rest invent something. They arrive with a fix built to satisfy the rule rather than to solve anything, and now you are evaluating their invention instead of examining the problem. That one is worse. It looks exactly like the conversation you asked for.

The instinct behind the line is not stupid. It is aimed at a real person: the one who forwards a customer complaint with thoughts? attached and calls that an escalation. But you do not fix that person with a standing rule that taxes everybody, including the people carrying the problems you cannot afford to hear about late.

If they could have solved it, it would not be on your desk.

You get the escalations you trained for

A leader I was coaching came to me frustrated about his team. He was spending nearly all of his time with them, and not in a good way. They pulled on him constantly, every decision seemed to route through him, and he wanted to talk about how to make them more independent.

I told him it was his fault, not theirs.

He had conditioned them, and it is almost always one of two things. Either he had not empowered them, so they did not believe they were allowed to decide. Or he had not enabled them: they were allowed, but they did not have what deciding actually requires. The context, the numbers, the access, the authority to spend. From where he was sitting those look identical. They have different fixes.

On their side there were two possible reasons they kept coming, and those look identical too. Either they thought they had to. Or they thought he wanted them to.

The second is the uncomfortable one. A leader who is good at this is a pleasure to bring things to: quick, decisive, visibly useful in the moment. If being consulted is the thing you are best at, people notice, and they will supply more of it. You can build a queue outside your own door without ever asking for one. And your own job stops getting done.

He wanted a technique for getting his team to back off. What he needed was to undo what he had taught them, then teach them something more valuable in its place.

Ask for the problem, not the symptom

Two things are worth demanding when somebody brings you something. Neither is a solution.

The first is clarity about what we are actually trying to solve.

Nearly everything that arrives is a symptom, because symptoms are the part you can see. The release slipped. The customer escalated. The number missed. Those are events. Fix an event and you will fix it again next month, and the month after, and eventually you will decide you have a people problem when what you have is a system that keeps producing the same event.

So I start by questioning. Not the person, the framing. What makes you think that is the cause? What else would be true if it were? What did you rule out, and how?

Warn people you are going to do this, because the first time it happens it does not feel like support. Somebody has carried a problem for two weeks, they finally bring it to you, and what they get is interrogation. Unexplained, that reads as doubt about them. Explained, it reads as what it is. A well-run fix aimed at the wrong thing is worse than no fix at all, because it also spends the time you had to find the real one.

This is where the work they have already done belongs. Bring me what you tried, and what you considered and set aside. Not as a proposal. As evidence. Four things somebody ruled out tells me more about the shape of a problem than one thing they are recommending.

Then tell me what you need from me

The second thing takes one sentence, and almost nobody offers it unprompted.

  • I am informing you. We have a problem and I am working on it. I wanted you to know.
  • I want your influence. We have a problem and I have a few directions I could go. I want your perspective to help me select the best one.
  • I need you involved. We have a problem and I am stumped. I need your help.

That sentence decides everything about what I do next: how I prepare, how much time I put against it, and whether anybody else needs to be in the room. An informing conversation needs five minutes and no preparation from me. An involving one might need an hour, two other people, and something moved off the calendar to make space for it.

I am a compartmentalized thinker by nature, so sorting work this way suits how I am built. That is not the reason to do it. The reason is that getting it wrong costs in both directions.

If I treat an involve as an inform, I nod, they leave with nothing, and we both find out in three weeks. That is the obvious failure, and the less damaging one.

The other direction does not look like a failure at all. When the ask is not stated, a senior person will assume the largest version of it. Somebody brings me a problem, I find it interesting, I have opinions, and ten minutes later I am running it. They came to keep me informed about something they had well in hand. They leave having handed it over. Not because they wanted to, and not because I decided to take it, but because neither of us said what the conversation was for. Do that a few times to a capable person and they will stop telling you things.

The one nobody says

Of the three, the third is the hardest to say, and it is the one you most need to hear.

Left to themselves, most people file I am stuck as an inform. Just keeping you posted. They do it because asking for help feels like a report card, and because nothing in most organizations has told them otherwise.

The value of naming the three is not that it is a tidy list. It is that it puts being stuck on the menu: an ordinary category of conversation rather than a confession.

How you teach it

Not with a form, and not by hinting at it. The homework I gave him was one staff meeting, in three parts, and the order is the whole thing.

  • First, the expectations. Say plainly what you expect them to run without you. Not a general encouragement to take ownership. The actual scope. These decisions are yours.
  • Second, the backing. If you make a call that turns out to be wrong, and you made it with sound judgment on what you knew at the time, I will back you. This is what makes the first part real. Authority without cover is not authority, it is exposure, and people can tell the difference immediately.
  • Third, and only then, the ask. When you do need me, tell me which of the three it is, because clarity is what lets me be useful quickly. Inform, influence, or involve.

Reverse that order and none of it works. Ask for the three sentences before you have granted the authority and promised the cover, and everything comes back as I need you involved, because that is the only safe answer available. The three do not create independence. They give independent people a clean way to ask for help, which is a different thing, and worth nothing without the first two parts.

After the meeting, you teach it by asking. Somebody starts in and you stop them. Before we get into it, what do you need from me today? The first several times they will not have an answer, and that is the finding, not a failure of the question. After a month or two they open with it. Not long after that they arrive having already worked it out, which is where the real value is. Deciding what you need from your boss forces you to establish what you already have.

You own this

Whatever your people do when they hit something hard, you taught them to do it. You may have allowed it, or asked for it indirectly, or wanted it. Which one hardly matters. As the leader you own it, and you are the only person in the building who can change it.

Managers manage. Leaders lead. A manager works the queue: takes escalations as they arrive, sorts the real ones from the noise, and is busy and useful all day. A leader decides what the queue is made of. Same inbox, different job, and only one of the two scales.

Do it routinely and the business gets stronger in two places at once. Your team owns its work, because you told them what was theirs and then proved you meant it the first time somebody got a call wrong. And what does reach you arrives already shaped, so your attention goes to the decisions that actually need you.

None of that comes from a rule about bringing solutions. It comes from telling people what is theirs, backing them when a sound call goes wrong, and asking for one sentence when they need you: inform, influence, or involve.