The Department of Buckets

There was, once, a department that managed drips.

Not in any formal sense. No one had ever set out to manage drips. It had simply… happened.

At first it was an occasional drip. Someone placed a bucket beneath it. Sensible. Temporary. The sort of thing that happens in any well-functioning organisation.

Then the drip became a trickle. Another bucket was introduced. Then a third.

Before long, the department had become exceptionally good at buckets.

There were small buckets for agile responses. Large buckets for strategic overflow. Some buckets were labelled. Others were not, but everyone knew what they were for. There was even, at one point, a short-lived working group on bucket standardisation, though it struggled to agree on what constituted a “medium” bucket.

New starters were always impressed.

On their first day, they would ask reasonable questions.

“Where is the water coming from?”

This was met, typically, with a pause. Not an awkward pause, just the sort of pause that suggests the question is slightly misaligned with how things are done.

“It’s always been there,” someone would say, helpfully.

“And has anyone tried to fix it?”

At this point, the conversation would gently move on. There were, after all, more immediate concerns. The water, for example, was rising.

Over time, the department developed real expertise.

There were people who could empty a bucket while filling another. This was widely admired.

There were escalation processes for when buckets reached critical levels. There were dashboards. There were weekly updates. Occasionally, there were reflections on whether the volume of water had increased, though this was difficult to confirm, as the organisation had become significantly better at handling it.

Importantly, the department delivered.

No one could deny this. Despite the water, despite the buckets, things kept working. Targets were met. Reports were written. Customers, who were thankfully unaware of the internal hydrology, received what they needed, more or less on time.

The system, if one could call it that, functioned.

From time to time, people arrived with ideas.

They would look around at the buckets, at the careful choreography of lifting, carrying, emptying, and they would say, quite reasonably:

“Should we fix the leak?”

This was not an unreasonable suggestion. In fact, it was broadly agreed to be the right suggestion.

There would be enthusiasm. Workshops. A paper or two.

Someone would draw a diagram of the ceiling.

But the water did not pause while these conversations took place.

Buckets still needed to be emptied. Overflow still needed to be managed. And those who had become very good at this work, who knew which bucket filled fastest, which corner flooded first, which workaround prevented a Monday morning incident, could not simply stop.

So the idea of fixing the leak remained, respectfully, in progress.

In time, improvements were made.

Better buckets were introduced. More ergonomic handles. Clearer labelling. A digital register of bucket locations, which was widely praised, though rarely updated.

There was even a pilot of a new bucket that could alert you when it was full. This was considered innovative.

And yet, the water remained.

The difficulty, though no one quite said it out loud, was this:

The work of coping had become the work itself.

The buckets were no longer temporary measures. They were the system. Skills had been built around them. Roles had formed because of them. Success was defined, in part, by how well the water was managed, not by whether it was still there.

And so, when change was proposed, it did not land on neutral ground. It landed in a place where people were already working at capacity, where stopping felt riskier than continuing, and where the reasons for the leak, if anyone had ever fully understood them, had long since faded into something like organisational folklore.

None of this was anyone’s fault.

The people managing the buckets were not resisting change. They were sustaining the organisation.

Those proposing change were not misguided. They were trying to improve it.

But between these two truths sat a quiet gap:

An absence of shared understanding about why things were the way they were.

And so the buckets remained.

Not because anyone believed they were the best solution,

but because they were the solution that worked, today, in the presence of water that had not yet been explained.

It is tempting, in such situations, to assume that progress is a matter of will.

If only people would change. If only priorities would shift. If only the right plan were agreed.

But more often, the challenge is simpler, and harder, than that.

Before anything can be fixed, someone has to understand the leak.

Not just that it exists, but how it came to be, what it connects to, and what would happen if, for a moment, the buckets were put down.

Because until then, the work of coping will continue to look like the work that matters most.

And in many ways, it is.