Brad G. Philbrick & Company

What I underlined

Brad Philbrick — Mon, 05 Oct 2026 14:20:08 +0000

The word caught my eye before the book did.

Risking.

Risk has always intrigued me. It still does.

These days, I’m taking a different kind of risk. I’m writing a book. Writing one is hard enough. Publishing it—and urging individuals to read it—requires another level of commitment. There is time, uncertainty, the possibility of rejection, and, in my case, a financial investment approaching $20,000.

And I’m still taking chances.

When I spotted Risking by David Viscott, M.D., among the books on my shelves, I remembered it immediately. I hadn’t opened it in years, maybe decades, and I couldn’t wait to skim it again. When I pulled it from the shelf, I noticed the old Waldenbooks price sticker.

$4.50. My risks are more expensive now.

As I began turning the pages, the price no longer held my interest—it was my highlighting.

I bought the book after leaving Fargo-Moorhead and starting a life of my own. Independence was liberating. It was also a little frightening. I was learning that leaving the familiar and knowing what comes next are two entirely different things.

I was looking for some guidance—and there it was in yellow.

I highlighted passages about knowing yourself, about looking inward before looking outward, about change and fear and accepting responsibility for the choices we make.

I wasn’t only rereading David Viscott. I read the reactions of a younger man who first encountered him.

Then I came to Chapter 8, “Risks of Change.”

There were more markings. Viscott wrote about the consequences of waiting too long to change. I had marked his observation that suffering isn’t necessarily wasted if it brings us to some point of resolution. Another passage reminded the reader that risk includes accepting responsibility for the possibility of loss.

And then I found the asterisks.

Viscott wrote that if we don’t ask questions about things we don’t understand, life will become increasingly difficult. That sentence mattered to me. I made sure I wouldn’t miss it or forget it.

And at the bottom of the page, in my own handwriting, I added:

Mom always told me to shut up.

I pondered that for a while. Judging the sentence or opening again an old grievance didn’t interest me. It was the young man who wrote it. He had no idea where his life headed.

He didn’t know that he would spend much of his career as a pharmacist, in a profession where asking questions isn’t a nuisance. Sometimes it is essential. A question can uncover a misunderstanding, prevent an error, or help someone use a medication safely.

He certainly didn’t know that decades later he would be writing a book encouraging patients and caregivers to ask questions when they don’t understand something about their healthcare.

And he couldn’t possibly know that I had published an essay called “Any Questions?” only days before pulling Risking from the shelf. But I smiled at that one.

Maybe the risks change as we do.

When I was younger, risk meant leaving familiar surroundings and learning to make my own decisions. Today it can mean submitting an essay, standing in front of an audience, walking into a room where I know almost no one, or investing years of work—and a considerable amount of money—in a book I believe should exist. None of those things comes with a guarantee.

Perhaps that’s why another sentence I highlighted years ago was still familiar. Among Viscott’s dos and don’ts of risking was a simple admonition:

Don’t pretend you’re sure when you’re frightened.

I like that better now than I probably did then. Certainty isn’t a prerequisite for moving forward.

Eventually I stopped reading Risking and started looking at the book itself. The pages were older. The highlighting had aged. The handwriting was definitely mine, although it belonged to a version of me I hadn’t visited in a long time.

And I realized that some old books become accidental journals. We underline what matters to us. We put stars beside sentences. We fold corners. We scribble a thought in a margin or at the bottom of a page. We think we’re marking the author’s words so we can find them again. Maybe we’re leaving something else behind.

Clues.

Not necessarily to what the author thought was important, but to what we needed when we were reading.

David Viscott’s words haven’t changed since I paid $4.50 for them. The reader has.

Maybe somewhere on your shelves is a book you haven’t opened in thirty or forty years. Pull it down sometime.

Perhaps the interesting question isn’t what the author wrote.

It’s what you underlined.

Any Questions?

Brad Philbrick — Tue, 29 Sep 2026 09:40:01 +0000

I used to tell my pharmacy technicians not to ask patients if they had any questions.

That sounds like strange advice coming from a pharmacist.

Of course I wanted patients to ask questions. I spent much of my career answering them. But there was something about that familiar question—Do you have any questions for the pharmacist?—that bothered me.

It was too easy to answer.

“No.”

So I taught my technicians to ask something specific instead.

If someone was picking up a new prescription for ciprofloxacin, for example, we might make sure the patient understood how to separate it from certain foods, supplements, or products that could interfere with its absorption. With levothyroxine, we might ask whether the patient understood when and how to take it in relation to food. With an NSAID, we might talk about taking it with food when appropriate to reduce stomach upset.

The point wasn’t to quiz anyone.

It was to find out whether the important part of the message had actually arrived.

An assumption is hidden inside the question, “Do you have any questions?”

It assumes we know what we don’t know.

Think about that for a moment.

You are handed a bottle containing a medication you may never have heard of. The label contains a name you may not be able to pronounce. Perhaps your doctor explained it, but that was twenty minutes ago, along with your diagnosis, your lab results, and three other things you were trying to remember.

Then someone asks:

“Any questions?”

What are you supposed to ask?

The person on the other side of the pharmacy counter knows things you don’t. That’s why you’re there. But somehow we’ve placed the responsibility on you to identify the missing piece of information.

Over the years, I learned that silence was a poor measure of understanding.

