Behavioral Scenario #23
The Timeline Pressure
“Your VP just told the board that AI tools will cut your team's delivery time in half. Your team says that's not how it works.”
The Situation
Your VP presented to the board that adopting AI coding tools would compress your team's 6-month roadmap to 3 months. Your team of 8 Android engineers has been using Copilot for 6 weeks. The actual productivity gain is real but narrower — boilerplate and test scaffolding are faster, but architecture decisions, code review, and integration work are unchanged. You're being asked to commit to the compressed timeline.
Context
- The board commitment has already been made — the VP cannot easily walk it back
- The VP's projection was based on industry benchmarks, not your team's actual 6-week data
- Real productivity gains exist but are task-specific — not uniform across the roadmap
- Your team has 6 weeks of granular task-level productivity data broken down by task type
- Team morale is at risk if engineers are asked to commit to a timeline they believe is impossible
- The roadmap timeline affects downstream hiring plans and product launch announcements
The Question
“Tell me about a time you had to push back on unrealistic expectations from leadership.”
Response Options
One of these is the strongest response. The others reflect common approaches with real trade-offs.
I committed to the compressed timeline to support the VP and maintain alignment with the board decision — then planned to raise concerns internally if we started falling behind.
I requested a meeting with the VP to present our 6-week productivity data broken down by task type — showing exactly where AI helps (boilerplate: 60% faster, test scaffolding: 40% faster) and where it doesn't (architecture: unchanged, code review: unchanged, integration: unchanged). I built a revised timeline model using the actual task distribution of our roadmap, calculated the real acceleration, and proposed a 4.5-month timeline with a clear methodology the VP could use to explain the recalibration to the board.
I refused to commit to the timeline without 6 more weeks of data to validate the productivity gains across more task types.
I committed to the timeline privately but told my team we'd re-evaluate after the first month and adjust scope if needed.
The Debrief
Why the Best Response Works
Answer B works because it gives the VP something to work with: a credible revised number and a methodology they can explain. The VP made a good-faith commitment based on bad data. Bringing the real data and a revised model isn't undermining the VP — it's giving them the tool to recalibrate credibly. Committing to an impossible timeline destroys trust faster than an early recalibration.
What to Avoid
Committing to an impossible timeline is the path of least resistance and the worst long-term outcome. The team knows the timeline is impossible — commitment without honest framing destroys morale before a single sprint. When the timeline slips (and it will), the damage is compounded because it was predictable. The Staff obligation is to surface delivery risk before commitment, not after.
What the Interviewer Is Probing
The interviewer is evaluating whether you can deliver difficult information to leadership constructively — not just say no, and not just comply. The revised model and the board-ready recalibration narrative are the signals that distinguish Staff-level delivery accountability from either obstruction or deference.
SOAR Structure
**Situation:** VP told the board that AI tools would compress a 6-month roadmap to 3 months; team had 6 weeks of actual productivity data showing narrower gains. **Obstacle:** Board commitment already made; VP couldn't easily walk it back; team morale at risk if asked to commit to an impossible timeline. **Action:** Requested a VP meeting; presented 6-week task-level productivity data; built a revised timeline model using actual roadmap task distribution; proposed 4.5 months with a clear methodology and a board-ready recalibration narrative. **Result:** VP recalibrated to 4.5 months with the board; team committed to a credible timeline; delivery completed in 4.5 months with no scope cuts.
The Learning Arc
"I learned that pushing back on leadership isn't about being right — it's about giving them the information they need to be right. The VP had good intent and bad data. My job was to bring better data, not to win an argument."
IC Level Calibration
Present the 6-week data to your manager, flag the timeline risk clearly, and ask for guidance on how to escalate the concern to the VP.
Build the task-level productivity model yourself, calculate the real acceleration, propose a credible revised timeline with a clear methodology, and give the VP the recalibration narrative they need to take back to the board — not just a revised number.
Reframe the conversation from 'timeline' to 'what outcomes matter most and what's the right level of investment to achieve them' — and propose a phased delivery structure that delivers high-value outcomes on the original timeline while being honest about what gets deferred.
Company Calibration
Amazon
LP: Are Right, A Lot + Deliver Results — data over benchmarks
OKRs at 0.7: commit to what's achievable, not what's aspirational
Netflix
Strong opinions loosely held: change your position when data changes
Stripe
RFC with evidence before commitment
Want to pick your response and see the full analysis?
Practice This Scenario Interactively