When improvement fades

Do not settle for having solved the problem today.

Ask yourself whether tomorrow it can be solved without you there.

That is the sentence I would say to myself on my first day as a Team Leader. And it is the question this series ends with.

What I have and what I do not

In last mile I worked with standards for loading, scanning, organising the ramp and safety. I ran into problems with procedures not being followed, and with drivers who were not yet fully used to the standards. In the hotel I organised the SOPs for Front Office and Night Audit.

But I do not have a documented case where an improvement I put in place worked for a few months and was then abandoned. I do not have a case that proves why a particular standard faded. I do not have a case where a colleague leaving caused a standard to be lost. And I have never measured whether results continued after I changed roles.

For an essay called “When improvement fades”, that is not a detail. It is exactly the subject.

The question I cannot answer

In 2025 I worked as a Team Leader and then as an Area Manager in last mile. Later I moved to remote coordination.

What was left of my way of working after I left that role? Which checks carried on? Which were forgotten in the first week?

I do not know.

And that is what I would most like to understand better today: whether a manager's results carry on when they are no longer there to check them. Because if I do not know that, I do not know whether what I did was an improvement of the process, or only my presence.

Why an improvement fades

As an opinion, not a proven case: I believe an improvement is at risk when it depends only on the person who started it, instead of becoming part of the everyday way of working.

Turnover makes this more visible. In last mile we had drivers called in at short notice, and drivers in ramp-up who were not yet used to the SOPs. That made it hard to keep the same level of compliance.

A standard should not only work with the people who have known it for years. If every new employee has to learn the process just by watching a colleague, the result depends on who trains them. I wrote about this in “Watch how I do it” is not training. Here you see its price: a standard that only passes from person to person loses a little with every change.

What keeps a standard alive

For me, no single element is enough. I would pick out five:

• Documentation: the standard has to be clear and easy to find.
• Training: people need to know not only what to do, but why.
• Responsibility: it has to be clear who follows up on whether it is applied.
• Checking: someone has to verify whether the standard is still working.
• Updating: when the process changes, the instruction has to change too.

I connect this with organising the SOPs for Front Office and Night Audit, which I wrote about in How I built Front Desk Control. A good document is useful. But on its own it does not guarantee that the process is followed correctly.

A standard that exists only in a document is not necessarily a standard that is applied.

Ten essays, one question

When I look at the nine earlier essays together, they seem to show the same problem from different angles.

Damage and incomplete orders show that we have to understand where a mistake starts. Gemba reminds us that the report does not always explain the process. 6S shows why visible order matters. The control chart and DMAIC teach us not to rush from a bad result to an untested solution. Remote coordination shows how much reliable information matters. High-volume days show whether the standards are strong enough to withstand pressure. And the work in the hotel has shown me the importance of responsibility and continuity between shifts.

The question that links them all is this:

Have we built an improvement that becomes part of the system, or a temporary result that depends on the manager's attention?

For me, that is the heart of the whole series.

On my first day as a Team Leader

If I could talk to myself on my first day as a Team Leader, I would say: do not try to solve every problem yourself. Be close to the operation, listen to people and understand the process before you change the rules. Do not judge a driver by a single negative KPI, and do not confuse a bad day with a systemic problem.

But above all, I would tell myself the sentence I opened this essay with.

You can improve a KPI, organise a ramp, write a procedure or solve a hard problem. But improvement does not end the moment the result gets better. You have to understand whether that result can be kept, whether new people can follow the same standard, and whether the process works without your constant intervention.

Real improvement is not the kind that only works while the manager is there. It is the kind that keeps working when the manager leaves.

You can fill in the sheet below for an improvement you have made, and copy it. Its last question is the one that matters most.

A good manager can improve a working day. A good system keeps the improvement alive even on the day the manager is not there.