Start With What You Can Fix This Month

Most improvement plans fail at the same place, and it isn't the analysis.

They fail because the first visible result is nine months out, and nothing survives nine months of a company's attention.

I learned the alternative on a factory floor.

What a Kaizen event actually is

At Milgard Manufacturing I ran and took part in Kaizen events. Strip away the terminology and it's this: you get the people who actually do the work into a room — not their managers, the people whose hands are on it — you walk every step of the process together, and you fix what can be fixed inside the week.

Not scoped for next quarter. Not routed through a steering committee. Fixed, this week, by the people who understand why it was broken in the first place.

The reason it works isn't the framework. It's that the person who does the job every day already knows where the waste is. Nobody has ever needed to be told. They've just never been asked in a setting where telling led to anything.

The part that worked, almost every time

The short-cycle fixes were clean and immediately impactful.

They shared four features, and I've since found these are the four that predict whether any change sticks:

• Small enough to finish. Days, not quarters.
• Visible. Somebody can see the difference without a report explaining it to them.
• Owned by a person in the room. Not a department. A name.
• Done before anyone loses interest. Attention is the scarcest resource in any company, and it has a half-life of about three weeks.

Hit all four and the change holds. Miss one and you're relying on discipline, which is a lovely thing to rely on right up until the quarter gets busy.

There's a second, less obvious payoff. Quick wins buy you credibility for the harder conversation later. Walk into a business, spend six weeks analysing, and hand over a transformation plan and you're asking for faith. Fix four irritating things in the first fortnight and the next conversation is entirely different, because you've demonstrated you understand how their day actually works.

One more thing about that first list, because the line has moved.

When I was running these events, "fixable this week" meant fixable with what you already had — a layout change, a checklist, a handoff removed, a form simplified. Anything that needed software went on the long list, which is where things go to evaporate.

That's no longer true. A fair number of fixes that used to require a system now take a few days to build directly for the way a specific business works. Which means the short list — the one that reliably gets done — is meaningfully bigger than it used to be. It's the single biggest practical change I've seen in how improvement work goes.

The part that was hit and miss, and I'd rather say so

We also identified the bigger-ticket items — the ones needing capital, or a system, or several departments to agree. Those went on a timeline with scheduled follow-ups to keep everyone in sync.

Sometimes that held. Sometimes it didn't.

I'm not going to dress that up. It's the most useful thing I know about how change works in real companies: the further out you plan, the more of it evaporates. Not because people are lazy or the plan was wrong. Because priorities shift, the person who owned it moves roles, a bigger fire starts, and the follow-up meeting quietly stops being scheduled.

Which leads to the practical conclusion most improvement plans get backwards. If your long-horizon items are the ones most likely to evaporate, you should not front-load your plan with them. You should bank everything you can bank now, and treat the long-horizon list as a real but discounted asset — worth planning, worth scheduling, worth following up, and worth being honest with yourself about.

The follow-up cadence is the part everyone drops first, and it's the only thing keeping the long list alive. A date in a calendar with a named owner is not bureaucracy. It's the entire mechanism.

The blind spot nobody mentions

Kaizen, at least as I used it, was built for taking cost out. Waste, motion, defects, time. It's excellent at that.

It did not naturally produce revenue ideas. Nobody walked out of a Kaizen event with a new pricing structure or a channel worth opening. I was at Milgard just over a year, so I can't tell you whether that changed after I left.

But I don't think it's a flaw in the method so much as a limit on where it got pointed. The cadence — look at all the parts, fix what's fixable now, schedule the rest, actually follow up — works on the growth side too. It's just that the people running these events were usually operations people, and operations people are measured on cost.

That's how I use it now. Same rhythm, pointed at the whole business rather than only the parts that spend money.

What you can do with this on Monday

You don't need a consultant to run the first version of this.

Pick one process that irritates everybody. Get the people who actually touch it in a room for ninety minutes — not their managers. Ask what they'd change if they were allowed. Write down everything, then split it into what could be done this month and what couldn't.

Do the first list. Put a date and a name against each item on the second, and put a follow-up in the calendar.

You'll fix some things. You'll also find out, quite quickly, which parts of your business your own people have been quietly working around for years. That second thing is usually worth more than the first.