For years, I could turn a problem into a plan before the person explaining it had finished talking.
A client needed attention. A process was breaking. A number was moving in the wrong direction. I would start connecting the pieces, assigning the work, and deciding what happened next.
That ability helped me build a company. It also created a habit I eventually had to undo.
The people around me knew their work. They had information I didn’t have and experience I needed. But when an issue reached me, I often supplied the recommendation before they had a chance to develop or explain their own.
Over time, bringing me the problem became enough to get a plan. I had made that the most reliable way to move work forward.
Then I wondered why so many decisions still needed me.
The cost of always having an answer
Solving something yourself can be faster in the moment. You know the history, you see a familiar pattern, and you want to help. When the calendar is full and a customer is waiting, answering feels responsible.
The cost is harder to see because it shows up later.
People begin checking with you on decisions they could make themselves. Meetings become updates followed by your instructions. Work waits while you’re traveling or handling something else.
You can mistake that dependence for evidence that you need to stay involved. I had to consider how much of it my own behavior had created.
If I wanted my leaders to bring their judgment into the room, I had to leave room for it. That meant resisting the urge to turn every concern into my own execution plan.
My responsibility is to make the direction clear. My leaders work together to recommend how we get there, build the plans, and own the results.
They also need room to question an assumption or tell me when a goal requires a different approach. Their knowledge should influence the direction, too.
The standard I introduced
For planned decisions that need my involvement, I ask leaders to arrive with four things. I call it decision-ready.
- The decision needed. What call do we need to make? State it clearly enough that we know what we’re discussing.
- The options. What approaches have you considered, and what are the tradeoffs? Bring meaningful alternatives when they exist. A second option invented to fill a template doesn’t help anyone.
- Your recommendation. Which approach do you recommend, and why? What information supports it? What are you still unsure about?
- The impact. What could this mean for revenue, cost, customers, team capacity, time, or risk? Use the measures that matter to the decision, and distinguish estimates from what we know.
For scheduled discussions, the expectation is one page, shared 24 hours before the meeting. That gives everyone time to read, consider the recommendation, and identify questions.
The point is to make the thinking visible before the discussion begins. A concise brief helps us spend the meeting evaluating a recommendation instead of discovering what decision we’re supposed to make.
There are exceptions. An urgent customer issue or emerging risk needs to reach the right person immediately. Nobody should delay raising a concern because they haven’t prepared a document. Sometimes the next step is getting help to understand the problem well enough to develop options.
Preparation should improve decisions. It should never make it harder to surface a problem.
Changing an expectation means explaining it
Some of the people who worked well under the old approach had good reason to find this change frustrating.
They knew their areas, kept me informed, and followed through on the plans we discussed. That was how we had worked. Asking for a recommendation and an impact assessment changed what preparation looked like and what responsibility they carried into the meeting.
I needed to acknowledge that.
I built the old pattern. I was asking us to change it. My team deserved to hear both parts before being held to a different standard.
A higher expectation also requires clearer authority. Which decisions can a leader make independently? Which require coordination with another department? Which need my approval? Asking someone to take ownership while leaving those boundaries unclear creates more hesitation.
And when a recommendation needs work, the feedback has to be specific. Is the customer impact missing? Does the plan depend on capacity we don’t have? Is there an assumption we need to test?
“Bring me a better plan” gives someone far less to work with than explaining what the decision still needs.
What changed when I stopped answering first
The first weeks were slower.
Some discussions got quieter. Some items came back without enough preparation, and we had to revisit them. I had to resist filling every pause with the plan I was already building in my head.
That discomfort was part of changing the habit. I couldn’t ask people to think through a recommendation and then take over as soon as the conversation became difficult.
Gradually, plans arrived that I wouldn’t have built myself. People closer to the customer or the day-to-day work brought details I would have missed. The discussion had more to work with because I hadn’t decided the approach before hearing them.
I also had to be careful about how I interpreted silence. A quiet room doesn’t tell me whether people agree, need more information, or see a problem they haven’t voiced yet.
Before a decision is made, the questions matter: What are we missing? Who sees this differently? What would make this plan difficult to carry out?
Leaders have a responsibility to prepare and speak up. I have a responsibility to make their contribution useful by listening before I settle on an answer.
Where my responsibility remains
I still make final calls where they’re mine to make. I remain accountable for the company’s direction, priorities, and performance.
But I don’t need to generate every option to make a sound decision. I need to understand the recommendation, examine the assumptions, and make sure the people responsible have the authority and resources to act.
Once we agree on a plan, ownership needs to be clear: who is responsible, what result we’re working toward, when we’ll review progress, and what should trigger an earlier conversation.
Without that clarity, even a productive meeting can end with everyone carrying a different understanding of what happens next.
The harder test comes when a leader chooses a reasonable approach that differs from mine. If I rewrite it simply because I would have done it differently, I teach the team to anticipate my preference instead of exercising judgment.
I have to distinguish a material concern from a personal preference. Sometimes I need to intervene. Other times, I need to let a capable person lead.
Try it in your next meeting
Start with one recurring discussion where you usually supply the solution.
Before the meeting, ask the person responsible to bring the decision, relevant options, a recommendation, and the likely impact. Be clear about which decisions they already have authority to make.
During the discussion, ask for their recommendation before offering yours. Give them time to explain it. Ask about uncertainty and concerns, then agree on the next step and who owns it.
If the preparation is incomplete, identify what is missing. If the issue is urgent, address it and improve the preparation afterward.
Then pay attention to your own behavior. How quickly do you interrupt? Do you ask questions to understand, or to steer someone toward the answer you already prefer? Once you approve a plan, do you give the owner room to carry it out?
Those are the habits I’m working on, too.
I spent years developing the ability to walk into a meeting and build a plan. Now I have to recognize when doing that prevents someone else from contributing theirs.
I still bring experience, questions, and accountability to my meetings. I’m learning to leave more room for the people I hired to bring their judgment.
Keep reading: Delegation Is Leadership and Lead the Agent, Don’t Be the Assistant.