Management Consulting Interview Questions

Interviewers tend to learn two things by asking this question:

First, interviewers are interested in learning more about your accomplishments and job history. Frequently, interviewers don't have enough time to review your resume before.

Two, interviewers are interested in learning why you might make an excellent consultant. Your accomplishments from prior employment and the abilities you have gained from the previous experience.

You can answer this way:

I have over four years of expertise in media and e-commerce as a specialist in marketing and strategy. I worked for Davidson Digital for the past two years, where I oversaw social media marketing. I devised and carried out marketing strategies that generated sales of over $2 million. Additionally, I created a marketing plan that reduced the cost of acquiring customers by 20%.

Prior to that, I worked for Myspace for three years in their advertisements team. To determine the main customer pain problems for ad buyers, I conducted customer feedback and focus groups. I used this information to launch more than fifty personalized email campaigns with a 25% greater conversion rate than earlier ones.

Choose three persuasive reasons for your interest in consulting when responding to this question, and then construct your response using the basic yet powerful format below.

• State that your top career option is consulting.
• Mention that consulting best meets your objectives and aspirations as a professional.

You can answer this way:

For the following three reasons, consulting is currently my top option for a profession.

First, I want to have a substantial influence by collaborating with billion-dollar company executives on their most difficult business issues. What motivates me to get out of bed in the morning is the chance to have such a significant impact.

Two, my past employment at ABC Company has given me a passion for the energy industry. Through advising, I can hone my energy expertise as well as the soft and hard abilities necessary to succeed as a corporate executive.

Three, I appreciate collaborating with groups of people, especially those that are exceptional and intelligent. I'm eager to get to know my coworkers better and form connections with them.

I currently believe that consulting is the one job that best fits my professional objectives and aspirations.

This is a tough variation of the same question, which is surprising. Because you want to demonstrate that you are a leader and an excellent team player, be careful when providing an example to avoid giving the impression that you did not "step up," that is, that you did not meet the expectations of people around you. It would be much better to give an instance where you were initially dubious of whether the former was the best course of action, but after more thought, determined that it was—and then carried out the former decision as effectively as you could.

These days, people don't ask this topic as much, largely because the responses are usually really uninteresting.

However, have a response ready that highlights a milestone that isn't necessarily the highlight of your résumé. It gives the interviewer more knowledge about you and admiration for your skills by revealing a different accomplishment.

This question is a great opportunity to establish a rapport with the interviewer while also repeatedly highlighting abilities and experiences that will demonstrate your potential as an "amazing" consultant and an engaging team member.

If the subject is work-related, your response to this question may trigger a more in-depth, focused discussion, so be prepared before your interview. If the question pertains to a particular industry that is mentioned on your resume, for instance, be familiar with the market size, growth rate, major competitors, factors that affect revenue and expenses, barriers to entry, key products, target market, market trends, legal and ethical considerations, etc. The interviewer will be astonished.

These days, fewer people ask this question.

Be ready with a response, though, that demonstrates that you really did encounter a challenging learning situation—some form of challenge to go past—and that you truly did learn something from that experience and have incorporated it into how you live today. This demonstrates resilience, which is a valuable quality in consulting. To put it gently, not all consulting projects go off without a hitch or run without a hitch. Your career and interview process may benefit from your ability to "turn lemons into lemonade.

Prepare a response that demonstrates your strengths with examples from your prior employment and academic experiences. Be precise. You should be able to respond to this query instantly and flawlessly.

Who would respond "no" to this question? However, this is a chance for you to share particular instances of when you performed effectively under pressure. Avoid situations when you could have avoided being under pressure, for as by putting off tasks.

In terms of time management, the interviewer is interested in learning how you prioritize important work, create precise time and action targets, keep to-do lists, etc. Show your detailed, well-organized planner to the person and explain your system if you do!

1. I have a strong interest in the public sector and in education. Among all consulting companies, BCG is the undisputed leader in these industries. I would love to learn from BCG's enormous experience and solid client contacts

2. Because BCG has a worldwide employment model, I get to travel and collaborate with colleagues from all around the world. Working with diverse teams gives me fulfillment, and BCG is the ideal environment for this.

3. BCG has employed many of the mentors I admire and respect. I know that BCG would be the ideal location to work to build my talents and advance my career because they have all strongly recommended working there.

This question is a great opportunity to establish a rapport with the interviewer while also repeatedly highlighting abilities and experiences that will demonstrate your potential as an "amazing" consultant and an engaging team member.

If the subject is work-related, your response to this question may trigger a more in-depth, focused discussion, so be prepared before your interview. If the question pertains to a particular industry that is mentioned on your resume, for instance, be familiar with the market size, growth rate, major competitors, factors that affect revenue and expenses, barriers to entry, key products, target market, market trends, legal and ethical considerations, etc. The interviewer will be astonished.

Supposing that BCG is the firm that you are interviewing for, you could go the following way:

1. I have a strong interest in the public sector and in education. Among all consulting companies, BCG is the undisputed leader in these industries. I would love to learn from BCG's enormous experience and solid client contacts.

2. Because BCG has a worldwide employment model, I get to travel and collaborate with colleagues from all around the world. Working with diverse teams gives me fulfillment, and BCG is the ideal environment for this.

3. BCG has employed many of the mentors I admire and respect. I know that BCG would be the ideal location to work to build my talents and advance my career because they have all strongly recommended working there.

I manage a team of 5 people while working on a project for Flipkart to improve customer service. Data from a recent customer survey was analyzed with the intention of finding methods to enhance customer service.

I assigned tasks based on each person's areas of interest and expertise. After a few weeks, I noticed that three of the team members were working efficiently and productively, however, Rohan was routinely submitting work that was of poor quality and delivered late.

I got down with Rohan to discuss the matter after realizing it might be a motivational issue. My leadership experience has shown me how crucial it is to comprehend your team members. Rahul had a transitional problem rather than a motivational one. If I had not taken the time to learn how John was truly feeling, I would have missed a straightforward fix for this issue.

The questions about leadership and teamwork are just being repeated here. Instead of explicitly responding with what you would do, give an example of a time when you experienced a similar circumstance, explain how you handled it, and explain how it might apply to the current scenario.

For this particular issue, it would be wise to state that the answer truly depends on the circumstances and that, when you balance your options, respect for all parties involved and consideration of the client's requirements and interests should come first.

There is no room for ambiguity in your answer to this question in a Management Consulting interview. You think that having integrity is crucial and that businesspeople should make every effort to stay out of any ambiguous circumstances.

You could also say that any successful businessperson, especially a consultant, should place a high value on keeping client information private and prioritizing the interests of the customer. These qualities are essential to the operations of consulting organizations.

Additionally, you can assert that a lack of ethics results in a less safe and effective business environment and that you support legislative measures to lessen conflicts of interest.

