The Kaizen Core: why implementation starts at the site, not in the software

ERP is usually bought at the moment the owner stops trusting the numbers being brought to them. The system is installed, the master data is migrated, and a year later it turns out that data is entered after the fact while decisions are still made from an old notebook. The reason is almost always the same: a process that already worked badly has been automated.

Gemba first

Gemba is the place where value is created: the pit, the repair bay, the spare parts store, the fuel point. A project starts there, not in a meeting room with a questionnaire. Together with the line staff we walk the chain from request to result and look for the breaks: who issues a part, who signs a work order, where running hours are recorded, where fuel consumption figures come from.

Root causes, not symptoms

The losses we find are broken down with Ishikawa diagrams and the five whys. Some root causes are closed without any software at all: a rule, a changed document route, a control point moved to where it belongs. That is cheaper than automation and pays off immediately. The rest becomes the requirements for the system, and by then it is clear why every screen exists.

Module by module

We do not switch on twelve modules at once. We take the area where losses are most visible, usually equipment maintenance and fuel accounting, and bring it to a working state. The first result is shown in the first months of the project, not at the end of the year. Accounting can stay in 1C: Tunuk connects through an API and takes over the operational side.

People matter more than the interface

Resistance is not removed by an order, but by answering why this matters to the person entering the data. A mechanic has to get something back from the system, not only feed reports upwards: repair history for a unit, standards, a maintenance plan, a clear request for a spare part. That is why training and support are part of the implementation for us, not a separate service.

These four steps make up the method we call the Kaizen Core: Gemba, root causes, module by module implementation, adaptation and support.