Answer-Giving to Thinking-Enabling: The Questions Strong Technical Leaders Ask

One of the greatest gifts coaching has given me is an appreciation for the power of questions.

Not clever answers. Not polished advice. Questions.

Questions such as what, how, and when. And yes, the occasional why—used sparingly, because “why” can sometimes feel like an interrogation rather than an invitation. Questions are the foundation of coaching because they help people think instead of simply following instructions.

The more I coach, the more I realise that this principle has enormous value in technical leadership.

As technical professionals, we are often promoted because we have the answers. We know the standards, the calculations, the code, the specifications, or the design process. Naturally, when someone comes to us with a problem, our instinct is to solve it.

The challenge is that what made us successful as engineers does not necessarily make us successful as leaders.

Leadership is less about having the right answer and more about helping others develop the ability to find it.

When Technical Leaders Become Human Search Engines

In a previous article, we explored the downside of leaders always being the person with the answer. When every decision flows through one individual, several things begin to happen:

• Team members learn to escalate instead of think.
• The leader becomes the project’s bottleneck.
• Engineers optimise for approval rather than outcomes.
• Critical assumptions remain hidden because nobody is challenged to articulate them.
• People execute decisions they do not fully understand.
• The team misses valuable opportunities to build decision-making capability.

Most leaders recognise these symptoms. Yet many continue answering every question because it feels faster.

It usually is—today.

Tomorrow, however, the same questions return.

Borrowing a Coaching Tool: The GROW Model

One of the foundational coaching frameworks is the GROW Model:

• Goal – What are we trying to achieve?
• Reality – What is true about the current situation?
• Options – What possible paths exist?
• Way Forward – What action will we take, and by when?

Although developed for coaching conversations, it adapts remarkably well to everyday technical leadership.

Whether you’re discussing a design issue, resolving a construction challenge, reviewing a programme, or helping an engineer think through a difficult decision, these four stages create a conversation that develops capability instead of dependency.

Notice where the conversation finishes.

Not with “Here’s what you should do.”

But with “What are you going to do, and by when?”

That’s where ownership begins.

Goal: What Are We Trying to Achieve?

Technical conversations often jump straight into solutions before everyone agrees on the problem.

Start by establishing the goal.

Instead of asking:

“What’s wrong?”

Try asking:

• What outcome are we trying to achieve?
• What does success look like?
• What decision needs to be made today?
• If we solve this well, what changes?

These questions align everyone’s thinking before the discussion dives into technical detail.

Reality: What Is Actually Happening?

Engineers are trained to work with evidence, yet discussions sometimes become filled with assumptions.

Reality questions help separate facts from opinions.

Examples include:

• What do we know for certain?
• What evidence supports that conclusion?
• What assumptions are we making?
• What constraints are influencing this decision?
• What have we already tried?

Often, simply asking these questions uncovers information that changes the entire direction of the conversation.

Options: What Else Could We Do?

This is where coaching becomes especially valuable.

Instead of presenting your preferred solution immediately, encourage your team to generate alternatives first.

Ask questions such as:

• What options have you considered?
• If this approach wasn’t available, what else might work?
• What are the advantages and disadvantages of each option?
• Which option carries the greatest risk?
• Which option best meets our project objectives?

Your expertise still matters.

The difference is that you contribute after your team has exercised their own thinking.

Way Forward: What Will You Do?

This is where conversations become commitments.

A discussion without a clear next step is simply an interesting conversation.

Helpful questions include:

• What will you do next?
• When will you complete it?
• What support do you need?
• How will we know the issue has been resolved?
• When should we review progress?

If every technical conversation ends with clear ownership, defined actions, and agreed timelines, accountability becomes part of the team’s culture rather than something the leader has to enforce continually.

Questions That Build Better Engineers

Different questions develop different capabilities.

Questions that develop judgement

• What information is influencing your recommendation?
• What assumptions could prove incorrect?
• What risks concern you most?
• If this decision failed, what would likely have caused it?
• What evidence would change your mind?

Questions that develop initiative

• What have you already tried?
• What would you do if I wasn’t available?
• What’s your recommended solution?
• What’s stopping you from implementing it?
• What would you do first?

Questions that develop ownership

• Who owns this decision?
• What commitment are you making?
• By when will it be completed?
• How will you communicate progress?
• What support, if any, do you need from me?

Notice the pattern.

None of these questions remove the leader from the process.

They simply move the leader from being the answer-giver to becoming the thinking partner.

A Simple Framework for Better Technical Conversations

The next time someone approaches you with a problem, resist the temptation to answer immediately.

Instead, try this simple sequence:

1. Pause – Don’t rush to solve the problem.
2. Clarify – Understand what decision or problem is actually being discussed.
3. Invite thinking – Ask what the person has already considered.
4. Probe – Explore assumptions, evidence, risks, and alternatives.
5. Transfer ownership – Make it clear who owns the decision.
6. Confirm action – Agree on what will happen, by when, and how progress will be communicated.
7. Teach when needed – Add your expertise after the person has had room to think.

It may feel slower initially.

In reality, you’re investing time once instead of solving the same problem repeatedly.

Final Thoughts

Many technical leaders believe their value lies in having the right answers.

That’s certainly valuable.

But the leaders who create high-performing teams offer something even more powerful: they help other people develop the ability to think well.

Every question you choose not to answer immediately becomes an opportunity to build judgement, confidence, ownership, and capability within your team.

The next time someone walks into your office—or pings you on Teams—with a problem, resist the urge to become the solution.

Instead, ask a better question.

You may discover that the strongest technical leaders aren’t remembered for always having the answers.

They’re remembered for helping others find their own.