MECE stands for Mutually Exclusive, Collectively Exhaustive. Applied to an issue tree, it means the branches at each level do not overlap and, together, cover the whole problem.

How to build one:

• Start from a precise question, not a topic. "Why has EBITDA fallen 12% year on year?" can be decomposed; "the business is underperforming" cannot.
• Choose a decomposition that is mathematically or logically complete. Profit splits into revenue and cost; revenue splits into price and volume; volume splits by product, channel or geography. Each split is MECE by construction, which is why these are used so heavily.
• Stop when a branch is directly testable with data you can actually obtain.
• Prune early. Size each branch roughly and drop the ones too small to matter. This is where the 80/20 principle does its work.

Note: The strongest version of this answer acknowledges that frameworks are a starting structure, not a checklist. Forcing a problem into a standard framework that does not fit is a common and visible mistake in case interviews.

Use the profitability equation as the spine, and narrow methodically rather than guessing.

Profit = Revenue - Costs. Establish first which side moved, and by how much. This single split determines everything that follows.

• If revenue fell: is it price or volume? Falling volume points at demand, competition or distribution. Falling price points at discounting, mix shift towards cheaper products, or competitive pressure.
• If costs rose: are they fixed or variable? Rising variable cost per unit points at input prices or efficiency. Rising fixed cost points at overhead, capacity added ahead of demand, or a step change such as a new facility.

Then segment. An aggregate decline is usually concentrated: one product line, one region, one customer segment. Finding where it is concentrated is often the entire answer.

Finally, establish whether it is internal or external. If competitors are affected equally, it is a market issue and the response is different from a company-specific problem.

Note: Ask early whether the decline is in absolute profit or margin, and whether it is one year or a trend. Those two clarifying questions frequently reshape the whole case.

Market sizing tests structured estimation, not knowledge. The interviewer is watching your assumptions, not your answer.

Two approaches:

• Top-down — start from a large known figure and narrow with successive filters. Population, then the relevant age band, then the proportion likely to buy, then purchase frequency and price.
• Bottom-up — build from units. Number of outlets, average transactions per outlet per day, average value, multiplied out.

Doing both and comparing is the strongest approach when time allows, because convergence gives confidence and divergence reveals a bad assumption.

What actually earns marks:

• State every assumption out loud and use round numbers that are easy to calculate with.
• Segment where behaviour genuinely differs — urban and rural, or income bands — rather than applying one average to everyone.
• Sanity-check the result. If your figure implies every household buys forty units a year, say so and revisit the assumption.

Note: Never guess silently. An answer that is wrong but transparently reasoned scores far better than a correct number with no visible logic.

The pyramid principle, developed by Barbara Minto, structures communication so the answer comes first and everything below it supports that answer.

The structure:

• The governing thought at the top — the recommendation or key finding, stated in one sentence.
• Supporting arguments beneath it, ideally three, which are MECE and each independently support the conclusion.
• Evidence beneath each argument — the data, analysis and examples.

Why it matters: executives read the top and stop unless they need to challenge something. A detective-story structure that builds to a conclusion frustrates senior audiences and buries the point.

How it changes practice:

• Slide titles state the insight, not the contents. "Two products drive 70% of the margin decline" rather than "Margin by Product". Reading only the titles should convey the whole argument.
• The executive summary is written last but read first, and should stand alone.
• Supporting detail goes to the appendix, available but not obstructing the narrative.

Note: The discipline this imposes is knowing what to leave out. Including everything you analysed dilutes the recommendation and signals that you could not distinguish what mattered.

An analytically correct recommendation the client cannot execute delivers nothing. Feasibility is part of the recommendation, not a separate concern.

What to assess:

• Capability. Does the organisation have the skills, systems and capacity? Recommending a data-driven pricing model to a client with no analytics function means the first recommendation is actually to build that function.
• Culture and appetite. A change that requires behaviour the organisation has resisted for a decade needs a different approach from one that fits how it already works.
• Ownership. Every action needs a named owner with the authority to act. Recommendations addressed to "the business" are not executed.
• Sequencing and dependencies. What must happen first, and where can early visible value be captured to sustain support?

How to build it in: involve the people who will implement it during the analysis rather than presenting to them at the end. A recommendation the operating team helped shape is defended by them; one imposed on them is quietly resisted.

Note: Include quick wins deliberately. Early results buy the political capital needed for the harder structural changes, and their absence is why many technically sound transformations stall.

Verify before you present. This is the decisive step. Check the data definitions, the date ranges, the segmentation, and whether the pattern holds across cuts. An unwelcome finding that turns out to be an error destroys credibility permanently, and every subsequent finding is discounted.

Then present it properly:

• Lead with the evidence, not the conclusion's implications. Walk through how you got there so the client can follow and challenge the logic rather than the messenger.
• Separate observation from interpretation. Be explicit about which parts are established by the data and which are your judgement.
• Frame it forward. "This channel is not returning its cost, and redirecting that spend could fund X" is actionable. "This has been failing for two years" invites defensiveness.
• Give the client the finding privately first where the politics warrant it. Being surprised in front of their own leadership rarely produces a good outcome.

If the client rejects it: propose a limited test rather than escalating the argument. Letting evidence settle it preserves the relationship and usually resolves the disagreement.

Note: What you must not do is soften a genuine finding into ambiguity. Clients pay for an independent view, and delivering only what is comfortable is the fastest way to become worthless to them.

A management consultant helps a client solve a specific, high-stakes business problem within a fixed time and budget. The problem might be ‘Should we enter this market?’, ‘Why are margins falling?’ or ‘How do we release ₹500 crore of working capital?’. The consultant brings structured problem solving, an outside perspective, data analysis and a team that can work full-time on the issue.

A typical engagement follows these stages:

1. Proposal and scoping: the partner discusses the problem with the client, agrees the key question, scope, deliverables, timeline, team and fees, and writes a proposal.
2. Kickoff: the team meets client leaders, confirms objectives, agrees a data request and an interview list, and sets up governance such as weekly check-ins and a steering committee.
3. Diagnostic: the team gathers data, interviews managers and frontline staff, and builds a fact base. An early hypothesis and issue tree decide which analyses matter.
4. Analysis and solution design: workstreams test hypotheses, model options and quantify impact. Interim findings are shared with the client so there are no surprises.
5. Recommendation: the team synthesises a clear answer, a business case and an implementation roadmap, presented to the steering committee or board.
6. Implementation support (optional): many clients now extend the engagement so the team helps deliver the change and track results.

Day to day, a consultant works on Excel models, runs client interviews, joins problem-solving sessions with the manager and turns analysis into slides. Engagements usually last from a few weeks to several months, often with the team based at the client site.

Note: In an interview, showing that you understand this rhythm, and the client-facing nature of the work, signals that you know what you are signing up for.

