Tell me about a strategic decision you had to make without clear data or benchmarks.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess how you operate when certainty is unavailable and waiting for perfect information is not an option. They want to see how you frame ambiguity, make reasonable assumptions, manage risk, and take responsibility for the consequences of a directional choice. At higher levels, they are also listening for whether the decision matched the scope of your role and whether you created a path to learn quickly after committing.
Key Insights
- You do not need a dramatic bet-the-company story, but you do need a decision that actually mattered. If the choice was trivial or easily reversible, it will be hard to show judgment under uncertainty.
- Do not answer this as if the point is that you were right. The stronger story is usually about how you made a sound decision process despite incomplete information, including what assumptions you made and how you reduced downside risk.
- You should make the uncertainty legible. Name what data was missing, why it was missing, what signals you used instead, and how you planned to learn after the decision rather than pretending you somehow had certainty.
What interviewers probe atlevel
Top Priority
Show that you knew what you did not know and still used reasonable signals instead of guessing blindly.
Good examples
🟢We had no direct usage data yet, so I looked at similar flows in the product, asked support what confused users most, and used that as a proxy for which version was safer to ship first.
🟢We couldn't benchmark the new path in production, so I broke the unknowns into technical risk and user risk and chose the option that reduced both enough for an initial release.
Bad examples
🔴We didn't really have data, so I went with my instinct that users would probably prefer the more flexible version.
🔴There weren't benchmarks, and my lead was out, so I just chose the approach that felt more standard.
Weak answers treat missing data as permission to rely on instinct; strong answers identify the unknowns and use substitute signals thoughtfully.
Valuable
Example answers atlevel
Great answers
On a small onboarding feature I owned, we had to decide whether to build a flexible setup flow that covered several future cases or a much simpler version for the current release. We didn't have user data yet because this feature was brand new, so I looked at support tickets from similar parts of the product and talked with a designer about where new users were most likely to get stuck. Based on that, I recommended the simpler version first, with the new behavior behind a flag so we could expand it later if needed. That let us ship on time without replacing the old path immediately. After release, I checked the support feedback and error reports for two weeks, and the simpler path handled the common cases well, so we kept it and only added one missing edge case later.
On a small mobile feature I owned for a health-focused app, we had to decide whether to add analytics now so we could learn how people used it, or wait because our privacy rules meant we couldn't collect identifiable data without explicit consent. There were no benchmarks to tell me which approach was safer or more useful, so I talked with our product manager, legal counsel, and a senior engineer to map the risks and benefits. I recommended sending only a tiny set of anonymous, aggregated events that couldn't be tied to a person, and pairing that with a clear opt-in prompt for richer tracking later. I also wrote a short implementation checklist so the team would avoid accidentally logging any personal data. After the release we got just enough high-level insight to prioritize two small usability fixes, and there were no privacy incidents or user complaints — which reassured us to expand tracking only after testing the opt-in flow.
Poor answers
I had to make a strategic decision on a feature when we didn't really have benchmarks, and I chose the more complete implementation because it seemed better to do it once. I didn't want to spend time on a temporary version that we'd just throw away. We shipped it, and overall it was fine because nobody raised major issues after that. I think it showed that I'm comfortable making decisions quickly.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid November, 2025
Early January, 2025
Early November, 2024
Tell me about a strategic decision you had to make without clear data or benchmarks. How did you make your final decision? What alternatives did you consider? What were the tradeoffs of each? How did you mitigate risk?
Hello Interview Premium
Your account is free and you can post anonymously if you choose.