Lesson 7: Why Your Improvement Initiatives Keep Failing

Lesson 7: Why Your Improvement Initiatives Keep Failing (And the 30-Day Fix That Changes Everything)

Most operational experiments don’t flop because the original idea was bad. It’s almost always because nobody spelled out what “done” looks like, or stuck to it when things got messy.

Just about every organization falls into the same trap. Spot a problem, come up with a solution, suggest a pilot. Everyone nods along, and things kick off. But then the drift starts. Somebody proposes a tweak. Another team wants to piggyback and try something else. Slowly, the goal keeps shifting. Fast forward six months, and the pilot is still running with no conclusion. All anyone can agree on is that “we need more time.”

So, it didn’t technically fail, but it never finished. Which means you never get the answer you were looking for. That’s what happens when you try to run experiments with no structure. And honestly, it’s one of the costliest habits in operations – not because each pilot is pricey, but because the pile-up of unfinished, unevaluated projects drains everyone’s energy. Teams stay busy, leadership debates endlessly, and problems stick around, now dressed up as “continuous improvement.”

The real fix? Draw harder boundaries, not tighter plans.

Here’s the thing. Quick, clear experiments deliver answers. Vague pilots just stir up politics.

Let’s say you’ve already mapped out the process, talked to people on the ground, hunted down key failures, confirmed the causes, put together your one-page summary, and picked your north star metric. You know what’s broken. You have a clear signal to track.

Now you need a “container” for the experiment – a set window, a single objective everyone can see, and a locked scope that stops your test from morphing every time the wind shifts.

It’s not about people having bad intentions. Ambiguity breeds opinions, and when there’s no finish line, those opinions turn into political debates instead of answers.

A well-built 30-day experiment solves this. Not ninety days, not “a few months.” Thirty days. Short enough to keep things urgent, long enough to spot real trends, and clear enough so nobody wonders when it’ll end.

Let me give you a real example.

There was a team running an “experiment” to shave down a process timeline. Baseline was 14 days. The goal? “Make it faster.” But nobody said how much faster. They threw a bunch of interventions at the wall. No single owner. No agreed end date.

As expected, every time things got stuck, the team changed tactics. Each new suggestion got added. When they reviewed progress, the conversation always turned to whether the methodology was right – not whether the intervention actually worked. Lots of effort, almost zero useful evidence.

So, we put a stop to it. We wrote a one-page experiment charter that spelled out six things:

1.    Baseline – 14 days. Not guessed, measured and agreed by all.

2.    Target – 9 days. A specific improvement, nothing vague.

3.    Interventions – three changes: a checklist, a daily stand-up, a single signal.

4.    Owner – one person, not a team, in charge.

5.    Window – 30 days, hard stop on the calendar.

6.    Scope lock – no parallel experiments, no mid-stream additions, unless the owner signs off.

We shared that charter with everyone up front. And that matters more than you’d think. When someone showed up halfway through with a bright idea, the owner could lean on the charter and say, “Not this round.” It wasn’t about shutting out good suggestions – it was about keeping the experiment pure.

Here’s how it played out:

–      The experiment actually finished. Might sound basic, but seriously, it’s rare.

–      The results were clear: interventions worked, the signal improved, the team had real data, not just hunches.

–      Arguments about “is it really working?” vanished, since the charter spelled out what “working” meant.

–      The learnings flowed into the next experiment – a real, new experiment, not just another leg of the same, never-ending pilot.

That last part matters. When experiments have true finish lines, teams get better at running them. Each one builds real evidence. Evidence builds judgment. Judgment feeds into operational skills that become your edge against the competition.

So, how do you build your experiment charter? Easy. One page, six pieces. Send it out before you start.

1.    Objective – one sentence about what you aim to learn or achieve. Skip the generic; make it clear enough that anyone can spot success.

2.    Baseline – the real, measured starting point. No estimates, no “feels like”; use the actual number.

3.    Target – what you will call a win. Again, write down a number, percentage, or crystal-clear outcome.

4.    Interventions – the exact changes, and nothing extra. If it’s not listed, it doesn’t happen unless the owner approves.

5.    Owner – name ‘ONE’ person. No committees here.

6.    Window – when it starts and ends. Put the stop date in everyone’s calendar.

Once it’s written, share it with every stakeholder, especially the ones who might derail the plan with new ideas halfway through. Your written charter is the tool the owner uses to stick to the plan, and gives everyone confidence that it’s being run right.

One personal note. For a long time, I let experiments drag on. There was always some logical excuse: the sample wasn’t big enough, maybe we should test another variable, results looked promising but needed more proof. Meanwhile, clarity never arrived.

Things changed when I forced hard finish lines and stuck to them, even when the pressure to keep going was intense.

A finished experiment with imperfect results is worth infinitely more than another that never ends. Even if it’s messy, at least you learn something. The never-ending experiment just eats up attention and gives everyone the comfortable feeling of progress without actually delivering it.

Write the charter. Lock the scope. Trust the finish line.

When the thirty days are up, measure honestly, share everything, including what didn’t work, and let the evidence decide what comes next. That’s how real improvement happens. Not from endless pilots, but by finishing what you start.

Look around at the improvement efforts happening in your organization right now. How many have a written charter and a hard end date? If it’s fewer than you want, pick the most important one and write the charter today. The experiment’s already underway, whether you like it or not. Give it an ending.

[Sample Experiment Charter]

In my next post I will be discussing why accountability needs simple rituals, see you then.