Consulting is not one job. The type of problem, the length of projects and the skills used vary a lot across segments:

• Strategy consulting: answers top-management questions such as growth strategy, market entry, portfolio choices, M&A and pricing. Projects are short and analytical. The best-known generalist strategy firms are McKinsey, BCG and Bain (often called MBB), with firms such as Kearney, Oliver Wyman, Roland Berger and Strategy& also active.
• Operations consulting: improves how a business runs, covering procurement, manufacturing, supply chain, lean, customer service and cost reduction. Projects are longer, more hands-on and measured in hard savings. Strategy firms, the Big Four and specialists all compete here.
• Technology and digital consulting: covers IT strategy, ERP and cloud implementation, data and analytics, cybersecurity and AI adoption. Accenture, the consulting arms of the Big Four (Deloitte, PwC, EY and KPMG) and Indian IT services firms such as TCS, Infosys and Wipro are major players.
• Financial and risk advisory: transaction services, valuations, forensic work and regulatory compliance, where the Big Four are strongest.
• Implementation and transformation: multi-year programmes where the consultant helps the client execute, sometimes with fees linked to outcomes.

There are also boutiques that specialise in one industry (healthcare, energy) or one function (pricing, HR), and in-house strategy teams at large Indian groups and new-age companies.

When answering, connect this to your own choice. Explain which segment suits your skills and why, for example ‘I enjoy ambiguous, board-level questions, so strategy work fits me better than a long IT rollout’.

Note: Boundaries are blurring. Strategy firms now build digital and implementation arms, and the Big Four do strategy work, so focus on the type of work rather than the logo.

Most consulting firms use a pyramid structure. Titles differ by firm, but the roles are similar:

• Partner or Managing Director: owns the client relationship, sells the work and sets the direction of the answer. Usually spread across several projects.
• Associate Partner or Principal: a senior problem solver who guides content and manages the client’s senior executives.
• Engagement Manager or Project Leader: runs the project day to day, plans workstreams, reviews every deliverable and manages the client team.
• Consultant or Associate (post-MBA level): owns a full workstream end to end.
• Business Analyst or Associate Consultant (graduate entry): owns a module inside a workstream.

For example, McKinsey uses Business Analyst, Associate and Engagement Manager; BCG uses Associate, Consultant and Project Leader; and Bain uses Associate Consultant, Consultant and Case Team Leader.

In the first year, an analyst is expected to:

1. Own the analysis: clean client data, build Excel models and produce numbers the manager can trust without rechecking every cell.
2. Turn analysis into slides: draft pages with clear action titles and correct sources.
3. Gather facts: run desk research, conduct client and expert interviews, and summarise notes quickly.
4. Think, not just execute: come to problem-solving sessions with a point of view on what the data means and what to do next.
5. Manage upward: flag risks early, give realistic timelines and ask for help before a deadline slips.

Analysts are also judged on reliability, speed of learning and how the client team feels about working with them.

Note: In an interview, mentioning that you understand the ‘own your module’ expectation shows maturity about the role.

Both formats test the same skills, structuring, numbers, business judgement and communication, but they give you different amounts of control.

Candidate-led case: the interviewer gives a prompt and then largely follows your lead. You decide which branch of your structure to explore first, ask for the data you need and drive towards a recommendation. BCG and Bain are generally associated with this style, and most Indian B-school placement cases use it too.

• Practise building a tailored structure within one or two minutes, then say which branch you want to start with and why.
• Keep summarising where you are: ‘We have ruled out price, so let us look at volume by channel.’
• Drive to an answer. A common failure is exploring endlessly without concluding.

Interviewer-led case: the interviewer asks a fixed sequence of questions, for example ‘How would you structure this?’, then ‘Here is an exhibit, what do you see?’, then ‘Calculate the market size’, then ‘What else could the client do?’. McKinsey is best known for this format.

• Treat each question as a mini-case with its own answer: structure, solve, then state the so-what.
• Practise brainstorming questions, where you must give a broad, MECE list of ideas rather than two random ones.
• Link each answer back to the client’s overall objective.

In both formats, clarify the objective at the start, do the maths out loud and finish with a clear recommendation plus risks and next steps.

Note: Formats vary by office and interviewer, so prepare for both. The best preparation is 30 or more live cases with partners who give honest feedback.

Knowing a few reliable ‘cuts’ makes it much easier to build a structure that is truly mutually exclusive and collectively exhaustive, rather than a list of ideas that overlap.

• Algebraic or formula split: break the metric into its mathematical parts. Profit = revenue − costs; revenue = customers × orders per customer × average order value. This is the safest cut because the maths guarantees it is MECE.
• Process or value-chain split: follow the steps in order, for example sourcing, manufacturing, distribution, sales and after-sales service. Useful for cost, delay or quality problems.
• Segment split: divide by customer type, geography, product, channel or time period, for example urban vs rural or B2B vs B2C. Segments must not overlap and must add up to the whole.
• Stakeholder split: customers, employees, suppliers, regulators and shareholders. Useful for change, public-sector or reputation questions.
• Opposite pairs: internal vs external, supply vs demand, short term vs long term, financial vs non-financial. Simple, but exhaustive by design.

Example: ‘Why are a bank’s branch visits falling?’ A strong answer might first split demand side (customers need branches less because of UPI and mobile banking) from supply side (branch hours, staffing, closures), and then segment customers by age and location.

Common traps are mixing cuts at the same level (‘North region’ next to ‘premium customers’), adding an ‘other’ bucket that hides the real driver, and going too deep too soon. Choose the cut that separates the likely causes most cleanly and makes the data easy to collect.

Note: Interviewers reward structures that are tailored to the case. Use these cuts as building blocks, not as a memorised template.

A hypothesis is your best guess at the answer, stated early so that it directs the analysis. It stops you from ‘boiling the ocean’ by analysing everything.

How to form one:

1. Use the prompt, your business sense and any early facts. If a cement company’s profit has fallen while revenue is flat, a sensible hypothesis is ‘costs have risen, most likely energy and freight, because these are the largest variable costs in cement’.
2. Make it specific and testable. ‘Something is wrong with costs’ is too vague. ‘Freight cost per tonne has risen more than 15% because of longer lead distances’ can be proven or disproven with data.
3. Link it to your structure. The hypothesis tells you which branch of the issue tree to explore first.

How to test it: say what data would prove or disprove it, and ask for that data first, for example ‘I would like to see cost per tonne by component over the last three years.’

When the data disproves it:

• Accept it quickly and without defensiveness. Say explicitly, ‘That rules out freight, so the cost increase is not logistics-driven.’
• Update the hypothesis using what the data did show. If costs are flat but realised prices fell, move to a pricing and competition hypothesis.
• Return to your structure and pick the next most likely branch.

