I was parked near the reception desk one morning, doing the thing you do when a new CSR is still finding her feet, half-watching, half-listening, ready to step in if a call went sideways. She was good, sharp and warm and eager to get it right. But somewhere around the third or fourth interaction, I started hearing a word on repeat.
No.
Could we get in today? No. Can the doctor refill that a few days early? No. Can I talk to the doctor the minute she is free? No.
Nothing she said was wrong, exactly, and every no had a reason behind it if you went looking. What bothered me was the speed. There was no pause, no “let me check,” no flicker of maybe. The answer arrived before the question fully landed, and I stood there long enough to get curious about where she had learned to do that, because nobody trains a new hire to say no on instinct.
So I thought back, and it did not take long to find the source.
It was me.
The thing about a reflex no is that it does not wait for the whole sentence. Think about your kid asking if he can ride his bike after dark. You hear “bike” and “after dark” and you are already shaking your head before he gets to the part where he is riding with his two best friends, and their parents are coming, and they are putting lights on the bikes and wearing the reflective vests from the garage. That is a different question, and it might even be a yes, but you never heard it, because the no fired before he got there.
I had become that parent at work, except it was not my kid, it was my whole team. Somewhere along the way I had built a hospital where no was the house default, and I had done it one refusal at a time without ever deciding to.
So I started wondering whether this was just me, or whether I was working against something older than my own bad habits.
We like to tell ourselves that people are built to please, and socially, we are. We want to be liked and we want to be helpful, and most of us will sit through a meeting we never wanted to attend rather than face the small discomfort of declining. Yes is the polite instinct, the one that keeps the peace, and sometimes no is genuinely the right call, because a boundary held on purpose is one of the most useful words a leader owns. But underneath the polite instinct sits an older one, and it is not nearly as agreeable.
The brain is wired with what researchers call a negativity bias, where bad news, threats, and risks get processed faster and weighted more heavily than good news of equal size. It shows up in infants by about six months old, which is why scientists call it hardwired rather than taught. No is the safe answer, because no protects, no commits you to nothing, and no cannot blow up in your face the way an unearned yes can. Every time I defaulted to no, some ancient part of my brain was congratulating me for dodging a threat that, in reality, was a client asking for a Saturday slot.
The polite instinct says yes and the protective instinct says no, and in a busy hospital on a busy day, the protective one wins almost every time. It is faster, it feels responsible, and it had become the personality of my practice.
To be fair to the no, the business case for it is real. A team that says yes to everything drowns, so no saves time. No saves the research a busy person does not have the hours to commit to. It keeps you from making promises you cannot keep, and a broken promise costs more trust than a clean refusal ever does. It guards against burnout, because every yes is a withdrawal from someone’s energy and the accounts are not bottomless. Business writers will tell you the ability to say no is a discipline, a sign of a leader who knows what the practice stands for, and they are not wrong.
I believe in boundaries. I believe there are protocols you do not bend, medications you do not dispense early no matter how nicely you are asked, and clients whose “just this once” is neither just nor once. Some hills are worth dying on, and the standard of care is one of them. But a boundary is a system you build on purpose, not a reflex you fire on instinct, and the two are easy to confuse.
So I am not here to tell you to turn your hospital into a place where the answer is always yes, because that is its own kind of mess. But here is the part the business case leaves out.
When no is the house default, your team stops bringing you things. I do not mean they get lazy, I mean you have handed them an out, and it is a generous one. Why check the schedule for a Saturday opening if the answer is already no? Why ask the doctor about an early refill if you know what she will say? Why sit on the phone and problem-solve a worried owner when “no, sorry” closes the call in four seconds and nobody can fault you for following the rule?
I had taught my staff that the safe answer was the right answer, and they learned it well. The trouble is that every reflex no is a conversation that ends before it starts. The client who might have been saved by a creative appointment never gets the chance, the new protocol nobody bothers to look into never gets tried, and the judgment that a “let me find out” would have built, one small problem at a time, never gets the reps. But the real cost is quieter than any of that. It is the employee who had a better way and learned to keep it to themselves. That is the one the efficiency argument never logs, because no is cheap today and expensive later. You save four seconds on the phone and lose the muscle that makes a team good.
Nobody walks into work deciding to build a culture of no. You just say it a few hundred times, and one day you look up and it is who you are.
There is a difference between a boundary and a trench, and I had stopped telling them apart. A boundary is a decision you defend because crossing it would hurt someone, the patient, the business, the morale of a team that is watching you hold it. A blanket no is different. It is just a reflex wearing a boundary’s clothes, and it usually announces itself with five words: that is how we do it here.
I heard those words constantly during my relief years. One hospital gave an antibiotic injection before every single surgery, and when I asked about the reasoning, I did not get reasoning, I got “that is how we do it here.” I had questions about the medicine behind it, and I had more questions watching a fully awake dog take that injection, because that shot stings, and more than once I saw a tech jump back from a snap. The dog was not being bad. The dog was being honest. Once I was the one in charge, I still gave the injection, but I waited until the pet was groggy from a premed with pain control on board. Same protocol, same drug, far less pain for the patient and far less risk to the person holding it. It had simply always been done the other way, and “always” is not a clinical rationale.
That is the thing about our field, where there are so many roads to the same right answer, so many drugs and sequences and workflows that all land the patient in the same healthy place. When “that is how we do it here” becomes the answer to every why, you are not protecting the standard, you are protecting the habit, and you are teaching everyone within earshot that curiosity is a waste of breath.
Realizing I was the source was the easy part, and fixing it was not, because I had not just picked up a bad habit, I had taught one. Every reflexive no I had ever handed down, my team had absorbed and handed forward, all the way to a new CSR who had never once been told to say no and said it anyway. If I wanted a different answer coming out of my hospital, I had to go put a different one in. So I started saying yes on purpose, out loud, over and over, until it stuck, retraining a whole team one interaction at a time. We teach our teams how to answer, the same way we teach our clients how to treat us, and I had taught mine to refuse. Now I had to teach them to ask first.
In practice it was small. When a manager or a new doctor wanted to try something a different way, “that is not how we do it” became “sure, show me what that looks like.” When a client asked about a protocol they had read about somewhere, “no” became “send me the research and I will read it too.” Half the time the idea did not pan out, and that was fine, because the point was never that every yes is right. The point was that the question got heard before the answer got given.
Here is what that looks like when it works, even when it does not work. A new-graduate associate came to me wanting to try a method she had learned in school. I looked into it myself first. There was not much out there, but it seemed possible, so I let her run with it. It did not pan out. The plan had a gap she had not caught, and we sorted it out before it ever reached the patient.
And it was still one of the best yeses I ever gave.
She learned she needed to research more carefully before she committed, and I learned she trusted me enough to bring me an idea in the first place. She walked away feeling heard instead of shut down. A no would have cost me all of that, and I would never have known what I was missing, because the thing you lose to a reflex no is the thing that never happens.
That is where empowerment actually starts, with a yes to the question. I wrote more about what it costs you when good people stop offering, and how to build a team that keeps bringing you the better way.
So the next time the no rises up fast and easy, stop and price it out. What does yes actually cost here, and what does no cost, in trust, in momentum, in the small daily proof that someone heard you? If the no has a real reason behind it, hold the line. But if the only thing behind it is that no is easier, that is not a reason. That is just the old wiring, doing what it has always done.
— Dr. V
The Gray Oak Journal
Dr. V is a veterinarian with over twenty years of clinical and operational leadership experience. She has owned and operated several veterinary hospitals, weathered many shifts in the industry, and served on advisory councils. She writes The Gray Oak Journal at grayoakjournal.com.