When to Stop Coaching in Project Management
Project Management, Leadership, Coaching, Risk Management
Is Coaching Enough? Knowing When to Stop Coaching and Protect the Project
One of the hardest parts of leading large, complex projects is knowing when to stop coaching and make the tough decision to remove a resource from the project. Project managers are often expected to support the team, guide the work, remove blockers, and help people improve. And yes, coaching is important. But coaching has limits.
Coaching Only Works When the Person Is Coachable
As I often say: "Coaching only works when the person is coachable." You can invest time, energy, and patience into someone, but if they are not willing or able to change their behavior, your coaching will not translate into better delivery. This is not about giving up on people; it is about being honest about what the project needs and what the person is actually demonstrating through their actions, not just their words.
On Agile teams, people are expected to work with autonomy. They should be able to manage their work, communicate blockers, understand dependencies, and keep the work moving. But that is not always the case. Some team members struggle with ownership. Some wait to be told what to do. Some do not communicate until the issue becomes urgent. Some continue the same behavior even after coaching, direction, and support have been provided. At that point, the issue is no longer just about performance. It becomes a delivery risk.
The Limits of Coaching and the Shift to Risk Management
There is a point where continued coaching stops being productive. You have clarified expectations. You have walked through the work. You have removed blockers. You have given feedback. Yet the behavior stays the same. Deadlines slip. Communication is late. Commitments are missed. The rest of the team starts compensating, or worse, losing trust in the process and in you as the project manager if nothing changes.
"When behavior does not change after clear expectations and support, it is no longer a coaching issue. It is a project risk."
That is the moment you must shift your mindset from I am helping this person grow to I am protecting this project. Coaching is still valuable, but it can no longer be the only strategy. Your responsibility is not just to the individual. It is to the customer, the scope, the timeline, the budget, and the rest of the team who are doing their part to deliver.
Documentation and Escalation: Protecting Yourself and the Project
This is where project managers must lead with both empathy and accountability. A resource should not be removed without first giving it a fair chance. That fairness is demonstrated through a clear, documented path of support. The project manager should clarify expectations, document concerns, provide feedback, offer support, and escalate appropriately. This is not about being punitive; it is about being transparent and responsible.
Because here is the hard truth: leadership may not always come to save the project when the customer complains. Sometimes the PM becomes the one held accountable, even when the issue was raised before. That is why documentation matters. Escalation matters. Clear expectations matter. And protecting the project matters. Your meeting notes, performance conversations, action items, and escalation emails are not just paperwork. They are your evidence that you led responsibly and did not ignore the risk.
Recognizing When Coaching Is No Longer Effective
The goal is not to give up on people too quickly. The goal is to recognize when continued coaching is no longer helping the person, the team, or the project. You know coaching is no longer effective when:
- The same behavior repeats despite clear, documented feedback and support.
- The behavior is impacting delivery, quality, or critical milestones.
- Other team members are picking up the slack or expressing frustration.
- You find yourself having the same conversation with no measurable change.
"Coaching matters. Accountability protects delivery."
Strong project managers know how to support people. But they also know when to protect the delivery. If a resource has been coached, supported, and given clear expectations, but the behavior still does not change, then the project manager must stop treating it like a coaching problem. It is now a project risk. And project risks must be managed, not wished away.
Making the Tough Call to Protect the Project
Making the decision to remove someone from a project is never easy, especially when you care about people and want them to succeed. But leadership is not about avoiding discomfort. It is about doing what is necessary to honor the commitments made to the customer and to safeguard the work of the team. When behavior persists and begins to impact delivery, the customer relationship, team morale, or project outcomes, the project manager has to make the tough call.
You can still be empathetic while being firm. You can acknowledge the person’s effort while clearly stating that the current performance is not sustainable for this project. You can offer support in finding a better fit or additional training while being unwavering about what this project requires. That balance—empathy with accountability—is what separates reactive project coordinators from true project leaders.
In the end, your role is clear: coach when it helps, document as you go, escalate when needed, and when coaching is no longer enough, have the courage to protect the project. Your team, your customer, and your professional reputation depend on it.
