Stop Giving Data Dumps

We're at the scrub sink. Case starts in four minutes. I look over and ask, "How's Mr. Johnson doing this morning?"

That question sounds casual. It isn't.

And I've been on both sides of it.

You take a breath and start: "Mr. Johnson is a 68-year-old male with a history of hypertension, hyperlipidemia, type 2 diabetes, GERD, a prior appendectomy in 1987, and a seasonal pollen allergy who presented two days ago with abdominal pain, his vitals overnight were 98.6, 118 to 146 systolic, heart rate 82 to 109, temp max 37.8, urine output was adequate, sodium 138, potassium 4.1, chloride 103—"

I'm still scrubbing.

And let me say this plainly: I haven't stopped you because I stopped caring about Mr. Johnson. I am listening. I'm just searching — combing through everything you're saying trying to find the one thing I actually need: is he okay, did something change overnight, and is there anything I need to know before I walk into this OR for the next four hours?

That information is in there somewhere. I just haven't found it yet.

I've stood at this same sink as the trainee, presenting to an attending who said nothing while I talked. I had no idea what they wanted. So I gave them everything I knew and hoped something would land. Too much and you look like you're reciting. Too little and you look like you haven't seen the patient. Nobody teaches you how to calibrate that.

That instinct is not wrong. And this is important: we'd genuinely rather you give us more than have you leave out something that turns out to matter. If you're not sure whether a detail is relevant, include it — but flag it. "I wasn't sure if this was significant, but his urine output dropped to 15 mL/hr around 4am." That sentence is exactly right. You noticed something, you weren't sure what to do with it, and you brought it forward anyway.

That's good clinical instinct. Don't filter that out.

What we're asking you to do is sort — not censor.

Pearl: Rounds are not a storage contest. They are a decision-making exercise.

A good presentation helps the team think forward. A thorough one that buries the point traps everyone in the rearview mirror.

Here's what we're actually listening for: is the patient safe, are they getting better, what's in the way, and is anything drifting? That's the frame. And the most important word in that list is what's different — what changed overnight? The change is almost always the story.

Start with a one-liner. Name, where they are in the course, and the single issue on the table today. "Mr. Johnson is POD2 from his colectomy — overall stable, but still no bowel function and his pain has been tough to control." Now we know where we are. Everything after that answers one question: so what do we do about it?

From there, give us the vitals that support the headline. If his pressure and his sat are fine, say so in four words and move on. If something is trending wrong, tell us by how much and in which direction.

"He was tachycardic overnight, peaked at 112, came down with fluids" is useful. "Heart rate was 88, then 92, then 97, then 104, then 112, then 98 after 500 of LR" is the same information — but now we have to assemble it ourselves.

A vital-by-vital reading of the overnight flowsheet is a spreadsheet. You can read us a spreadsheet, or you can tell us the story.

Labs work the same way. Lead with what changed or what's abnormal. If the white count was 14 yesterday and it's 18 today, say that first. If the patient is stable, we do not need a dramatic reading of every normal sodium, magnesium, and chloride. Nobody has ever saved rounds by announcing a normal chloride with confidence. We respect the commitment. That is not the win.

Pearl: Do not confuse available information with necessary information.

Here's how the sorting works in practice. The relevant data changes based on the clinical question in front of us. If the issue is return of bowel function, we care about distention, nausea, NG output, gas, exam, and whether labs suggest we're still in expected territory. If the issue is possible sepsis, we want the fever curve, heart rate trend, urine output, mental status, white count, lactate, and possible sources. If the question is discharge, we care about pain control, PO tolerance, ambulation, oxygen requirement, wound, and drains.

Not less data. Organized data.

Lead with what's urgent. Follow with what's relevant. Hold the rest until we ask.

Pearl: Brevity earns trust when it is paired with judgment. Not random brevity. Focused brevity.

Here's what it sounds like in practice. Same patient, same information.

Data dump: "So this is a 24-year-old female with a PMH of asthma and anxiety who presented with right lower quadrant pain and leukocytosis, CT showed acute appendicitis, she went to the OR yesterday for laparoscopic appendectomy, intra-op there was an inflamed non-perforated appendix, now POD1, overnight vitals were 98.7, 120/70, heart rate ranged from 88 to 102, sats 97 to 100 on room air, urine output was…"

By the third line, we've lost the story. Not because we stopped caring — because we can't find where it's going.

The same patient, done right: "Ms. Jones is a 24-year-old, POD1 from laparoscopic appendectomy for uncomplicated appendicitis. No overnight events. Pain controlled on PO meds, tolerating diet, ambulating, afebrile, WBC down from 14 to 10. I think she's ready to go home later today or tomorrow."

Same patient. One version makes us search. The other tells us exactly where to look.

Now, do not disappear at the end.

A presentation without an assessment and plan is just organized transcription. We do not need perfection. We need to know what you think. Not a speech — one sentence is enough.

"I think he's recovering appropriately and the main issue is pain limiting ambulation."

"I'm worried her tachycardia is out of proportion and we may be missing a developing problem."

"I'm not sure yet — it could be atelectasis or something brewing, and I wanted your read before rounds."

That last one is also a complete sentence. Say what you think, even if you're wrong. Especially if you're wrong. Wrong and thoughtful is teachable. Vague and overloaded is not.

Polished is overrated. Reliable is better.

The team can work with wrong. They cannot work with lost.

Pearl: Know your patient well enough that you could close your notebook and still tell us what matters. If you can't do that, you don't know the patient yet — you know the chart.

If you don't know something, say so directly. "I'm not sure" is a complete sentence. What hurts you is not the gap. It's the hedge. The ninety-second runway to an answer that never lands. "I don't know, but I'll find out" is much more useful than watching you take the long detour. It is not a scenic route.

And if we ask for more detail after a tight presentation, that is not failure. That is rounds. It usually means we're engaged. You are not supposed to preload every answer into the monologue.

Pearl: If you wouldn't put it in a text at 2am, think hard about whether it belongs in your morning presentation.

Before you open your mouth, take ten seconds. What's the main issue? What data support it? What happens next? That pause will clean up half your presentations. One slow breath before you start is not a wellness technique. It keeps your working memory online so you can think instead of perform.

Pearl: When in doubt, shorten the numbers and lengthen the thinking.

Bottom Line: We are always listening — for the delta, for the headline, for your read on the patient. Sort before you speak. Lead with what matters, flag what you're uncertain about, and end with what you think. The team can work with wrong. They cannot work with lost.

---

What's Next: Let's not make us Dizzy in Your First Laparoscopic Case. Additional Reading: What Does the Team Actually Want? It's a conversation worth having once you understand what attendings are actually listening for.