1. If your team has to complete a project before a deadline and your manager will become unavailable after a few days, how would you coordinate with y…
The full question
If your team has to complete a project before a deadline and your manager will become unavailable after a few days, how would you coordinate with your team to meet the deadline?
Model answer
- Situation — On a delivery project with a fixed release date, our manager had to become unavailable shortly after the work began. The team still had several dependent tasks to finish, so the main risk was losing time to unclear priorities or waiting for decisions.
- Task — I needed to help the team agree on a realistic plan, make ownership clear, and keep work moving without relying on the manager for day-to-day decisions.
- Action
- I first asked the manager to confirm the deadline, the must-have scope, known risks, and which decisions we could make independently. I documented the answers, along with escalation contacts and any decisions that genuinely required management approval.
- I worked with the team to break the remaining work into small, verifiable tasks. We mapped dependencies, estimated effort together, and identified the critical path rather than treating every item as equally urgent.
- I proposed owners and backups for each critical task, and checked that the workload was balanced. For example, if an API change blocked both UI and testing, I made that dependency explicit and arranged an early integration point instead of leaving integration until the end.
- Before the manager became unavailable, I shared a concise plan and risk list with them and asked for quick agreement on scope trade-offs. We also agreed who would make routine technical decisions and how to escalate a blocker that could affect the deadline.
- I set a short daily team sync focused on progress, next steps, and blockers, plus a shared status page. I kept updates factual and raised risks early, with options—for example, defer a lower-priority enhancement rather than reduce testing on a critical path.
- I reserved time for integration, regression testing, and release preparation, and adjusted task assignments when a dependency slipped. I would keep stakeholders informed rather than presenting an optimistic date without evidence.
- Result — The team had a shared plan and clear decision ownership before the manager stepped away, which reduced waiting and made risks visible early. We completed the agreed release scope by the deadline, while documenting any deferred items for follow-up. I learned that preparation for a manager’s absence is less about adding meetings and more about securing decisions early, distributing ownership, and making progress transparent.