Skills nobody teaches — an angry client, a stalled meeting

A consultant who gets replaced is rarely replaced for not knowing a configuration screen.

They get replaced for promising something they could not deliver, for not writing down what was agreed, or for meeting anger by defending themselves rather than resolving it.

None of these appear in any certification. All of them decide your trajectory from about the second year onward.

Why the client is angry — and what it usually is

Anger on an implementation is almost always misdiagnosed. It presents as an objection to the system, and it usually originates somewhere else entirely.

What is said	What it usually means
“The system is difficult”	I was not trained on my job
“The system can’t do this”	Somebody promised me it could
“We never agreed to that”	What was agreed was never written down
“The project is late”	Nobody is telling me where we are
“I’m not going to use it”	I am afraid it will expose my work or remove my role

The last row is the most consequential and the least often named. Resistance to a system is frequently a legitimate fear of transparency rather than a technical opinion — and anyone who responds to it by explaining features has responded to nothing.

Rule one: separate the complaint from the complainer

The instinctive error is to answer immediately that the system does do that, or that this was never in scope. Both are usually true. Both escalate.

The sequence that works, in this order and no other:

1. Restate the complaint in your own words until they confirm it. Someone who hears their complaint accurately played back is halfway calm already, because what angers people most is the sense that nobody understands.

2. Separate the facts from the interpretation. “The invoice came out with the wrong amount” is a fact. “The system doesn’t calculate tax” is an interpretation. Most interpretations are wrong even when the fact is right.

3. Say what you will do and when, not what you cannot do. Even a negative answer is delivered as an action: “I’ll examine it today and come back to you before four.”

4. Write it down. What is not written did not happen, and will later exist in two versions.

How to say no without losing the client

Most new consultants cannot say no, so they say “that should be possible” and pay for it three months later.

The phrasing that works replaces the refusal with a price: “That is possible. It is a customisation of this many hours, and it moves delivery by this much. Do you want it now or after go-live?”

You have not refused. You have moved the decision to the person who owns it, with its cost attached. Most requests die at that single sentence — not because the client did not want them, but because they did not know they had a price.

The minutes — the cheapest protection on the project

Four lines after every meeting are enough: what was agreed, what is still open, who does what, and by which date.

Send it the same day, phrased as “this is my understanding, correct me if I have it wrong.” The wording is deliberate: anyone who does not object within three days has agreed.

Do this after every meeting and nobody argues with you six months later about what was said. Skip it and you will be argued with and you will lose, because a client’s memory of the promise is always clearer than their memory of its condition.

When to escalate — and everybody gets this wrong

New consultants escalate late, believing escalation is an admission of failure.

Three signs that the moment has arrived:

• A decision is needed from somebody who does not attend your meetings.
• The same request returns after being refused twice — that is a scope dispute, not a technical question.
• A task owned by the client has slipped far enough to threaten the go-live date.

Professional escalation is written as a decision required, never as a complaint: “The following decision is needed before this date, and the effect of delay is this.”

The skill that saves years

Ask about the work before you talk about the system.

Anyone who opens a screen in the first meeting is selling a product. Anyone who asks “show me how you do this today” gains two things at once: the actual requirement, and the trust of the person sitting opposite.

The difference between the two shows up around month six — when one of them is requested by name for the next project and the other is replaced.

What to do today

• Write four lines of minutes after your next meeting and send them the same day.
• Try the price phrasing once, instead of “that should be possible”.
• At the next objection you meet, restate it before you answer it.
• Review your open requests and escalate anything matching one of the three signs.

Where to go from here

Most of the causes of anger listed above are the same causes projects fail, set out in why ERP projects fail, and at their most compressed in go-live night.

Which of the four skills matters most depends on the role you hold — the six are in ERP implementation roles. And the whole basis of the trust is understanding the client’s business before their system, which is built from the learn ERP page.