Strategy question

You are two weeks into a six-week forward-deployed engagement when three things happen at once: the partner asks for additional scope, engineering finds an integration blocker, and executives want a firm go-live date. How would you re-scope the work, protect pod focus and pace, make the right trade-offs, and keep hospital leadership aligned on an outcome that is still worth shipping?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Ability to manage competing pressures in a time boxed deployment and protect the team's ability to ship something real.

Triage the three pressures by what actually threatens the go live date: the integration blocker is the most immediate technical risk and must be assessed first for severity and workaround options.
Push back on the additional scope request explicitly, proposing it as a follow on phase rather than absorbing it into the current six week window, to protect the pod's focus.
Work with engineering to scope a fallback for the integration blocker, for example a narrower initial integration that still delivers core value, if the full solution cannot be fixed in time.
Bring executives a concrete, evidence based go live date recommendation based on the narrowed scope and blocker workaround, rather than agreeing to an arbitrary date under pressure.
Communicate transparently with hospital leadership about what will ship on the original date versus what moves to a follow on phase, framing it as protecting quality and reliability for their clinicians.
Document the deferred scope explicitly as a committed next phase, so the partner does not feel the ask was simply dropped.

Protects the six week scope by explicitly deferring the additional ask rather than silently absorbing it and risking the whole engagement.
Proposes a concrete fallback for the integration blocker instead of just reporting the problem upward.
Gives executives an evidence based date instead of caving to pressure for an arbitrary one.
Keeps hospital leadership aligned by being transparent about tradeoffs rather than overpromising.

Trying to absorb all three pressures at once, which risks shipping something rushed and unreliable on go live day.
Caving to executive pressure for a date without validating it against the real technical blocker.

How would you decide if the integration blocker was severe enough to delay go live entirely?
What would you do if the partner refused to accept deferring the additional scope?