“Tell Me About a Time You Made a Decision With Limited Information”: How to Answer

The short answer: pick a real decision where you couldn’t wait for all the facts, and show your reasoning, not just the outcome. Say what you knew and what you didn’t, how you weighed the risk (could the decision be reversed?), what you decided and how you limited the downside, then the result and what you’d do differently. Two minutes, told with the STAR method. The same structure works for the close cousin, “Tell me about a time you used data to make a decision.”

What interviewers are looking for

Most real decisions are made before the data is complete, so this question tests how you act under uncertainty:

• Judgment: do you know what information matters, and when you have enough?
• Speed with care: do you move when waiting costs more than being wrong?
• Managing risk: do you make the decision reversible, test it small, or set a checkpoint?
• Ownership: do you take responsibility for the call, including if it turned out wrong?

Amazon builds the idea into its Leadership Principles. “Bias for Action” reads: “Speed matters in business. Many decisions and actions are reversible and do not need extensive study. We value calculated risk taking.” In his 2016 letter to shareholders, Jeff Bezos wrote that “most decisions should probably be made with somewhere around 70% of the information you wish you had,” and distinguished reversible decisions (“two-way doors”) from ones that are hard to undo.

How to structure your answer

Use STAR, with the reasoning in the middle made explicit:

1. Situation: the decision and why it couldn’t wait. One or two sentences.
2. Task: your role in it. Were you deciding, or recommending?
3. Action, in four parts:
   • What you knew, and what you didn’t.
   • How you filled the gap quickly: a quick check, a small sample, one expert, a comparable case.
   • How you weighed the risk: could it be reversed? What was the cost of waiting?
   • What you decided, and how you limited the downside: a pilot, a checkpoint, a fallback.
4. Result: what happened, ideally with a number, and what you learned.

Aim for about two minutes. If it went wrong, you can still use it: say what you learned and what you’d do next time.

Choosing your example

Good examples have a real deadline or cost of waiting, a genuine gap in information, and a decision that was yours or that you shaped. They come from anywhere: a launch date, a hiring choice, a customer escalation, a supplier problem, a class project.

Avoid examples where:

• You didn’t really lack information, you just didn’t look.
• Someone else made the call and you only carried it out.
• The stakes were trivial, like choosing a meeting time.
• You were reckless: acting fast without any check isn’t judgment.

Three sample answers

Examples are illustrations, not quotes from real candidates. Use your own decision and details.

A launch decision (product or marketing)

“We were two days from launching an email campaign when a tracking bug meant we couldn’t see results from our test send. I was the campaign owner. What we knew: the content had passed review and the audience was right. What we didn’t know was whether the new subject line outperformed the old one. Waiting a week for the fix would have missed the seasonal window. So I split the audience: 80% got the subject line we’d used successfully before, 20% got the new one, and I asked engineering to recover the data after launch. The campaign went out on time, and when tracking came back, the new subject line had a slightly higher open rate, so we used it for the next send. I learned to pick the version we could live with, and turn the uncertain part into a small test.”

An operations call (retail or hospitality)

“As a shift supervisor, I got a call an hour before opening that our delivery would arrive four hours late, with no detail on which items were affected. I knew our top sellers and roughly how much stock we had in the back; I didn’t know what the delivery contained. Closing a section would lose sales for certain; waiting risked empty shelves. I checked the back stock for our ten best sellers in fifteen minutes, moved staff to restock those first, and told the team to direct customers to substitutes for anything missing. We opened on time, kept the top sellers stocked, and the delivery filled the gaps by early afternoon. Afterwards I suggested a simple backup plan for late deliveries, which the store manager adopted.”

Using data to make a decision (analyst)

“Our support team wanted to hire two more people because response times had doubled. I was asked to check the data before the hiring request went up. The overall numbers supported it, but I only had three weeks of data after a product change, so I couldn’t tell if the spike would last. I split tickets by type and found that most of the increase was one question about the new billing page. Rather than recommend two hires on uncertain data, I proposed a help article and an in-app message for that question, and a check-in after two weeks. Tickets on that topic fell by more than half, response times recovered, and we hired one person instead of two.”

Mistakes to avoid

• Only describing the outcome. The interviewer wants your reasoning: what you knew, what you didn’t, and why you acted.
• Pretending you had no doubts. Naming the risk shows judgment; ignoring it sounds reckless.
• Blaming the lack of information. It’s the premise of the question. Focus on what you did about it.
• Choosing a story with no result. Even “we reversed it after a week and here’s what we learned” is a result.
• Going over three minutes. Cut the background to a sentence or two.

Related questions this answer covers

• “Tell me about a time you had to make a quick decision.”
• “Describe a decision you made without all the facts.”
• “Tell me about a time you used data to make a decision.”
• “Tell me about a time you took a calculated risk.”
• “Tell me about a time you made a decision you later changed.”

Prepare one strong story and you can adapt it to each. For more behavioral questions, see our mock interview questions.

Frequently asked questions

Sources

• Amazon, Leadership Principles: Bias for Action. Read on 30 September 2026.
• Jeff Bezos, 2016 Letter to Shareholders, Amazon, April 2017.