Coaching Skills for Managers: A Practical Framework

Coaching skills for managers include careful listening, useful questions, specific feedback and support for another person’s thinking and development. They work alongside the manager’s responsibilities to set expectations, provide information, make decisions and address performance fairly.

A manager does not need to turn every conversation into coaching. The skill is recognizing what the situation requires and making that role clear. An employee should not have to guess whether a question is an invitation to think or a disguised instruction.

This guide develops the core skills, a GROW conversation, a complete fictional workplace case and a practical one-to-one structure. For a closer look at understanding another person’s account, see active listening in coaching.

Choose the conversation the situation needs

CIPD’s coaching and mentoring factsheet highlights the power relationship and the need for impartiality when managers coach their own staff. It also calls for clear confidentiality and information arrangements. Those issues remain relevant when a conversation is supportive and informal.

Several modes may be needed in one meeting. Name the transition: “The deadline is fixed. I can explain why, then we can explore how you want to organize the work.” This makes the available choice honest.

Coaching is especially useful where the employee has relevant knowledge and a real decision to consider. It cannot supply missing authority or make an impossible workload feasible by itself.

Listen before solving

Start with the person’s actual question. A statement such as “The project is a mess” may concern priorities, a relationship, missing information or a decision outside their authority. Asking what would be useful now prevents an early answer to the wrong problem.

Invite a specific example. What happened, what did the person do and what remains uncertain? Check your understanding in ordinary language and leave room for correction.

Notice your urge to supply the solution. Your experience may be useful, but first check whether the person wants advice and whether you understand the conditions. Advice given too quickly can miss information they have not yet described.

Listening does not mean agreeing with every interpretation. You can acknowledge frustration while asking what evidence supports a conclusion about a colleague or customer.

Avoid reading silence, posture or a short answer as proof of disengagement. Ask about the experience and any adjustment that would help the conversation.

Ask questions with a genuine open answer

A useful question helps the employee examine something they can actually influence. “What has already been tried?” or “Which decision do you need from me?” may be more valuable than an elaborate question about their deepest barrier.

Keep questions short and ask one at a time. Give the person space to think. Several questions in a single turn can make it unclear which one matters.

If you have a view, own it. “I think we need to check the customer commitment before changing the date” is more honest than asking “Wouldn’t a strong leader check the customer commitment?”

Invite disagreement without promising an absence of all consequences. You can explain how concerns will be considered and which decisions remain yours. A manager’s authority remains part of the relationship even in a supportive conversation.

Questions are not a universal replacement for expertise. If a person needs a safety procedure, accurate information or an authorized decision, provide the appropriate route.

Use GROW as a flexible map

Performance Consultants describes GROW through Goal, Reality, Options and Will or Way Forward. Associated with John Whitmore and collaborators, it offers a simple way to organize a conversation rather than a script that must be followed mechanically.

You may return to the goal when new information emerges. A person who begins wanting to become more assertive may discover that they need a priority decision between two managers.

The framework does not guarantee an outcome. Its value depends on the quality of listening, the honesty of the choices and whether the practical conditions support action.

A complete fictional one-to-one: a dependency and a correction

Leonie is an invented manager, Ira a team member, Jules the Operations lead and Vale the owner of a customer rollout note. All meeting and deadline times in this case use UTC. This original case shows a coaching conversation within a management relationship. It is not an employee assessment, a customer result or evidence that one method improves every team's performance.

Make the role and the actual goal clear

At their thirty-minute meeting on 7 June, Ira says: “Operations keeps delaying us. I need you to make Jules do our request first.” Leonie initially interprets this as a confidence issue and asks how Ira could be more assertive.

Ira corrects that interpretation: “I can ask. The problem is that I do not know who can decide which deadline moves.” Leonie acknowledges the distinction rather than turning the discussion back to confidence.

Leonie: I am still your manager. The rollout note needs current service hours and an escalation contact, checked before release. Its current deadline is 9 June at noon. Vale owns any change to that deadline; I cannot promise one. We can explore your next request, and I will own any priority escalation that needs my role.

Ira: That helps. I want to leave knowing the smallest request to make and when you will step in.

They agree to keep a short record of the work question, chosen actions and decisions in the authorized team system, visible to them and the relevant work owners. This is ordinary work coordination, not a promise of private coaching records or a formal performance process disguised as a development chat.

Check the evidence before choosing an option

