“Software is bought with money; acceptance is earned with trust.”
In transformation projects, whether AI, information security or MES, success depends on people who do not report to the project: head of IT, plant management, head of quality, the team at the plant. They have their own daily business and their own priorities, and they decide whether something arrives in daily work or ends up in a binder.
This applies especially to interim mandates and to anyone coming from outside or from another department. Argue with the organisation chart here and you lose the room before the work begins.
What does not work
- Threatening with hierarchy. “Management wants this.” That may secure a commitment, but not cooperation.
- Know-it-all. Anyone who explains from outside what is going wrong on site has listened without understanding.
- A project that only brings effort. If every party has to give something and gets nothing back, commitment stays minimal.
What works: three building blocks
1. Diagnosis instead of know-it-all. The start is questions, not answers. What works well today? Which solution has proven itself, even if it is not official? What costs daily work the most time? The answers show where trust can grow, and they often show that parts of the solution already exist on site.
2. Create benefit at the base. Every party involved has to feel something in the first weeks that makes their work easier. A report that no longer has to be made by hand. A follow-up question that disappears. A sequence that goes faster on the line. Small, visible improvements are the capital with which later demands can be paid for.
3. Name the shared opponent. What is shared is not the project but the problem. Production standstill, incalculable liability, the audit coming in three months. When everyone involved sees the same risk, squabbling over responsibilities becomes a shared task.
Reliability
Trust is a consequence of kept promises. Whoever says they will get back by tomorrow gets back by tomorrow. Whoever says “I do not know” looks it up and comes back. In an environment where many claim to know everything, that sets you apart.
This includes saying what is not necessary. Anyone who credibly explains that something can be dropped is taken seriously on what remains.
Two worlds
A transformation moves between two languages. One thinks in shifts, plant states and hand movements. The other in liability, evidence and risk. Most projects fail at the translation between them. Anyone who can speak both languages prevents misunderstandings before they become conflicts.
What follows
- Listen first, before presenting a concept.
- Deliver something early that visibly helps at the base.
- Name the shared risk, not the project.
- Keep promises, including the small ones.
- Say what is not necessary.
Technology can be bought. Trust cannot.