How to Answer "Describe Delivering Difficult Recommendations to a Client"

Delivering uncomfortable truths is the mark of a trusted advisor. This question tests whether you have the courage to share findings clients don't want to hear and the diplomatic skill to do so without destroying the relationship. Consulting firms need people who tell clients what they need to know, not what they want to hear.

The best answers show a thoughtful approach to both the content and the delivery—preparing the ground, leading with data, and providing an actionable path forward.

What Interviewers Are Really Assessing

• Courage: Will you deliver hard truths or hedge to avoid discomfort?
• Empathy: Do you understand why the recommendation is difficult for the client?
• Communication skill: Can you deliver bad news in a way that preserves trust?
• Preparation: Do you set the stage properly rather than blindsiding stakeholders?
• Solutions orientation: Do you pair difficult findings with constructive next steps?

How to Structure Your Answer

Cover: (1) what the recommendation was and why it was difficult, (2) how you prepared for the delivery, (3) the actual conversation and how you handled reactions, and (4) the outcome for the client relationship and the business.

Sample Answers by Career Level

Entry-Level Example

Situation: Recommending a process change that would make a client team's favorite tool obsolete. Answer: "Our analysis showed that a client's custom-built reporting tool—which their analytics team had spent two years developing—was producing inaccurate data. Switching to a commercial solution would save $200K annually and improve accuracy. The analytics team lead had built her reputation on this tool. Before the formal presentation, I met with her privately, shared our data quality findings, and asked for her input. She confirmed some issues she'd been aware of but hadn't had time to fix. I positioned the recommendation as an opportunity for her team to focus on higher-value analysis rather than tool maintenance. In the formal readout, I acknowledged the team's effort on the existing tool and framed the transition as an upgrade, not a failure. The analytics lead became an advocate for the change because she'd been included in the process rather than surprised. The client adopted our recommendation and realized the projected savings within six months."

Mid-Career Example

Situation: Recommending workforce reduction as part of a post-merger integration. Answer: "During a post-merger integration, our analysis identified $8M in redundant costs, with $5M coming from overlapping roles. Recommending headcount reduction is always the most difficult conversation. I prepared extensively: I built a detailed capability mapping showing which roles were truly redundant versus which were complementary, I modeled the cost of severance and productivity loss during transition, and I developed a redeployment plan for 40% of affected roles into open positions. I presented the recommendation to the CEO and CHRO together, leading with the redeployment plan before the reduction numbers. I was transparent about the human impact and the risks of executing poorly—including retention risk among employees who weren't affected but might leave due to uncertainty. The CEO appreciated that I hadn't sugar-coated the numbers but had also shown genuine concern for the people involved. They adopted our recommendation with modifications, achieving $7.2M in savings while redeploying 35 of 52 affected employees. The CHRO later told me it was the most humane restructuring recommendation she'd received from a consulting firm."

Senior-Level Example

Situation: Telling a PE firm their acquisition target had fundamental problems. Answer: "A private equity client was deep into due diligence on a $150M acquisition. Our commercial diligence revealed that 45% of the target's revenue came from three contracts with related-party entities, and the organic growth story was significantly weaker than represented. The PE partner had already told his investment committee this was a strong deal. I requested a private meeting with the lead partner before circulating the report. I presented our findings methodically—starting with the data, then the implications, then the risk scenarios. I didn't tell him what to do; I laid out three options with risk-adjusted returns for each: walk away, renegotiate at a lower valuation reflecting the revenue risk, or proceed with enhanced protections. The partner was initially frustrated but acknowledged the analysis was sound. They renegotiated the price down 25% with an earn-out tied to organic revenue growth, which protected them when two of the related-party contracts were indeed not renewed post-acquisition. The partner told me that deal would have been their worst investment without our finding. That engagement led to a long-term advisory relationship worth $3M in annual fees."

Common Mistakes to Avoid

• Blindsiding stakeholders: Delivering a difficult recommendation in a group setting without previewing it privately with key decision-makers is a relationship risk.
• Leading with the recommendation before the evidence: Build the logical case first so the conclusion feels inevitable rather than imposed.
• All diagnosis, no prescription: Telling a client they have a problem without offering a path forward is incomplete consulting. Always include actionable next steps.

Practice This Question

Ready to practice your answer with real-time AI feedback? Try Revarta's interview practice to get personalized coaching on your delivery, structure, and content.