Interviewers are testing exactly this behaviour. Consultants describe it as ‘strong opinions, weakly held’: commit to a view so the work stays focused, but change it as soon as the facts demand.

Note: Being wrong about an early hypothesis is not a mistake. Holding on to it after the data says otherwise is.

A hypothesis tree starts from a proposed answer and breaks it into the sub-statements that must all be true for that answer to hold. An issue tree asks questions; a hypothesis tree makes claims that can be tested.

Example: a regional dairy asks whether to launch a premium A2 milk brand. The top hypothesis is ‘The client should launch a premium A2 milk brand in Bengaluru and Pune’. For this to be true:

1. The market is attractive: urban premium milk is large enough and growing faster than regular milk.
2. Customers will pay the premium: target households accept a price of roughly 1.5 to 2 times regular milk.
3. The client can deliver: it can source enough A2 milk and has cold-chain distribution in those cities.
4. The economics work: the launch pays back within about three years.

Each branch then lists the analyses needed, for example consumer surveys for the second branch and a supply audit for the third.

Prioritising which branches to test first:

• Deal-breakers first: test the branch that would kill the idea if false. If farmers cannot supply A2 milk at scale, nothing else matters.
• Uncertainty: spend time where you genuinely do not know the answer, not where the result is obvious.
• Impact: favour branches that move the business case most.
• Speed and data availability: a desk check that can settle a branch in a day should come before a four-week survey.

Update the tree as results come in. A proven branch is ticked off; a disproven branch forces you to revise the top hypothesis.

Note: A good hypothesis tree also shapes the final storyline, because each proven branch becomes a supporting argument for the recommendation.

Missing data is normal in consulting and in case interviews. The skill being tested is whether you can still reach a sound answer while being transparent about uncertainty.

1. Ask first, then assume. Check whether the interviewer or client has the figure. If not, say, ‘I will assume X; please stop me if that feels off.’
2. Make assumptions reasonable and explain the logic. ‘An average Indian household has about four members, so 350 million households is a fair starting point for 1.4 billion people.’ Anchoring to a known fact makes an assumption credible.
3. Use proxies and benchmarks. If you lack the client’s churn rate, use a competitor’s published figure or an industry average. If you lack costs for a new plant, scale from a similar plant.
4. Use round numbers. They keep the maths fast and reduce errors. Precision beyond the quality of your inputs adds nothing.
5. Test sensitivity. Identify the one or two assumptions that drive the answer and ask, ‘Does the recommendation change if this is 20% higher or lower?’ If not, the missing data is not critical. If it does, flag it as the first thing to validate.
6. Give ranges where needed. ‘The market is between ₹3,000 and ₹4,000 crore, most likely around ₹3,500 crore.’

On a real project, you would also record each assumption in an assumptions log, show it in the footnotes of the slides and replace it with real data as soon as possible.

Note: Never hide an assumption inside a calculation. A stated assumption shows judgement; an unstated one looks like an error when someone finds it.

A market entry case asks two linked questions: should the client enter, and if so, how? A clear structure covers four areas.

1. Market attractiveness: How large is the café market and how fast is it growing? Which cities and formats (malls, office parks, highways) are most attractive? What margins do existing players earn? What regulations apply, such as foreign investment rules, food safety licensing and property constraints?
2. Competitive landscape: Who are the incumbents (international chains, Indian chains and independent cafés), what are their shares and positioning, and how might they react? Is there a gap, for instance an under-served premium segment in tier-2 cities?
3. Client capabilities and fit: Will the brand resonate with Indian consumers? Can it adapt the menu and pricing? Can it source coffee locally and manage real estate and staff at scale?
4. Entry mode and economics: options include a wholly owned subsidiary, a joint venture with a local partner, franchising or acquiring a local chain. Each trades off control, speed, investment and risk. Then estimate investment per store, revenue per store, time to breakeven and the network size needed to be profitable.

A useful real example is Starbucks, which entered India in 2012 through a 50:50 joint venture with Tata, gaining local real-estate knowledge and sourcing while keeping control of the brand.

Finish with a recommendation such as ‘Enter through a joint venture, starting with 20 to 30 premium stores in the top metros, targeting breakeven in year three’, plus the key risks (high rentals, price sensitivity, incumbent response) and next steps.

Note: Always ask about the client’s objective early. Entering to build scale and entering to test the market lead to very different recommendations.

An acquisition case asks whether the deal creates value for the buyer at the likely price. A strong structure has five parts.

1. Strategic rationale: why does the client want this target? Common reasons are market share, new geographies, new products or capabilities, access to customers, or removing a competitor. Check whether building organically or partnering could achieve the same goal more cheaply.
2. Target’s standalone value: how attractive is the target’s market? What are its growth, margins, customer concentration and management quality? Value it using a DCF and trading or transaction multiples.
3. Synergies: cost synergies such as combined procurement, shared plants and removal of duplicate overheads, and revenue synergies such as cross-selling and wider distribution. Cost synergies are more reliable; revenue synergies are often overestimated. Deduct one-off integration costs.
4. Price and financing: the deal creates value only if the price paid is below standalone value plus the synergies the buyer can realistically capture. Consider cash vs stock funding and the effect on the client’s balance sheet.
5. Risks and integration: cultural fit, retention of key talent, customer loss, regulatory approval (for example from the Competition Commission of India if the thresholds are met) and hidden liabilities found in due diligence.

Worked example: the target is worth ₹800 crore standalone, net synergies are worth ₹200 crore after integration costs, and the seller asks ₹950 crore. The maximum value to the client is ₹1,000 crore, so the deal creates only ₹50 crore, a thin margin for error if synergies slip.

Close with a clear recommendation, a walk-away price and the conditions under which the client should proceed.

Note: Many acquisitions destroy value because buyers overpay for synergies. Showing that you would cap the price at what the client can actually capture is a strong signal.

Pricing cases ask what price the client should charge for a new or existing product. Start by clarifying the objective, because maximising profit, gaining share and building a premium brand lead to different prices. Then use three lenses and compare the results.

• Cost-based (cost-plus): unit cost plus a target margin. It sets the price floor, because below variable cost every sale loses money. It suits commodities, government contracts and custom work, but ignores what customers will pay.
• Competitor-based: price relative to close substitutes, adjusted for differences in features and brand. It suits crowded markets where customers compare prices easily, such as FMCG or telecom plans.
• Value-based: price according to the economic value delivered to the customer. It sets the price ceiling and suits differentiated products, B2B equipment and software.

Worked example of value-based pricing: a new industrial pump costs ₹6 lakh to make. The customer’s current pump costs ₹10 lakh, but the new pump saves ₹3 lakh a year in electricity over a five-year life. The economic value to the customer is roughly ₹10 lakh + ₹15 lakh = ₹25 lakh (before discounting). The price should sit between the ₹6 lakh cost floor and the ₹25 lakh value ceiling, sharing some of the value with the customer, for example ₹14 to 16 lakh, so that switching is clearly worthwhile.

