A 90-day plan to improve your clinic operations

An operational planning guide for dental and aesthetic clinics. The timetable is an adaptable working proposal, not a promise of results within a fixed period. Examples are hypothetical.

A clinic may have many improvement ideas and little capacity to execute them simultaneously. Reviewing scheduling, clarifying responsibilities, updating the website, improving follow-up and organising training are all reasonable projects. The difficulty begins when they start together, compete for the same people's attention and become a collection of open tasks that nobody manages to complete.

A 90-day plan provides an understandable horizon for choosing a focus, testing changes and reviewing learning. It does not suggest that every problem can be resolved in three months. It means agreeing what the clinic will try to improve, which resources it will use and how it will choose the next step. This guide turns priorities into work with owners, dependencies and reviews while preserving capacity for everyday operations.

1. Define an operational result you can recognise

Start by describing what should work differently at the end of the period. “Improve the clinic” is too broad. “Open enquiries have an owner and next action”, “shift handovers preserve continuity” or “management meetings produce decisions with follow-up” describe recognisable conditions. The wording should identify the working practice you want to establish rather than a general ambition that could mean different things to different colleagues.

Distinguish the result from the tasks used to achieve it. Creating a template, training staff or configuring a field are activities. They can be completed without changing actual work. The plan needs both executable actions and a definition of how you will know the practice is being used. Otherwise, completed documents may be celebrated while the original operational problem continues.

Check that the result falls within the agreed scope. Do not turn it into a guarantee of acquisition, revenue or individual performance. Some variables are not entirely under the clinic's control. A clearly defined operational objective supports learning and decisions without presenting a 90-day horizon as an automatic formula for growth or a substitute for understanding local conditions.

2. Establish a straightforward starting point

Before planning changes, describe how the selected process currently works. Review a recent sample, listen to those involved and record recurring difficulties. An endless audit is unnecessary. You need enough information to avoid basing the plan exclusively on the latest incident or one person's perception. Different functions may observe different consequences of the same underlying handover.

Select two or three signals for reviewing progress. These might be cases without owners, repeated clarification requests, uncommunicated changes or commitments passing their dates without a decision. Define how they are obtained and who checks them. If information remains incomplete, acknowledge the limitation and include an action to improve recording before interpreting the figures with excessive certainty.

Record the period's conditions too: planned absences, timetable changes, new starters and projects already committed. These affect available capacity. The plan should begin with the actual clinic rather than an imaginary week without interruptions. Clinic leadership and management support can help establish that starting point and choose a scope that fits the organisation's circumstances.

3. Choose a main focus and limit open work

Order improvements by the problems they address, the people affected and their dependencies. Then select one main focus. A supporting action may remain necessary, but avoid opening several transformations requiring the same attention. Coordination time is limited even when every project appears simple in isolation. The combined load can be much greater than the visible task list suggests.

Keep a list of matters outside the current period. Add a short reason: information is missing, another decision comes first or capacity is unavailable. This preserves ideas without continually adding them to active work. Deliberate postponement does not mean neglect. It makes the choice visible and provides a place to revisit the idea when conditions change.

Agree how a new priority enters the plan. When an important need appears, review what will be paused or reduced to accommodate it. Adding work without removing anything turns the plan into an accumulation of wishes. Limiting open work makes completion, observation and an honest discussion of capacity more likely than continually expanding the list.

4. Assign owners able to act

Each action needs somebody coordinating progress and a route for resolving obstacles. A name beside a date is insufficient. Check that the owner has time, information and authority to do what has been agreed. If a management decision is required, they should know how to obtain it and when it will be reviewed rather than repeatedly asking through informal messages.

Distinguish the owner, participants and people who need information. A handover change may have one coordinator and several colleagues testing it. Not everyone must attend every conversation, but everyone affected should understand the change to their work. Clear allocation prevents both excessive meetings and unexpected instructions reaching the people expected to implement them.

Review workload distribution. The most capable colleague often receives additional tasks because they inspire confidence, but can become the next bottleneck. Team organisation should account for responsibilities already in place. Delegating a project does not remove the recipient's existing daily work. Capacity needs to be adjusted explicitly rather than assumed from their willingness to help.

5. Reserve capacity for coordination

