The idea I used to hold onto
Early on, I believed that a good outcome was the whole story. A patient left the clinic feeling better, a procedure went smoothly, a lab value improved. I counted those as wins and moved to the next patient. It took years of practice before I started questioning that habit.
What made me reconsider
The turning point came from watching the same good outcome happen for different reasons. Sometimes it came from a method that was sound and repeatable. Other times it came from luck, or from a patient’s own body compensating for something I had not actually fixed. Both looked identical on the day of discharge. Only one of them would still look good a year later.
That gap bothered me. If I could not tell the difference between a result I earned and a result I got lucky with, I was not really practicing medicine. I was gambling with better odds than most.
The shift in how I think about it
I stopped asking “did this work” as my main question. I started asking “why did this work, and can I explain it well enough to teach it to someone else.” That second question is harder to answer honestly, and it exposes a lot of shortcuts that outcomes alone will hide.
This matters more in nephrology and vascular work than people outside the field might expect. A dialysis access site can function for a while even when the underlying technique is not quite right. A stent can hold for months before a poorly chosen approach catches up with the patient. If I only track the short-term result, I will keep repeating methods that are due to fail later, just not on my watch.
What this looks like in practice
Now, when I evaluate my own work, I look at the mechanism first. I ask what I actually did, step by step, and whether each step was the right one given what I knew at the time. If the mechanism was sound, I trust the result more, even when it takes longer to see. If the mechanism was shaky, I do not let a good outcome talk me out of fixing it.
I do the same thing when I review a new technique or procedure that comes into the field. I do not ask how many people it helped last year. I ask how it works, what it assumes about the body, and whether that assumption holds up under scrutiny. Plenty of things get adopted quickly because early results look promising, then quietly get walked back once the mechanism turns out to be wrong.
Why this changed how I teach
Once I made this shift for myself, it changed how I explain things to younger physicians and to patients. I stop at outcomes less often. I try to walk through the reasoning: this is why we chose this vessel, this is why we timed it this way, this is what we are watching for and why. Patients do not need a lecture, but they respond well to a doctor who can explain the “why” instead of just the “what.”
For physicians I work with, I push them to defend their reasoning before I care much about their results. A resident who can explain a decision clearly, even if the outcome that day was mixed, is building something durable. A resident who gets a good result but cannot explain how they got there is building on sand.
What I would tell someone weighing the same question
If you work in medicine, or in any field where results can mask process, it is worth asking yourself the same question I had to ask. Would your explanation for a good outcome hold up if someone asked you to repeat it exactly, on a harder case, with less room for error? If the answer is yes, you likely have something real. If the answer is uncertain, the good outcome was probably doing you a favor you have not earned yet.
I do not think outcomes are unimportant. They are the only thing that matters to the patient in the room. But if I want to keep getting them right, I have learned to spend most of my attention on the method, not the scoreboard.
