# Lead a Project Through Ambiguous Requirements Describe a project that had to move forward before the requirements and available information were clear. Explain how you reduced the most dangerous uncertainty, made reversible progress, and aligned the people who needed to decide. Do not claim that you “created clarity” in general terms. Identify what was unknown, which unknowns mattered first, what you learned, and how that learning changed the plan. ### Constraints & Assumptions - Use a real situation where waiting for complete certainty was not practical. - Distinguish reversible decisions from commitments that would be expensive to undo. - Explain who had decision authority and how stakeholders participated. - Include a point where new information changed your direction or scope. ### Clarifying Questions to Ask - Is the interviewer interested primarily in product ambiguity, technical ambiguity, or both? - Was the candidate the formal decision owner or an influencer? - Can the example involve an exploratory project that did not proceed to full launch? ```hint Rank unknowns by consequence Resolve the assumption that could invalidate the project before polishing details that are easy to change later. ``` ```hint Turn opinions into tests A prototype, user observation, interface spike, or operational rehearsal can replace a debate with evidence. ``` ### What a Strong Answer Covers - The goal, known constraints, unresolved questions, and cost of waiting. - Prioritization of uncertainties by impact and reversibility. - Small experiments or prototypes tied to explicit decision criteria. - A decision log, owners, checkpoints, and communication that prevented different groups from using incompatible assumptions. - A course correction based on evidence rather than attachment to the first plan. - An outcome that includes what was learned even if full scope was not delivered. ### Follow-up Questions 1. Which unknown could have invalidated the entire project? 2. What did you choose not to investigate at first? 3. How did you prevent a prototype from becoming accidental production code? 4. Who disagreed with your sequencing, and how did you resolve it? 5. What evidence caused you to change the plan?