Management Consulting Essentials

0 of 18 lessons complete (0%)

Framing the problem

Turning a vague ask into a sharp question

This is a preview lesson

Purchase this course, or sign in if you’re already enrolled, to take this lesson.

Clients rarely arrive with a well-formed question. They say "our margins are slipping," "we need a growth strategy" or "something is wrong with the sales team." A consultant’s first job is to turn that vague ask into a sharp question that can be answered within the time and budget available. Everything else in an engagement depends on getting this right.

Why vague asks are dangerous

A vague ask allows everyone to imagine a different outcome. The chief executive expects a market entry plan, the finance director expects cost savings and the sales director expects validation of a hiring plan. At the final meeting, at least two of them are disappointed. Sharpening the question early aligns expectations and prevents wasted work.

Features of a sharp question

A sharp question is:

  • Specific: it names the business, the decision and the metric.
  • Actionable: answering it leads to a decision someone can make.
  • Time-bound: it states the time horizon.
  • Measurable: success can be assessed.
  • Owned: a named decision maker cares about the answer.

Compare:

  • Vague: "How can we grow?"
  • Sharp: "Which two of our five regional markets should we prioritize for additional sales investment over the next 18 months to add £4 million in annual gross margin?"

Techniques for sharpening

Ask what decision will be made
"When this work is finished, what will you decide differently?" If the client cannot answer, the question is not ready.

Ask what success looks like
"In a year, how will you know this was worthwhile?" This reveals the metric that matters.

Ask why now
Understanding the trigger, such as a lost customer, a board request or a competitor move, reveals urgency and constraints.

Ask what has been tried
Previous attempts reveal assumptions, politics and dead ends.

Ask about constraints
Budget, timing, capabilities, regulatory limits and options already ruled out by leadership.

The problem statement

Capture the result in a one-page problem statement:

  • Core question.
  • Context: what is happening and why it matters.
  • Decision maker and key stakeholders.
  • Criteria for success.
  • Scope: what is in and out.
  • Constraints.
  • Timeline.

Share it with the client and get explicit agreement. Revisit it at each steering meeting.

Common traps

  • Accepting the client’s solution as the question: "Help us implement a new CRM" may hide the real problem of poor sales conversion.
  • Questions that are too broad: "Fix our operations" cannot be answered in eight weeks.
  • Questions that are too narrow: answering a small question precisely while the real issue sits elsewhere.
  • Multiple questions merged into one: split them and prioritize.

Testing the question

Imagine the final recommendation. Would it answer the question in a way the decision maker can act on? If the answer is "it depends," refine further.

Your exercise

Take a vague business problem from your experience, such as "customer complaints are rising." Use the techniques above to write a sharp core question and a one-page problem statement. Identify who would need to agree to it.

Editorial & AI Disclosure