People nod for all kinds of reasons. Sometimes they understand. Sometimes they’re embarrassed. Sometimes they’re in a hurry. Sometimes three people are waiting behind them, and they don’t want to hold up the line.

And sometimes they say they have no questions because they genuinely don’t know there is a question they should be asking.

That isn’t unique to healthcare.

A teacher finishes explaining an assignment and asks the class, “Everybody understand?”

Heads nod.

A manager explains a new procedure and asks, “Any questions?”

Silence.

A parent gives instructions to a child who says, “I know.”

Maybe they do.

But we’ve all experienced what happens next.

Information has been delivered. Understanding has not necessarily followed.

There is a difference.

I learned the same lesson in other settings. As a director of pharmacy, explaining a new hospital protocol wasn’t enough; I needed questions to discover what my staff had heard and what I had failed to make clear. Years later, selling microscopes and laboratory equipment, I found that questions often mattered more than the presentation. Before I could explain what someone needed, I had to understand what they were trying to accomplish.

I spent years dispensing medications, but much of what I was really doing was translating. Medical language into ordinary language. Instructions into actions. What the prescriber intended into what the patient needed to do when they got home.

And translation requires more than speaking clearly.

It requires finding out what the other person heard.

That’s why I preferred the specific question. Not Do you understand? but something closer to Tell me how you’re going to take this when you get home.

The difference is subtle, but important.

One asks for reassurance.

The other invites understanding.

That could be something worth remembering outside the pharmacy, too.

Whenever we know more about something than the person we’re talking to, it’s easy to believe we’ve communicated simply because we’ve explained.

But the responsibility for understanding cannot always belong to the person who knows the least.

Sometimes the most important question isn’t the one someone knows to ask.

It’s the one we care enough to ask them.

The Clues Were There All Along

Brad Philbrick — Wed, 23 Sep 2026 11:38:20 +0000

I was reading Agatha Christie’s “The Disappearance of Mr. Davenheim” when Hercule Poirot stopped me. Not literally, of course. But I reached a passage and stopped reading.

“It is the brain, the little grey cells… on which one must rely. The senses mislead. One must seek the truth within—not without.”

I read it again. The little grey cells. I closed—or perhaps lowered—the book and sat with that phrase for a moment.

Poirot was talking about solving a mystery.

I was thinking about hippocampal brain slices.

Years ago, during my biomedical sales days, I spent a great deal of time in research laboratories. They were fascinating places. Patch clamps. Oscilloscopes. Ion channels. Living cells revealing tiny electrical events most of us would never imagine were happening.

I wasn’t the scientist conducting those experiments. I was a pharmacist who had wandered into their world through biomedical sales, and I was endlessly curious about what they were doing. One day, that curiosity gave me a glimpse of something I already knew. Or thought I knew.

I was visiting a researcher who was studying cardiomyocytes—living heart muscle cells. His work involved measuring the electrical activity that allows those cells to do what heart cells have been doing faithfully since before any of us took our first breath. He knew I was a pharmacist.

“Brad, do you want to see diltiazem work?”

Of course I did.

Diltiazem is a calcium-channel blocker, a medication used for conditions such as high blood pressure and certain heart rhythm problems. I knew its pharmacology. I knew what blocking calcium channels did to cardiac cells. I had learned it in school, talked about it with physicians, and explained it to patients.

The researcher added diltiazem to the cardiomyocytes, and I watched the oscilloscope. The electrical activity changed.

There it was. Not a diagram in a pharmacology textbook. Not an explanation of a mechanism of action. Not something I had memorized for an examination years before. I was watching a drug affect a living heart cell.

I knew what diltiazem did. But now I had seen it. There is a difference.

I think that is why Poirot’s little grey cells stopped me all these years later. We spend much of our lives collecting information. We read books. We attend classes. We listen to experts. We learn our professions. Eventually, some things become so familiar that we stop wondering about them.

But every so often, something interrupts us. A researcher asks a question. An oscilloscope flickers. A sentence in an old mystery story makes us put the book down. And suddenly something we thought we understood asks to be looked at again.

Perhaps that is what observation really is. Not merely seeing what is in front of us, but being curious enough to stop when something catches our attention—and then wondering why.

Poirot solved mysteries that way. Scientists make discoveries that way. Writers sometimes find essays that way.

The clues were there all along.

Pills to Prose

Brad Philbrick — Mon, 14 Sep 2026 16:35:45 +0000

Of all the prescriptions I filled during my years as a pharmacist, some of the most satisfying were for teenagers with acne.

They often came to the counter with a parent, prescription in hand, already carrying more embarrassment than any teenager needs. In the 1970s, Retin-A was a commonly prescribed treatment for acne. But these young patients needed to know something important: when they first started using it, their skin could become more irritated and their acne might look worse before improvement became noticeable.

Imagine being a teenager, already self-conscious about your face, faithfully using the medicine your doctor prescribed—and then looking in the mirror and thinking it was making things worse.

These poor kids needed to hear what might happen.

So I explained it. I told them what to expect, why patience mattered, and why they shouldn’t assume the medicine wasn’t working right away. I could often see some of the worry leave their faces. Mom or Dad seemed relieved too.

I was dispensing Retin-A, but what stayed with me wasn’t the acne cream.

It was the explanation.

I didn’t know then how much of my working life could fit into those few minutes across a pharmacy counter.

