In partnership with
Did you know I have two self-paced courses available? You can level up your leadership practice in your own time with these affordable courses. Learn more.
There's this instinct most leaders have: when someone asks a question in a meeting, you jump in. You have context, you have an opinion, and you want to be helpful, so you answer. It's not that you're wrong. It's that by answering, you might be stepping over the person who should have spoken, missing the chance to develop someone on your team, or framing something in a way that doesn't land with the audience.
The impulse to be the person with the answer is pretty deeply ingrained in how most of us learned to lead: prove your expertise, add value, be useful. But intentionality and restraint are the opposite of that impulse, and they're often what the room actually needs from you.
A friend shared a framework with me recently that I think is a really good lens for this. Before you answer a question or jump into a conversation, ask yourself three things.
1. Does this need to be answered right now?
Not everything requires an immediate response, and some things don't need your input at all. The first check is whether this is even a moment that calls for an answer, or whether acknowledging the question and letting it sit is the better move. It's important to acknowledge whether something is actually asking for your input before you just jump in with your opinion. Sometimes the most useful thing you can do is say "let me think about that" or "let's come back to this when we have more information." This is a muscle that requires building over time.
2. Am I the right person to answer?
This is related to the first, but instead of "does it need an answer," the question is "should the answer come from me?" Is there somebody else in the room who has more information, more context, or more visibility into the problem? This matters a lot when you're a manager in a room with your direct reports. If your product manager has deeper knowledge on the topic, letting them answer does two things: the team gets a better answer, and your product manager gets the visibility and ownership they should have. Jumping in because you can answer isn't the same as being the right person to.
A thank you from this week’s sponsor:
Find out why 200K+ engineers read The Code twice a week
Staying behind on tech trends can be a career killer.
But let’s face it, no one has hours to spare every week trying to stay updated.
That’s why over 200,000 engineers at companies like Google, Meta, and Apple read The Code twice a week.
Here’s why it works:
No fluff, just signal – Learn the most important tech news delivered in just two short emails.
Supercharge your skills – Get access to top research papers and resources that give you an edge in the industry.
See the future first – Discover what’s next before it hits the mainstream, so you can lead, not follow.
3. How should I frame this?
If you've cleared the first two and the answer is yours to give, then the question becomes how. Are you speaking to a technical audience or a cross-functional one? Should you go deep or stay high level? Is this a moment for a definitive answer or for raising the question in a way that opens up discussion? Make sure you’re formulating your answer in a way that will resonate for your current audience, and if you’re unsure, you can always follow up by asking if your response was clear.
I was coaching a manager recently who had a good example of this playing out in a group setting. Someone asked a question in a meeting, and his instinct was to answer it. He knew the answer, and the room was waiting. In any normal situation, he’d just jump in. Here’s what it looks like instead to pause and ask those three questions.
Does this need to be answered right now? Maybe. It was a fair question. But he didn't have the full picture, and jumping in without it would've meant giving an incomplete answer that the room would treat as final.
Am I the right person to answer? His product manager was sitting right there. She had more context, was closer to the details, and was the person who actually owned the work. If he answers, the team hears from him instead of her. She doesn't get the visibility, the team doesn't hear from the person closest to the decision, and the hierarchy of who owns what gets a little muddied.
How should I frame this? In his case, the right move wasn't answering at all. It was giving his product manager the floor. And if he did need to add something afterward, he had to think about whether he was about to frame it too technically for the audience or whether he should adjust. In this situation, the best way to frame this would be to offer to have his product manager answer the question, teeing her up.
A lot of managers jump in because they can, not because they should. The instinct makes sense. You got to where you are by being competent, by having answers, by being the person people relied on. But as a leader, your job shifts. You're not just the person with the answer. You're the person who makes sure the right answer comes from the right person, framed the right way, at the right time. Restraint actually builds more credibility than always being the one who speaks first. It signals that you trust your team and that you're thinking about more than just the immediate question.