top of page
Search

Why Coaches Dont Need to Know Your Job to Coach You Well

A good coach does not need to be able to do your job. They need to help you think more clearly about the work, the choices in front of you, and the way you are showing up in the situation.


That distinction matters.


I have coached GPs, engineers, data scientists and CEOs. I could not safely run a GP clinic, design a bridge, build a predictive model or lead a multi-million-pound organisation in the same way they do. That is not what they came to coaching for. They came because something in their work, leadership or confidence needed attention, and because thinking alone was not getting them where they wanted to go.


The value of coaching is not that the coach climbs inside your technical role and takes over. The value is that they help you see the issue with more space, more honesty and more choice.


The coach is not there to be the expert in your job


Many people assume a coach needs direct experience of their profession before they can be helpful.


It sounds reasonable at first.


A GP may ask, "How can someone coach me if they have never managed a full surgery list, dealt with patient risk, or handled the emotional weight of the role?"


An engineer may wonder, "How can a coach understand the pressure of technical accuracy, safety, deadlines and stakeholders?"


A data scientist may think, "If a coach does not understand models, messy data and competing business demands, will they ask useful questions?"


A CEO may be concerned that a coach who has not sat in the same seat cannot grasp the loneliness, pace and responsibility of senior leadership.


Those are fair concerns. But they rest on a misunderstanding of what coaching is for.


A coach is not usually there to teach the content of the job. They are not there to be a substitute manager, technical adviser or subject specialist. They are there to work with the person doing the job.


That means paying attention to areas such as:


  • How the client frames the problem

  • What assumptions they are making

  • Where they are stuck

  • What choices they believe they have

  • What patterns keep repeating

  • What they avoid saying, deciding or noticing

  • How they relate to pressure, uncertainty and other people


Those themes appear across professions. They just wear different clothes.


The details of a GP’s day look very different from a data scientist’s day. But both may wrestle with overload, confidence, difficult conversations, competing priorities, perfectionism, boundaries or fear of getting something wrong.


The coach does not need to know every technical term to recognise those human patterns.


Coaching is not mentoring, consulting or training


A lot of confusion clears up when we separate coaching from other forms of support.


A mentor often draws on personal experience. They may say, "When I was in your position, this is what helped me." That can be valuable, especially when someone wants guidance from a person who has walked a similar path.


A consultant brings expertise and recommends answers. They diagnose a problem and advise on what to do. That is useful when the issue needs specialist knowledge or an external expert view.


A trainer teaches skills or knowledge. They have content to deliver and clear learning outcomes.


A coach works differently. A coach helps the client examine their own thinking, make sense of their situation and decide how to act. They may offer observations, challenge patterns and hold a clear structure, but they are not there to hand over a pre-written answer.


That can feel strange at first, especially for people in expert professions. If you spend your working life being valued for answers, it can be unsettling to sit with someone who does not rush to give you one.


Yet that is often the point.


A coach creates the conditions for a different quality of thinking. The client is not being rescued from the problem. They are being supported to engage with it more fully.


The client remains the expert in their role. The coach brings expertise in attention, enquiry, reflection and change.


The David Rock image is a useful way to understand the work



David Rock, in his book Quiet Leadership about leaders using a coaching style, uses a helpful image of two chairs. That simple picture captures something essential.


The coach is not staring at the problem as if it belongs to them. They are not grabbing it, fixing it or proving they understand it better than the client. Their attention is mostly on the thinker.


What is happening as the client looks at the issue?


Are they narrowing too quickly? Are they circling the same explanation? Are they dismissing options before testing them? Are they confusing fear with fact? Are they carrying someone else’s expectation as if it were a rule?


The issue matters, of course. But the client’s relationship with the issue matters too.


Two people can face the same situation and experience it very differently. One sees a career-ending risk. Another sees a difficult but manageable conversation. One hears feedback as proof they are failing. Another hears it as useful data. One treats conflict as danger. Another treats it as a signal that something needs to be named.


A coach helps the client notice that relationship.


That is why the coach does not always need deep domain knowledge. In fact, too much familiarity can sometimes get in the way. A coach who has done the same job may jump too quickly to recognition.


They may think, "I know this one."


But they may not.


The client’s situation may look familiar on the surface, while the real issue sits somewhere else entirely.



Outside perspective can make the coaching stronger


There are benefits to a coach not being from the same profession.


They are less likely to be trapped by the norms of that world. Every profession has unspoken rules. Some are useful. Some are inherited habits that nobody questions.


A coach from outside may ask the question that insiders have stopped asking.


"Who says it has to be done that way?"


"What would happen if you named that directly?"


"What are you treating as fixed that might actually be negotiable?"


"What are you protecting by staying silent?"


These questions do not require the coach to know the exact software, clinical pathway, engineering process or board structure. They require curiosity and skill.


An outside coach may also be freer from status games within the profession. They are not impressed by the same titles or intimidated by the same myths. They can listen for what is being said, what is being avoided and what does not quite line up.


That can be useful for high-achieving clients.


Experts often live inside cultures where competence is prized. They may be used to sounding certain, even when they feel unsure. They may have learnt to keep doubts private. They may receive plenty of advice but very little clean attention.


A coach can provide that.