Years later, I left pharmacy for biomedical sales. I knew I was entering a completely different career. I had watched pharmaceutical representatives call on me, and during my interviews, the hiring manager told me that teaching would be an important part of the job.

That appealed to me.

I would need to understand complicated medical information well enough to explain it to someone else. The setting changed. The audience changed. The job title certainly changed.

But something came with me.

I was still teaching, still explaining, and still translating.

More changes followed over the years. I wrote grant proposals. I did copywriting and medical and health writing. Eventually, I began submitting personal essays for publication.

By any reasonable definition, I was writing.

But I didn’t call myself a writer.

That word required something I hadn’t yet earned. Writers had publications. Recognition. Accomplishments. I wrote, certainly, but saying I am a writer felt different.

Then an email arrived from Writer’s Digest.

My essay, “Breakfast with a Ghost,” had received an Honorable Mention in its annual writing competition.

I remember what that recognition meant to me, but not because an award suddenly transformed me into something I hadn’t been the day before.

It allowed me to recognize something that had been there all along.

I am a writer.

Looking backward, careers can seem far more orderly than they felt while we were living them. We draw neat lines between jobs and give each period a title. Pharmacist. Biomedical sales representative. Grant writer. Medical writer. Essayist.

But lives aren’t lived as résumé entries.

The more I look at mine, the less interested I am in the titles and the more interested I am in what happened underneath them.

What was the work beneath the work?

For me, much of it was remarkably consistent. I liked taking something complicated, understanding it, and helping someone else understand it too.

Sometimes that meant explaining a medication to a worried teenager. Sometimes it meant discussing medical information with a healthcare professional. Sometimes it meant finding the right words for a grant proposal. Today, it may mean sitting at my desk with an essay taking shape on the screen.

Different work.

And yet, perhaps not as different as I once thought.

Over the past several days, I’ve spent some time scrolling through LinkedIn. I’ve noticed how many people are looking for jobs, contemplating career changes, announcing transitions, or wondering what comes next.

We use words such as pivot, reinvent, and start over.

Those words can make change sound like we must abandon one version of ourselves and build another from scratch.

I’m not sure that’s always true.

We may not reinvent ourselves as often as we finally recognize ourselves.

A teacher who leaves the classroom doesn’t stop knowing how to teach. A nurse who becomes a writer doesn’t stop knowing how to listen. An executive moving into nonprofit work doesn’t leave behind the ability to bring people together. The setting may change. The title may disappear. But some part of the work travels with us.

So, when we’re wondering what comes next, there’s another question worth asking.

Instead of only asking, What should I become?

Maybe we should also ask:

What have I been doing all along?

What is the work beneath your work?

I once stood behind a pharmacy counter helping a teenager understand what might happen next.

Today I sit at a desk trying to help readers understand what happens next.

The tools have changed.

The work hasn’t.

I thought the journey was from pills to prose.

It could be a matter of recognizing what I’d been doing all along.

What Counts

Brad Philbrick — Tue, 08 Sep 2026 14:18:29 +0000

I love productive days.

My life has a purpose, and I am determined to live it out. I
like finishing a chapter of my book, submitting an essay to a literary journal,
or completing a grant proposal for a foundation. At the end of a day like that,
I can look back and say, “Boy, I had a good day today.”

Not everything on a to-do list qualifies. Picking up
groceries is necessary. Cleaning out my email inbox feels good. Answering
messages keeps life moving. But I don’t confuse activity with accomplishment.

One Friday afternoon, I had two things on my calendar that I
wanted to attend.

At one o’clock, Stephanie Chandler was presenting a webinar
about building an email subscriber list. Stephanie always spends some time
chatting with everyone before getting into the material. I enjoy that. It’s an
opportunity for a little networking and camaraderie with other writers.

At three, I had a Google Meet with Circle City Scribes, an
informal group of Indiana grant writers. We talk. We share experiences. We help
one another solve problems. I’m gradually moving away from grant writing, but I
still enjoy the people.

I missed both.

Jane had an appointment with her cardiologist.

I was irritated and disappointed when I realized my
afternoon plans were gone. Stephanie records her webinars, so I knew I could
watch that later. Circle City Scribes would meet again. Still, I wanted to be
there.

Then I reminded myself where I needed to be.

With Jane.

The cardiologist sat at the little desk in the examination
room, her monitor and keyboard in front of her. Jane sat next to the desk. I
sat to Jane’s right.

Once the appointment began, the webinar and Google Meet
completely left my mind.

I listened.

I also watched Jane.

After years in healthcare, I know how easily a conversation
that makes perfect sense to a healthcare professional can become confusing to a
patient. I could tell there were moments when Jane wasn’t completely following
what the cardiologist was explaining.

The retired pharmacist in me was interested, too.

At one point, I questioned the cardiologist about two
medications. I understood what each one did, but I wanted to understand why
Jane was taking both. The doctor explained her reasoning. Once she did, it made
sense.

She was stellar.

When she wanted to explain what was happening with Jane’s
heart, she didn’t rely only on medical terminology. She pulled out a model of
the heart and showed us. She explained what she knew, what concerned her, and
what she wanted to learn from further testing.

I found the entire conversation fascinating.

But I wasn’t there primarily as a pharmacist.

I was there as Jane’s husband.

And I was glad I was there.

Jane doesn’t like to cause alarm or draw attention to
herself. It’s one of the things I know about her after all these years
together. Sometimes that means I may not hear the complete weight of something
when she tells me about it later.

