The Difference Between Helping and Rescuing Your Team
The difference between mentoring and coaching — and why it matters for your team's growth
This is Empathy Elevated - your weekly guide and shortcut to mastering emotional intelligence through the power of empathy. Last week, I wrote Leadership Observability: Making Your Intentions and Values Queryable
Emotional Intelligence • Stoicism • Human–AI Partnership
Practical frameworks for clearer communication, better judgment, and less friction in modern work.Some of the best conversations start with a cold message.
About a month ago, Roman Nikolaev reached out, not to pitch something, but to connect. He’d been thinking about leadership and emotional intelligence in tech. So had I. The conversation found its footing fast.
Roman spent 20 years as an engineer before leadership found him. He didn’t chase management. He was building software, and then one day, he was building team culture and helping team members realize their potential. He learned most of it the hard way. In November 2025, he started the High-Impact Engineering Substack to share what he learned, for the engineers and leaders figuring it out in real time.
I’m glad he reached out. I’m glad to have his voice here.
What follows is something worth sitting with. There’s a difference between solving someone’s problem and actually developing them. One builds dependency. The other builds capacity.
Here’s Roman.
~Colette Molteni
Give a person a fish, and you feed them for a day. Teach them to fish, and you feed them for a lifetime.
Many managers prefer to give a fish.
Mentoring
What do you do when someone asks you to help them solve a technical or organizational problem?
Most senior engineers and managers default to giving advice.
It’s the most natural approach — and sharing hard-earned wisdom feels good. This approach is called mentoring. Mentoring is about helping others by sharing your own experience.
But this is only half of the toolkit.
What is coaching?
Another approach that works better in many situations is coaching.
Coaching, unlike mentoring, is not about you providing answers. It is about helping another person to find and articulate the answers themselves. A coach doesn’t need to know the answer. Instead of telling someone what to do, you ask questions that help them explore the problem, consider options, and reach their own conclusions.
Imagine your team lead comes to you and says, “I’m not sure how to handle the deadline for Project X, we’re behind, and I don’t know what to cut.” Instead of telling them what to prioritize, you ask: “What are the options as you see them?” They start thinking out loud, weigh the tradeoffs, and arrive at a plan. That’s coaching.
Coaching is a more sustainable, yet empathetic, approach.
Sustainability
It is more sustainable because, by coaching, you facilitate another person’s abilities to find solutions to their own problems. They learn to drive by sitting in the driver’s seat, instead of watching you drive. As a manager or a senior engineer, you cannot scale indefinitely by thinking and making decisions for everyone. To scale yourself, you need to invest in another person’s growth.
Empathy
Without understanding another person’s emotions and motivations, coaching becomes difficult if not impossible. Yes, this technique is more work than coming up with a solution or decision, but it both develops the other person’s long-term growth and strengthens the work relationship by building empathy.
Discipline
Have you ever been in a situation where your colleague starts telling you about a problem, you get the gist of it, and you stop listening because you’re already thinking about what you want to say, preparing the answer in your head?
Instead of focusing on yourself and your knowledge, you focus on another person. You suppress your impulse to jump forward with a solution and save the day.
You really listen, not in order to answer, but in order to understand.
And then reflect this understanding back by asking powerful questions.
How to start?
Starting with coaching can be difficult. It is hard to remember to downshift from giving direct advice to actively listening and guiding through questions.
If you’re not sure where to start, these are the clearest signals to reach for it:
You don’t have the full context. Maybe it’s a project with details you don’t know about, or an interpersonal issue on another team.
The situation is ambiguous, and there is no clear right answer; your past experience may not apply.
You deliberately want to invest in another person’s growth rather than solve the problem immediately.
In all these cases, instead of trying to get all the details and give advice, ask questions.
First, the current state; then, the options another person has; and finally, what they are going to do about the problem based on the discussion.
When not to coach
If the question is direct and you know the answer, there is no need to start coaching; just answer the question.
If, for example, your team member asks you why a certain part of the database is structured a certain way, and you know the answer, just tell them.
That leads to a simple rule of thumb. If resolving the problem requires you to dive deep into the details and do the work yourself, default to coaching. Help the other person find the answer instead of taking their seat.
What is next?
The goal of this article wasn’t to give you a complete overview of coaching practice and techniques — it is too big a subject to cover in depth here.
If you want to know more, I recommend looking at the GROW framework: https://www.britishschoolofcoaching.com/the-grow-coaching-model/.
It is a simple model that you can practice using immediately.
For those who want to go even further, I recommend picking up the latest edition of “Coaching for Performance” by Sir John Whitmore.
Coaching Habit
Develop a habit of coaching. When asked a difficult question, don’t start solving it — guide the other person to find their own answers instead.
This habit is not easy — it requires discipline and empathy. But it is worth it.
About Roman
This guest post was written by Roman Nikolaev.
He’s an engineering leader who shares hard-won lessons on building engineering organizations that deliver.
Find Roman on the High-Impact Engineering Substack, where he publishes weekly mental models and playbooks for engineering leaders and senior developers who want to scale their impact.
Subscribe to Roman’s High-Impact Engineering Substack
 | A guest post by
|
This is a useful and practical breakdown of how managers can shift from the instructor to coach mindset. It's one of the best ways to help ICs and teams develop and grow.
Another great collaboration to read!
A good read! I'm still not very good at asking questions to help them draw conclusions. While continue practicing I have a shortcut. 1) Repeatedly encourage my team members to form their own opinion on everything; 2) For specific question, tell them how I would tackle it and then emphasis it's only for reference, they make their own decisions.