Feedback Script: Addressing Missed Deadlines with a Senior Engineer

Feedback Script: Addressing Missed Deadlines with a Senior Engineer

TL;DR

The senior engineer’s missed deadline is a symptom, not a failure; the conversation must surface the underlying signal, apply a coaching framework, and set measurable next steps. A tight opening, a diagnostic listening phase, and a forward‑looking plan turn a setback into a performance upgrade. Execute the script, follow up with concrete metrics, and the engineer regains credibility within a sprint.

Who This Is For

You are a mid‑level engineering manager at a large technology firm, responsible for a team that includes senior engineers earning $150,000 base plus 10 % bonus and a modest equity grant. You have just learned that a senior engineer on a critical feature missed a milestone by eight days, jeopardizing a product launch slated for Q4. You need a reproducible script that respects the engineer’s seniority, preserves morale, and aligns the team to the revised schedule. This guide is for managers who have already tried generic “you need to improve” emails and found them ineffective; you need a calibrated, data‑driven conversation that delivers feedback without demotivating a high‑performer.

How should I frame the opening of a feedback conversation with a senior engineer who missed a deadline?

Start with a neutral fact‑statement and a purpose clause: “I want to discuss the recent deadline shift so we can align on expectations and support you moving forward.” The opening must acknowledge the engineer’s expertise while signaling that the talk is about process, not personal judgment. In a Q2 debrief, the VP of Engineering pressed me to avoid “blame language” after a senior lead missed a release by ten days; the resulting opening saved the session from devolving into defensiveness. The opening is not an accusation, but a collaborative invitation; that distinction keeps the senior engineer engaged rather than shutting down. Use the “SBI” (Situation‑Behavior‑Impact) model only for the impact clause, then pivot to a purpose that frames the conversation as a joint problem‑solving effort.

What signals should I listen for to diagnose the root cause of missed deadlines?

Listen for three diagnostic signals: (1) workload overload, (2) ambiguous dependencies, and (3) autonomy friction. In a hiring‑committee style debrief, a senior engineer disclosed that his code review queue had doubled, a fact that explained the eight‑day slip without any competence question. The not‑observed signal is not “he is lazy”, but “the process bottleneck is hidden in the review pipeline”. Ask open‑ended questions such as “What blockers surfaced that you didn’t anticipate?” and note whether the engineer mentions external constraints versus internal decision‑making. Apply the “5 Whys” technique to each blocker; the depth of the answer reveals whether the issue is systemic (e.g., unclear API contracts) or personal (e.g., poor time‑boxing). The key judgment is that the missed deadline is a data point, and the real issue is the underlying signal you uncover through focused listening.

Which coaching framework turns a missed deadline into a growth opportunity?

Deploy the GROW model (Goal, Reality, Options, Way forward) immediately after the diagnostic phase. The senior engineer’s goal is to deliver on schedule; the reality is the eight‑day delay; the options include reallocating review resources, tightening acceptance criteria, or adjusting sprint cadence. In a recent senior‑engineer performance review, I used GROW to convert a missed deadline into a “process ownership” assignment, resulting in a 20 % reduction in future overruns. The not‑intended outcome is not “to reprimand”, but “to empower the engineer to own the bottleneck”. Conclude the GROW loop with a concrete way forward: a revised sprint plan, a measurable checkpoint in three days, and a documented escalation path. This structured coaching turns a negative event into a proactive development plan that the engineer can champion.

How can I convey expectations without sounding punitive?

State the revised expectations as a future‑oriented commitment, not a past‑focused indictment. For example: “By the end of next sprint, I expect the feature flag to be production‑ready, and I’ll track progress in our stand‑up with a 24‑hour milestone.” In a senior‑engineer one‑on‑one, I found that phrasing expectations as “commitments” rather than “requirements” increased compliance; the engineer responded positively, noting that the language respected his autonomy. The not‑effective phrasing is “you must not miss deadlines again”, but the effective phrasing is “let’s agree on checkpoints that keep the project on track”. Tie the expectation to a tangible metric—e.g., a 95 % on‑time rate over the next two releases—and anchor it to the engineer’s compensation band, which includes a $5,000 performance bonus tied to delivery reliability.

What follow‑up actions solidify the improvement after the feedback session?

Implement a three‑step follow‑up: (1) a written recap emailed within 24 hours, (2) a mid‑sprint check‑in, and (3) a post‑mortem that captures lessons learned. The written recap should restate the agreed‑upon way forward, include the specific metrics (e.g., “feature flag ready by day 12”), and reference the coaching framework used. In a recent post‑mortem, a senior engineer who had missed a deadline by eight days saw his next sprint deliver on time, directly because the manager logged the commitment and revisited it at the day‑7 stand‑up. The not‑sufficient follow‑up is “just hope it improves”, but the sufficient one is “track, review, and iterate”. By institutionalizing the follow‑up, you transform a single feedback moment into a sustainable performance loop.

Preparation Checklist

• Review the engineer’s recent deliverable timeline (the last three sprints showed a 12‑day variance on average).
• Draft the opening fact‑statement and purpose clause; keep it under 20 words.
• Identify three diagnostic signals by scanning the engineer’s JIRA comments and code‑review backlog.
• Map the conversation to the GROW framework, writing one bullet for each quadrant.
• Prepare the revised expectations with concrete dates and a success metric (e.g., 95 % on‑time rate).
• Schedule the follow‑up stand‑up and post‑mortem in the calendar, ensuring all stakeholders receive invites.
• Work through a structured preparation system (the PM Interview Playbook covers the GROW coaching model with real debrief examples, so you can see how senior engineers responded in similar scenarios).

Mistakes to Avoid

BAD: Starting the conversation with “You missed the deadline again; this is unacceptable.”

GOOD: Opening with “I want to discuss the recent deadline shift so we can align on expectations and support you moving forward.” The former attacks the person, the latter frames the talk as a collaborative problem‑solving session, preserving the senior engineer’s dignity and openness.

BAD: Assuming the cause is a personal time‑management issue and offering a generic productivity tip.

GOOD: Listening for systemic signals such as review queue size or unclear dependencies, then applying the “5 Whys” to uncover hidden process flaws. This avoids misdiagnosing the issue and directs corrective action to the right lever.

BAD: Sending a one‑off email that recaps the feedback but never revisiting the commitments.

GOOD: Sending the recap within 24 hours, scheduling a mid‑sprint check‑in, and documenting a post‑mortem to close the loop. The follow‑up reinforces accountability and demonstrates that the manager is invested in the engineer’s success, not merely reprimanding.

FAQ

What if the senior engineer pushes back on the revised expectations?

The judgment is to re‑anchor the expectations to shared product goals; say, “Our launch depends on this feature, so the checkpoint is non‑negotiable for the release timeline.” Offer a concrete mitigation option, such as reallocating a reviewer, rather than yielding to an indefinite timeline.

How do I handle a senior engineer who repeatedly misses deadlines despite the script?

Escalate to a performance‑management plan after documenting at least two cycles of the GROW‑based feedback, each with measurable outcomes. The script is not a one‑off; it becomes part of a documented improvement trajectory that can be escalated if the pattern persists.

Can I use this script for a junior engineer who missed a deadline?

Adopt the same structure but simplify the diagnostic phase; junior engineers often need clearer guidance on process constraints. The core judgment remains—focus on the underlying signal, not the missed date—and the GROW model still applies, albeit with more hand‑holding on the “Options” step.

The 0→1 PM Interview Playbook (2026 Edition) — view on Amazon →