This time, I was sitting beside her.

She heard the doctor.

So did I.

When we left the clinic, we didn’t go home.

We went to the butcher shop.

Don’s Butcher Shop wasn’t far away, and we needed beef for
the shish kabobs we were grilling the next day. Our son Drew, his wife, and our
two grandchildren were coming over.

There was something wonderfully ordinary about walking out
of a cardiologist’s office after a serious conversation and going shopping for
beef.

I always enjoy stopping at the butcher shop. The people
there are friendly and knowledgeable, and buying meat becomes a conversation
rather than a transaction.

On the drive home, Jane and I talked about the appointment.
We both thought the cardiologist had done an excellent job. We talked about
what we’d learned and what would happen next.

Then Jane was ready to let the information rest.

I understood.

There was nothing more for us to solve that afternoon.
Another test would provide more information. We knew what we knew.

Besides, the family was coming tomorrow.

By the time we got home, Jane and I had shifted into what I
call Entertainment Gear.

What did we need to get ready? What could we do that
afternoon? What could wait until morning? There were shish kabobs to make and a
family gathering to look forward to.

I had missed everything on my Friday afternoon calendar.

And it had been a great afternoon.

I’ve been thinking about that.

I don’t want to redefine what happened by calling it
productive. Sitting beside my wife at a doctor’s appointment wasn’t productive.
Supporting someone I love isn’t productive. Spending time with a friend isn’t
productive. Love isn’t productive.

Nor does it need to be.

I still love productive days. There are books I want to
write, essays I want to submit, and work I want to finish. Accomplishment gives
me satisfaction. Purpose gives direction to my life.

But productivity is only one way to measure a day.

Some days I can point to what I accomplished. Other days,
what matters is where I was, who was sitting beside me.

Nothing on my Friday afternoon calendar happened as planned.

What mattered wasn’t on the calendar.

When to Shut Up

Brad Philbrick — Tue, 01 Sep 2026 19:27:48 +0000

Early in my sales career, I traveled frequently with Harold Anderson, my sales mentor. Harold had been around long enough to know something I was still learning: knowing your product was important, but knowing when to stop talking could be even more important.

One of those lessons came during a sales call at a hospital in southern Indiana. A pathologist was considering a clinical microscope equipped with high-quality objectives, a camera system, and polarizing-light accessories that could be used, among other things, to examine the crystals associated with gout. It was an impressive system, and I was eager to demonstrate everything it could do.

The pathologist was friendly, knowledgeable, and, as it turned out, already mostly sold. He had my quotation. He had studied the brochures—this was long before a customer could pull up specifications, reviews, and demonstration videos online. What he wanted now was to see the microscope for himself.

So I presented.

As I worked through the demonstration, he occasionally stopped me. He would point out a feature he particularly liked or explain why something about the microscope would be useful in his work. I was smart enough to let him finish. Then, with all the enthusiasm of a young salesman determined to make his case, I jumped right back into my presentation.

He would tell me another reason he liked the microscope.

I would listen.

Then I would start selling again.

The pathologist was practically telling me why he wanted to buy my product, and I kept explaining why he should.

Harold sat nearby, sometimes grinning, sometimes looking increasingly perturbed. I noticed neither expression. I was too busy giving what I thought was a very good demonstration.

When it ended, I packed up the microscope and its accessories, and Harold and I headed down the hospital corridor. I was exhilarated. The sale seemed like a done deal, and I wanted to talk about it. Harold tried two or three times to cut me off, but apparently I had not yet exhausted my supply of words.

Finally, he looked at me.

“Walls have ears.”

I didn’t fully understand what he meant until later, when we were safely away from the hospital and having lunch.

Harold had a way of teaching that could be almost parable-like. Rather than simply telling me what I had done wrong, he asked a question.

“When a customer is telling you the features and benefits of your product, or why he likes it while you’re giving your demonstration, Brad, do you know what to do?”

I must have given him a rather dumb look. I had no idea where he was headed.

Harold waited.

Finally, I said, “I don’t know.”

He smiled.

“Shut up!”

I have remembered those three words for more than forty years.

Harold wasn’t merely teaching me a sales technique. When customers tell you why they like your product, they are giving you information no brochure can provide. They’re telling you what matters to them. They’re also teaching you what may matter to the next person you meet. My job at that moment wasn’t to demonstrate how much I knew. It was to listen closely enough to learn something.

Harold eventually returned to our conversation in the hospital corridor. Talking business within a customer’s workplace, he explained, could damage a reputation or a relationship. You never knew who might be standing around the corner, walking behind you, or sitting behind a partially open door.

“Remember,” he told me again, “walls have ears.”

It took me years to appreciate that Harold had taught me two different lessons about silence that day.

There are times to stop talking because someone else is telling us something worth hearing. And there are times to stop talking because what we have to say doesn’t need to be said there—or perhaps doesn’t need to be said at all.

Harold understood something else that I didn’t recognize at the time. He practiced the very lesson he was teaching me. He could have corrected me in front of the pathologist. He could have interrupted my demonstration and shown his young salesman how it was supposed to be done. He didn’t. Even in the corridor, he didn’t deliver the lecture I probably deserved. He waited until lunch, when we were alone.