Improvement takes time for observation, agreement, configuration, practice and review. A plan containing only the final task overlooks much of the effort. Estimate the needs of each stage with those doing the work and reserve periods compatible with clinic activity. A simple estimate is more useful than assuming the project will happen in whatever gaps appear during the day.

Include external dependencies where relevant: a software supplier, technical support, designer or adviser. Clarify what you need and when it can be requested. Do not fix implementation around a response that has not been confirmed. The preceding task may be to establish availability and scope, giving the rest of the plan a more realistic basis.

Allow room for adjustments. Initial use often reveals unexpected questions, and a schedule with no capacity to address them may cause staff to abandon the change. This margin is not a lack of ambition. It recognises implementation as real work and learning as part of execution rather than an inconvenient interruption to the original timetable.

6. Divide the period into understandable phases

A useful structure separates understanding, testing, adjustment and consolidation. Exact dates can vary by clinic. Each phase should have a purpose and an exit condition. Do not move to broad implementation solely because a date has arrived if the process remains unclear or the tool has not been checked. The calendar should support decisions rather than replace them.

Indicative period	Main work	Reviewable output
Days 1–15	Define the problem and observe the journey	Question, starting point and owners
Days 16–35	Design and trial a limited change	Working trial and recorded questions
Days 36–60	Adjust and extend only what fits	Updated procedure and training
Days 61–90	Consolidate, review and choose continuity	Maintained practice and next priority

Use this timetable as guidance rather than an obligation to progress without evidence. A phase may need longer when information is insufficient or an important dependency emerges. Explain why the change is necessary and how it affects the rest of the plan. Transparency supports a realistic commitment more effectively than preserving dates that no longer reflect the work.

7. Form a hypothesis and a concrete trial

Choose an explanation that can be checked. For example: “Outstanding work is lost because handovers lack owners and review dates.” A trial might add these elements for one shift or team over a limited period. State what changes and what will be observed without modifying the entire system simultaneously. The scope should be small enough to understand what happens during actual use.

Agree in advance which signs would lead you to retain, adjust or stop the trial. If continuity improves but recording effort becomes excessive, simplification may be needed. If the practice is unused, investigate training, access and whether its purpose is clear. Results include learning why a proposal fits or does not fit everyday work, not merely a change in a headline figure.

Do not expect a small trial to demonstrate a broad impact with very few cases. It can provide useful operational learning before reliable trend conclusions are possible. Record examples, questions and observed conditions. That information supports a better decision than declaring success or failure only because a number changed during a handful of days.

8. Keep weekly review brief and useful

A weekly review establishes what has been completed, what is blocked and which decision is needed. It should not become a lengthy presentation of every activity. Each owner can prepare a short evidence-based update: a validated document, completed practice, resolved question or outstanding condition. The emphasis is on progress that can be checked rather than an impression of being busy.

Separate overdue tasks from obstacles. A task may take more effort than expected; an obstacle requires a decision, resource or missing information. Treating them identically leads to repeated date changes without resolving the cause. Ask what must change to move forward and who can act. If nobody can address the dependency, reconsider the scope or sequence.

Finish with a few agreements and preserve continuity. The next meeting should check what happened to them. Update the current plan and explain changes to the team. A calendar displaying only the original intention becomes unhelpful when actual conditions have moved on. Maintain a short decision record covering significant changes to scope, sequence or resources, with the date, choice and reason.

For example, extending a trial because too few comparable cases occurred should be recorded with its new review date. This prevents the adjustment later being interpreted as unexplained failure. It also preserves why an alternative was rejected when somebody proposes it again. Every conversation need not be documented; consequential planning decisions should remain understandable.

9. Explain the change to its users

A well-designed project may fail in use because staff receive incomplete instructions. Explain why the change matters, what each function should do and where the current rule is available. Use ordinary situations and exceptions as examples. Avoid presenting the tool as a solution by itself without explaining the working practice that the tool is intended to support.

Listen to difficulties reported by the people doing the work. Some reveal training needs; others reveal a design that does not fit. Do not interpret every question as resistance. Ask what happens when the rule is applied and observe a case. Information from actual use should be allowed to change the plan rather than being dismissed because it challenges the original design.

