The hardest moment in a consulting mission isn't technical. It's not the workflow that won't run or the integration that won't connect. It's when you know exactly what needs to be done, you've explained, documented and argued for it, and the decision made by the other side is the opposite of your recommendation.
Over 10 years of CRM missions, Adobe Campaign, Salesforce, Imagino, I've experienced this situation dozens of times. I've learned to distinguish two very different cases that look the same on the surface but call for radically different responses.
They've heard your recommendation. They understand the stakes. They make a different decision for legitimate reasons, budget constraints, imposed deadlines, political priorities. That's their absolute right.
They haven't grasped the technical stakes. They make a decision by default, by habit, or because they trust someone else who doesn't understand either. It's not bad faith, it's a communication problem.
The distinction is fundamental because the posture to adopt is radically different in each case.
Your role ends at advice. Once you've presented your recommendation with its justifications, risks and alternatives, you've done your job. If the client decides otherwise with full knowledge, you deliver.
But, and this is non-negotiable, you document your recommendation in writing. A summary email, a note in the meeting minutes, a comment in the project documentation. Not to cover yourself legally: so everyone is aligned on what was decided and why.
The phrase to always write: "Following our discussion on [date], I recommended [recommendation] for the following reasons: [reasons]. It was decided to go with [alternative]. I remain available should you wish to revisit this choice." Sober, factual, non-judgmental.
What you don't do: say "I told you so" when problems arise. That's not your role, and it serves no purpose. Your role at that point is to help fix things, not to justify yourself.
This is the hardest case to manage, and the one where most consultants give up too quickly. You rephrase once, face a refusal, and give up. That's a mistake.
If your contact doesn't understand your recommendation, that's your problem, not theirs. Your mission is to find the angle that will get the message across. Not to repeat the same explanation louder.
Translate to business impact. "This workflow will saturate your database in 6 months" means nothing to a busy CTO. "Your campaigns will start missing sends in 6 months, costing X days of emergency work to fix", that lands.
Offer a concrete demonstration. On a test instance, in 30 minutes, you show what happens if the problem isn't fixed. What you see sticks infinitely better than what you hear.
Change contact.. Sometimes the issue isn't technical understanding, it's that you don't have access to the right decision-maker. Asking to present your recommendation to an additional level isn't impolite. It's your professional responsibility.
What you don't do: adapt to your contact to the point of distorting your recommendation. Simplify the message, yes. Water down the risks to avoid scaring them, no. A consultant who tells their client what they want to hear is no longer a consultant, they're a compliant supplier.
What's exhausting in these situations isn't the intellectual effort. It's the emotional management. When you see a Campaign instance in production with technical workflows sending deliveries without applying typologies, when you see a Salesforce architecture stacked over 5 years without documentation, when you see decisions made by people who've never opened the interface they oversee, the frustration is legitimate.
But visible frustration serves no one. It closes doors, puts your contact on the defensive, and undermines your ability to change things.
The posture to maintain is that of a doctor delivering a difficult diagnosis to a patient who refuses to believe it. They don't raise their voice. They don't give up. They rephrase, bring evidence, allow time. And when the patient decides not to follow the prescription, they document it and remain available for what comes next.
Is this client in a better position than at the start of my mission, regardless of the decisions they made along the way?
If the answer is yes, even partially, even imperfectly, the mission had value. That's the criterion.
Not whether everything was done as I would have wanted. Not whether all my recommendations were followed. Did the situation improve? If so, I did my job.
Scoping is free and commitment-free. 30 minutes to define scope and validate feasibility.
Contact →