We aren’t always very good at that kind of restraint. Someone tells us about a problem, and we rush to solve it. Someone shares an experience, and we counter with one of our own. Sometimes we’re so busy preparing our response that we stop hearing what the other person is actually saying.

I’ve spent much of my life communicating—in healthcare, sales, teaching, public speaking, and now writing. Words have served me well. I love them. I’ve built much of my professional life around finding the right ones.

But a mentor sitting across from me at lunch in southern Indiana taught me that knowing the right words isn’t always enough.

Sometimes wisdom lies in knowing when not to use them.

Harold told me to shut up.

I’m still listening.

Knowing and Doing

Brad Philbrick — Tue, 25 Aug 2026 15:31:01 +0000

She was a regular customer, the kind you came to recognize even when she wasn’t coming to the pharmacy. She liked to shop. Candy, cosmetics, stationery, whatever else caught her attention as she wandered the aisles of the chain drugstore.

Once or twice a month, though, she came to see me. She had Type 2 diabetes, and I filled her prescriptions for insulin and the syringes and testing supplies she needed to manage it. She was probably in her late fifties or early sixties. I wasn’t yet thirty.

One day, as she stood at the pharmacy counter, I happened to glance into her shopping cart. There were miniature candy bars, candied orange slices, gumdrops, cookies—the very things I knew she ought to be limiting. I hesitated before saying anything. She wasn’t an especially warm woman, and our conversations could have an edge. Still, I was her pharmacist. I knew diabetes wasn’t managed by insulin alone. Diet mattered. So I gingerly suggested that she might want to be careful about how much candy she was eating.

She snapped back. “Well, I’m taking my insulin, so I’m okay, and you should know that!”

I did know something. I knew the insulin didn’t make the candy harmless. I knew what diabetes could do when it wasn’t well controlled. And standing behind that pharmacy counter, young and confident in what I had been taught, I knew what she should be doing.

What I didn’t know nearly as much about was people.

We had a word for patients like her: noncompliant.

Healthcare professionals used it freely. A patient didn’t take a medication as prescribed, follow the recommended diet, check a blood sugar, stop smoking, lose weight, or return for follow-up care. We explained what needed to be done. The patient didn’t do it. Noncompliant.

Health care providers didn’t intend for the term to be cruel. Most of us genuinely wanted our patients to get better. We had been trained to recognize disease, understand treatment, and explain what could happen when patients didn’t follow recommendations. When someone repeatedly ignored advice that seemed so obviously beneficial, frustration could creep in. Why wouldn’t they do what they knew they should do?

It took me years to recognize the weakness in that question. Knowing and doing are not the same thing.

We know exercise is good for us, yet the comfortable chair wins. We know saving for the future matters, yet tomorrow always seems far enough away to begin later. We know certain foods aren’t good for us, yet we eat them anyway. We know relationships require attention, apologies sometimes need to be made, and careers rarely move forward simply because we wait for someone to notice us.

Knowing isn’t usually the hard part. Doing is.

And perhaps that woman standing at my pharmacy counter understood more than I gave her credit for. She almost certainly knew that candy wasn’t good for her diabetes. Another lecture about sugar probably wasn’t going to provide some missing piece of information. The more interesting question—the one I wasn’t experienced enough to ask then—was why knowing wasn’t enough.

Shakespeare understood the problem long before we had words like compliance or behavior change. In Hamlet, Laertes is preparing to leave Denmark when he offers his sister, Ophelia, some earnest advice about how she should conduct herself. Ophelia listens, but she isn’t about to let her brother escape without a warning of her own. Don’t be one of those people, she tells him, who point out the “steep and thorny way to heaven” while choosing the easier “primrose path” for themselves.

More than four hundred years later, we are still walking both paths. We are remarkably good at knowing what should be done. We may even be better at recognizing what someone else should do. Spend less. Exercise more. Put down the phone. Eat better. Make the appointment. Have the difficult conversation. Stop putting off whatever we have been promising ourselves we will begin tomorrow.

The advice is usually sound. Following it is another matter.

Perhaps that is because knowing asks relatively little of us. Doing may ask us to surrender something—a pleasure, a habit, some money we would rather spend today, an evening on the couch, a comfortable routine, even the satisfaction of believing that we were right.

Sometimes the obstacle is greater than reluctance. A person living paycheck to paycheck may understand perfectly well the importance of saving and still have nothing left to save. Someone may know that exercise would be beneficial but be limited by illness, disability, time constraints, or other circumstances. Knowing what someone should do is easy when we aren’t living that person’s life.

That is something I understood imperfectly when I stood behind that pharmacy counter. My patient had diabetes. The candy wasn’t helping her. I was right about that.

But being right was never the whole story.

So what helps move us from knowing to doing? Part of the answer lies not only in the advice itself, but in how it is offered.

We’ve all encountered people who know a great deal and make certain that we know they know it. They instruct. They correct. They sometimes leave us feeling smaller than we did before the conversation began. Even excellent advice can become difficult to hear when it arrives wrapped in superiority.

And then there are the people who possess just as much expertise—perhaps more—but wear it differently. They explain. They listen. They tell us not only what they recommend but why. They invite questions. They don’t surrender their expertise, nor do they pretend that every choice is equally wise. But somehow, when the conversation is over, the decision feels as though it belongs to us.

I recently spent time with an adviser like that. He offered several recommendations, each accompanied by a thoughtful explanation. There was confidence in what he knew without a trace of arrogance about knowing it. I never felt instructed or diminished. I felt like a partner.

