Critique the statement that product strategy should be fixed for two years

WHAT THIS TESTS: This question tests whether you view engineering as a partner in product discovery or as an order-taking function. The interviewer wants to see if you understand that technical execution quality degrades when teams are forced to ship against static assumptions for years. Specifically, they are probing for systems thinking: can you connect a business planning choice (fixed roadmap) to technical pathologies like lock-in, erosion of observability culture, and talent attrition.

A GOOD ANSWER COVERS: First, acknowledge the superficial appeal. A two-year fixed plan can offer temporary clarity on staffing, budget cycles, and foundational architecture choices like data model contracts or infrastructure commitments. Second, pivot immediately to the systemic drawbacks. Fixed plans incentivize feature factories where success is measured by roadmap completion rather than user or business outcomes. Third, explain the technical waste: senior engineers become executors instead of problem solvers, leading to disengagement and attrition. Fourth, describe the feedback blackout: without short iteration cycles and explicit decision points, teams cannot respond to telemetry that invalidates assumptions. Fifth, note technology lock-in: committing to stack choices for twenty-four months ignores market shifts and can saddle the team with obsolete dependencies. Finally, propose the alternative: an outcome-driven roadmap with observable metrics, small reversible iterations, and quarterly decision checkpoints.

COMMON WRONG ANSWERS: A major red flag is endorsing the statement because it lets engineers focus without distraction. This reveals a waterfall mindset and ignores that requirements decay the moment they are written. Another trap is criticizing the plan solely because requirements change, without naming the structural mechanisms that make adaptation possible, such as event tracking, feature flags, or evolutionary architecture. Complaining about product without proposing how engineering enables adaptability also signals passivity.

LIKELY FOLLOW-UPS: The interviewer may ask how you would structure a decision-making ritual if the roadmap is no longer the central contract. They might probe how to maintain architectural coherence without a fixed plan, or ask for a specific example of a time you killed a project based on data rather than delivering the original spec. Be ready to discuss how OKRs or North Star metrics replace Gantt charts without creating chaos.

ONE CONCRETE EXAMPLE: Imagine a team building a recommendation engine on a two-year fixed plan. Six months in, user behavior data shows that users prefer editorial curation over algorithmic feeds. Under a fixed plan, the team continues tuning models for eighteen more months because the roadmap says machine learning. Under an adaptive strategy, the team has a quarterly checkpoint tied to engagement outcome metrics, sees the signal, and pivots to a hybrid editorial system, saving compute costs and improving retention within the same budget cycle.

Source: 20tab.com