Also consider price elasticity, channel margins, how competitors might react and regulatory limits such as price controls on essential medicines.

Note: A strong answer triangulates all three methods, then recommends a specific price or range with a clear rationale.

Start by diagnosing why growth has stalled before jumping to new ideas. Then lay out growth options in a MECE way and prioritise them.

Step 1: Diagnose. Break revenue into its drivers, for example number of customers × purchase frequency × average ticket size, and look at each by segment, region, channel and product. Compare with market growth. If the market grows at 12% and the client at 2%, it is losing share, which points to a competitive problem. If the whole market is flat, the client needs new markets or products.

Step 2: Lay out growth options using the Ansoff matrix.

• Market penetration (existing products, existing markets): win share through pricing, promotion, distribution reach or better retention. Lowest risk.
• Market development (existing products, new markets): enter new cities, tier-2 and tier-3 towns, export markets or new customer segments.
• Product development (new products, existing markets): extensions, premium variants or services sold to the current customer base.
• Diversification (new products, new markets): highest risk, usually pursued through acquisition.

Also separate organic growth from inorganic growth such as acquisitions, partnerships and joint ventures.

Step 3: Prioritise. Score each option on revenue potential, investment, time to impact, fit with capabilities and risk. For example, a packaged foods company might find that extending direct distribution from 3 lakh to 5 lakh retail outlets adds more revenue, faster, than launching a new category.

End with a recommended portfolio of two or three initiatives, the expected revenue uplift and the sequence in which to pursue them.

Note: Interviewers look for the diagnosis first. Recommending new products when the real problem is losing share in the core business is a classic mistake.

First confirm the facts: by how much has cost per unit risen, over what period and compared with what benchmark? Also ask whether volumes have changed, because falling volume raises unit cost even when total costs are flat.

Break unit cost into components and see which have grown the most:

• Raw materials: price per unit of input (commodity prices, supplier terms, currency) and consumption per unit of output (yield, scrap, rework).
• Direct labour: wage rates, headcount, overtime and productivity (units per labour hour).
• Energy and utilities: tariff per unit and consumption per unit of output.
• Plant overheads: maintenance, depreciation, quality and supervision, spread over the volume produced.
• Logistics: inbound and outbound freight, and warehousing.

Worked example: unit cost rose from ₹100 to ₹112. Materials rose ₹5, labour ₹1, energy ₹2 and overheads ₹4. Overheads jumped because volume fell 20% while fixed overheads stayed the same, so ₹16 per unit became ₹20 per unit. A third of the increase is therefore underutilisation, not inefficiency.

Then identify levers for the biggest components:

• Procurement: renegotiate, consolidate suppliers, use alternative materials, hedge commodities.
• Operations: lean methods, lower scrap, better overall equipment effectiveness, automation.
• Energy: switch to cheaper or renewable power, recover waste heat.
• Footprint: consolidate lines or plants, or fill spare capacity with new volume.

Prioritise levers by savings, investment, speed and risk, and check that cuts do not damage quality, safety or customer service.

Note: Separating price effects from consumption effects, and fixed costs from variable costs, is what makes a cost case answer look rigorous.

This is a competitive response case. Avoid reacting instantly with a price cut; first understand how serious the threat is.

1. Understand the competitor. Which segments and regions is it winning? Is its low price sustainable because of a genuinely lower cost structure (a leaner model, new technology, cheaper sourcing), or is it funded by investors burning cash to buy share?

2. Understand the client’s exposure. Which customers are switching and why? Price-sensitive customers may leave while loyal, service-sensitive customers stay. Quantify the revenue and profit at risk over the next two to three years.

3. Evaluate response options:

• Do nothing: reasonable if the competitor targets a small, low-margin segment.
• Match the price: protects share but can destroy margins across the whole customer base. Test it with a quick calculation: if a 10% price cut applies to all volume, how much share must it save to pay for itself?
• Launch a fighter brand: a cheaper, stripped-down offer that competes at the low end without repricing the core brand.
• Differentiate: strengthen quality, service, loyalty programmes or bundles so the premium feels justified.
• Cut costs: close the cost gap so the client can compete profitably over time.

A well-known Indian example is Jio’s 2016 entry into telecom with very low data prices. Incumbents had to cut tariffs sharply and invest heavily, and the industry consolidated into fewer players.

Recommend a combination, for example a fighter brand for the price-sensitive segment plus a service push for high-value customers, and define the metrics to monitor.

Note: The best answers always ask whether the competitor’s low price is sustainable before recommending how hard to fight.

A product launch case asks whether the client should launch a new product and, if so, how. Structure it around four questions.

1. Is there a real customer need? Who is the target customer, what problem does the product solve and what do they use today? Estimate the addressable market and expected adoption.
2. Can we win against competitors? What alternatives exist, how is the product differentiated and how will competitors respond?
3. Can we deliver it? Does the client have the manufacturing, distribution, brand and after-sales capability, or will it need partners? Does the product cannibalise existing products?
4. Does it make money? Estimate price, volume ramp-up, unit margins, launch investment, payback period and NPV.

Worked example: a consumer electronics firm considers a ₹50 crore investment in a smart air purifier. At a ₹10,000 price and a ₹6,000 unit cost, contribution is ₹4,000 per unit. If it expects 30,000 units a year from year two, annual contribution is ₹12 crore. After ₹2 crore of extra annual marketing and support, cash flow is about ₹10 crore a year, so simple payback is about five years. That may be acceptable in a durable category but weak for a fast-changing technology product.

Go or no-go criteria to state explicitly:

• NPV positive at the company’s hurdle rate, and payback within its target period.
• Share and volume assumptions that are realistic against the market size.
• Acceptable cannibalisation of existing products.
• Manageable risks: regulatory approvals, supply chain and technology.

You may also recommend a pilot launch in one or two cities to test demand before a national rollout.

Note: Always check cannibalisation. A product that mainly steals sales from the client’s own portfolio adds little.

Public sector and social impact cases use the same problem-solving tools, but the objective is a social outcome rather than profit, and the stakeholders are more varied. Start by clarifying the goal and baseline: current full immunisation coverage, the target and deadline, and which vaccines and age groups are lagging.

Structure the problem into supply, demand and tracking.

• Supply side (can services reach the child?): vaccine availability and stock-outs, cold-chain equipment and power backup, the number and training of health workers such as ANMs and ASHAs, session schedules, and reach into remote villages and urban slums.
• Demand side (do families come?): awareness of the schedule, vaccine hesitancy and misinformation, distance and travel cost, lost wages for a day at the clinic, and trust in health workers.
• Tracking and governance: accurate registers of births and due dates, follow-up of drop-outs between doses, and use of data to target low-coverage blocks.

