Skip to main content

Management Consultant

How do you decide what not to analyse when time is short?

TechnicalAny levelTests: Problem structuring
Drill this questionCreate a free account to answer out loud with Ava and get feedback.

What the interviewer is looking for

  • This question tests problem structuring. Breaks a vague problem into clear, non-overlapping parts, forms hypotheses and focuses on what matters most.
  • Strong answers: Prioritises by impact on the decision, uses hypotheses to focus, accepts good-enough precision and flags what remains uncertain.
  • Likely follow-up: Tell me about a time you skipped something that later mattered.

Another way it may be asked: You have two days and could spend two weeks on analysis. How do you choose what to skip?

A structure to follow: Answer, explain, example, limits

  1. Step 1

    Answer

    Give your direct answer in the first sentence so the interviewer knows where you are going.

  2. Step 2

    Explain

    Say how it works or why you would do it that way, in plain words before jargon.

  3. Step 3

    Example

    Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

  4. Step 4

    Limits

    Say when your approach would not be the right one. It shows judgement.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

  • Reciting a definition without showing you have applied it.
  • Using terms you cannot explain if asked a level deeper.
  • Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Browse all questions

How do you decide what not to analyse when time is short? | How to answer