Tell me about a time you rescued a project in trouble.

Question

Accepted Answer

This tests **turnaround leadership**: diagnosing why a project is failing, making hard calls, and rallying a demoralized team. Show structure, not heroics.

## How to approach it

```text
1. Diagnose honestly — scope, technical, or people problem?
2. Stabilize — cut scope to a credible, shippable core
3. Rebuild trust with stakeholders via small, frequent wins
4. Re-energize the team with a clear, achievable goal
```

## Worked example

```text
S: A project was three months late with a burned-out team and no clear end.
T: Leadership asked me to get it back on track.
A: I found the real issue was scope creep, not ability. I renegotiated to a
   focused MVP, set a weekly demo cadence to rebuild stakeholder trust, and
   protected the team from new requests.
R: We shipped the MVP in six weeks; stakeholders got value early and signed off
   on a realistic plan for the rest.
```

## Good vs weak

```text
✓ Diagnose, cut scope, rebuild trust, protect the team
✗ "I just told everyone to work harder"
✗ Blaming the previous lead with no plan
```

## Why it matters

Struggling projects need calm diagnosis, not blame — the cause is usually scope or clarity, not effort.

Frequent small wins rebuild the stakeholder trust that a late project has lost.

Protecting and re-energizing a demoralized team is leadership that delivery alone can't replace.