Your first 90 days as a sterile processing supervisor can fill up quickly: assignments, callouts, questions from the operating room, incomplete records, equipment concerns, and requests from your own manager. The temptation is to prove yourself by fixing everything immediately.
A more useful starting point is to learn how the department actually works, make responsibilities clear, and complete a small number of improvements people can see. This guide offers a practical 30-60-90-day structure for doing that.
The timeline is a planning aid, not a performance standard. Urgent safety concerns must follow the facility's immediate escalation process; they do not wait for a scheduled phase of your plan.
What recent leadership coverage is asking of SPD
In a May 2026 Infection Control Today interview, Kevin Bush and Brandon Gantt discussed the authority, education, and organizational recognition sterile processing leaders need. Their conversation places SPD leadership within patient safety, risk, and team development.
That framing helps a new supervisor define the role. Your work includes supporting reliable decisions, developing staff, and communicating constraints to the people who influence them. Completing today's assignment board matters, but it is only one part of leadership.
Begin by clarifying what decisions you can make, which require approval, and whom you contact when a problem crosses those boundaries.
Days 1-30: learn the department's actual work
Start with observation and conversation. Spend time across the shifts and work areas you supervise. Ask staff to show you how tasks, information, and unresolved concerns move through the department.
Read the relevant policies and compare your understanding with what people describe. If you see a discrepancy, investigate it through the appropriate process. Do not assume either the written document or the informal explanation gives you the whole story.
Make a simple list of recurring obstacles. Separate immediate concerns from issues that need more evidence and ideas that can wait. This keeps a long list from becoming a set of premature promises.
At the end of the first month, aim to explain the department's main responsibilities, escalation routes, and a few specific problems you intend to address.
Meet people with questions you can act on
Ask technicians what makes the required work difficult, which recurring questions lack an owner, and where handoffs become unclear. Ask educators where staff need support and which training resources are missing.
Ask your manager how priorities are set and how requests for staffing, equipment, or policy review should be presented. Ask partner departments what information they need from SPD and what they can provide earlier.
Avoid asking for feedback if you have no plan to respond. Keep a short record of themes and report back on what you heard. You can acknowledge an issue before you have a complete solution.
Learn the difference between history and current evidence
Every department has stories about why something is done a certain way. Those stories can identify useful questions, but they may not reflect the current instruction, agreement, or constraint.
When someone says a problem has always existed, ask for a recent example. Identify the task, the effect, and the information needed to understand it. Use authorized records rather than relying only on recollection.
Do not dismiss experience. Use it to guide investigation. Staff may be describing an issue that formal reports have failed to capture.
Days 31-60: establish a few reliable routines
Choose routines that make work and decisions clearer. Examples include a brief shift handoff, a consistent way to track unresolved questions, and a scheduled review of one recurring quality issue.
Keep the routines small enough to survive a busy day. A form that takes too long to complete may encourage staff to maintain an unofficial version somewhere else.
Agree on who owns each routine and where its information lives. If a concern is recorded, the team should know who reviews it and how the response returns to staff.
Use this period to test whether the routine helps. Ask what it clarified, what it duplicated, and which parts should be simplified.
Use huddles to update the plan
AHRQ's TeamSTEPPS huddle tool describes huddles as a way to reassess a situation and adjust the team plan. For SPD, you can adapt that principle to changing workload, equipment availability, and unresolved dependencies.
A useful huddle answers: What changed? What does it affect? Who owns the next action? When will the team receive another update?
Do not let the huddle become a public performance review. Individual coaching belongs in an appropriate setting. The group's time should clarify the work ahead.
Make your follow-through visible
If staff raise an issue, tell them what happened next. That may be a correction, an investigation, an escalation, or an explanation of why a request cannot proceed yet.
Use specific status language. “Submitted for equipment review; awaiting the owner's response” is clearer than “working on it.” Include the next point at which you will update the team.
Follow-through does not require pretending you control every resource. It requires keeping the concern connected to an owner and communicating honestly about progress.
Days 61-90: complete and evaluate one improvement
Select a problem with a manageable scope and enough evidence to understand it. Define what will change, who approves it, and how you will judge whether the change helped.
For example, a handoff problem might involve unclear ownership of unfinished work. A document problem might involve staff being unable to locate the current reference. A training problem might involve inconsistent assessment records between preceptors.
Choose a response that addresses the identified cause. Do not default to retraining when the obstacle is unavailable information or unclear authority.
Review the result using the same definition you used at the beginning. Explain what improved and what remains uncertain. A small honest result is more useful than a large claim unsupported by the evidence.
A one-page supervisor plan
Use this original template to organize your own plan with your manager.
| Area | First-month question | Evidence or action to pursue |
|---|---|---|
| Authority | Which decisions belong to this role? | Agreed escalation and approval boundaries |
| Staff support | What prevents people from completing required work? | Specific observations across shifts |
| Training | Where are learning needs or authorization unclear? | Review with the educator |
| Handoffs | Which concerns lose ownership between teams? | A mapped example and responsible roles |
| Quality | Which recurring issue can be defined consistently? | A small baseline and review plan |
| Resources | What request needs evidence for leadership? | Clear problem, options, and decision needed |
Review the plan regularly. Remove tasks that no longer address the priority and avoid adding every new suggestion to an already full list.
Handle pressure with facts and a next action
A supervisor may receive a request that the current process cannot safely or realistically satisfy. Respond with the known status, the unresolved requirement, and the available escalation route.
In a hypothetical example, another department requests a set sooner than the team can confirm its readiness. A useful response identifies its current stage, the information still needed, and when an updated estimate will be available. Any clinical scheduling or substitution decision belongs to the authorized team.
Avoid promising a completion time solely to end an uncomfortable conversation. A promise that later changes without explanation damages the relationship and adds more calls to the department.
Clear communication gives colleagues something they can use in their own planning.
Coach the decision, then examine the system
When a staff member makes an error, first follow the facility's process for addressing any immediate concern. Then examine both the person's understanding and the conditions surrounding the task.
Ask what information was available, what instruction applied, what the person understood, and what competing demands existed. The answers help distinguish a learning need from a process obstacle, or reveal both.
Give feedback on observable actions. Explain the expected decision and provide the support needed to practice it. Follow the organization's accountability policies rather than inventing your own disciplinary rules.
Consistent coaching does not mean every situation gets the same response. It means your reasoning is clear and grounded in the facts.
Build relationships before you need an urgent favor
Identify the partners whose decisions affect SPD: perioperative leadership, infection prevention, educators, purchasing, equipment services, and others in your organization.
Ask how they prefer to receive issues and what information helps them act. Learn which meetings or planning processes include decisions about equipment, new services, and workload.
Healthcare Purchasing News's discussion of giving SPD a seat at the table includes firsthand perspectives on involving processing expertise in organizational decisions. Use that idea locally by identifying a specific decision where SPD input is missing.
Bring useful evidence to the conversation. A clear description of a processing constraint is easier to address than a general request for more recognition.
Make a resource request understandable
Start with the problem and its operational effect. Describe what the team has observed, what has already been tried, and what decision you need from leadership.
Present realistic options, including the limitations of each. If the evidence is incomplete, say what you still need to learn. Do not attach a dramatic patient-outcome claim to a small operational observation.
For a training request, explain which responsibilities need support and how the department will evaluate the training. For an equipment request, involve the people responsible for compatibility, maintenance, and implementation.
A well-prepared request helps leadership evaluate the tradeoff. It also shows staff that their concerns are being translated into a decision the organization can make.
Avoid three common first-supervisor traps
Changing too many things at once. When several processes change together, staff may struggle to learn them and you may not know which change helped. Keep an improvement focused unless an urgent situation requires a broader response.
Becoming the only person who can solve a problem. Answering every question personally may feel useful, but it can leave the team dependent on your presence. Clarify roles, references, and escalation routes.
Treating every delay as a motivation problem. Investigate the work before assigning a cause. Missing supplies, unclear instructions, and unavailable decisions need different solutions from an individual performance concern.
These traps are avoidable when you keep the question concrete: what is preventing the required work, and who can change that condition?
Review your own progress with your manager
At the end of the period, prepare a short summary of what you learned and completed. Include the routines established, issues resolved, open risks, and decisions still needed.
Use evidence appropriate to the claim. If you improved document access at one workstation, say that. Do not label the entire department transformed.
Ask your manager for feedback on prioritization, communication, and use of authority. Identify one leadership skill to develop next and a practical opportunity to practice it.
The technician-to-leader career guide offers a broader view of advancement. Your first months in a supervisory role are where those ambitions become daily habits.
Protect time for the work only you can do
Keep a short record of what repeatedly pulls you away from planned leadership work. Some interruptions belong with you; others may reveal an unclear assignment or missing reference.
Review that pattern with your manager. Decide which responsibilities can be delegated within existing roles and which require protected time, such as staff reviews or follow-up on a quality concern. Delegation needs a clear owner and appropriate support, not simply a transfer of unfinished work.
Leave room for unplanned needs. A schedule with every minute assigned can make an ordinary disruption feel like a failure. Your aim is dependable follow-through on the most important responsibilities, with enough flexibility to respond when conditions change.
Frequently asked questions
Should a new supervisor wait 30 days before making changes?
No. Immediate concerns follow the facility's escalation process. The timeline helps organize planned improvement; it does not delay required action.
How many projects should I begin?
Start with a scope you can complete while meeting daily responsibilities. A finished improvement with clear evidence is more useful than several projects without owners or review dates.
Do I need to have every technical answer?
You need to recognize the question, locate the appropriate source, and involve qualified people. Guessing beyond your expertise is not a leadership requirement.
Choose the next conversation
If you are entering supervision, meet with your manager to clarify your authority and first priority. If you already supervise, choose one recurring obstacle and ask staff to show you how it affects the work.
For organizations exploring educational or operational support, contact ATS about consulting. Describe the specific challenge so the conversation can begin with the work your team needs to improve.
