Where to Start With Veterinary Hospital Culture: Five Practical Steps
I have stepped into hospital leadership four times: once as a build from scratch and three times with established teams. My starting priorities were nearly the same each time.
To start improving veterinary hospital culture, whether you are new to the role or inheriting a culture that is not working, begin with five systems: safety reporting, first 1:1s, team-defined non-negotiables, specific recognition, and clear ownership of the problems that keep reaching you. Hospital culture shows up in small decisions on a hard shift: whether a near miss gets reported, whether a handover includes everything, how colleagues speak to each other after a bad case, and who decides when something unexpected comes up. Those decisions follow what the team has learned about how leadership responds when someone speaks up, when a standard is missed, and when someone does the right thing.
1. Start a patient safety committee that works on systems, not blame
Begin with a short form that any employee can submit at any time, anonymously, to report a safety concern, an error, or a near miss. Keep it short. A long form is more likely to be used only for events that already felt too big to ignore. Make near misses easy to report, too. They can reveal a process gap before a patient is harmed.
Then build a committee from different roles in the hospital: a doctor, a nurse or technician, someone from animal care, someone from reception. Choose people who are willing to work through a problem and help find the fix. Review what has come in at least monthly, and put the same three questions to every report: What made this possible? What needs to change in the system or process? Who owns the follow-through?
Tell the team what changed and what prompted it, without including details that would identify who wrote the report. People are more likely to keep reporting when they have seen a report lead to something. Urgent safety concerns do not wait for the committee. They are escalated immediately, through whatever route your hospital uses, and the committee reviews them afterward.
If few reports come in, check whether people trust the process, can find and use the form, and understand what counts as a report. Low reporting does not establish the cause. Amy Edmondson's 1996 study of eight hospital nursing units Journal of Applied Behavioral Science supports separating detected errors from underlying error frequency: units with stronger leadership and better working relationships had higher detected medication error rates, and she argued that a detected rate reflects both how many errors occur and how many get reported. In an observational study of two UK veterinary practices, Kinnison, May and Guile wrote that where a culture of blaming a single individual persists, "it is perhaps unsurprising that some errors fail to be reported" Veterinary Record, 2015. For the wider case, see why psychological safety is built by pattern, not invitation.
2. Book the first 1:1 with every direct report
Do this before there is a problem to raise. Ask each person four things: what is working, what is making their role harder, where they want to grow, and "Is there anything I should be focusing on that I'm not?" The first two can show you where friction sits before it becomes an incident. The third gives you something to build together that is not a performance concern, and a mentorship system is one structure for acting on it. The fourth asks for feedback on you. It invites them to point out something you may have missed. How you respond matters, especially when the feedback is uncomfortable.
Put quarterly follow-ups on the calendar before each first conversation ends. Quarterly is my starting cadence, with more frequent check-ins when needed. A follow-up that is not booked while both people are in the room tends to lose to whatever the next shift brings. Bring what you heard to the next conversation, along with what you did about it. It is the same loop as the safety committee, at the scale of one person.
Treat these meetings as proactive problem solving. Ask what is getting in their way. Agree on what they can address, what needs your support, and what requires a wider system change. They are not where frustration or difficult feedback waits its turn. Anything that needs saying is said when it happens, because feedback saved for the next meeting reaches the person late and can turn the meeting into something people brace for. How to have those conversations without carrying them home covers the how.
3. Define the hospital's non-negotiables together
Ask for contributions from every role and every shift, and let the team shape the working agreements that matter most to its culture. Examples include how we speak to each other, what gets cleaned every shift, and what a complete handover includes. Required clinical and safety standards, such as those set by regulation or hospital policy, sit outside this exercise. The team's input there is on how to meet them.
Then ask the question that turns a list into an agreement: How do we want to be held accountable when we miss these? Settle how reminders, direct feedback, and follow-up will work, and include what happens when leadership misses the standard. If leadership is exempt, the team is likely to notice, and the agreement starts to look like a list of obligations for the team alone.
Once the agreement exists, your job is to apply it consistently. When a standard is missed, return to it without making it personal: "This is what we said we would do. What needs to happen now?" The question puts the agreement in the room instead of your opinion, and it can be asked the same way whether the person who missed it is the newest hire or the longest-serving doctor. For the wider argument, see accountability that doesn't feel like cruelty.
I recommend repeating the process every six to nine months. Teams change, and new people should have a hand in writing what they are held to.
In a 2026 cross-sectional study of 367 veterinary professionals in Australia and the UK Oginska and colleagues, Veterinary Record, psychological safety was associated with lower intention to leave. Supervisor feedback partly mediated that relationship, meaning it accounted for part of the link. Co-worker feedback did not mediate it. The data is cross-sectional, so it shows association, not cause, but it is a reasonable prompt to agree in advance how direct feedback will be given and by whom.
4. Recognize the behaviors you want repeated
Notice when someone raises a concern early, gives a clear handover, or helps a colleague through a difficult shift, and say so in specific terms: "You flagged that discrepancy before treatment started. Thank you for speaking up." That sentence names the behavior and the moment, which makes it easier for the person, and anyone who hears about it, to repeat it. "Great job today" expresses appreciation, but doesn't tell them which behavior made the difference.
Make sure recognition reaches every role and every shift, including the people whose work you do not regularly see. Reception, animal care, and the shifts you rarely work are easy to miss because you are not there to see the work. Ask the people who are.
A team learns part of what the hospital values from what leadership notices, and a concern raised early that is met with thanks makes the next concern more likely. Gallup reports that employees who do not feel adequately recognized are twice as likely to say they will quit in the next year, and that the most effective recognition is "honest, authentic and individualized". That data comes from the general workforce, not veterinary teams.
5. Track the problems that keep coming to you, and clarify who owns them
Culture includes who is expected to decide, and what reaches your desk by default teaches the team the answer. If a type of problem is always settled there, the people who could own it can come to wait for you, and the people who do step in can end up carrying more than their role. Tracking it shows you where the hospital has not yet said who owns what.
When the same type of problem reaches you more than twice and belongs with another role, write it down: the date, the problem, and who brought it. A few weeks of entries show what your hospital routes through you by default. The same rule runs through a medical director's first year.
When a problem keeps coming to you, start by checking ownership, authority, and support. Who should own this? Do they know that? Do they have the authority and support to handle it? Then settle what that person can decide on their own, when they need to escalate, and who the backup is. Each gap needs a different fix, and answering faster is not one of them. If shift swap requests keep reaching you, find out who owns the schedule and whether they know it.
Agree on what belongs in an email, what warrants a text, and what requires a call. For example, you might agree that urgent safety concerns require a call, while routine shift swap requests go to the scheduling owner by email. Without that agreement, problems tend to reach you by the fastest route, whatever their weight.
This step also protects the leaders involved, you included. A leader who is the default route for every decision rarely gets uninterrupted time to think, and the interruptions can follow them off shift. Over time that load can contribute to burnout, and the same applies to any other leader whose desk has become the catch-all. Moving a decision to the person who should own it, with the authority and support to make it, frees capacity for the work only leadership can do.
Role clarity covers decision authority, and what happens when work follows willingness instead of role shows what it costs the people who absorb the gap.
Teams tend to repeat what leadership responds to. If a near miss draws blame, reports dry up. If a missed standard draws nothing, the standard fades. If a recurring problem always lands on the same desk, the hospital's process for that problem becomes one person. Whether you are a month into the role or five years in, start with the step your hospital is missing.
Find out where to start in your hospital
The free PIVOT Stability Audit examines role clarity, accountability, operational reliability, team culture stability, and leadership structure. Twenty-five questions, about ten minutes, and a scored report with your strongest domain, your highest-risk area, and three priorities. → Take the Stability Audit.
Common questions
How often should a veterinary hospital leader hold 1:1s with direct reports?
Hold the first one early with every direct report, covering what is working, what is making the role harder, where they want to grow, and whether there is anything you should be focusing on that you are not. Quarterly follow-ups are a reasonable starting cadence, with more frequent check-ins when needed. Frustration and difficult feedback are raised when they happen, not saved for the meeting.
What should a hospital do if few safety reports come in?
Check whether people trust the process, can find and use the form, and understand what counts as a report. Low reporting does not establish the cause, because a count of reported errors reflects both how many errors occur and how many get reported.
Which standards can a veterinary team set for itself?
The team can shape working agreements such as how colleagues speak to each other, what gets cleaned every shift, and what a complete handover includes, with input from every role and shift. Required clinical and safety standards, such as those set by regulation or hospital policy, are not up for a vote, and the team's input there is on how to meet them. A review of the agreement every six to nine months is recommended.
