Lesson 6: Managing People When You Are Also Working the Schedule

Look at an office manager's written list of things to do today and then look at what they actually did. The list says reconcile the month, work the aging report, follow up on two claims, and prepare for Thursday's meeting. What happened was forty-one interruptions: a patient at the window with a question about a statement, a hygienist who needs a decision about a schedule change, a payer on hold, a doctor who wants to know about Friday, an assistant who is upset about something that happened in the sterilization area, and a delivery that needs signing. At five o'clock the list is untouched and the day was completely full.

The instinct is to treat that as a failure of discipline and to look for a system that will protect the calendar. Some of that helps. But the interruptions are not an obstacle to the job, they largely are the job, and the management work that keeps getting postponed has to fit inside a day shaped like that rather than waiting for a quieter one. This lesson is about the people part specifically: running meetings that decide things, giving feedback that lands, having the conversation you have been avoiding, doing reviews without an HR department, handling conflict between two people who both have to work chairside tomorrow, and telling the difference between a person problem and a system problem.

The Job Is Mostly Interruptions

A dental office manager is the practice's exception handler. Anything that does not fit a process arrives at their desk, and by definition those things cannot be scheduled. Fighting that produces a manager who is unavailable, and an unavailable manager generates more problems than they solve, because the team starts making their own decisions about things that should have been asked.

What works is sorting rather than blocking. Three questions handle almost every interruption: does this need me, does it need me now, and does it need a decision or just an answer?

• Needs a decision, now. A patient is waiting, money is involved, or the day changes. Handle it immediately. This is the job.
• Needs a decision, not now. Goes on a list with a name, and gets handled in a set window later.
• Needs an answer, not a decision. Answer it, and then notice: if the same question arrives three times, it is a missing written system, which is Lesson 5's territory.

Two structural habits do most of the work. First, a visible window: a stated time each day, usually mid afternoon, when people bring the non-urgent things. Announcing that window is what makes it acceptable to say later, because later now has a specific meaning. Second, two protected blocks a week for the work that requires uninterrupted thought, blocked in the schedule like a patient, with a named person covering the desk. Anything less than about an hour is not enough to reconcile or analyze anything.

The Team Meeting That Is Not a Complaint Session

Team meetings fail in a specific way. Someone raises a frustration, several people agree, twenty minutes disappear, nothing is decided, and everyone leaves slightly more annoyed than they arrived. Do that twice and attendance becomes compliance rather than participation.

The huddle from Lesson 2 handles today. The team meeting handles everything else, and it needs a different shape.

• Published agenda, in advance. Two or three items, not eleven. Anyone can add an item before the deadline, which is what makes the agenda a real constraint rather than a formality.
• One substantial topic per meeting. One thing discussed properly beats five things mentioned.
• Problems arrive with a proposal. Not a solution, a proposal. This single rule changes the meeting more than anything else, because it moves people from describing a frustration to thinking about it beforehand.
• Every item ends in a decision, an owner and a date, or it ends with a stated reason for not deciding yet and when it will be decided.
• A parking lot. Off-topic items get written on a visible list and genuinely revisited, which is how you cut a tangent without dismissing the person.
• Open by reading last meeting's decisions and what happened to them. Same mechanism as the huddle, same reason.

Rotate who brings the main topic. A meeting where the manager talks and the team listens is a briefing, and briefings do not surface the things you most need to hear. And never use a team meeting to address one person's performance, even obliquely. Everyone knows who it is about, the person it is about feels ambushed, and everyone else learns that this room is not safe.

Feedback That Lands

Most feedback in dental offices is either absent or delivered in a rush, at the wrong moment, about the wrong thing. The shape that works is unglamorous and can be learned in an afternoon.

Timing first. Close to the event, never in front of patients or coworkers, and never while either person is still hot. Same day is the target. A week later the feedback is about a memory, and the person will spend the conversation reconstructing what happened rather than thinking about what to change.

Then four parts. The specific behavior, described as an observation rather than a characterization. The effect it had, concretely. What you are asking for next time, stated plainly. Then stop talking and hear their side, which frequently contains information you did not have.

The word that ruins feedback is always. You always run late, you never write the notes. It is almost never true, it invites an argument about the exception rather than the behavior, and it turns a fixable event into a statement about who someone is. Describe the instance.

Praise Has the Same Rules

Specific and prompt, and about something the person actually chose to do. Great job today is pleasant and forgettable. Noticing that someone stayed with an anxious patient through a long appointment, or caught a coding error before a claim went out, tells them exactly what to repeat. Generic praise delivered constantly also devalues the specific kind when you need it.

