The Day the Broom Wouldn’t Stop

There is a story I keep coming back to.

Not because it is literary.

But because it feels uncomfortably real.

It is the story of The Sorcerer’s Apprentice.

The master leaves the room.

For the first time, the apprentice is alone.

No supervision.

No instructions.

Just possibility.

And like most of us would, he looks at the work in front of him and thinks:

There has to be a smarter way to do this.

So he decides to try something bold.

He takes a broom. Uses a spell he has observed, and brings it to life.

The broom starts working.

Fetching water.

Faster than any human could.

Relentless. Efficient. Perfect.

At first, it feels like a breakthrough.

The work is getting done. The system is working. The apprentice feels in control.

Then something small happens.

The water does not stop.

The bucket keeps coming. Again. And again. And again.

The floor starts to flood.

That is when the realization hits.

He knows how to start the system.

He does not know how to stop it.

I have seen versions of this play out more than once, and never in exactly the same way.

Not with brooms, of course.

But with systems.

A lending engine that scales beautifully, until risk quietly builds beneath it.

An onboarding process that becomes frictionless, until fraud follows the same path.

A model that improves performance, until no one questions its assumptions anymore.

At the beginning, everything works.

That is exactly what makes it dangerous.

Back in the story, the apprentice panics.

He shouts at the broom.

Nothing happens.

He tries to command it.

Nothing.

So he does what many of us do when control starts slipping.

He takes drastic action.

He grabs an axe and breaks the broom in half.

For a moment, there is relief.

Then both halves stand up.

And start working.

Twice as fast.

That part of the story always stays with me.

Because it captures something we do not talk about enough.

When systems are poorly understood, intervention can amplify the problem.

Not solve it.

Eventually, the master returns.

One word.

Everything stops.

Order is restored.

But here is the uncomfortable part.

In the systems we are building today, there is often no master returning.

No single person who fully understands the system end to end.

No one is holding the complete “stop” command anymore.

What we have instead are:

Teams that understand parts

Leaders who see dashboards

Systems that optimise continuously

And risks that move faster than conversations.

This is why the story feels less like fiction now.

I have felt this shift more than once.

And more like a pattern.

Over time, I have come to believe that the real lesson is not about the misuse of power.

It is about an incomplete understanding.

The apprentice was not reckless.

He was confident.

Just not fully aware of what he was triggering.

That is a thin line.

And we cross it more often than we admit.

So perhaps leadership today is less about control.

And more about restraint.

Less about starting systems.

And more about knowing:

When to pause.

When to question.

When to step back.

Because most systems do not fail immediately.

They drift.

Quietly.

Until they don’t.

And when they don’t, the question is no longer:

Why did this happen?

It becomes:

Did we really understand what we set in motion?

References & Acknowledgment

This reflection draws inspiration from Goethe’s The Sorcerer’s Apprentice and is influenced by ideas on systems and control explored by Yuval Noah Harari.

Rajarshi Banerjee writes on risk, governance, and leadership across India and Africa.