In this video, former physician and 20‑year entrepreneur Luke Murray explains how the incentives that governed his behavior in medical school—where appearing competent was rewarded—led him to hide confusion and miss learning opportunities. Once the external grading pressure vanished during residency, he deliberately began admitting ignorance, which dramatically accelerated his learning. He argues that the same principle applies in business: when there’s no penalty for looking stupid, you can expose knowledge gaps and close them. Murray shares concrete tactics for turning abstract explanations into tangible understanding: (1) stop the speaker on a specific word and ask for a concrete definition, (2) repeat the explanation back to reveal missing pieces, (3) demand numerical examples for technical concepts (e.g., net present value), and (4) reframe processes from the customer’s perspective. He illustrates these methods with real‑world examples, such as deciphering billing terminology and simplifying a CFO’s description of valuation. Underlying all the tricks is a single principle—force the abstract into a concrete gap so you can see and fill it. He ends by urging viewers to identify areas in their own businesses where they avoid being publicly wrong and to apply these techniques.
Chapters
In medical school, we'd be standing in the hallway listening to a doctor talk about a patient in like a patient room we were about ready to go in. And there'd be a crowd of us med students, and I'd be in the back. My back would be hurting. I wouldn't be able to see or hear him that well. And he'd be explaining something about the patient's physical exam, like what their body would look like, or about a lab value that would correlate with whatever problem they were having. And sometimes he would like ask a question or he would make a statement that I wouldn't really understand, and I didn't want to check out of the conversation and go look it up. Actually, I did want to do that, but you're not allowed to do that. And I also didn't want to raise my hand and draw attention to myself for not knowing something that I wasn't sure if I was supposed to know already or was reasonable to not know. And given that I was already at the bottom of the class, and had been there basically since my first day of medical school, I just kept my mouth shut, kept my head low, and hoped that whatever the heck they were talking about didn't come up on a test or in some future conversation. And no, this isn't the part where I tell you that, like, I learned to raise my hand instead, and you should too, and just speak up when you don't understand. Because in medical school, shutting up and keeping your head down was arguably the smart move. I mean, you're being graded on looking competent, not just on tests, but in conversations, on rounds, every time an attending asks me a question in front of people. So that mattered. Looking like I knew things, or at least not revealing when I didn't, had a real payoff. So protecting the image of how smart I was or wasn't was a strategic play. So yeah, sometimes the smart play is to shut up. As long as you're honest with yourself that the price you're paying is not learning that thing. If you don't know who I am, my name's Luke Murray. I'm a former physician. I've been an entrepreneur for about 20 years. During that time, I've done a little over $100 million in revenue. I currently have a portfolio of businesses that does about $3 million a year in revenue. And I make these videos because I would like to have ambition without the bullshit. And I'm guessing you would too. Anyway, I got into residency and at some point it hit me that that I was basically out of tests to take. I mean, I wasn't trying to— since I was, I don't know, 16 years old, I'd been worried about getting the best grade possible so that I could get to the next thing, and that stopped at residency. And as soon as I realized it, I was like, oh yeah, no one's scoring me anymore. I don't want to do anything competitive after residency. So I started doing the thing that I'd been scared to do for years. I started admitting when I didn't know what was going on. And surprise, I learned way more. Now, to be fair, it probably made me look worse at first, not better, because I was finally asking questions that I should have already known the answer to. So again, there's a cost to opening your mouth, but staying confused to protect how you come across costs more once looking good is no longer literally part of your grade. And here's the thing I want you to notice. The second the incentive changed, my habit changed with it. I didn't slowly evolve out of hiding over the next decade. As soon as I saw there was no longer a real consequence to looking stupid, I just stopped hiding and let myself look stupid. So by the time I got into business, the math had already settled. In my companies, that med school test is totally gone. So nobody's deciding whether I get to be the boss based on whether I sound sharp in a meeting. Sure, there's a small chance I can look dumb in front of my team and maybe they'd lose a little confidence in me. Or maybe they don't, and they respect me because of my humility and transparency. But even if it did, that's nothing next to the real cost, which is not actually deserving their confidence in the first place, because you don't know what the fuck is actually going on in your own company. And nowhere does that show up more than the parts of your business that start to feel like a black box, the corner of the business that everyone, including yourself, has quietly agreed is too complicated to look at directly. The part you're just supposed to leave to whatever expert owns that problem. And for me lately, that's been billing. Someone will explain it to me, like our billing person, and be like, well, like, we have to get the claims posted, and then we'll get remits and make sure that they match. And the frustrated version of me will say, like, I didn't understand anything you just said, which is true. And I have said that sometimes, but it's also really useless because now what are they supposed to do? They just repeat themselves, but slower and louder so that we both feel stupid together. Here's what I actually do instead. I mean, yes, step 1 is to admit that you're confused in no uncertain terms. But after that, the first move is I stop them on the exact word. So I will say, you said the word claim. What is that? Is it a piece of paper? Is it an email that you get? Is it a notification? And what purpose does it serve? Then you said the word posted, like there's no corkboard where we put checks. Like, what does that mean? And you said remit, like, is that a physical check? Is it a piece of paper? What problem does that piece of paper solve? And I'm not just throwing my hands up and saying, this is stupid, or I don't know what you're talking about. I'm going to the precise spot where my understanding broke. So that's one of the moves that I do. The second move, if it's like a longer sentence or story, is that I'll just repeat the thing to them and say, hey, look, what you just explained to me. This is what I would tell someone else if they were like, hey, Luke, what did so-and-so just say? And I'd be like, yeah, they said something about posting something to somewhere. I don't really know why. At the end of the day, I'm not sure how you get money if it was about billing. And so when I do that, they can hear what landed and what didn't and where their logic that supposedly is clear in their brain fell apart. There are other versions of the same move. And depending on what someone's trying to explain, like if it's any kind of mathematical concept, I say, give me a real numerical example. Recently, a CFO told me that the value of a business was the net present value of its future cash flows discounted at certain rates. And as much as I wanted to look super smart, I just told him I don't know what any of those words meant and that he needed to put numbers to each one. And he did. A very simple version is like, if you're gonna make $10 tomorrow, and $10 the day after, and you'd rather have $9 instead of $10 tomorrow and $8 today instead of $10 2 days from now, then you've got the net present value of future cash flows discounted at a certain rate. Way easier to follow that than that fancy sentence. The other thing that I'll say is that I'll say if it's about like a, a business issue or like something something around a customer-facing issue, I'll say, tell me the story from the customer's side. Like, what problem does this solve for them? Not in the abstract, but in an actual, like, they wake up in the morning, they have breakfast, and then this product or service saves the day for them. If it's a step in the process, kind of like I was talking about with billing, I will say, what problem does this specific step solve? Solve, or what value does it add to the product or service? Now, all these sound like different tricks, but underneath them, they're really just the same one. Every one of them forces the abstract into something concrete enough that the gap becomes visible. And once you see the gap, you can learn about how to close it and close it. So let me ask you, where are you nodding along and just telling yourself something in your business is too complicated for you to understand? When the truth is she's just never been willing to be specifically publicly wrong about it. Let me know in the comments, and thanks for watching.