And I listened.

That experience made me think again about the woman with diabetes and her shopping cart. I’m curious how often, as healthcare professionals, we believed our responsibility ended when we had given patients the correct information. We explained the medication. We warned about the interaction. We recommended the diet, the exercise, or the follow-up appointment. If the patient didn’t act on our advice, we had a word ready: noncompliant.

But communication asks something more of us. People are more likely to consider difficult advice when they feel respected enough to examine it. They are more likely to take ownership of a decision when they have been invited to participate in it. Expertise matters enormously, but expertise and humility are not opposites.

The best advisers I have known don’t use their knowledge to make themselves bigger. They use it to reduce the distance between us.

That may be where doing sometimes begins.

Of course, it is easier to see the distance between knowing and doing when we are looking at someone else. I could see it in that woman’s shopping cart. Healthcare professionals could see it in patients who continued smoking, skipped medications, or ignored recommendations. Financial advisers see it in people who postpone saving. We see it in friends who remain in situations they complain about but never change.

The view becomes less comfortable when we turn the mirror around.

I have known that exercise is good for me, yet I have found reasons not to exercise. I have known that a difficult conversation needed to happen, but I have postponed it. I have received advice that I initially resisted, only to discover later that the person offering it had seen something I was not ready to see.

I have known better and not done better. Most of us have.

Perhaps that is why I am less comfortable today with the word noncompliant than I once was. It places the problem conveniently on the other side of the counter: I told you what to do. You didn’t do it. But human behavior is rarely that tidy.

Being willing to listen doesn’t mean doing everything someone tells us. Good advice can be wrong. Experts can disagree. Circumstances matter. We still have to question, weigh, decide, and sometimes say no. Being teachable is something different. It is the willingness to remain curious when advice makes us uncomfortable, to ask whether our resistance comes from thoughtful disagreement or simply from not wanting to change, and to consider the possibility that another person may see something we cannot yet see for ourselves.

I wish I could say I have always done that. I haven’t. But growing older has made me less interested in proving that I already know and more interested in discovering what I still have to learn.

I haven’t thought about that woman in years, but I can still picture her standing at the pharmacy counter, her shopping cart nearby. I don’t know what happened after she left the store that day. I don’t know whether she ever changed what she ate or whether another physician, pharmacist, nurse, or family member eventually managed to reach her. Perhaps no one did.

I do know that I was right about the insulin. Taking it did not make the candy harmless. Her diabetes required more from her than filling a prescription, and nothing I have learned since has changed that.

But something else has changed.

The young pharmacist behind that counter believed that knowing what was right and explaining it clearly should have been enough. If the patient understood but still didn’t act, the failure seemed to be the patient’s.

I no longer believe it is that simple.

Knowledge matters. Expertise matters. Good advice matters. But between knowing and doing lies all the complicated territory of being human—habit and fear, pleasure and circumstance, resistance and readiness, trust and choice.

Sometimes we cross that distance because someone helps us see what we could not see ourselves. Sometimes we cross it because someone offers knowledge without making us feel small. And sometimes, despite everything we know, we remain exactly where we are.

“Well, I’m taking my insulin, so I’m okay, and you should know that!”

She was wrong about the insulin.

But after all these years, there was something I should have known.

Knowing what someone needs to do is one thing.

Understanding what might help them do it is another.

McKenzie at the Gallery

Brad Philbrick — Wed, 19 Aug 2026 13:08:56 +0000

When I walked into J. Petter Galleries in Douglas, Michigan, I wasn’t quite sure where to look first.

Color seemed to be everywhere. Paintings covered the walls. Sculptures occupied tables and corners. Bowls, prints, carvings, and other pieces appeared wherever my eyes landed. And woven among all that art were bottles of wine—rows and rows of them, their labels and shapes sometimes so distinctive that the bottles themselves seemed like part of the gallery.

A young woman was busy at the register when I entered. I didn’t know her name yet. She looked up and gave me a warm smile, the kind that manages to say welcome without requiring anything in return.

I did what I suspect many people do when entering an unfamiliar place. I turned right.

There was a wine bar, and nearby, a beautiful dining table and chairs. I continued wandering and discovered more wine than I had expected to find in an art gallery. Then came a small collection of food: crackers, cheeses, dips, and spreads. There were corkscrews and wine openers, glasses and napkins, cheese slicers and cutting boards.

The gallery staff beautifully arranged the entire gallery; even the food and corkscrews looked like art.

I kept wandering.

That may be one of the pleasures of a good gallery. No one tells you where to begin. You follow whatever catches your eye.

For me, one of those things was Paul van Heest’s work. I stopped and studied it, trying to make meaning of what I was seeing. Elsewhere were the Lake Michigan shoreline scenes one might expect to encounter in western Michigan, but there were also animals, abstracts, impressionist works, sculptures, and pieces that required me to stand still for a while.

Eventually, I circled back toward the young woman at the register.

This time she introduced herself.

McKenzie.

I asked whether the wine bar was open.

“Of course,” she said enthusiastically.

Could I purchase a glass of wine?

Absolutely. And, she told me, I was welcome to take it with me while I wandered through the gallery.

That sounded like an excellent arrangement.

We walked over to the bar, where I decided I wanted a white wine. McKenzie suggested a Viognier.