Leonie asks what Jules has actually accepted. Ira explains that a long request was sent, but Jules has not confirmed a date or capacity. Ira had treated the absence of an answer as deliberate delay. They correct the working description to “no delivery commitment confirmed.”

Ira identifies three options: ask only for the two required fields, use last month's note or request a deadline change. Leonie gives information where it is needed: the previous note cannot be assumed current. The release requirement is current, checked information. It would be misleading to present an old contact as verified.

Ira asks who approves the final note. Leonie answers directly that she checks it before Ira sends it to Vale. She does not ask Ira to guess the approval process in order to preserve the appearance of coaching.

They return to the goal. Ira chooses to send the smaller request with an answer-by time. Leonie accepts the escalation responsibility if Operations cannot meet the current need. The employee's next action and the manager's next action are separate commitments.

Send the request and hear an actual refusal

On 8 June, Ira sends this original request:

For the current rollout note, I need the verified service hours with their time zone and the current escalation contact. The note is currently due to Vale on 9 June at noon. Can you supply those two fields in time? Please confirm capacity by noon today. If that timing is unavailable, I will ask Leonie to resolve the priority or deadline decision rather than assume an agreement.

Jules replies that existing work prevents delivery before 9 June at 14:00. The reply does not meet the current deadline. Ira records the actual answer and contacts Leonie through their agreed escalation route.

Leonie discusses the conflict with Vale and Jules. Vale authorizes a revised submission deadline of 15:00 on 9 June, retaining the requirement for current checked information. Jules confirms the two fields can be supplied by 14:00. Leonie sends the revised arrangement to Ira, who acknowledges it.

The request has been answered and the relevant owners have accepted a new timetable. No one treats Ira's first email as proof that Jules had committed earlier. Leonie does not judge Ira's development solely by whether another team abandoned its existing priorities.

Give feedback on a real error and complete the correction

At 14:00 on 9 June, Jules sends the current contact and service hours stated as 08:00–16:00 UTC. Ira prepares the note but writes “08:00–16:00 local time.” During the agreed check at 14:30, Leonie notices the discrepancy.

Leonie: The source says UTC; this draft says local time. Those are not the same instruction for a reader in another time zone. We need the checked source wording before release. What happened when you transferred the information?

Ira: I copied the old sentence structure and missed the qualifier. I will correct the note and check the contact against Jules's message too.

Leonie describes the observed error and relevant effect. She does not call Ira careless or claim that the whole coordination problem reflects poor motivation. The current requirement remains clear; the conversation does not invite Ira to decide whether accuracy matters.

Ira checks both fields, corrects the time zone and returns the note. Leonie verifies the corrected version at 14:50 and approves it. Ira sends it to Vale at 15:00, and Vale acknowledges receipt. The delivery and correction are complete inside the fictional case.

Review the manager's contribution as well as the employee's

At their 14 June review, Ira and Leonie compare the original description, Jules's actual response, the approved timetable and the corrected note. Ira says it was useful to know when Leonie would take ownership. Ira also says the initial confidence question made it seem that a priority problem was being treated as a personal weakness.

Leonie acknowledges that misreading and records a development action for herself: check what decision the person needs before proposing a personal-development goal. They rehearse a different opening, but neither counts that rehearsal as proof of a later workplace change.

Ira identifies a practical lesson: distinguish a request sent from a commitment received, and check source qualifiers when adapting an earlier document. Leonie and Ira agree a short shared work note containing the decisions and these learning points. Ira reads it, corrects Leonie's initial phrase “Operations delivered late” to “Operations met the revised agreed time,” and Leonie makes that correction.

They close this work item without creating a performance rating from it. The completed outcome is a clarified request, an authorized revised timetable, a corrected output and a reviewed conversation. Future dependency problems still need their own answers; the case does not claim that coaching eliminated every coordination error.

Give specific feedback without turning it into a verdict

Describe the event and relevant effect, then ask for the person’s account. Distinguish what you observed from what you inferred. “The customer received two different dates” is more useful than “You do not care about coordination.”

Be clear about the standard where one applies. A coaching conversation can explore how the person will meet it, but should not imply that an essential requirement is optional.

Invite practical learning. Was information missing? Did the workflow assign the same responsibility to two people? Does the employee need practice, a decision or another kind of support?

Keep the feedback proportionate to the evidence. One event does not establish a stable character trait, and a friendly tone does not remove the need for accurate preparation.

When a formal process is required, explain it and follow it. Do not promise that a conversation is confidential if your managerial duties require reporting or action. The ICF Code of Ethics offers a professional reference on role clarity, information exchange and power differences; it does not replace an employer’s actual policies or obligations.