Diagnose with data. Compare coverage by block and by dose. If first-dose coverage is high but third-dose coverage is low, the problem is follow-up, not access.

Recommend targeted interventions, for example SMS reminders to parents, health-worker incentives linked to completed schedules, mobile sessions in hard-to-reach hamlets, working with religious and community leaders to counter hesitancy, and a dashboard for district officials. India’s Mission Indradhanush, launched in 2014, used a similar approach of focusing catch-up drives on high-risk, low-coverage areas.

Prioritise interventions by cost per additional child fully immunised and by ease of implementation, and propose a pilot in the weakest blocks.

Note: In social sector cases, show empathy for beneficiaries and frontline workers. Interviewers look for practical, low-cost ideas, not only technology fixes.

Breakeven volume is the number of units a business must sell for total contribution to cover fixed costs, so that profit is exactly zero.

Formula: breakeven volume = fixed costs ÷ contribution per unit, where contribution per unit = price − variable cost per unit.

Worked example: a client plans a new bakery unit with fixed costs (rent, salaries, depreciation) of ₹60 lakh a year. A box of cookies sells for ₹500 and variable costs (ingredients, packaging, delivery) are ₹300 a box.

• Contribution per box = ₹500 − ₹300 = ₹200.
• Breakeven volume = ₹60,00,000 ÷ ₹200 = 30,000 boxes a year, about 82 a day.
• Breakeven revenue = 30,000 × ₹500 = ₹1.5 crore.
• To earn a target profit of ₹20 lakh: (₹60 lakh + ₹20 lakh) ÷ ₹200 = 40,000 boxes.

How to use it in a case:

1. Test feasibility: compare breakeven volume with market size or capacity. If breakeven needs 30% of the local market, the plan is risky.
2. Assess price changes: a 10% price cut to ₹450 lowers contribution to ₹150 and raises breakeven to 40,000 boxes, so a third more volume is needed just to stand still. This shows why price cuts are dangerous for thin-margin businesses.
3. Compare operating models: an automated line with higher fixed costs but lower variable costs has a higher breakeven but earns more profit beyond it.
4. Estimate payback: if the unit needs ₹1.2 crore of upfront capital and earns ₹30 lakh of annual profit, payback is four years.

Note: In interviews, state the formula before plugging in numbers, and always interpret the result against something, such as market size or capacity.

Use a demand-side estimate: number of children in diapers × usage × price. State each assumption and use round numbers.

Step 1: Children in the diaper-age group. India has about 1.4 billion people and roughly 24 million births a year. Children typically use diapers until about two and a half years, so about 24 million × 2.5 = 60 million children are in the relevant age group.

Step 2: Segment by usage. Adoption differs sharply between urban and rural families.

Total ≈ 44 million diapers a day. Many Indian families use disposables selectively, at night or when travelling, which is why daily usage is lower than in developed markets.

Step 3: Annual volume. 44 million × 365 ≈ 16 billion diapers a year.

Step 4: Value. Assume an average price of ₹12 per diaper across premium and economy packs. 16 billion × ₹12 ≈ ₹19,000 crore a year.

Sanity checks and insights:

• Cross-check against the reported revenues of the leading brands and their estimated market shares.
• The biggest swing factor is rural adoption. Raising it from 15% to 25% adds about 1.4 billion diapers a year, or roughly ₹1,700 crore.
• Growth drivers include rising incomes, urbanisation, e-commerce and smaller, cheaper packs for rural buyers.

Note: Interviewers care more about a clear, segmented logic and sensible sanity checks than about hitting an exact figure.

This is a unit-level guesstimate. Estimate vehicles served per day, litres per vehicle and price per litre, then annualise.

Step 1: Vehicles per day. Assume the pump runs 24 hours with a daytime peak.

• Daytime (16 hours) at about 30 vehicles an hour = 480 vehicles.
• Night (8 hours) at about 10 vehicles an hour = 80 vehicles.
• Total ≈ 560 vehicles a day. Check capacity: with 6 to 8 nozzles and 3 to 4 minutes per fill, the pump could serve far more, so demand rather than capacity is the constraint.

Step 2: Litres per vehicle, by vehicle mix.

The average is about 27 litres per vehicle, so daily volume ≈ 560 × 27 ≈ 15,000 litres.

Step 3: Revenue. Assume a blended price of about ₹95 per litre across petrol and diesel. Daily revenue ≈ 15,000 × ₹95 ≈ ₹14.25 lakh, and annual revenue ≈ ₹14.25 lakh × 365 ≈ ₹52 crore.

Step 4: Profit view (optional). A dealer earns a margin per litre rather than the full price. Assuming about ₹3 per litre, gross margin is ₹45,000 a day, or about ₹1.6 crore a year, before salaries, electricity and other costs. Add income from a convenience store, lubricants and air or car-wash services if present.

Note: Trucks are only 15% of vehicles but more than half of the volume. Pointing out insights like this lifts a guesstimate above plain arithmetic.

A single estimate can be off by a factor of two or more because one assumption is wrong. Triangulation means estimating the same number through an independent route and checking whether the answers land in the same range.

Approaches to combine:

• Demand side: number of users × usage rate × price, for example households × cups of tea a day × cost per cup.
• Supply side: number of providers × output of each, for example tea stalls × cups sold a day × price.
• Company-based: revenue of the market leader ÷ its estimated market share.
• Proxy or ratio-based: spend per head in a comparable market adjusted for income, or the category’s share of total consumer spending.

Worked example: gym memberships in a metro of 20 million people.

1. Demand side: about 4 million people aged 20 to 45 in higher-income households; assume 10% hold a gym membership, giving 4 lakh members at ₹15,000 a year ≈ ₹600 crore.
2. Supply side: assume about 1,500 gyms averaging 300 paying members, giving 4.5 lakh members at ₹15,000 ≈ ₹675 crore.

The two estimates are within about 12% of each other, which supports a figure of roughly ₹600 to 700 crore. If they had differed by a factor of three, you would revisit the weakest assumption, perhaps the membership rate or the number of gyms.

Other quick checks:

• Per-capita check: ₹600 crore across 20 million people is ₹300 per person a year, plausible for a discretionary service used by a minority.
• Compare with known data points such as listed companies’ revenues or industry reports.
• Check the order of magnitude against a related total, such as household spending on health and fitness.

Note: In interviews, even a brief ‘let me sanity-check this another way’ shows the judgement consulting firms value.

Unit economics asks whether each order, customer or store makes money before fixed costs. For delivery platforms the key unit is the order, and the key metric is contribution margin per order.

Worked example: a food delivery order with an average order value (AOV) of ₹400.

