Late but Critical Colleague
Company: Amazon
Role: Product Manager
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Online Assessment
##### Question
In a recurring bi-weekly meeting a teammate who owns essential data is habitually late because the meeting overlaps with their prior call. Describe how you would:
Decide whether to approach the colleague in-person, by phone, or another channel and why.
Evaluate options such as moving the meeting, collecting their data in advance, or sending a delegate.
Select and implement the best solution while preserving team morale and delivery cadence.
Overview: Practice a behavioral scenario about a late but critical colleague in a recurring planning meeting. The solution covers private communication, option evaluation, pre-reads, delegates, agenda changes, meeting reliability metrics, morale, and escalation.
Solution
This solution follows the enhanced behavioral scenario by balancing empathy, meeting reliability, async pre-reads, backup coverage, metrics, and escalation discipline.
## Approach
Use a structured, empathetic, and data-driven process: diagnose the root cause, choose the right communication channel, evaluate alternatives against clear criteria, implement a pilot, and measure outcomes.
---
## 1) Choosing the communication channel
Goal: quickly understand constraints and co-design a fix without creating friction.
Decision guide:
- Sensitive or nuanced topic (habitual lateness, tradeoffs)? Choose a private synchronous channel: 1:1 in-person if co-located; otherwise video/phone. This reduces misinterpretation and builds trust.
- Need an audit trail or to share artifacts (agenda, pre-read, proposed new process)? Follow up with written confirmation (email/Slack) after the 1:1.
- Urgency high (next meeting is imminent)? Send a brief heads-up via chat, then book a 15–20 min 1:1 ASAP.
Sample flow:
- Step 1: DM: "Noticed the overlap is making it hard to start with your metrics; could we do a quick 15 min to adjust the process?"
- Step 2: 1:1 call to understand constraints (time zones, immovable prior call, bandwidth, manager expectations).
- Step 3: Summarize agreements in writing to avoid misalignment.
Rationale: Private synchronous conversation shows respect, enables rapid problem-solving, and preserves morale; written follow-up creates clarity.
---
## 2) Evaluating options
Define success criteria before choosing a solution:
- Reliability: required data available by meeting start ≥ 95% of time.
- Cadence: meeting length and start time unchanged or improved.
- Load: minimal additional burden on the data owner and team.
- Morale: respectful of schedules; avoids public pressure.
- Sustainability: works across time zones and vacations.
Options to consider:
1) Collect data async in advance (pre-read)
- Pros: decouples meeting from individual availability; improves prep quality.
- Cons: requires discipline and reminders; may need templates/automation.
- Enablers: standard template, due 24 hours before; automated reminders; dashboard link.
2) Send a delegate (backup)
- Pros: keeps meeting unblocked; knowledge spread; vacation coverage.
- Cons: delegate must be empowered and prepared.
- Enablers: RACI with named backup; access to dashboards; decision guardrails.
3) Move or reshape the meeting
- Pros: addresses root scheduling conflict.
- Cons: may disrupt many calendars; could harm morale if time zones suffer.
- Variants: shift 15–20 min; reorder agenda so data section occurs after the colleague can join; or split into two short sessions (async review + brief decisions sync).
4) Calendar engineering
- Pros: reduces friction without major change.
- Tactics: shorten prior meeting by 5–10 min; add travel buffer; align with their manager.
Small scoring example (1–5, higher is better) against success criteria:
- Pre-read + delegate + agenda reorder: Reliability 5, Cadence 4, Load 4, Morale 5, Sustainability 5 → Avg ≈ 4.6
- Move entire meeting: Reliability 4, Cadence 3, Load 3, Morale 3, Sustainability 3 → Avg ≈ 3.2
- Rely on reminders only: Reliability 2, Cadence 4, Load 5, Morale 4, Sustainability 2 → Avg ≈ 3.4
Conclusion: Start with an async-first workflow (pre-read) plus a named delegate and minor agenda tweaks; consider small time shift only if needed.
---
## 3) Selecting and implementing the solution
Recommended plan (low-friction, high-reliability):
Phase A — Align (week 0):
1) 1:1 discovery: confirm the overlap is persistent; ask about feasible micro-shifts (±15 min) and backup coverage.
2) Co-design norms:
- Pre-read/data due 24 hours before meeting in a standard template (owner, last updated, key metrics, risks, decisions needed).
- Named delegate with decision bounds if the owner can’t attend on time.
- Agenda reordered so their segment is 10–15 min after start or at a predictable slot they can make.
- Automate reminders (calendar invite description + reminder bot) and link to a live dashboard.
3) Socialize in writing with the broader group; invite feedback within 24–48 hours.
Phase B — Pilot (2–3 cycles):
4) Implement for the next two meetings. Add guardrails:
- If pre-read not submitted by T-24h, ping owner and delegate; at T-12h, ping manager only if pattern persists (avoid first-time escalation).
- Meeting begins on time; decisions proceed using pre-reads; questions for the owner/delegate captured in notes.
5) Measure:
- On-time data availability (%).
- Start-on-time rate.
- Decision completion rate.
- Qualitative feedback on load/morale.
Phase C — Adjust or expand:
6) If reliability < 95%, consider a small shift (e.g., +15 min) or split: 20-min async review + 15-min sync for decisions.
7) Document the working agreement in the team’s operating playbook; reaffirm quarterly.
---
## Communication templates
- Kickoff note: "To keep our bi-weekly review efficient, we’ll use a one-page pre-read due 24h before. If the data owner is unavailable, [Delegate] will represent. We’ll review this segment at HH:MM to accommodate schedules. Success = data ready by start and decisions unblocked."
- Friendly reminder (T-26h): "Gentle nudge: metrics pre-read due by tomorrow HH:MM. Reply if any blockers; happy to help."
---
## Pitfalls and mitigations
- Pitfall: Publicly calling out lateness → Mitigation: handle 1:1; praise publicly when the new process works.
- Pitfall: Over-reliance on a single person → Mitigation: delegate + shared dashboard; rotate coverage.
- Pitfall: Process creep → Mitigation: keep templates lightweight; automate reminders.
- Pitfall: Moving the meeting harms other time zones → Mitigation: try agenda reorder or micro-shift first; rotate only if necessary.
---
## Validation and guardrails
- Define success upfront (e.g., 95% of meetings start with all required data; decision completion ≥ 90%).
- Run a 2–3 meeting pilot; if metrics don’t improve, revisit time shift with a short survey to gauge impact.
- Escalate to the colleague’s manager only if repeated misses persist after agreed changes; frame as a joint scheduling problem, not a performance issue.
---
## Outcome
This approach preserves morale (private, empathetic alignment), protects cadence (on-time start, async pre-reads), and improves reliability (delegate + automation), while keeping escalation and meeting moves as last-resort options.
Community answers
Answer by rschroeter2124
I would have a call, or a 1:1 with the employee at our earliest convenience after the most recent incidence of lateness.
Discuss the issue with the owner of the previous call and ask why they are always late in ending. See if we can come to an agreement given the disruptive costs and impact.
Keep it light, keep it fact-based, explain the impact, and cost that is currently happening.
