The Question You Keep Answering For Your Team Is the Reason They Never Learn to Decide

The four-dollar freeze

On a weekly team call, Shaina Ballesteros was stuck. Buzzsprout or Transistor. Fifteen dollars a month or nineteen. A four-dollar difference. She said she was afraid of getting it wrong.

Same call, Sophia Mendoza had just come off a cold-email campaign that spent real money and produced nothing. She said she was disappointed in herself.

Here is what most leaders would do. Answer Shaina's question so the meeting moves on. Quietly note that Sophia can't be trusted with the next budget. Both moves feel responsible. Both are wrong, and both are the same mistake wearing different clothes.

What you're actually delegating

Most delegation fails for one reason: it hands off what to do and never touches how to think about it. You write the SOP, you hand it off, you check back later, and you wonder why the team still can't move without you. They're not short on checklists. They're short on the thing you see and they don't.

Delegation: the transfer of how to think about a problem, not what to do about it. Handing someone a task without the reasoning behind it is not delegation. It's dictation with extra steps.

That's why "I don't answer questions" is the habit worth building, and why it sounds arrogant until you understand it's the opposite. When someone asks "how should I handle this," the move is "how do you think it should be handled." Not to dodge them. To make them do the reasoning out loud, so they see the answer themselves. They grow more in five minutes of thinking it through than they ever would from a one-line directive. (There's a real exception: when withholding information would be bad leadership, you answer. The habit is pushing the question back, not going silent.)

The freeze was never about the money

Shaina was frozen over four dollars a month. Sophia had just lost almost a thousand pesos deciding wrong. The one with less to lose had more fear. That's not a math problem. That's a permission problem.

Name what's actually happening in that room: Shaina isn't bad at math, she's scared of being blamed for choosing. And the reflex to "fix" that is to just tell her which service to pick. Which teaches her, permanently, that deciding is dangerous and someone else will catch it if she waits long enough.

So here's the turn. The person Atiba handed more budget to wasn't the one who'd been careful. It was Sophia, the one who'd just burned money and gotten nothing for it. He told her: you get to decide whether we spend even more on it. She said she wanted to. He said okay.

If he'd treated her failed campcampaign as proof she needed less authority, both women would have learned the same lesson: deciding is dangerous, so don't. Instead the failure became the credential. That's the part that doesn't compute for most leaders, and it's the part that matters most in this whole piece. Everything else here is commentary on that one move.

The reflex vs. the return

Name the fear, because it's real

You will resist this, and the resistance isn't laziness. Handing a bigger budget to the person who just lost money on the last one feels reckless. It costs you the comfort of being the one who catches mistakes before they happen. It costs your ego the hit of not being needed for every call. And it means sitting through the discomfort of watching someone reason slowly toward an answer you already have, instead of just saying it.

That discomfort is the whole job now. If you skip it and answer anyway "just this once," you've told the team the real rule: bring me the question, I'll bring you the answer. They will comply with that instruction forever.

Evidence over metric

There's a second decision buried here, and it's not about you delegating, it's about what you trust when you decide who earns more room. Atiba's son, a recruited college quarterback, chose between two schools. One ran the offense he wanted, in a place he'd hate living. The other was the reverse. He picked based on the coaches who'd sent him three handwritten postcards a week, not the offense.

He ended up hating the system he played in. And at graduation four years later, those same coaches came up, shook his father's hand, and said they remembered recruiting him.

Choosing on the flashier variable (the offense, the bigger spend, the impressive résumé) gives you the thing on paper. Choosing on demonstrated behavior, how someone has already treated the relationship, gives you the thing that's still true four years later. Sophia's disappointment in herself wasn't a mark against her. It was the postcard. It was evidence of ownership, and ownership is what you're actually trying to buy when you hand someone a budget.

Why this feels slow, and why that's not a bug

If you're running an existing team, you're not building from scratch. You're steering people who are already aboard. There are only two ways to change how a team behaves: replace the people, or steer the ones you have. If you're not willing to fire everyone, you've already chosen the slow path, and being impatient with how long it takes is being impatient with a choice you already made.

Returning questions instead of answering them is a culture change, not a policy change. It won't look different next week. Frame it against the brutal alternative (replace the crew) and the slow path stops feeling imposed on you and starts feeling chosen.

flowchart LR
A[Team member has a question] --> B{Your reflex}
B -->|Answer it| C[They wait for you next time]
B -->|Return it: 'How would you handle it?'| D[They reason it out loud]
D --> E[They see the answer themselves]
E --> F[They own the decision]
F --> G[You