Management Consultant interview questions

I turn ambiguity into a clear decision, a bounded scope, and a small set of testable drivers.

• I restate the decision the client must make, the deadline, and the metric that defines success.
• I separate known facts, assumptions, and open questions so the team does not treat opinions as evidence.
• I build an initial issue tree around the outcome and revise it after the first fact base is available.

A strong problem statement names the decision, scope, constraints, and measurable outcome.

• It identifies the decision owner and the date by which that person needs an answer.
• It sets boundaries such as geography, business unit, customer group, and planning horizon.
• It defines success with a metric such as margin improvement, growth, or payback period rather than a vague goal.

I link each priority hypothesis to the analysis, evidence, owner, and decision it will support.

• I phrase hypotheses so evidence can disprove them, such as margin decline being driven mainly by discount leakage.
• I assign a minimum proof standard and a deliverable to each hypothesis before work begins.
• I sequence tests by decision value and effort, then stop low-value analyses once the answer is sufficiently clear.

A useful hypothesis is specific, falsifiable, material to the decision, and tied to observable evidence.

• It states a proposed relationship, not a topic, such as churn rising because service failures increased among high-value customers.
• It identifies what evidence would support or reject it, including the relevant segment and time period.
• It matters enough that confirming or rejecting it changes the recommendation or the next analysis.

I split the outcome into branches that do not overlap and together explain the full problem.

• I choose one logic at each level, such as revenue versus cost, rather than mixing financial and organizational categories.
• I define branch boundaries explicitly so the same driver cannot appear in two places.
• I test completeness against the governing equation, process, or customer journey and add an explicit residual only when necessary.

I test every level for duplicate causes and for outcomes that cannot be assigned to any branch.

• For mutual exclusivity, I take sample facts and verify that each belongs in only one branch.
• For collective exhaustiveness, I reconcile the leaves to a total, equation, or complete process boundary.
• I ask another team member to classify edge cases because overlap is often invisible to the person who built the tree.

I prioritize branches by likely impact, uncertainty, and the effort required to resolve them.

• I first rank materiality using a rough calculation so a small driver does not consume a large share of the workplan.
• I move uncertain branches upward when resolving them could change the direction of the case.
• I favor quick tests with decisive evidence and defer expensive analyses that would not alter the recommendation.

I define in advance what combination of data, triangulation, and confidence is enough to make the decision.

• I specify the metric, comparison group, time window, and threshold that would support or reject the hypothesis.
• I distinguish directional evidence for an early steer from audited evidence required for an investment case.
• I require a second source when one dataset has known bias, weak coverage, or an interested owner.

I start with low-effort analyses that can eliminate major branches before commissioning detailed work.

• I use rough orders of magnitude to identify which drivers could materially affect the answer.
• I schedule long-lead inputs such as customer data or expert interviews early, even if their analysis comes later.
• I preserve time for synthesis and quality review rather than letting data collection consume the full timetable.

Answer-first checkpoints expose the emerging conclusion and evidence gaps before the team overinvests in analysis.

• I ask each module owner to state the current answer, confidence level, and one fact that could change it.
• I compare findings against the original hypotheses and retire branches that no longer matter.
• I update the storyline and next actions immediately so the workplan follows the decision rather than the initial task list.

Top-down and bottom-up estimates provide independent views that should converge within an explainable range.

• Top-down starts from a broad market total and applies relevant filters such as geography, segment, and eligibility.
• Bottom-up multiplies operating units such as customers, annual volume, and average price using observable drivers.
• I reconcile the gap by checking definitions, missing channels, double counting, and whether price includes discounts or taxes.

I structure commercial due diligence around market attractiveness, target position, customer quality, and the durability of the plan.

• Market work tests size, growth, profit pools, regulation, and structural risks using consistent definitions.
• Company work tests share, differentiation, customer retention, pricing power, and the credibility of management forecasts.
• I convert findings into base, upside, and downside cases linked to the investment thesis and key deal risks.

I assess whether the market offers durable growth and accessible profit pools rather than growth in headline revenue alone.

• I segment historical and forecast growth by product, customer, geography, and price versus volume.
• I examine margins, concentration, cyclicality, regulation, substitutes, and capacity additions that could change economics.
• I triangulate published data with customer interviews and competitor evidence because management definitions often overstate the addressable market.

I evaluate competitive position through share, differentiation, customer behavior, and the economics required to defend that position.

• I calculate share by relevant segment and distinguish organic gains from acquisitions or favorable mix.
• I test differentiation through win-loss data, customer interviews, price realization, and switching behavior.
• I examine competitor capacity, product roadmaps, and response options to judge whether current advantages can persist.

The most useful customer evidence explains retention, share of wallet, purchase criteria, and future demand by segment.

• I combine cohort data on churn and spend with interviews that reveal why customers stay, leave, or split purchases.
• I separate stated intent from observed behavior and challenge optimistic survey responses with transaction history.
• I weight evidence by customer value and representativeness so a vocal small account does not drive the investment view.

I structure market entry around attractiveness, right to win, entry economics, and execution requirements.

• Attractiveness covers demand, profit pools, regulation, channel structure, and likely competitive response.
• Right to win tests the client's capabilities, brand, customer access, cost position, and transferability of its advantage.
• Entry economics compare investment, ramp-up, cash flow, break-even, and downside exposure across feasible entry modes.

I compare entry modes on control, speed, investment, capability access, and reversibility.

• Organic entry offers control and learning but usually has the slowest customer and capability ramp.
• Acquisition accelerates scale but adds valuation, integration, and legacy-risk exposure.
• Partnership or licensing lowers capital needs but requires clear economics, governance, data rights, and exit terms.

I decompose growth into retention, expansion, acquisition, price, mix, and new-market contributions.

• I build a bridge from current to target revenue so every source of growth is explicit and additive.
• I segment the bridge by customer, product, channel, and geography to locate where growth is actually changing.
• I separate market growth from share gain because they require different evidence, capabilities, and risk assumptions.

I prioritize growth initiatives by incremental value, confidence, time to impact, capability fit, and investment required.

• I estimate revenue after cannibalization and apply contribution margin rather than ranking ideas on gross sales.
• I discount value for adoption risk, execution dependencies, and the time needed to reach scale.
• I build a balanced portfolio of quick wins and larger bets instead of selecting only high-value but distant opportunities.

A price waterfall reveals how list price becomes pocket price through discounts, rebates, fees, and leakage.

• I quantify each deduction by customer, product, channel, and salesperson to locate inconsistent realization.
• I distinguish contracted concessions from avoidable leakage such as waived fees or unapproved discounts.
• I connect pocket price to volume and margin so recommendations protect valuable accounts while closing unjustified gaps.