The Missing Checklist: How One Slip-Up Led to a System That Saved Us

We were delivering a large, custom order for a client event — the kind of job that feels like a proper win.

Big order. Tight deadline. Everything timed to a specific day.

I’d personally overseen the whole production. I’d been hands-on, checking the work, pushing things forward, making sure we hit the deadline.

And because I was so involved, I made a decision that felt reasonable at the time:

We skipped the final review.

Not because we didn’t care.

Because we were rushing.

Because everyone was tired.

Because it felt like an unnecessary delay when we were already under pressure.

And because I told myself the most dangerous sentence a founder can say:

“It’s fine. I’ve got it.”

Everything was in my head.

What could possibly go wrong?

What Went Wrong: Plenty

The phone call came a few hours after delivery.

I remember seeing the client’s name and feeling that little flicker of relief — like, “Great. They’re happy.”

They weren’t happy.

They were furious.

One of the key items was missing from around 30% of the packages.

Not a tiny optional piece.

One of the things the entire order was built around.

Their event was happening in hours.

The attendees would be arriving.

The packages would be handed out.

And a third of them were incomplete.

My stomach dropped.

Because immediately I knew what had happened.

It wasn’t sabotage.

It wasn’t incompetence.

It wasn’t even that someone didn’t care.

It was much worse than that.

It was a simple, human packing mistake that should have been caught by a final check.

And because we skipped the check, it slipped through.

We scrambled a fix.

We delivered missing items as fast as we could.

We apologised.

We did everything you do when you’re trying to rescue a situation that should never have happened in the first place.

But even though we “solved” it, the damage was done.

Not just operationally.

Emotionally.

Reputationally.

Because nothing shakes a client’s trust faster than being let down when it matters most.

The Wake-Up Moment: It Wasn’t a People Problem

That night, I couldn’t switch off.

I kept replaying it.

Where did it go wrong?

Who missed what?

How did we let something that basic slip through?

And eventually the uncomfortable answer surfaced:

This wasn’t a team issue. It was a process issue.

We hadn’t failed because someone was careless.

We’d failed because the system allowed a single moment of human error to reach the customer.

We were relying on:

• memory
• assumptions
• good intentions
• “I’m sure it’s fine”

And that might work when you’re small and calm.

But when you’re busy, scaling, rushing, and trying to deliver under pressure… memory is not a reliable safety net.

That’s why this saying exists for a reason:

Never rely on memory for critical tasks.

Not because people are unreliable.

Because people are human.

The Lesson: Build a System That Catches Mistakes Early

The next day, we implemented a checklist.

Not a 10-page SOP.

Not a heavy process that slowed everything down.

Just a simple, clear checklist that forced the important steps to happen every time.

And we added one rule that made all the difference:

No package goes out unless two people have ticked off every item.

At first it felt slightly “corporate”.

Like something that belonged in a bigger business, not a fast-moving team trying to be agile.

But what it actually created was something I hadn’t realised we were missing:

Protection.

Not protection from “bad staff”.

Protection from pressure, fatigue, distractions, assumptions, and rushing.

And the result was simple.

We never made that mistake again.

Not because we suddenly became perfect.

Because we stopped relying on perfection in the first place.

The Takeaway: Systematise the Repeatable

This is the founder takeaway I wish I’d learned earlier:

Anything repeatable should be systematised.

The more repeatable the task, the more likely it is that someone will eventually do it while distracted, tired, rushed, or overloaded.

And the more costly the mistake, the less you can afford to let it slip through.

Checklists aren’t bureaucracy.

They’re quality control.

They’re consistency.

They’re how you protect your reputation when things get busy.

Actionable Idea: Your 5-Minute Checklist

Here’s a simple exercise you can do this week.

Pick one recurring task in your business where a mistake would be expensive.

It might be:

• sending invoices
• publishing content
• packing and shipping orders
• handing over client deliverables
• onboarding a new customer

Now write a checklist for it.

Not 20 steps.

Just 5 bullet points that catch the most common errors.

Then commit to running it every single time.

This doesn’t slow you down.

It saves you from rework, stress, awkward client conversations — and reputation damage you can’t undo.

If you want to take it further, tools like PathWAI can help you turn these into structured workflows that are repeatable, trackable, and team-proof — but even a simple checklist in a shared document is enough to change how stable your operations feel.