Clean attention means listening without rushing to compare, compete or correct. It means allowing the client’s thinking to unfold without forcing it into the coach’s own story.


That kind of attention is rare. It is also practical. People often make better decisions when they can hear themselves think.


The coach still needs to understand enough


None of this means the coach can be ignorant, vague or passive.


A good coach does need to understand enough about the client’s context to ask grounded questions. They need to learn the broad shape of the work, the pressures, the stakeholders, the risks and the language that matters.


If a GP mentions safeguarding, clinical risk or continuity of care, the coach should know enough to recognise that these are not casual details. If an engineer talks about safety, regulation or design sign-off, the coach should take that seriously. If a data scientist talks about imperfect data, bias or stakeholder misuse of a model, the coach should hear the weight in it. If a CEO talks about cash flow, board dynamics or organisational trust, the coach should understand that these are not abstract themes.


But "understand enough" is not the same as "have done the job".


A coach can ask for clarification without losing credibility. In fact, a well-timed simple question can be powerful.


"Can you talk me through what that means in practice?"


"Where is the real risk here?"


"Who is affected by this decision?"


"What makes this hard in your particular setting?"


These questions invite the client to slow down and name what may be obvious to them but hidden inside the pressure of the moment.


The coach’s responsibility is to stay oriented. They should not pretend to understand what they do not understand. They should not bluff expertise. They should not wander into technical advice unless they are qualified to give it.


The boundary is part of the professionalism.


Close-up view of a hand writing a simple question in a notebook beside a cup of tea.
A simple question can open up complex thinking.

The real work is often below the job description


When someone brings an issue to coaching, they usually describe it through the language of work.


"I need to manage my workload."


"I need to influence a stakeholder."


"I need to decide whether to apply for the role."


"I need to stop overthinking."


"I need to have a difficult conversation."


The job context matters. But the deeper work is often about something more transferable.


A GP might be exploring how to set boundaries without feeling they are failing patients.


An engineer might be working out how to challenge a decision when everyone else seems comfortable with it.


A data scientist might be learning how to explain uncertainty to people who want a simple answer.


A CEO might be facing the fact that being decisive has become a way of not being vulnerable.


Different professions. Similar human territory.


That territory includes confidence, identity, responsibility, clarity, courage, grief, ambition, loyalty, resentment, fear and hope. It includes how people think under pressure and how they behave when the stakes feel high.


A coach does not need to share the profession to work there. They need to notice the person inside the profession.


This is especially true when the client has already had plenty of technical input. Many experienced professionals do not lack information. They have read the guidance, spoken to colleagues, checked the data and gathered opinions. What they lack is space to process it all and decide what they actually think.


More advice is not always the answer. Sometimes it adds noise.


A good coaching conversation can reduce that noise.


Knowing the job can sometimes help, but it is not the main thing


There are times when professional experience is useful.


If someone wants career mentoring in a very specific field, a person who has been there may offer relevant guidance. If the issue involves technical competence, specialist supervision or regulatory judgement, the client may need support from someone qualified in that area. If the question is, "How do I perform this task correctly?", coaching alone may not be enough.


So the claim is not that domain knowledge never matters.


The claim is that it is not the core ingredient in good coaching.


In some cases, shared experience can even create problems. A coach who knows the field too well may assume the client’s experience mirrors their own. They may offer advice too soon. They may collude with the profession’s blind spots. They may focus on the technical puzzle because that feels safer than the human one.


The best coaches, whether they know the profession or not, resist that pull.


They stay curious. They test their understanding. They ask rather than assume. They notice shifts in energy, language and emotion. They help the client move from fog to form.


Most of all, they keep the client responsible for their own thinking.


That is not a lack of support. It is respect.


What to look for in a coach instead


If shared professional background is not the main test, what should matter?


Look for evidence that the coach can create useful thinking. That may show up in the way they listen, the quality of their questions, their ability to challenge kindly, and their comfort with complexity.


A good coach should be able to:


  • Build trust without becoming cosy

  • Ask clear questions that make you think, not perform

  • Hold silence without rushing to fill it

  • Challenge assumptions without trying to win

  • Stay with uncertainty

  • Notice patterns across different situations

  • Respect the limits of their role

  • Help you leave with clearer choices


Pay attention to how you feel after an initial conversation. Not whether you feel flattered or impressed. Ask whether you found yourself thinking differently.


Did the conversation create space?


Did it help you see the issue more clearly?


Did the coach listen for what mattered, rather than trying to prove their own intelligence?


Did they understand enough of your world while keeping their attention on you?


Those are better signs than a matching job title.


Wide-angle view of a quiet path through trees with two empty benches facing a pond.
Good thinking often needs room, not more advice.

The best coaching gives the problem back to you in a better shape


A coach does not need to have worn your name badge, used your systems or sat in your chair to help you well.


They need to understand how to sit beside your thinking without taking it over.


They need to hold the conversation so that the issue becomes clearer, the assumptions become visible and the next step becomes possible. They need to see the person who is looking at the problem, not just the problem itself.


That is why a coach can work with a GP, an engineer, a data scientist and a CEO without being all four.


The role is not to become the expert in every job. The role is to help the expert think, choose and act with more clarity.


The work stays on the table between you. The coach’s attention stays on how you are meeting it. That is often where the change begins.


 
 
 

Comments


bottom of page