Employee Coaching

What coaching looks like in practice

Good coaching is short, frequent and tied to real work. A supervisor and an employee look at something concrete, such as a recorded call, a sales conversation, a set of claims or a project plan. They talk through what went well and what didn't, the employee proposes what to try differently, and both agree on one or two specific actions to check next time.

The coach asks more than they tell. "What was the customer really asking for at that point?" builds judgment that "you should have offered the payment plan" doesn't. That said, coaching is not purely non-directive. When someone is new or a compliance issue is at stake, the coach states the expectation clearly.

Typical rhythms: weekly 15 to 30 minutes for frontline staff in measured roles, every two weeks for professional roles, plus in-the-moment coaching when something notable happens. In contact centers this is formalized as call coaching, built around recorded interactions and quality scores.

The GROW model with a worked example

GROW, popularized by John Whitmore, is the most widely used coaching structure:

• Goal: what does the employee want to achieve?
• Reality: where are things now, with evidence?
• Options: what could they try?
• Will (or Way forward): what will they do, by when?

Example: Tyler, a collections agent, has a promise-to-pay rate of 18% against a team average of 25%. His team lead, Andrea, runs a 20-minute session.

Goal: Tyler wants to reach 23% within a month. Reality: they listen to two of his calls together. Tyler notices he jumps to the payment demand before the customer has finished explaining their situation, and customers become defensive. Options: Tyler suggests summarizing the customer's situation back before asking for payment, and offering two payment options instead of one. Andrea adds a phrase top performers use to transition. Will: Tyler will use the summary step on every call this week. Andrea will review three calls on Friday.

The next session starts with those three calls. Writing the commitment on a coaching form makes the follow-up easy and keeps a record.

Coaching versus mentoring and training

Training teaches a skill to a group, usually away from live work. Coaching applies and refines skills one-to-one on the actual job. Mentoring is a longer relationship focused on career and broad development, drawing on the mentor's experience; a mentor usually isn't the employee's manager.

Coaching is also different from a performance improvement plan. A PIP is formal, documented and time-bound, with consequences. Coaching should come long before that, and if it's done well, most PIPs never happen.

Coaching at scale

The biggest barrier is time. A team lead with 18 agents and a full floor to run often has coaching sessions bumped first. Practical fixes: protect coaching time in the schedule as you would breaks; keep sessions short and focused on one behavior; use data to pick which interactions to review rather than random samples; and give leads a simple structure so sessions don't drift.

AI coaching tools now handle part of the load by scoring interactions, flagging coachable moments and letting employees practice with simulated customers between sessions. They work best as a supplement to the manager's conversation, not a replacement for it.

Common mistakes

• Coaching only when something goes wrong. Employees learn to dread the invite. Coach strengths and good calls too.
• Too many points at once. Pick one behavior per session.
• Talking more than listening. If the coach does 80% of the talking, it's a lecture.
• No follow-up. An agreed action that nobody checks is forgotten in a week.
• Inconsistency between leads. If two supervisors coach to different standards, employees get mixed messages. Calibrate coaching standards across the team, just as you calibrate quality scores.