Consultant’s Survival Manual: Soft Skills for Hard Days

(Spin-off of the series “The Human Code of ERP”)

The Go/No-Go decision is ten days away, and the boardroom feels like an arena. The air is thick with blame, and you are sitting right in the middle, taking the hits.

If you have spent any time implementing enterprise software, you have lived this exact scene.

Slightly to your left, on the high-definition display, sits a brilliant, three-year strategic digital transformation roadmap. It’s a masterpiece of colorful diagrams, filled with promises of seamless flows and real-time operational synergy. It cost the company millions of dollars in strategic advisory fees.

Then, the Chief Operating Officer turns away from the slides, looks you straight in the eyes, and asks: So, operatively, how do we make sure we do not block shipments on Monday morning?

You stare at the slide, then at the client. Inside your head, a silent, frustrated scream echoes: And you are asking me? What exactly have those overpaid strategic advisors been doing with their slides for the last three years?

Welcome to the reality of the ERP ground troops.

PowerPoint vs. Shop Floor

There is a classic, comfortable myth that has circulated in our industry for a long time. It says that an ERP consultant is merely a software instructor. You show up, open the session menus, explain what the flags do, leave.

If the business processes do not fit the system, or if the users refuse to use it, that is a change management issue for the client to solve.

It’s indeed a beautiful theory. The problem is that is also a dead one.

Modern enterprise software standardizes processes by force. When you implement an ERP platform of almost any tier, you are rewriting how people live their workdays.

Today, the role of the ERP consultant has fused with change management, whether we like it or not. The strategic consultants leave as soon as the slides are approved. When the Go/No-Go meeting arrives, you are the only one left standing between the boardroom expectations and the physical reality of the loading bay.

You cannot afford to be just a manual reader, at least not in 2026 when even the cheaper LLM can summarize you the content of a longer text and explain it. You must understand the physical operational flows and help the organization adapt to the limits and standard processes of the ERP.

I can tell it’s an exhausting act of constant mediation. You are balancing the dreams of directors who want absolute control with the anxiety of operators who just want to finish their shifts.

Believe it or not, navigating this emotional crossfire requires a manual that was never written in the software documentation.

Pillar 1: Surviving the PowerPoint Legacy

When you step into a project, you are rarely starting from a clean slate. You inherit a history of strategic decisions made far above your pay grade. The client has spent years looking at high-level diagrams that promise to streamline their operations.

The trouble is that PowerPoint slides don’t have to deal with physics. They don’t account for the physical layout of the production line or the drop in Wi-Fi signal at the far corner of the warehouse floor.

When those high-level advisory teams pack up and leave, a vacuum is created. The client suddenly realizes that the beautiful strategy doesn’t tell them how to handle a partial shipment of raw materials on a rainy Tuesday afternoon.

Survival begins with accepting that you will have to be the translator. You must take those abstract business desires and reconstruct them into concrete, practical steps that fit the rigid standard logic of the ERP. That is not an IT job, working within data all the time. You are rebuilding a bridge that was sold as complete but was never actually designed for the terrestrials.

Pillar 2: Operational Empathy (Drop the Manual, Understand the Flow)

The easiest trap for an ERP consultant is to hide behind the system’s standard rules. When a user asks why a process has to change, it is tempting to cross your arms and say something like: Because the Cloud standard requires it.

This is the fastest way to build a wall of silent boycotts.

Users do not care about standard system logic. Just like you, they care about their daily survival.

If the new process makes their shift twice as hard, they will find a workaround, even if it means feeding the system with fake data to bypass a lock.

To survive, you must cultivate operational empathy. Step away from the computer, take a long walk on the shop floor. Stand next to the assembly line operator, the one who probably has to click through five different screens while wearing heavy gloves.

When you understand the physical pain of their daily routine, your configuration choices will change. You stop lecturing them on features and start helping them adapt their flows to the standard constraints of the ERP. They will gradually stop seeing you as an invader who came to slow them down, and start seeing you as a partner who came to protect their time.

Pillar 3: Fire Control at the Go/No-Go

As the Go/No-Go decision point approaches, the client’s anxiety spikes, as it always happens during those funny days. The realization that they are about to turn off the old, friendly familiar software triggers a wave of panic.

Because they don’t know how to handle this fear, they project it outward, looking for immediate answers to problems they ignored for months.

They will pull consultants into meetings that last for hours, demanding to know how the ERP will solve every minor operational gap.

Your job in these high-pressure moments is fire control. You must act as an emotional circuit breaker.

When a client dumps a mountain of chaotic panic on you, you cannot afford to react emotionally. You must listen, absorb the shock, and translate their anxiety into a clean, binary list of technical tasks. You filter out the screaming and keep the logic intact.

Most importantly, you must act as a shield for your development team. When the boardroom is in a frenzy (and they will be), the temptation is to pass that panic down to the developers, demanding rapid customizations to appease a nervous director. Don’t even start to think about it. As I wrote in chapter 2 of the Human Code main series, protect your team from the noise so they can focus on delivering clean, stable solutions. You take the heat at the steering committee, and let your developers write the code in peace.

The Invisible Metric of Success

At the end of the day, enterprise software is just a repository of database tables. It doesn’t have feelings, it doesn’t get stressed, and it doesn’t care if the company makes a profit.

The people, however, care deeply.

If you treat an ERP implementation as a purely technical exercise, you are probably setting yourself up for a bumpy ride that is going to end with a failure. Remember that anyone can memorize session configurations or write SQL queries. In the era of Generative AI, those technical skills are rapidly becoming commoditized.

The true value of a consultant lies in their ability to stand in the eye of the chaos. It’s the capacity to translate abstract executive desires into practical operational realities, to calm a panicked warehouse manager, and to protect a development team from administrative noise.

The success of your project is not and it will never be measured by the number of custom extensions you built. It is measured by the number of human beings you successfully guided across the valley of change.

Because in the end, the code is binary, but the implementation is entirely human.

Written by Andrea Guaccio 

June 4, 2026