A contribution of ₹40 is 10% of AOV. If the platform delivers 20 lakh orders a day, contribution is about ₹8 crore a day, which must cover fixed costs such as technology, brand marketing and corporate staff before the business is profitable.

Levers to improve unit economics:

• Raise AOV through bundles, minimum order values and recommendations.
• Increase the take rate with advertising income from restaurants or brands.
• Cut delivery cost per order through order batching, denser demand and shorter distances.
• Reduce discounts once customers are habituated, and target them better.

For quick commerce, add the dark store. Its rent and staff are largely fixed, so contribution per store depends on orders per day. Below a certain daily volume the store loses money; above it, each extra order is highly profitable.

Note: Always distinguish contribution margin from overall profit. Positive unit economics is necessary but not sufficient for a profitable company.

Customer lifetime value (LTV) is the total contribution a customer generates over their relationship with the business. Customer acquisition cost (CAC) is what it costs to win that customer. Comparing the two shows whether growth is creating or destroying value.

Simple LTV formula: LTV = monthly contribution per customer × average customer lifetime in months, where average lifetime ≈ 1 ÷ monthly churn rate.

Worked example: an edtech subscription app.

• Subscription price ₹300 a month with a 70% gross margin, so contribution = ₹210 a month.
• Monthly churn of 5%, so average lifetime = 1 ÷ 0.05 = 20 months.
• LTV = ₹210 × 20 = ₹4,200 (before discounting).
• ₹14 lakh of monthly marketing spend brings 1,000 new paying users, so CAC = ₹1,400.
• LTV to CAC ratio = ₹4,200 ÷ ₹1,400 = 3 times.
• CAC payback = ₹1,400 ÷ ₹210 ≈ 6.7 months.

How to interpret it: an LTV to CAC ratio of about 3 or more, with payback well within a year, is commonly treated as healthy. A ratio near 1 means the company spends almost as much to acquire customers as it ever earns from them.

Levers you might recommend:

• Reduce churn: cutting it from 5% to 4% raises lifetime to 25 months and LTV to ₹5,250, a 25% increase.
• Raise contribution: annual plans, premium tiers, lower content or server costs.
• Lower CAC: referrals, organic content and sharper targeting of paid channels.

Cautions: look at CAC by channel as well as blended, discount future cash flows when lifetimes are long, and do not assume today’s churn will hold as the business targets less loyal customers.

Note: Churn is often the most powerful lever, because small improvements compound into much longer customer lifetimes.

Case maths is simple arithmetic under pressure. Speed and accuracy come from a few habits and shortcuts.

Handle large numbers cleanly

• Convert Indian units early: 1 lakh = 100,000; 1 crore = 10 million; 100 crore = 1 billion. Many errors come from mixing lakh and million.
• Write large numbers in shorthand: 4.5 million × 3,000 is 4.5 × 3 with nine zeros, which is 13.5 billion.
• Track the leading digits and the zeros separately.

Percentages and growth

• Build any percentage from 10% and 1%: 17% of 640 = 64 + 7 × 6.4 = 64 + 44.8 = 108.8.
• Percentages are reversible: 16% of 25 equals 25% of 16, which is 4.
• Rule of 72: an amount growing at 12% a year doubles in about 72 ÷ 12 = 6 years.
• Small combined changes: a 10% price rise and a 5% volume fall give roughly 5% more revenue (exactly 4.5%).

Multiplication and division shortcuts

• Multiply by 5 by halving and multiplying by 10: 48 × 5 = 24 × 10 = 240.
• Round and adjust: 29 × 42 = 30 × 42 − 42 = 1,260 − 42 = 1,218.
• Divide by simplifying: 7,200 ÷ 240 = 720 ÷ 24 = 30.
• Know common fractions: 1/8 = 12.5%, 1/6 ≈ 16.7%, 1/7 ≈ 14.3%.

Habits that prevent mistakes

1. Say what you are calculating before you do it, so the interviewer can follow and catch errors.
2. Round sensibly when precision is not needed, and say that you are rounding.
3. Label units on every number (₹ crore, units per day).
4. Sense-check every result: does ₹5,000 crore of revenue for a single shop make sense?

Practise daily with drills and with numbers from business news until these steps become automatic.

Note: Interviewers forgive a slow, structured calculation far more readily than a fast answer that is wrong by a factor of ten.

Exhibits test whether you can find the insight quickly and link it to the client’s problem. Use a consistent routine.

1. Take a moment to read before speaking. Ask for 30 to 60 seconds if needed. Rushing leads to misreading.
2. Understand what the chart shows. Read the title, axes, units (₹ crore or ₹ lakh, percentages or absolute values), time period, legend and footnotes. Many candidates miss that one axis is in thousands or that the data is indexed to 100.
3. Describe the key pattern in one sentence. Look for the biggest number, the largest change, outliers, trends and differences between segments.
4. Quantify it. ‘Segment B’s margin fell from 18% to 11%, a 7-point drop, while the other segments were stable.’
5. State the so-what. Link it to the case: ‘This suggests the profit decline is concentrated in Segment B, so I would focus there, particularly on its costs.’
6. Propose next steps. Say what you would like to see next to confirm the hypothesis.

Example: an exhibit shows a retailer’s sales per square foot by store age. Stores under two years old average ₹9,000, mature stores ₹18,000. A weak answer reads out the numbers. A strong answer says, ‘New stores deliver half the productivity of mature ones. Since 40% of our stores opened in the last two years, the recent profit fall may be a temporary ramp-up effect rather than a structural problem. I would check whether the new stores are on the same ramp-up curve as earlier ones.’

If the chart is unclear, ask a precise question rather than guessing, and ignore details that do not matter to the question.

Note: Always end with the so-what. An accurate description without an implication is only half an answer.

Consulting slides are built so that a busy executive can grasp the message in a few seconds. Each slide should communicate one idea.

• Action title: a full sentence stating the insight, not a topic. ‘Rural distribution’ is a label; ‘Rural outlets deliver 40% of volume but only 15% of profit because of high delivery costs’ is an action title. Keep it to one or two lines. Reading only the titles, in order, should tell the whole story.
• Tracker or section marker: a small tag showing where the slide sits in the storyline, such as Diagnostic or Recommendations.
• Body: the chart, table or framework that proves the title. It should show exactly what the title claims and nothing more. Remove gridlines, extra decimals and 3D effects.
• Highlighting: use one accent colour, callout boxes or bold numbers to direct the eye to the evidence.
• Takeaway box (optional): the implication or next step, when it is not already obvious.
• Footnotes and source line: definitions, assumptions and the data source, for example ‘Source: client sales data FY23 to FY25; team analysis’. This lets readers trust and verify the numbers.

Good practices:

