Coaching the Drag: Turning Underperformance into Uplevelment in Remote Teams

Managing a cross-functional team spread across multiple time zones demands more than just ticket tracking; it demands astute leadership. Occasionally, a core team member begins to drag. Their output dips, commitments slip, or their enthusiasm noticeably slackens. The natural, low-effort response is to call a formal critique, pointing out missed deadlines or poor quality work.

However, seasoned project managers know that this reactive approach seldom fixes talent issues. It usually just builds defensiveness. Our goal shifts radically: we must transition from being fault-finders to being genuine process-coaches. Coaching a struggling teammate isn't about pointing out failures; it's about diagnosing systemic roadblocks, whether those roadblocks exist in skill, process familiarity, or wellbeing.

Diagnose First, Judge Second

Before any structured conversation, take time to analyse the evidence impartially. Is the struggling member struggling because they don't know how (a skill gap), don't know where to look (a process gap), or are they struggling because of something outside the work?

Consider reviewing your last two retrospectives. Did the team collectively highlight difficulty with estimations? Did one specific subsystem fail repeatedly? Often, the individual struggling mirrors a weakness within the team's established workflow.

Example: Say we have a developer, Alex, whose estimates wobble wildly. Instead of chastising Alex publicly, run a quick, anonymous poll asking the team: "What is the biggest source of estimation inaccuracy for our next feature?" If the pattern points to flaky local API credentials that only QA can access, the problem isn't Alex’s estimation skill—it's environment setup, a process issue.

Remote work complicates this diagnosis. Observation is key. Beyond the task management board, look at communication patterns. Is Alex suddenly quiet in video calls? Are their responses delayed and vague across Slack channels? These subtle shifts provide data points just as valuable as bug reports.

Building the Coaching Conversation

When you initiate the conversation, treat it like a retrospective with them, not on them.

1. Establish Context (Non-Judgmentally): Start by referencing observable behaviour, avoiding labels. Instead of, "You seem disorganized lately," try, "I noticed on yesterday's sprint board that the last three tickets you touched were reopened, requiring rework."
2. Probe and Listen (The 80% Rule): Aim to listen 80% of the time. Ask open-ended questions: "What is your biggest bottleneck right now?" or "If you could instantly improve one thing about the process, what would it be?"
3. Co-Create an Action Plan: Never dictate the solution. Work together to define 1-3 measurable, small actions for the next week. For instance: "Okay, instead of aiming to finish the whole feature, let's agree you will spend 30 minutes tomorrow mapping out the database migration flow beforehand, and we’ll review that."

Sustaining Momentum Remotely

Maintaining coaching momentum when you can't have coffee by the water cooler requires rigorous structure.

Schedule these follow-ups immediately. If you agree on a small action, schedule a 15-minute check-in for the next day specifically to review that action. This constant, small feedback loop builds accountability and rebuilds confidence.

Remember that competency is not fixed. By framing problems as process gaps and implementing small, achievable micro-improvements, you help the individual rebuild belief in their own process, and in the team's ability to support them.

*

Potential Focus Areas for Team Review:

• Self-Assessment Prompts: Ask team members to rate their own confidence in different process stages (e.g., "How confident are you in the requirements hand-off? 1-5").
• Pairing Over Punishment: Assigning junior members to pair with "coaches" (more experienced devs) for challenging tasks shifts the focus from blame to shared learning.