It was splendid.

Glass in hand, I set off again.

Something changes when you wander through an art gallery with a glass of wine. Perhaps you slow down. Perhaps you permit yourself to linger. I found myself moving from painting to painting, sometimes studying the work and sometimes simply enjoying the color and form around me.

Later, I returned to McKenzie with another question.

I wanted to take some Michigan wine home.

She explained that the gallery carried quality wines from around the world, so their Michigan selection was relatively small. There was no attempt to turn my request into something it wasn’t. She showed me what they had and began telling me about the wines.

I eventually chose six bottles.

As she described them, I found myself thinking:

How can you know the details of all these wines?

There were so many bottles in that gallery. Different grapes. Different regions. Different characteristics. Yet McKenzie spoke about them comfortably and specifically, just as she had when recommending my glass of Viognier.

What impressed me, though, wasn’t simply what she knew.

It was what she did with what she knew.

There was no performance to it. No sense that I was being given a lesson I hadn’t requested. No suggestion that she was the expert and I was the novice. She answered my questions, offered suggestions, and then allowed me to continue exploring.

Knowledge can sometimes create distance between people.

We have all encountered the person who knows a great deal and makes certain that we know they possess a vast amount of knowledge. Expertise can become its own kind of barrier. It can make us reluctant to ask the next question because we don’t want to reveal how little we know.

But knowledge can do something else.

It can invite us in.

That was what McKenzie did.

She knew the wine, but she didn’t make wine intimidating. She knew the gallery, but she didn’t make art intimidating. She was available without hovering, knowledgeable without being haughty, friendly without seeming artificial, and helpful without becoming pushy.

Those combinations are rarer than they sound.

There must have been considerable preparation behind what I experienced that afternoon. No one becomes knowledgeable about wine or art simply by standing near it. Whatever combination of study, training, experience, curiosity, and practice had brought McKenzie to that gallery, the result appeared effortless.

That is one mark of genuine professionalism.

We notice the ease without seeing all the work that made the ease possible.

Eventually, it was time for me to leave. McKenzie rang up my purchases. We exchanged pleasant goodbyes, and I headed down the road to Borrowed Time, where a marvelous dinner awaited me.

My Michigan trip continued.

There would be other restaurants, other conversations, other places to explore. I would eventually drive home with six bottles of Michigan wine among the reminders of where I had been.

But something else came home with me.

I remembered McKenzie.

Not because she had done anything dramatic. Not because she had tried to make herself memorable. Perhaps almost the opposite.

She had helped me enjoy something she knew well without ever making the experience about her.

There is a quiet generosity in that kind of expertise.

The people who know the most don’t always need to show us how much they know.

Sometimes they pour the Viognier, answer our questions, and send us back into the gallery to discover something for ourselves

Some people become memorable without ever trying to be.

What Refuses to Leave

ydm_alex_brad — Wed, 12 Aug 2026 21:10:05 +0000

There is something my father used to say to me. Whenever an idea captured my attention, he’d smile, shake his head, and say, “Brad, when you get something on your mind, you never let it go.”

Years later, Jane has said much the same thing. So has my son, Drew. A few friends have been even less diplomatic.

“Geez, Brad,” they’ve laughed, “drop it, will you?”

The truth is, I’ve never been very good at letting go.

For most of my life, I assumed they were describing my personality. I was the person who stayed with an idea longer than most people did. If something interested me, I wanted to understand it. If a question remained unanswered, I kept turning it over in my mind until it finally made sense.

Only recently have I begun to wonder if they were describing something else entirely.

People occasionally ask me where the ideas for Observations come from. It’s a fair question. After all, every Wednesday another essay appears. Sometimes it’s about pharmacy. Sometimes it’s about Michigan, a conversation with a stranger, or a quiet moment that unexpectedly stayed with me. From the outside, I keep a notebook filled with topics, ready to choose one each week.

I don’t.

In fact, I rarely go looking for ideas at all.

Most weeks are filled with moments worth remembering: a thoughtful lunch with a friend, a sentence in a book that makes me stop and read it again, a walk, a patient, a chance remark that disappears almost as quickly as it was spoken.

Most of those moments quietly become part of the background of life.

But now and then, one doesn’t.

It stays with me. It follows me home. It interrupts my thoughts while I’m exercising, returns while I’m making dinner, and quietly joins me on a morning walk.

And after a while, I find myself asking a different question.

Not, What should I write this week?

But…

Why won’t this leave me?

I used to think the answer was persistence. Maybe even stubbornness. After all, there was plenty of evidence. My father had noticed it. Jane noticed it. Drew noticed it. Friends certainly noticed it.

But persistence doesn’t quite explain what happens when an idea stays with me. I’m not always trying to solve it. Sometimes I’m barely thinking about it at all.

Then it returns.

A conversation I thought was over resurfaces while I’m walking. A sentence I read in the morning comes back while I’m making dinner. Something I noticed days earlier suddenly connects with something else.

And gradually, I begin to understand that the idea hasn’t been waiting for me to do something with it. It has been waiting for me to understand why it mattered.

That realization has changed the way I think about writing.

Writing doesn’t begin when I sit at my keyboard. It begins when something quietly refuses to leave me.

The keyboard comes later. By then, the essay has often been underway for days.

A few weeks ago, I spent an afternoon wandering through galleries in southwest Michigan. One stop, in particular, stayed with me.

