The Dental Morning Huddle: Why Yours Stopped Working

Every practice management consultant tells you to run a morning huddle. Almost nobody tells you what to do when yours quietly turns into ten minutes of reading the schedule out loud to people who already have the schedule open.

That is where mine ended up. We had the meeting. We had it every day. And somewhere in the second year it stopped changing anything.

The failure mode nobody names

A huddle goes bad in a specific way, and it is worth naming because the fix follows from it.

It starts as a real conversation. Who needs what today, what went sideways yesterday, what we are worried about. Then somebody decides it should be consistent, so it gets a format. The format becomes a script. The script becomes a readout. And a readout is information transfer, which is the one thing software already does better than a meeting.

Once your huddle is a readout, your team is standing in a circle listening to facts they could have read on a screen. They know it. You know it. Attendance gets loose, people scroll, and eventually someone suggests it is not a good use of clinical time — and they are right, because at that point it isn't.

The schedule is not the content of a huddle. The schedule is the context for it.

What the ten minutes are actually for

The things worth saying out loud in the morning share one property: they are not in any system, and they die if nobody says them.

Four categories cover most of it.

Today's landmines. Not the appointment list — the specific risks inside it. The 2pm crown seat where the patient was unhappy about the temporary. The new patient who has already called twice with questions. The long procedure sitting right before lunch with a hygiene check wedged in behind it. Your PMS knows there are appointments. It does not know which ones are going to hurt.

Yesterday's loose ends. The insurance question nobody chased. The lab case that should have arrived. The patient who said they would call back and didn't. These are the things that fall through the cracks precisely because they belong to nobody in particular after 6pm.

Readiness. Does everything we need today exist in the building. Not "do we have supplies" in general — do we have the specific thing today's schedule requires.

One thing we are trying to do better. A single, current, shared focus. Not five goals on a poster from March.

If a huddle covers those four and nothing else, it takes about six minutes and it changes the day. If it covers the appointment list, it takes fifteen and changes nothing.

The readiness one is where I got humbled

We had a bone graft on the schedule. The membrane was not in the building.

Nobody had done anything wrong. The assistant who normally tracks it was out. The item had been used the previous week and the reorder had not been placed because the person who noticed it was busy with something more urgent, which is what always happens. The graft material was there. The membrane was not.

We found out the morning of. We got lucky — a supplier run made it work — but the honest version is that we were about twenty minutes from calling a patient who had arranged his day around a surgical appointment and telling him to come back in two weeks.

What struck me afterward was that every individual person in that chain had behaved reasonably. There was no one to blame, which meant there was nothing to fix by talking to anyone. The information had simply never surfaced anywhere a human would trip over it in time.

That is a systems problem wearing a people problem's clothes, and practices misdiagnose it constantly. You do not need a more responsible team. You need the fact to arrive before the day it matters.

Why the huddle is the right place to put things

Here is the thing that took me too long to understand: your practice already has an excellent system for scheduling patients and a completely unmanaged system for everything else.

Your PMS is very good at the schedule. It is very good at the ledger. It knows about production, collections, recall, treatment plans. Every piece of software the dental industry sells you is aimed at the same two things — more patients, more dollars.

None of it runs your team. There is no system of record for "the autoclave maintenance is due," "the new hire's first solo day is Thursday," "the membrane runs out in nine days," "Maria still hasn't been shown the closing checklist." Those live in people's heads, in group texts, on sticky notes, and in the gap between what one person assumed and what another person remembered.

The huddle is the only moment in the day when the whole team is in one place and paying attention. That makes it the natural surface for everything that has no other home. Not because meetings are good, but because that information has nowhere else to land.

So the fix is not "run a better meeting." It is: make the huddle the output of a system instead of a performance of one.

What that looks like in practice

Concretely, the huddle should arrive already written.

Nobody should be assembling it at 7:50am. The things that need saying are knowable in advance — a supply that will cross its reorder threshold before the next order date is knowable a week out; an onboarding task due Thursday is knowable Monday; an unresolved item from yesterday is knowable the moment it goes unresolved.

When those surface automatically, the meeting changes character. You are not reporting, you are responding. Somebody reads the four or five things that need a decision, decisions get made, names get attached, and everyone leaves.

The test for whether yours is working: could the meeting have been an email? If yes, it is a readout and it is dying. If the ten minutes produced decisions and owners that did not exist at 7:59, it is doing its job.

If you want to fix yours this week

You do not need software to start. Try this for five days.

Cut the schedule readout entirely. Everyone can see the schedule.

Replace it with two questions: what on today's schedule is going to be hard, and what from yesterday is still open?

Add one readiness check: does anything today need something we might not have.

End with one named owner for each thing that came up. Not "we should look into that." A name.

If five days of that is better than what you have now — and it will be — then the only remaining problem is that it depends on somebody remembering to prepare it. That is the part worth automating, and it is the part we built OperatoryOS to handle.

The meeting was never the problem. The meeting was the only place the real work had left to show up.

Written by a practicing dentist in Las Vegas. OperatoryOS is the team-operations layer for dental practices — the huddle, the checklists, the onboarding, and the supply thresholds that keep the day from falling over.