In the rugged frontier cabins of the 1800s, a woman would labor in childbirth while a midwife worked swiftly. A nervous husband often hovered, asking questions, shifting furniture, and generally getting in the way. “Go boil some water,” the midwife would order, without even looking up.
So off the husband would go to stoke the fire, haul the bucket, and tend to the kettle hopefully for a long spell—feeling useful, staying occupied, and staying out of the way. And soon enough the baby would arrive safely. The hot water proved handy for cleaning and compresses. The real gift was the breathing room.
Fast-forward to a sleek conference room today. A software implementation is underway. The client’s IT director—resentful of the purchase, convinced he could run it better—looms over every decision. He nitpicks requirements, second-guesses timelines, and derails the daily stand-up with war stories about the old system.
The project manager catches her CEO’s eye. “We gotta send this guy off to boil some water.”
A quiet nod. Within the hour the stakeholder is handed an “essential” assignment: a comprehensive audit of legacy data mappings, complete with detailed reports and stakeholder interviews—important work, genuinely useful, and conveniently scheduled in another building for the next three weeks.
Progress accelerates. The team delivers on time. The project succeeds.
The lesson is timeless:
When you hold ultimate responsibility for the outcome, watch for the signs— the meddler, the resister, the overly invested executive who risks derailing momentum. Don’t hesitate to assign the modern equivalent of boiling water: a purposeful task that channels their energy productively and gets them out of the critical path.
And when a sharp team member leans in and whispers the insider code—“This one needs to boil some water”—listen. That phrase just might save the project.
It worked for midwives then. It still works for leaders today.