Closing the Gap Between a Two-Week Deadline and a Four-Week Engineering Estimate

You are a product manager responsible for delivering a new product feature. The engineering team estimates the work at four weeks, but your stakeholders need the feature in place within two weeks. How would you handle the gap between the estimate and the deadline? ```hint Question both numbers Before picking a fix, learn what sits behind each number: why the stakeholders need the feature in two weeks, and which pieces of work add up to the four-week estimate. ``` ### Clarifying Questions - What happens if the feature is not ready in two weeks: is the date tied to a customer commitment, a legal requirement or a launch event, or is it a preference? - Do the stakeholders need the whole feature by then, or a specific outcome that a smaller version could deliver? - What does the four-week estimate include (design, build, testing, reviews, rollout), and is the team committed to other work during those weeks? - Who has the authority to change the scope, the date or the team's other priorities? ### What a Strong Answer Covers - Discovering the reason behind the deadline and the make-up of the estimate before proposing a solution. - A range of options (reducing scope, releasing in phases, removing dependencies, adding or reassigning people, a temporary workaround, moving the date) with the cost and risk of each. - A clear stance on quality and the team: no silent cuts to testing on risky changes and no pressure on engineers to shrink an honest estimate. - How the decision is communicated and agreed with stakeholders and engineering, and how delivery is tracked afterwards. ### Follow-up Questions - Engineering says no smaller version of the feature would be useful on its own. What do you do? - A senior stakeholder tells you to have the team "just make it happen" in two weeks. How do you respond? - Describe a time you faced a deadline your team could not meet with the original scope, and what you did.