1. Write the titles first, as a storyline, before building any charts.
2. Use consistent fonts, colours, units and number formats across the deck.
3. Keep text short and use bullets with parallel structure.
4. Move detail to an appendix instead of cramming the main slide.
5. Test the slide by asking whether someone outside the team would get the point in ten seconds.

Note: Managers review drafts for ‘horizontal logic’ (the titles alone tell the story) and ‘vertical logic’ (each body proves its title), so practise building decks that pass both tests.

Choose the chart based on the message you need to prove, not on what looks impressive. The common types and their uses are:

Useful rules:

• Waterfall charts are a favourite for explaining changes in profit or cost, because each floating bar shows how much a driver added or removed.
• Marimekko charts show two dimensions: column width for segment size and stacked height for share, making it easy to see where the client is strong or weak relative to the size of each segment.
• Avoid pie charts except for very simple two- or three-part splits, because people struggle to compare angles.
• Start bar axes at zero, sort bars in a meaningful order and label values directly instead of relying on a legend.
• Use colour to highlight the one bar or line that matters, and grey for the rest.

Note: If you cannot write an action title for a chart, the chart probably has no clear message and should be reworked or dropped.

The final recommendation is often what the interviewer remembers most. Deliver it answer-first, as a partner would to a CEO who has two minutes.

A reliable structure:

1. Lead with the answer. ‘I recommend the client enters the Indonesian market by acquiring a local player.’ Do not start with a recap of everything you did.
2. Give two or three supporting reasons, with numbers. ‘First, the market is worth ₹12,000 crore and growing at 15% a year. Second, buying a top-three player gives us 40% of the distribution network immediately. Third, at the asking price, payback is about four years including synergies.’
3. Acknowledge the key risks. ‘The main risks are integrating the sales force and currency volatility.’ Add how you would mitigate them.
4. State next steps. ‘I would validate the synergy estimates in due diligence and meet the target’s top 20 distributors.’

Tips for doing this well:

• Take 20 to 30 seconds to organise your thoughts, and tell the interviewer you are doing so.
• Commit to a clear answer even if data is incomplete. ‘It depends’ without a view signals weak judgement; instead say, ‘Based on what we have seen, yes, subject to confirming the synergy numbers.’
• Use the numbers you calculated during the case; they make the recommendation credible.
• Keep it to about one minute. Short, stand-alone sentences work better than a long narrative.
• Tie it back to the client’s original objective, for example ‘This meets the goal of doubling revenue in five years.’

If the interviewer interrupts with ‘The CEO has just walked in, what do we tell her?’, use the same structure with whatever you have so far.

Note: This is the pyramid principle applied under time pressure: the answer, then the supporting arguments, then detail only if asked.

Scope creep happens when the client asks for extra analyses, deliverables or workstreams beyond what was agreed, without changing the timeline, team or fees. Left unmanaged, it overloads the team and puts the core deliverables at risk. The goal is to protect the project without damaging the relationship.

1. Anchor on the agreed scope. The proposal or statement of work defines the key question, deliverables and timeline. Refer back to it politely: ‘Our agreed focus is procurement savings; this request relates to sales force effectiveness.’
2. Understand the request. Ask why it matters to the client. Sometimes existing data answers it in an hour. Sometimes it reveals a higher priority than the original scope.
3. Size the impact. Estimate the effort and what it would displace: ‘This would take one consultant about two weeks and delay the savings business case.’
4. Offer clear options: do a light version within the current scope, swap it for a lower-priority item, extend the timeline or team through a formal change order, or park it for a follow-on phase.
5. Escalate appropriately. As an analyst, never agree to or refuse significant work on your own. Flag it to your engagement manager, who will discuss it with the partner and the client sponsor.
6. Document the decision in meeting notes or a revised work plan so that expectations stay aligned.

Prevention helps: define in-scope and out-of-scope items clearly at kickoff, agree a single client sponsor who prioritises requests, and hold regular check-ins where new ideas are captured and triaged.

Note: Handled well, a scope conversation builds trust and can lead to follow-on work. Handled badly, it leads to burnt-out teams and missed deadlines.

Resistance is common, especially from managers whose teams, budgets or reputations are affected by the recommendations. The aim is to turn a blocker into a co-owner of the answer.

1. Understand the source of resistance. Meet the stakeholder one-on-one and listen. Is the concern job security, loss of control, a past consulting project that failed, disagreement with the data, or simply workload? The right response depends on the cause.
2. Map stakeholders. Assess each person’s influence and level of support. A highly influential sceptic, such as a plant head whose cooperation is needed to implement changes, deserves the most attention.
3. Involve them early. Ask for their input on the problem and hypotheses, use their team’s data and credit their ideas in the deliverables. People support what they help create.
4. Use facts and their language. Present evidence from their own operations and frame benefits around what they care about, for example fewer stock-outs rather than ‘working capital optimisation’.
5. Pre-wire before big meetings. Walk them through findings privately before the steering committee so that they are never surprised or embarrassed in public.
6. Create quick wins. A small, visible improvement in their area builds credibility for the larger change.
7. Escalate carefully. If resistance continues and threatens the project, raise it with your manager and the client sponsor, focusing on the issue rather than the person.

Example: a regional sales head dismisses a pricing project as ‘head office theory’. The team invites him to shape the pilot, runs it in his region with distributors he chooses, and shares weekly results with him first. When margins rise without volume loss, he becomes the project’s strongest advocate with his peers.

Note: Interviewers look for empathy and patience here. Consultants succeed through influence, not authority.

Post-merger integration (PMI) is the work of combining two companies after a deal is signed so that the promised value, especially synergies, is actually delivered. Consultants typically help the acquirer plan and run the integration.

Typical consultant activities:

• Set up an Integration Management Office (IMO): a central team that coordinates all integration workstreams, tracks milestones and escalates issues to leadership.
• Day 1 readiness: ensure that on the closing date employees are paid, customers are served, systems work and communications go out, so the business does not stumble.
• Synergy planning and tracking: turn the deal model’s synergy estimates into specific initiatives with owners, targets and timelines, such as supplier consolidation or closing duplicate offices, and track realised savings.
• Organisation design: define the new structure and leadership, and fill key roles quickly to reduce uncertainty.
• Culture and change management: diagnose cultural differences, such as decision-making speed or hierarchy, and plan how to bridge them.
• Clean team work: before closing, an independent clean team can analyse competitively sensitive data, such as customer prices, without breaching competition law.

What makes integrations succeed: a clear deal thesis that guides priorities, fast decisions on leadership and structure, early focus on retaining key customers and talent, and rigorous, owner-level tracking of synergies.

Why they fail: overestimated synergies, especially revenue synergies; distraction from the core business; culture clashes that drive out key people; slow decisions that leave employees uncertain for months; and incompatible IT systems that delay benefits.

Note: In interviews, linking PMI back to the M&A case, where synergies justify the price, shows you understand that deals are won or lost after closing.