Structure a useful one-to-one

Agree the purpose and give the employee an opportunity to shape the agenda. Operational updates may belong in the same meeting, but make room for development rather than allowing every minute to disappear into status reporting.

Choose one issue that deserves thought. Clarify the desired outcome, explore the situation and identify what requires the manager’s input. A fixed thirty-minute meeting does not require equal ten-minute blocks.

Close by checking the next step and support. The employee may choose an action; the manager may owe a decision, resource or introduction. Record both responsibilities accurately.

Our goal-setting worksheet can help make a chosen action clear. Keep it short enough to use during ordinary work.

Agree the review point according to the task. The next regular meeting may be suitable, while a time-sensitive blocker needs an earlier route. Avoid creating a new daily reporting burden without a clear reason.

A manager’s conversation worksheet

Use a short preparation and review record, with only the information needed for the work. The entries below follow the actual fictional case, so a later reader can distinguish the initial interpretation from what the conversation established.

This is an original work-conversation aid, not an employee assessment or a confidential personnel record by default. Clarify purpose, storage, audience and any required reporting. Do not put sensitive workplace material into a separate coaching service merely because a form is available.

Practise the skills and ask for useful feedback

Choose one specific skill to develop in a routine conversation. For listening, check whether your first summary leaves room for correction. For questions, notice whether you are asking for an answer you genuinely do not know or trying to disguise a direction.

Afterward, ask what was useful and what was unclear. An employee may not feel able to give candid feedback to their manager immediately. Offer an appropriate route and avoid turning a request for feedback into a requirement to reassure you.

Review your own actions, including the responsibilities you accepted. Did you give the promised information, obtain the needed decision or reply when you said you would? A manager who records only employee actions can miss their own contribution to the blockage.

Use an appropriate supervisor, development partner or trained coach for your own learning. Share only what the arrangement permits, and use fictional material for practice where real details are unnecessary. Support should improve judgment, not create an unofficial parallel assessment of the employee.

Use Coachful to support the manager's own development

Coachful is our #1 recommendation for organizing coaching that helps managers practise these skills, choose development actions and review actual conversations. An authorized leadership coach can work with the manager on their listening, questions and follow-through while the organization's work and personnel records stay in the appropriate systems.

An original worksheet can hold the manager's chosen development goal and a suitably limited account of an interaction. Explain which authorized coaching-team members can see submitted answers. The private Coach review belongs to that team and is excluded from the client response PDF; saving it is not delivering feedback to the manager.

Review sensitive-session recap settings before relying on privacy expectations. Recaps for summarized sessions send automatically by default. Sessions > settings gear > Session AI > Session recaps > Approve before sending can hold new recaps for review, but an explicit session-type On or Off overrides the workspace default. Turning approval on cannot recall a recap already sent.

Check the intended client-facing content and choose Send recap or Keep private appropriately. A coaching task can record the manager's next practice and review question. It does not authorize employee-record sharing, complete a workplace decision or turn a rehearsal into evidence of changed management behavior.

A different case: the employee asks for a straight answer

A new colleague asks which approval process applies. Their manager responds with repeated questions about what they think the answer might be. The colleague becomes more confused and the work waits.

Here, useful support begins with the accurate process or the right source of information. After explaining it, the manager can invite questions and check understanding.

Later, when the colleague has relevant knowledge, a coaching conversation may help them handle an unfamiliar case. Development can progress from instruction to supported judgment without treating one mode as inherently superior.

Ask for feedback on your own approach: did the conversation help, and was your role clear? A manager develops coaching skill by examining actual interactions, including moments when a question was less useful than a clear answer.

Frequently asked questions

Should managers stop giving advice?

No. They should choose advice, instruction, decisions or coaching according to the need, and make the transition clear.

What does GROW stand for?

Goal, Reality, Options and Will or Way Forward. Use it as a flexible map for a useful conversation.

Can a manager promise full coaching confidentiality?

They need to explain the actual limits of their role, policies and reporting duties. Managerial authority does not disappear when the conversation uses coaching skills.

How long should a coaching one-to-one take?

There is no universal duration. Protect enough attention for the issue and agree when a blocker or next step needs review.

What if the employee needs an answer?

Provide accurate information or the appropriate decision route. Do not make someone guess a requirement in the name of coaching.

A useful managerial conversation combines curiosity with clear responsibility. Coachful’s coaching workspace can support the chosen action, preparation and review.