Never Coach Your Team Members
Coaching your team creates insecurity and dependency. Use walks, data, and training cycles instead to build ownership.
Key takeaways
- Never coach your team members one-on-one. Coaching creates insecurity and removes ownership. Use group training instead to close performance gaps without anyone feeling targeted.
- Ask every team member why they actually work for you, then let them answer out loud. The act of saying it integrates it into how they operate, which is the real alignment mechanism.
- Deliver the data before the evaluation so people can assess themselves. When team members identify their own improvement areas, they take responsibility for fixing them.
- Write down what team members do not name in their self-evaluation. Use that list to build your training, not your coaching conversations.
- Acknowledge what is going well and connect it to the company vision. People feel seen and heard without any performance theater.
Timestamps
Show notes
What this episode is about
Paul Veth argues that coaching your team members is a negative spiral. The alternative is a three-step framework he tested as a manager with a 26-person customer service team. NPS went from +21 to +43 in six weeks. Team satisfaction and trust went up at the same time.
The three moves
1. Go on a walk
One-on-one, no agenda. Paul shared something from his own personal life first, which made it natural for team members to do the same. The key question: why did you choose this company? Most managers assume the answer. Almost nobody asks. When a person says the reason out loud, it gets integrated into how they operate. That is the mechanism.
2. Deliver data, then ask
Before any evaluation, give team members the data on their own performance. At the evaluation, sit next to each other, not across a table, and ask two questions only: what do you think you can do better, and what is going well? Acknowledge what they name. What they do not name, write it down. Do not say it. That list becomes your training material.
3. Train, never coach
Run a short daily, weekly, or monthly training on the gaps nobody named in the evaluation. This keeps it group-level and removes the feeling of being singled out. People connect the training to their own data in the next cycle and start naming the improvements themselves. No insecurity. No dependency. Just ownership.
The result
NPS score moved from +21 to +43 within six weeks. Team satisfaction increased. Trust in leadership increased. And managers who use this framework get asked the same question by everyone around them: how do you have so much time left?
Framework mentioned
This episode describes a practical management framework developed and tested by Paul Veth. Related: Identity First approach to team alignment via Aligned.
Topics
Full transcript
View full transcript
Frequently asked questions
Why does Paul Veth say you should never coach your team?
Coaching one-on-one signals to the individual that they are falling short, which creates insecurity and removes ownership. When people feel singled out, they stop taking responsibility for their own improvement. Group training on the same gaps produces growth without the negative spiral coaching creates.
What is the one-on-one walk and why does it work?
Paul started by sharing something from his own personal life on a walk, which made it natural for team members to open up. The key question is why they chose the company. When a person says the reason out loud, it gets integrated into how they operate. That spoken reason becomes the anchor for alignment later.
How does delivering data replace the need to coach?
When team members see their own performance data before an evaluation, they can identify what needs to improve without being told. Self-identified gaps generate ownership. Gaps named by the manager generate defensiveness. The data shifts the evaluation from a top-down judgment to a shared conversation.
What do you do with things a team member does not name in their self-evaluation?
Write them down and say nothing in the evaluation itself. That list becomes the input for your next group training. Addressing gaps at the group level means nobody feels called out, and the next evaluation cycle shows whether the training landed because people start naming those same improvements themselves.
What results did this framework produce in Paul's own experience?
Running this with a 26-person customer service team at a major telecom company, the NPS score moved from +21 to +43 within six weeks. Team satisfaction went up, trust in leadership increased, and Paul found himself with significantly more time because the team was largely self-managing.
Related episodes
Get in touch
Want to learn more or collaborate? Feel free to reach out.
Get in touchDiscussion
The idea that coaching your team actually creates dependency instead of ownership flips a lot of conventional management advice on its head. Have you ever noticed a team member become less confident or more reliant on you the more you coached them? Share what actually worked instead.