The Conversation You Keep Putting Off

Every manager has one. Someone who is late regularly, someone whose tone with the team has become a problem, someone coasting. It is not urgent on any particular day, so it never makes the list, and it is quietly costing more than anything on the list.

Waiting makes it worse in three ways, all of them predictable. The behavior becomes precedent, because months of silence read as acceptance. Your resentment builds, so when the conversation finally happens it is heavier than it should have been. And the rest of the team notices, which costs you credibility with the people who are doing the right thing.

The way through is mechanical. Write the first three sentences down and say them as written, because the first thirty seconds are where people soften into vagueness and the whole conversation loses its point. Pick a private room and a time when neither of you is about to do something else. Say the thing plainly, then stop and listen. Agree what changes, by when, and how you will both know. Write down what was agreed, on the same day, factually.

Before any conversation that could lead to discipline or a change in employment, talk to your employment advisor about what to document and how. Our lessons on what to do when it is not working go further into that territory.

Reviews When There Are Eight People and No HR

Small practices tend toward one of two extremes: an elaborate annual review borrowed from a corporate template that exhausts everyone and happens once, or nothing at all for years. Both fail, and the middle is easier than it sounds.

Four principles carry it.

1. Frequent and short beats annual and heavy. A structured half hour every few months, with a written summary, does more than two hours once a year.
2. No surprises. If something in the review is news, the manager failed at feedback during the months in between. A review summarizes a conversation that has been happening.
3. Separate the pay conversation from the development conversation. Run them in different meetings, even if they are in the same season. When money is on the table, nobody hears anything else.
4. Ask first. Send three questions in advance: what went well, what was harder than it should have been, and what would make the job better. Read the answers before the meeting. Many managers learn more from those than from anything they prepared.

Keep it simple and consistent, and keep a written record of each one. The Hiring and Keeping a Team course covers the fuller retention picture, and the office manager guide covers the breadth of the role.

Conflict Between Two People Who Work Together Tomorrow

This is the situation that keeps managers awake, because in a small practice there is no transfer, no other department and no distance. They will both be in the building at eight in the morning.

The move that fails is trying to resolve the feelings. You are not going to adjudicate who was rude to whom in a room with no witnesses, and attempting it makes you a judge, which is a role you cannot win in.

What works is narrowing to the operational problem. Meet each person separately first, listen without agreeing to a version of events, and find the concrete thing that is not working: a handoff that is unclear, a workload that is unevenly divided, a room that two people need at the same time. Then bring them together for that specific problem, with the standard stated plainly: you do not have to be friends, you do have to work together professionally and neither of you gets to involve the rest of the team. Agree what changes operationally, and check back within two weeks rather than hoping.

Sometimes there is a genuine behavior problem underneath, and that becomes an individual conversation rather than a joint one, with your employment advisor consulted if it may go further.

Is It a Person, or Is It the System?

This is the most valuable question in the lesson, and the honest answer is usually the system, which is not the answer managers are trained to reach for.

The test: would a competent, well-intentioned person in this exact situation, with this training, this information and this amount of time, probably do the same thing? If yes, you have a system problem wearing a person's name, and disciplining the person will produce compliance, resentment and the same outcome from the next person in that seat.

Three signals point at the system rather than the individual. The problem survives a change of personnel. More than one person does it. And the person who does it can explain exactly why, and the explanation makes sense given what they were working with.

It is genuinely a person when the behavior persists after the system is fixed, when it is specific to them under conditions others handle fine, or when it is about conduct rather than performance. Conduct is a different category and belongs in a different conversation, with advice from your employment advisor. The managing chapter covers the distinction in more depth.

THE CHAIRSIDE TAKE

If you take one habit from this lesson, make it the system test, because most of what looks like a people problem in a dental office is a person doing their best inside a process nobody designed. Fix the process and the person usually becomes good at their job again, which is cheaper and kinder than replacing them. The thing I would not soften is the conversation you are avoiding. It is not going to improve, the team already knows about it, and every month you wait costs you credibility with the people who are doing everything right. Write the first three sentences tonight. What no lesson can settle for you is the legal side, so before anything formal, call someone who knows your state.

Lesson 6 of 6 in Practice Management: Running the Day

This guide is educational content and does not constitute legal, financial, tax, or clinical advice. Laws and regulations vary by state and change over time. Consult your own dental-specific attorney, CPA, and state dental board before acting.