The Most Dangerous Words in Business Might Be “We're Good.”

They were doing a terrible job of looking overwhelmed.

Eating the chocolates. Hiding them in their hats. Stuffing them into their clothes.

Lucy and Ethel were falling behind, but you wouldn’t know it from the conveyor belt.

It was clear.

If you remember the chocolate factory episode of I Love Lucy, you know how they got there.

Their assignment was simple: wrap the chocolates as they came down the belt.

At first, they could manage it.

Then the chocolates started arriving faster than they could wrap them.

So they improvised.

And by the time their supervisor returned, they had managed to hide the evidence.

She saw a clear belt.

They knew what it had taken to keep it that way.

Her conclusion?

“Speed it up.”

That is the moment I keep coming back to.

The effort keeping the operation from falling apart had become the reason to put it under more pressure.

And I wonder how often we make that same decision.

We see the deadline met. The event delivered. The report submitted.

But do we know what it took?

Or are we looking at a clear conveyor belt?

What a Chocolate Factory Can Teach Us About Business

I recently broke down this scene in a Behind the System video, looking at seven lessons about standards, pressure, visibility, and what happens when the work moves faster than the system can support.

But I think the real value comes when you start recognizing these same behaviors inside your own organization.

Watch the breakdown below. Then we’ll look at where these hidden gaps show up in everyday work.

This 3-Minute I Love Lucy Scene Could Save Your Business Thousands

The Work Gets Done. But at What Cost?

Think about the last time someone on your team said, “We’re good.”

Maybe it was during your weekly meeting.

You asked whether everything was on track, and everyone gave you the answer you were hoping to hear.

The event is covered.

The customer was contacted.

The report was submitted.

The program is running.

And from where you’re sitting, there’s no obvious reason to question any of it.

But what you may not see is everything that happened to make those answers possible.

Someone stayed late because information arrived too late.

Another person recreated a document because they couldn’t find the original.

A program manager used a personal spreadsheet because the information wasn’t available in the organization’s shared system.

A team member followed up with a customer manually because the handoff never happened.

The work got done.

And that’s worth recognizing.

But the effort required to get the work done may be telling you something the final result never will.

The Problem With Measuring Only What Made It Through

In the chocolate factory, the supervisor sees an empty conveyor belt.

From her perspective, the output looks good.

But if she had followed the work, she would have discovered an entirely different situation.

Chocolates weren’t being wrapped.

Workers were improvising.

The pace was unsustainable.

And the information she was using to make her next decision was incomplete.

Now imagine this in your own organization.

You see that 50 people attended a program.

But how many people registered and never received a reminder?

You see that 20 new customers were acquired.

But how many required someone to step in and rescue the onboarding process?

You see that your team completed every assignment.

But how much time was spent chasing information, correcting mistakes, or doing work that should have happened automatically?

I’m not suggesting that every organization needs another dashboard.

In fact, that might create more work.

What I’m suggesting is that you need to understand what it takes for your team to produce the numbers you’re celebrating.

Because the final result doesn’t always reveal the condition of the system that produced it.

Three Signs Your Organization Might Be Hiding Its Own Chocolates

There are three things I’d pay attention to before deciding an operation is running smoothly.

1. The same work gets handled differently depending on who’s doing it.

One employee has a checklist.

Another keeps everything in their head.

Someone else created a spreadsheet because it was easier than using the existing process.

They may all get the job done.

But what happens when one person is absent, leaves the organization, or suddenly has twice as much work?

The gap may not be in their ability.

It may be in the absence of a shared, reliable way to complete the work.

2. Your reports look better than the experience of doing the work.

Your dashboard says everything is on schedule.

But your team is exhausted.

Meetings are getting longer.

People spend more time checking on work than completing it.

And the same problems keep getting solved by the same dependable employees.

That deserves attention.

Because you may be measuring completed work while overlooking the effort required to complete it.

3. You hear about problems only after they become urgent.

A deadline gets missed.

A customer complains.

A funder asks for information nobody can find.

Suddenly, everyone is trying to determine what happened.

But the issue probably didn’t begin that morning.

There may have been several opportunities to recognize it earlier.

The question is whether your system made those warning signs visible to the right person while there was still time to act.

The Move Most People Miss

Here’s what I find most interesting about that I Love Lucy scene.

The supervisor didn’t need more evidence that the belt was moving.

She needed to understand what was happening between the moment the chocolates arrived and the moment they were supposed to leave.

That’s where the work was breaking.

And it’s often where organizations have the least visibility.

Think about three parts of your business:

Win the work. What happens between someone showing interest and becoming a customer, donor, or participant?

Deliver the work. What has to happen for your organization to fulfill the promise it made?

Run the work. How do you know whether those activities are working without constantly asking someone for an update?

In each area, there are moments when work changes hands, decisions get made, or information needs to move.

Those moments are worth studying.

Not because your people are doing something wrong.

But because they’ve probably developed ways to work around problems you haven’t identified yet.

And those workarounds may be keeping your organization running.

Try This Before Your Next Team Meeting

Pick one process that your organization relies on every week.

Not your entire operation.

Just one.

Maybe it’s following up with new leads, registering participants, onboarding customers, submitting reports, or responding to service requests.

Now sit with the person who actually performs that work.

Ask four questions:

1. What does completed work look like? Make sure your definition matches theirs.
2. What usually happens when things get busy? Look for the steps that get skipped, delayed, or handled differently.
3. What do you have to do that nobody else sees? This is where hidden work often becomes visible.
4. How would I know something was falling behind before it became a problem? Identify the signal, the person responsible, and when that signal should appear.

Don’t turn the conversation into an audit of the employee.

You’re trying to understand the work.

And when you find a gap, resist the temptation to immediately purchase software or automate another step.

First, determine what information, decision, or handoff is missing.

Then decide what needs to change.

A Clear Conveyor Belt Doesn’t Mean Everything Is Working

Lucy and Ethel weren’t sitting around doing nothing.

They were working harder and harder just to survive the pace.

And that’s what makes the scene so recognizable.

I’ve seen organizations where the people care deeply about the work, understand the mission, and find creative ways to make things happen.

But their commitment can also make it harder to see where the operation needs support.

The dependable employee becomes the workaround.

The workaround becomes the routine.

And eventually, leadership starts treating that routine as evidence that the system works.

Until the belt speeds up again.

The goal isn’t to build an organization where nobody ever has to improvise.

It’s to build one where improvisation doesn’t have to remain invisible.

Because when you can see how the work is really getting done, you can make better decisions about what to improve, what to simplify, and where your people need more support.

And that’s how you create room to grow without asking everyone to keep running faster.

Keep building,

Touré

────────

P.S. If this story made you wonder where your own organization might be hiding a few chocolates, I created a practical resource called the Hidden Gap Finder. Use it to examine one workflow and identify where the work, the standard, or the visibility may be breaking down. It’s a good place to start before adding another tool, another meeting, or another person.