The first 90 days after the audit decide everything

An audit creates attention. Shift leaders, clerks and supervisors have answered questions, shown procedures, named problems. They have given something of themselves. Now they are watching: does anything happen with it? Or was it another exercise for the report?

This attention does not last long. If weeks pass after the audit without anything tangible changing, it tips into indifference. And indifference is more expensive for any lean and change initiative than open resistance. Resistance you can work with. Indifference you first have to break open again.

So the first 90 days are not about working through as many findings as possible. They are about proving that findings have consequences in this company. You achieve that with a few well-chosen steps, not with a long list.

The most common mistake after an audit is to translate the report directly into an action plan. Twenty findings become twenty actions, each gets an owner and a date. On paper that looks decisive. In practice it spreads the energy so thinly that nothing visible emerges anywhere.

I do it differently. In the first week I sit down with the managing director and plant management and ask three questions:

• Which two or three findings actually move lead time, delivery performance or quality?
• Where among those can people in the plant or in the office see a change within a few weeks?
• What do we deliberately drop, even though it is in the report?

The third question is the most important. What you do not touch, you also have to name. Otherwise the people involved are left with the feeling that everything is open and nothing has been decided. A clear "We are not doing this now, and here is why" is often worth more than another action.

A quick win is not the easiest action in the report. It is the action that meets three conditions: those affected see the change without explanation. It can be implemented without major investment and without an IT project. And it sits in a place the plant is already talking about anyway.

An example: in a plant with several assembly lines, the audit had shown that orders sat in production planning for a long time because drawing releases ran via email and nobody knew the status. The quick win was not a new system, but a board in production planning with three columns and a daily alignment of a few minutes. After a short time, assembly and sales knew which orders were stuck and why. That did not solve the problem, but it made it visible, and assembly management experienced for the first time that the office was reaching out to them.

Important: the quick win has to sit where the pain is loudest. If the whole hall is complaining about missing parts and you start with a 5S campaign in the warehouse, people do not see the connection. The first visible success has to fit the story the plant tells itself.

After the decision comes the moment when many leadership teams schedule an information event. Slides, action plan, timeline. That is better than nothing, but it is not enough. Anyone who is merely informed remains a spectator.

I involve the people who are supposed to implement the quick win in shaping it. Not in the question of whether it will be implemented, that has been decided. But in the question of how. Which columns does the board need? When is the alignment? Who facilitates when the supervisor is on holiday? These details decide whether a standard is lived or whether it gathers dust in three weeks.

That applies on the shop floor just as much as in the office. Clerks in order processing often have very precise ideas about where their time is lost. Anyone who asks them gets not only better solutions but also people who stand behind the solution because it is their own.

A project plan with milestones looks professional, but it does not keep the implementation alive. What keeps it alive is a rhythm: a short, fixed alignment that does not get dropped even when things get hectic.

In the first 90 days I recommend two levels. A weekly round of the implementers, short, at the place where things happen, with the single question: what is hindering us this week? And every few weeks a round with the managing director and plant management in which reports are not read out but obstacles are decided on. A supplier who is not cooperating. A release that is stuck at group headquarters. An interface that refuses.

Leadership has a single task in this phase: clearing obstacles. Not checking progress, not evaluating slides. When plant management visibly clears stones out of the way, the plant understands that it is serious. That is the real lever of the first 90 days.

A quick win that nobody notices is not one. That is why the first 90 days include a moment in which the plant sees what is different. No party, no brochure. A walk by the management team to the board. A short report in the shopfloor meeting by the people who did it. A before-and-after photo on the notice board.

This is not about self-congratulation. It is about setting the pattern: here, something is recognised, decided, implemented, shown. Anyone who has experienced this pattern once is more likely to trust the next initiative.

And honesty is part of it. If something did not work, say so. I have seen an openly named failed attempt bring more trust than a polished success. The team notices the difference immediately.

After 90 days you ideally have a visible success, a rhythm that carries, and a leadership team that has learnt to clear obstacles. Only now is the time to bring out the rest of the findings again and choose the next two or three topics.

This sequence is not a detour. It is the reason why the second and third wave are easier than the first. The plant has learnt a procedure, not just implemented an action. That is exactly what distinguishes an audit that moves something from an audit that ends up in the folder.