Ask Questions

Early in my career, I sat in meetings and stayed quiet. I had questions. Plenty of them. But I was scared that asking would expose how much I didn't know.

That fear cost me years.

The truth about questions

When you ask a question, you're doing two things at once. You're showing the speaker you're engaged. And you're helping them communicate more effectively — because good questions force clarity.

I've been in architecture reviews where one well-placed "why?" from a junior engineer changed the entire direction of the conversation. The senior folks were too deep in assumptions to see the gap. The junior wasn't afraid to point at it.

Not all questions are equal

There's a spectrum. Some questions build awareness: "What does this service do?" Others require analysis: "How does this interact with the billing system under load?" The deeper questions are harder to ask — and harder to answer. But they're the ones that move projects forward.

Here's a rough hierarchy I keep in mind:

• Knowledge — What is this thing?
• Comprehension — How does it work?
• Application — How do we use it in practice?
• Analysis — What happens when it interacts with everything else?
• Synthesis — How do we combine what we know across systems?
• Evaluation — Is this the right approach?

You don't always need to operate at the top of that list. Basic questions are perfectly valid. I still ask them constantly.

The real fear

The fear of looking dumb is universal. But here's what I've learned after 15+ years: the people who ask the most questions are usually the ones who grow the fastest.

The ones who stay silent? They stay stuck.

Ask the question. Every time.