Why the Same Problems Keep Coming Back in Your Med Spa

Key Takeaways

• Recurring problems are almost always model problems before they are people problems. Fixing the symptom without touching the underlying operating model means the problem comes back.
• Research described in the Harvard Business Review found that 85 percent of executives believe their organizations are bad at diagnosing problems, and 87 percent think that flaw carries significant costs.
• Structured diagnostic methods — such as asking what caused the cause, not just what went wrong — are what stop the cycle. Without structure, a team defaults to surface-level fixes every time.
• The 1-3-1 method has a team member bring one problem statement, three possible solutions, and the one action they would commit to first — with a date to measure whether it worked. The thinking happens before the conversation.
• When your team learns to bring solutions this way, you stop being the only person in the building capable of resolving anything. That is what operational separation looks like at the floor level.

---

“We keep fixing the same problem over and over. I’ll address something, the team nods, and three weeks later we’re right back where we started.”

You have held the staff meeting. You have retrained the person. You have addressed it directly, documented it, and made clear it cannot keep happening.

And then it happens again.

This is one of the most demoralizing cycles in a growing med spa. Not because your team is indifferent. Most of them are not. It is demoralizing because every time you fix it, you believe it is fixed. And every time it comes back, you wonder what you are missing.

Here is what you are missing: you have been solving the symptom. The operating model underneath it has not changed at all.

What she already tried — and why it keeps failing

The standard advice is to address problems directly and hold people accountable. So that is what she does. Staff meeting. Retraining. A written warning if it gets that far.

It doesn’t hold. Not because the team isn’t trying, and not because she’s addressing it wrong. It doesn’t hold because accountability without a model is just pressure. She is correcting the behavior. Nobody has examined why the behavior keeps occurring in the first place.

Research described in the Harvard Business Review found that 85 percent of executives believe their organizations are bad at diagnosing problems, and 87 percent think that flaw carries significant costs. The pattern is not unique to med spas. Most organizations, across most industries, manage backwards — something hurts, they act, then they measure whether the action seemed to work.

That produces activity. It does not produce understanding.

The other thing the standard approach produces is dependency. Every time you step in to resolve something, you confirm to your team — and to yourself — that resolution requires you. You become the diagnostic system. Which means every recurring problem waits for you to notice it, address it, and correct it again.

That is not a people problem. It is how the practice is built.

What actually produces recurring problems

When the same issue keeps surfacing, there are three places to look.

No model exists. Nobody ever defined how this task should run, so each person does it differently and nobody is wrong. Inconsistency looks like a behavior problem. It is an absent standard.

The model exists but nobody wrote it down. It lives in one person’s head — usually the owner’s, sometimes a senior team member’s. When that person is busy, traveling, or leaves, the model goes with them. New hires guess. Drift sets in.

Two models are running in conflict. One person was trained one way. Another was trained differently. They both believe they are correct. The inconsistency looks like a personality conflict or a communication problem. It is a documentation problem.

In every one of these cases, the failure is structural. According to the CertLibrary blog on root cause analysis training, structured problem-solving techniques — methods that systematically dissect complex challenges and uncover core contributors — lead to targeted corrective actions that not only resolve current problems but also prevent their reappearance. That precision in diagnosis is what a staff meeting alone cannot produce.

The 1-3-1 method — and what it changes

The 1-3-1 method is a simple structure for how a team member brings a problem forward.

One problem statement. Not a complaint, not a story. A single sentence that names what is happening and when. “Patients are not being rebooked at checkout” is a problem statement. “The front desk doesn’t seem to care” is not.

Three possible solutions. Before bringing the problem to you, the team member works out three things the practice could do differently or try. Not one — three. This step is where the real work happens. It forces the person past “remind everyone again” to options like “add a rebooking prompt to the checkout screen,” “agree on who owns rebooking when a provider is still with another patient,” or “move the rebooking ask into the treatment room before checkout.”

One commitment. Of the three, the team member says which one to try first — and answers the question that makes it real: how fast can we measure it to see if it is working? Not a list of maybes. One action, with a date on it.

That is the whole structure. One problem, three possible solutions, one commitment with a measurement date.

What it changes is who does the thinking, and when the follow-up happens. Right now, your team brings you the symptom and waits. You diagnose, decide, and direct. The 1-3-1 structure moves the thinking to the team member before they ever come to you — and because every commitment arrives with its own measurement date, the follow-up conversation is scheduled before the fix is even tried.

How you’d know it’s working

The signal is not that problems stop occurring. Some always will. The signal is that the problems your team brings you are different. They come with options and a commitment attached, not just a complaint. And the fixes hold.

A useful number to track: how many times in a 30-day period does the same category of problem surface? If your front desk rebooking rate is low in week one and low again in week four, the category is recurring. If it is low in week one and improved by week four because your team committed to a change and measured it, the method worked.

Watch whether your team is bringing you the same five things every month or new things. Same five means the model hasn’t changed. New things means they are working through their own problems and you are getting escalations, which is healthy.

What to do starting Monday

Pick the problem that has come back the most times in the last 90 days. One problem. The one that makes you feel like you’re going in circles.

Write the problem statement yourself first, in one sentence. Then ask the team member most directly involved to do the same exercise independently — one problem statement, three possible solutions, one commitment — before you meet to discuss it.

Compare what she wrote with what you wrote. The gap between them is almost always the real problem. It surfaces where the model is missing, where it was never communicated, or where two people have been operating from two different versions of the same assumption.

Once you have agreed on the one thing to try, document it. Not in a policy manual nobody opens. One sentence, posted where the task happens, owned by a named person who checks it — and put the measurement date on the calendar before the meeting ends.

Then do it again next month. The practice gets more stable each time not because you got better at fixing problems, but because you got better at not having the same ones.

Recurring problems are model problems. The practice stops running on your memory the day your team starts bringing solutions instead of symptoms.

FAQ

Why does the same problem keep coming back even after I’ve addressed it directly?

Because addressing it directly fixes the behavior in the moment without changing the conditions that produced it. If there is no documented standard, no system prompt, or no clear ownership, the drift returns as soon as your attention moves elsewhere. The fix has to reach the model, not just the person.

What is the difference between a people problem and a model problem?

A people problem is specific to an individual — performance, attitude, capability. A model problem recurs across different people or the same person in different situations. If you have had the same issue with two or more staff members, or the same person across multiple roles, the model is almost certainly involved.

How do I introduce the 1-3-1 method to my team without it feeling like more homework?

Start with yourself. Use it the next time you address a recurring issue — walk through three options out loud with your team rather than just announcing the fix. When they see it produces better answers than the usual staff meeting, they adopt it because it works, not because you assigned it.

How long before recurring problems actually stop recurring?

That depends on how many overlapping model gaps exist. Some practices work through two or three recurring issues in a month. Others find one change that was driving several surface problems. The pattern to watch for is whether new problems start looking genuinely new, rather than old problems wearing different clothes.

What if my team brings me a 1-3-1 and I don’t agree with their commitment?

That is a good outcome. It means options are on the table and the conversation is about what to try, not who to blame. Push back on the option, not the effort. Ask which of the three she believes will move the number fastest, and how soon you would both know. The discussion that follows is usually more useful than the pick itself.

---

If recurring problems are running your week, the Build Plan call is the next step. It is a working session, not a pitch — we look at where the model gaps are and what to address first.

Book a MedSpa Build Plan call