4 Coaching and Developing Team Members
Learn how to guide ongoing coaching conversations, set employee-owned goals, give behavior-based feedback, address obstacles, and build team members’ ownership of their development.
What effective involves
is a purposeful, ongoing conversation that helps a team member improve performance and build skills. Rather than only giving instructions, the manager listens, asks questions, offers specific feedback, and helps the employee choose and follow through on actions. It works best as a two-way partnership with clear expectations and regular check-ins.
Structure the conversation
A practical conversation can follow five steps:
Agree on the focus. Ask what the employee wants to work on, or describe the work-related observation that prompted the discussion.
Explore the current situation. Listen for the employee’s perspective, strengths, obstacles, and relevant context. Open questions include “What feels most challenging?” and “What have you tried so far?”
Set a goal. Define what progress will look like and when it will be reviewed. For a straightforward task, a specific, measurable goal can clarify expectations. For unfamiliar or complex work, focus first on learning and practicing the needed skills.
Choose development actions. Identify practical ways to learn and apply the skill, such as practice, job shadowing, feedback from a colleague, training, or a stretch assignment. Agree who will do what and what support is needed.
Review and adjust. Set a check-in date to discuss what changed, what was learned, and whether the goal or support needs to change. Ongoing feedback helps people track progress and make timely adjustments.
Set goals the employee can own
Invite the team member to help shape a goal and connect it to an actual work need. Make sure it is achievable with the available time and resources. A goal should state the desired result, how progress will be observed, and a review date.
For example, replace “get better at presentations” with: “Over the next six weeks, lead two project updates, use a clear opening and summary, and ask two colleagues for feedback after each.”
For complex learning, set a before requiring a particular result. Specific expectations and regular progress checks support accountability without treating development as a one-time event.
Give feedback that supports growth
Make feedback timely, respectful, and based on observable behavior rather than assumptions about personality. The structure keeps feedback focused:
Situation: When and where did it happen?
Behavior: What did the person do or say?
Impact: What effect did it have?
For example: “In yesterday’s handoff meeting, the status of two open tasks wasn’t shared. The incoming team had to follow up before they could begin. What would help make the next handoff clearer?” Then listen to the employee’s perspective and agree on a useful next step. Two-way discussion can make feedback more specific and constructive.
Address obstacles and accountability
When progress stalls, approach the issue with curiosity and clarity. Ask what is getting in the way: a missing skill, unclear priorities, limited resources, competing workload, or low confidence may each call for different support. Separate what the employee can control from what requires the manager’s action, and be explicit about expectations, available help, and the next review point.
does not mean avoiding accountability. If performance is below an agreed standard, describe the gap and its work impact, hear the employee’s perspective, and agree on specific improvement steps. Follow organizational processes where applicable, and keep the conversation focused on work and behavior rather than personal labels.
Build ownership over time
The manager provides direction, feedback, opportunities, and resources. The team member takes an active role in choosing actions, practicing, and reporting progress. Questions such as “Which option do you want to try?”, “What support would help?”, and “How will you know it’s working?” return responsibility to the employee.
Record the agreed goal and actions, then revisit them during regular check-ins. A is most useful as a shared, continuing plan, not as a one-time form or a substitute for conversation.
For example, a team member wants to handle customer escalations more confidently. The manager asks which part is hardest, and they identify opening the conversation and clarifying the customer’s concern. They agree that the employee will observe a skilled colleague, practice two opening questions, and handle one suitable escalation with support. At the next check-in, they review what worked, feedback received, and a next opportunity to practice.
Effective combines listening, clear expectations, useful feedback, achievable development actions, and regular review. The aim is not for the manager to solve every problem, but for the team member to gain the skills and confidence to take increasing ownership of growth.