Are Consultants "Liars"? A Field Engineer's Prejudice
When you have been in the IT industry long enough, you inevitably end up with a job type you just can’t get along with.
Between engineers, even when opinions clash, things eventually get settled by talking about code and design. But for as long as I can remember, there has been one group I could never quite get on the same page with.
Consultants.
Of course, not all of them. But when I was younger, I rather crudely thought, “Consultants just sell fairy tales for a living.”
Meeting the Poisoned Sweet
Years ago, I joined a project to launch a web service.
The plan a consultant brought in was truly attractive. Build this feature, and you will crush the competition, grow your users, and increase sales. Looking at the slides alone, anyone would want to say yes.
But once we got into the design, things started to look doubtful.
There was no way to build it. Or if there was, it would take years of development. Or the technical risk was so high that the service itself would not work.
The engineers naturally investigated and explained: “This is difficult.” “This is dangerous.” “This is impossible.”
At that moment, the room went cold. The people who had been dreaming a minute earlier were suddenly dragged back to reality.
And somehow, the engineers who cooled the room became the bad guys.
It looked delicious, but it made you sick once you ate it. In Japan, we call this a “poisoned manju,” a sweet bun with poison inside. The phrase fits perfectly.
Back then, every time, I muttered to myself, “Then don’t bring us something like that in the first place.”
Those Who Sell the Future and Those Who Carry the Present
As I got older, my thinking changed a little.
Consultants are not trying to lie. At least, not usually.
What they sell is not technology but “the future.” What clients want is not technology either, but sales, new businesses, and market share.
Engineers, on the other hand, talk about the present. The server can handle this much. Development will take this long. This design will fall apart.
They are looking in different directions to begin with, so of course they clash.
The real problem is who ends up getting the bill for that future.
When the schedule collapses, when contradictions in the specifications burst out, when the client starts demanding answers, the people in the room are usually the engineers.
By then, the people who described the dream are already describing a new dream to their next client.
A consultant’s greatest talent is not talking about the future. It is being gone from the project before that future arrives.
AI Is Very Similar
Lately, when I look at proposals from AI, I get a sense of déjà vu.
AI produces one brilliant idea after another and draws an inspiring architecture diagram in an instant. But when you try to implement it, small problems come crawling out everywhere.
In the end, it is the people on the ground who get stuck cleaning up the mess.
Something that talks about possibilities and turns them into flashy materials. In that sense, AI and consultants are very similar.
But there are differences.
AI costs a few thousand yen a month, about the price of a couple of lunches, and apologizes politely when you point out a mistake. Consultants cost several million yen a month, tens of thousands of dollars, and when you point out a mistake, they send you a quote for the next phase.
Lately, I hear those same consulting firms are eagerly selling “AI adoption support.”
In other words, they are personally escorting into their clients’ offices the very thing most likely to take over the job of telling fairy tales.
Since they are going around selling their own successors, consultants do occasionally describe the future correctly.