How do you deliver when time is tight?

## What a strong answer looks like A great answer shows **structured execution under ambiguity**: clarify success criteria, cut/sequence scope, manage risk, and communicate proactively. ### 1) Align on “definition of done” and constraints (fast) - Ask for the **deadline, hard vs soft**, and what happens if you slip. - Confirm **success metrics** (e.g., latency, correctness, revenue impact, user experience). - Identify non-negotiables: compliance/security, data integrity, SLOs, launch criteria. - Clarify dependencies (other teams, vendor approvals, data availability). ### 2) Break down scope and choose an MVP - Decompose work into deliverables and list **Must-have / Should-have / Could-have** (MoSCoW). - Propose an **MVP** that meets the core goal by the deadline. - Make trade-offs explicit: - reduce features - reduce platform coverage - phase rollout (internal → % traffic → GA) - accept short-term manual steps with a plan to automate later ### 3) Create an execution plan with milestones and owners - Produce a short plan: milestones, dates, owners, dependencies. - Parallelize work streams where possible. - Use a lightweight tracking mechanism (ticket board + daily check-in or async updates). - Define “go/no-go” checkpoints and what evidence is required (tests passing, dashboards live, etc.). ### 4) Manage risks proactively - Make a risk list early (top 3–5) and add mitigation: - risky integration → spike/prototype first - unclear requirements → quick stakeholder review / mock - performance unknowns → load test early - Escalate early when risks threaten the date; bring options, not just problems. ### 5) Communicate clearly and frequently - Provide a predictable cadence: brief daily update or 2–3 times/week status. - Communicate in terms stakeholders care about: timeline, trade-offs, and risk. - If scope changes, explicitly renegotiate: “If we add X, we must drop Y or move the date.” ### 6) Protect quality without overbuilding - Focus on the highest ROI quality gates: - unit/integration tests on critical paths - monitoring/alerting and rollback plan - staged rollout and feature flags - Avoid gold-plating; document known limitations and follow-up work. ## A STAR-style sample answer outline - **S (Situation):** Deadline moved up by 3 weeks; multiple dependencies. - **T (Task):** Deliver a reliable MVP by the new date. - **A (Action):** Clarified success metrics, created MVP scope, split work, ran early spike on riskiest dependency, set daily updates, implemented feature flag + staged rollout. - **R (Result):** Shipped on time, met key metric, avoided incident; followed up with planned enhancements. ## Common pitfalls to avoid - Saying “I just work longer hours” without mentioning prioritization and trade-offs. - Not mentioning stakeholder alignment (shipping the wrong thing on time is still failure). - No risk management or rollback plan. - Ignoring quality entirely (which often causes deadline misses later due to outages/hotfixes).