I’ve been managing engineers for a while now, and if there’s one thing I keep relearning, it’s this: telling people what to do almost never works as well as you think it will.
You’d think it would, right? You have the context. You’ve been in the weeds. You know the answer. So why not just share it and save everyone the trouble?
Because it doesn’t build anything lasting.
What actually happens when you tell
When you tell someone the answer, a few things happen:
- They execute your solution, not theirs. They don’t own it the same way.
- They learn that you’ll solve it for them. Next time, they wait for you.
- You miss context you didn’t know you were missing. Your solution might be wrong in ways you can’t see from your vantage point.
I’ve done this more times than I’d like to admit. I’d jump into a design review with “just do X” and then wonder why the team wasn’t developing their own judgment over time.
The ask, don’t tell shift
The ask, don’t tell principle is simple: when someone brings you a problem, respond with questions instead of answers.
Not interrogation. Not “why didn’t you think of this already?” Just genuine curiosity.
Instead of “you should use a queue here,” try:
- “What happens if the downstream service is slow?”
- “How would you handle retries?”
- “What’s the simplest version of this that would work?”
The questions aren’t leading. You’re not guiding them to your answer. You’re helping them think through the problem more thoroughly.
Why this is hard
It’s hard because:
- It feels slower. It is slower — in the short term.
- It requires trust. You have to believe your team can figure it out.
- It’s uncomfortable to watch someone struggle when you know the answer.
But here’s the tradeoff: you’re slower today so you can be faster tomorrow. Every time someone works through a problem with your help (not your answer), they get better at solving the next one.
When to break the rule
Not every situation calls for questions. Sometimes you need to be direct:
- Production is on fire. Just tell them what to do.
- Someone explicitly asks for your opinion. Give it to them.
- The stakes are high and they’re clearly stuck. Offer a starting point, not a full solution.
The principle isn’t “never give answers.” It’s “default to questions.”
The meta-lesson
Here’s what I find interesting: the ask, don’t tell principle applies to more than just management. It’s how good parents operate. It’s how good teachers operate. It’s how good therapists operate.
The pattern is always the same: help people develop their own capacity rather than creating dependency on yours.
It’s the hardest shift to make as a new manager, and the most important one.