At first, I assumed it was because of the art. Or perhaps because I enjoyed a glass of Viognier while browsing the gallery. But after I returned home, I realized neither of those things explained why I kept thinking about the visit.

What stayed with me was McKenzie.

She welcomed visitors with the rare combination of warmth and knowledge. She knew the paintings. She knew the local wineries. She knew the stories behind both. Before long, I wasn’t simply looking at art or tasting wine. I was seeing southwest Michigan through the eyes of someone who genuinely loved the place she called home.

I didn’t write about McKenzie that afternoon. Or the next day.

But she quietly accompanied me home.

Several days passed before I understood why. It wasn’t really about wine. It wasn’t really about art.

It was about the quiet generosity of someone who loved something enough to help someone else see it more clearly.

That’s when I realized something.

The essays in Observations don’t begin on Wednesday morning. They begin much earlier, when an ordinary moment quietly asks for a little more of my attention.

That’s why I don’t think of Observations as simply a weekly newsletter anymore.

It has become my public notebook of noticing.

Not a diary. A diary records what happened.

Not a memoir. A memoir explores how life changes us.

A notebook of noticing quietly asks a different question:

What am I being invited to understand?

Perhaps you’ve had moments that refused to leave as well: a conversation that lingered long after it ended, a sentence you couldn’t stop thinking about, a person whose kindness stayed with you, a question that quietly followed you for days.

It’s easy to dismiss those moments and move on. Life gives us plenty of reasons to hurry toward the next obligation, the next appointment, the next notification.

But I’ve begun to wonder if those moments aren’t interruptions at all.

Perhaps they’re invitations.

Not every passing thought deserves our attention. But every so often, one quietly asks us to slow down, to look again, to understand a little more deeply than we did the first time.

I’ve come to believe that those are the moments worth trusting. They’ve given me essays. More importantly, they’ve given me a richer way of moving through the world.

So if someone were to ask where the ideas for Observations come from, I could tell them they begin with a notebook, a keyboard, or a Wednesday morning.

But that wouldn’t be true.

They begin much earlier than that.

They begin the moment something quietly refuses to leave.

And when it does, I’ve learned not to chase it or force it into words. I’ve learned to walk with it.

Because sooner or later, if I’m patient enough to keep paying attention, it usually reveals what it came to teach me.

Perhaps it will do the same for you.

As Promised

Brad G. Philbrick & Company — Wed, 05 Aug 2026 20:17:03 +0000

Some of my favorite emails begin with two simple words.

As promised.

Those words tell me something before I read another sentence.

They tell me someone remembered.

They tell me our conversation mattered enough that they came back to finish it.

Over the years, I’ve come to appreciate those two words more than I ever expected.

As a pharmacist, I learned that keeping a promise wasn’t simply good customer service. It was one of the quietest ways we show another person they matter. A returned phone call. The information we promised to research. A question we said we’d answer tomorrow.

Each one quietly says, I didn’t forget you.

Years later, in pharmaceutical and biomedical sales, I discovered something similar. More than once, I earned the business not because I gave the best presentation, but because I did exactly what I said I would do. If I promised additional information, I sent it. If I said I would call on Tuesday, I called on Tuesday.

People remembered who followed through.

Recently, I attended a writers conference where three people reminded me of that lesson once again. One promised to send information about professional editing organizations — two others promised recordings of their presentations and information about submitting a manuscript.

Both followed through.

Both quietly said the same thing.

As promised.

As grateful as I was for those emails, they reminded me of another promise I made many years ago.

Mary Singer worked as a cashier in the pharmacy where I practiced. She was one of those dependable people every workplace treasures — quiet, kind, and faithful.

Life had not always been easy for Mary. From what I understood, her husband could be difficult. Now he was dying of cancer, and with death drawing near, fear had replaced much of his anger.

One day I told Mary I would stop by the hospital to see him.

I didn’t want to go.

I went because I had told Mary I would.

I think she wanted to believe me.

I also think life had disappointed her often enough that she quietly wondered whether I really would.

A few days later, I walked into his hospital room.

The room was quiet.

Mary sat beside her husband’s bed.

He looked at me with relief, tears welling in his eyes.

For reasons I still can’t fully explain, my presence seemed to bring him comfort and peace.

As I prepared to leave, Mary looked at me and quietly said,

“Thank you for coming, Brad.”

She seemed surprised.

Not because I had done something extraordinary.

Because I had done what I said I would do.

As I drove home from the hospital that day, I felt something I hadn’t expected.

I had gone because I wanted to support Mary.

I hoped my visit might bring a little comfort to her husband.

I never imagined how much the visit would change me.

For days afterward, I found myself thinking about that quiet hospital room.

About Mary’s gratitude.

About the tears in her husband’s eyes.

About how a simple promise had become something much larger.

Looking nearly forty-five years later, I realize I wasn’t simply keeping my word.

I was discovering that the promises we keep are rarely about calendars or appointments.

They’re about people.

They’re about showing another person they matter.

Looking back, I’ve also come to believe that the promises which shape us most are often the ones we almost didn’t keep.

I thought I was going to the hospital to bring a little peace to Mary and her husband.

I never imagined I would come home carrying some of that peace myself.

That may be why two simple words still catch my attention whenever they appear at the beginning of an email.

As promised.

They remind me that every promise we keep quietly tells another person,

You mattered enough for me to come.