Improving a Product After Shipping Its MVP: Deciding What to Iterate On

This question comes from a behavioral round that also covers goals: "Have you been in a situation at work where you first built a minimum viable product (MVP) and then had to keep improving it? Walk me through it." The interviewer wants to hear how you scoped the first version, what you learned once it was in use, how you decided what to improve next, and what came of it. ```hint Pick a story with a real second act Choose a case where the first version was deliberately scoped down and the improvements that followed were driven by what you learned after launch, not a backlog that was fixed before you started. ``` ```hint Name your signals Be ready to say exactly which evidence told you what to change next (usage data, incidents, feedback from specific users) and what you chose not to do. ``` ### Clarifying Questions - Should the example be a customer-facing product, or can it be an internal tool, service or platform component? - Is the interviewer more interested in how the system evolved technically or in how you made decisions and worked with stakeholders? - How recent should the example be, and does it matter whether you led the work? ### What a Strong Answer Covers - Why the MVP was scoped the way it was: which shortcuts were taken on purpose and what was deferred - The specific post-launch signals and how they were turned into a prioritized list of improvements - How MVP shortcuts and technical debt were weighed against new functionality - The candidate's personal role and decisions, clearly separated from the team's - Measurable outcomes of the iterations and an honest reflection on what they would do differently - A link to goals: what success meant for the iteration phase and how progress was tracked ### Follow-up Questions - Which MVP shortcut caused the most trouble later, and would you take it again? - How did you decide between incrementally improving the MVP and rebuilding parts of it? - What goals did you set for the iteration phase, and how did you know when the product was good enough to stop iterating? - Tell me about a piece of feedback you deliberately decided not to act on.