Coordinate communication outside the team where appropriate. If a contact channel or administrative step changes, public information and confirmations should remain consistent. An internal improvement should not transfer uncertainty to patients. Implementation includes checking those connections before extending the change, so different parts of the clinic do not unintentionally explain different processes.

10. Manage risks and dependencies simply

List a few situations that could obstruct the plan: an owner's absence, missing access, a supplier delay or an unresolved definition. For each, identify an early signal and a possible response. A complex document is unnecessary. You need to know what to watch and who decides if the issue appears, especially where it affects several actions at once.

Distinguish a dependency from a task you can perform independently. If configuration requires supplier confirmation, do not mark it as committed without checking. Record the request and its review date. If a delay affects other actions, adjust their sequence rather than leaving dates that are no longer achievable. The plan should reflect constraints instead of concealing them.

Define what must be preserved during the trial: continuity of service, necessary information access and clear responsibilities. A management change should not weaken essential processes to improve one indicator. If an important unintended consequence appears, pause or adjust the trial and review the design with the people responsible. Progress includes recognising when the proposed approach needs to change.

11. Review progress through measures and examples

Compare the starting point with the current process using equivalent definitions. If recording changed, acknowledge it. Apparent improvement may result from more complete information, while an initial increase in incidents may mean previously hidden issues are now visible. Interpretation needs context, including changes in workload or staffing during the period being compared.

Combine measures with working examples. Can a handover continue without locating the previous colleague? Does an enquiry have an answer or a clear next step? Does the team know when to escalate an exception? These questions check actual use. Management indicators should support that review rather than substitute a number for understanding the practice.

Examine the effort required to maintain the change. If it depends on someone checking everything manually every evening, it may not be sustainable. Seek simplifications and support before extending it. The desired outcome is a working arrangement maintained with agreed resources, not a temporary improvement created through exceptional effort that cannot continue once attention shifts elsewhere.

12. Consolidate before opening another project

When a practice helps, document its current version, owner and review method. Update training and retire instructions that no longer apply while preserving the history the organisation needs. Staff should know where to find the current reference and how to report a question. Consolidation includes removing ambiguity between old and new ways of working.

Check continuity through a shift change or planned absence. If the process works only for people involved in the trial, part of implementation remains unfinished. Use a supported handover to reveal knowledge still held informally. Training and protocols help convert local learning into a shared practice that new colleagues can understand and apply.

Set a reasonable future review frequency. Consolidation does not mean declaring the process unchangeable. It means having a way to maintain and adapt it without rebuilding from zero. Once that exists, a new priority can be introduced more safely without silently abandoning the improvement that has just been established.

13. A hypothetical 90-day plan

Imagine a clinic where new enquiries arrive through several channels and some have no next action. The period's objective is for open cases to have an owner, status and appropriate next step. During the first weeks, a sample is reviewed and definitions agreed. A daily handover is then tested during one shift rather than introduced everywhere immediately.

The trial reveals that some statuses are too similar and absence cover is missing. Staff simplify categories and practise the handover. Later, the rule extends to the other shift, with checks on whether cases can continue without reconstructing earlier conversations. The plan adapts to learning while preserving its operational objective and clear review points.

At the end, management examines what is being used, which questions remain and the effort required. It may consolidate, extend the practice or devote another cycle to a specific difficulty. No economic outcome or complete transformation is assumed. The value lies in turning a broad concern into a tested practice and an informed next decision.

14. Prepare a one-page starting plan

Summarise six elements: intended result, starting point, main actions, owners, reserved capacity and review dates. Add the short list of deferred matters and the rule for introducing priorities. The document should be understandable without a lengthy explanation and remain current throughout the period. It is a working reference rather than a presentation created only for the launch meeting.

Review the plan with those executing it. Check whether the scope fits actual activity and whether each person knows their next action. Reduce it before delays accumulate if necessary. A small, maintained plan can provide a solid basis for continued improvement; an ambitious plan without capacity can increase the disorder it was intended to resolve.

Request a free one-hour call with Eusklinic to assess your clinic's current situation and organise an initial priority. We can help clarify what to review and the conditions a realistic plan requires. You can also use the service finder to prepare for that conversation.

Related reading: Assessing clinic operations: how to find bottlenecks · Clinic management indicators: a dashboard that supports decisions