Decoding AI, health tech & policy transforming healthcare—practical playbooks for clinicians, operators, & builders, from the OR to the boardroom. <br/><br/><a href="https://techysurgeon.substack.com?utm_medium=podcast">techysurgeon.substack.com</a>
Techy Surgeon Podcast
Claim This Podcastby Christian Pean MD, MS
5.0(1 reviews)
26 episodes
Updated Daily
Accepts GuestsHas SponsorsLocation 🇺🇸
Podcast Overview
Decoding AI, health tech & policy transforming healthcare—practical playbooks for clinicians, operators, & builders, from the OR to the boardroom. <br/><br/><a href="https://techysurgeon.substack.com?utm_medium=podcast">techysurgeon.substack.com</a>
Language
🇺🇲
Publishing Since
7/13/2025
1 verified contact email on file for Techy Surgeon Podcast
Pitch yourself as a guest, propose sponsorships, or reach out directly to the host.
Recent Episodes
June 6, 2026
You're Prompting Wrong: A Claude Cowork session with Dr. Christian Péan
<p>Thank you to everyone who tuned into my live video! Join me for my next live video in the app.</p><p>Prompt With CARE</p><p>What watching someone else prompt taught me about the skill we all think is basic—plus two prompt packs that set up your Claude Cowork in one afternoon</p><p>Yesterday I asked a student to sit at my computer and prompt Claude Cowork to build a presentation. He typed a single sentence, hit enter, and waited. Watching him, I realized two things: the conversational interface with these tools is a genuine skill, and I’d been doing it so long I’d forgotten it had to be learned. I teach people AI tools constantly—I had never once sat down and watched someone else prompt. It was the most instructional thing I’ve done in months.</p><p>So this piece is the session I ran afterward, in writing. One framework, one habit loop, and—because readers keep telling me prompt packs are the most useful thing I publish—two packs you can paste into Claude Cowork today: a <strong>Cold Start Interview</strong> that sets up your workspace from scratch, and five <strong>Workflow Interviews</strong> that teach it your voice, your week, and your standards. Nothing here is specific to medicine. If you have a job and a desk, this applies.</p><p><strong>Housekeeping:</strong> I don’t type my prompts—I speak them. You will never type as fast as you talk, and the more descriptive your language, the better your output. I use <a target="_blank" href="https://ref.wisprflow.ai/christian-pean-wi5k">Wispr Flow</a> (function + spacebar, then just talk—you can literally whisper). If you want to try it, <a target="_blank" href="https://ref.wisprflow.ai/christian-pean-wi5k">downloading through my affiliate link</a> supports this newsletter.</p><p>The Frappuccino Problem</p><p>A close friend of mine has a habit that drives me a little crazy. He’ll say, “I don’t like the way AI writes X.” or he’ll say “AI never makes my images or powerpoints right”. And every time, I think: it’s not that you don’t like what AI makes. It’s that you don’t like what AI makes for <strong>you</strong>…because you’re giving it poor instructions.</p><p>Think of these tools as a very smart intern. Maybe a PhD-level Harvard graduate of an intern. If I tell that intern “go get me coffee,” and they come back with a Frappuccino when I wanted an Americano with oat milk, that’s on me. The intern did their best with what I gave them. A language model is the same: every detail you leave out, it fills in with the most average assumption available. Vague prompts don’t produce bad output. They produce median output, which for any real professional task is the same thing.</p><p>The fix is a framework I call prompting with <strong>CARE</strong>:</p><p><strong>C — Context.</strong> Who you are and what situation this output lives in.</p><p><strong>A — Audience.</strong> Who actually reads, sees, or uses this. </p><p><strong>R — Role.</strong> Who the AI should be—”you are a patient educator,” “you are a skeptical CFO”—so it pulls the right body of knowledge into the task. </p><p><strong>E — End product.</strong> The exact artifact you want: format, length, tone, what it should be usable for the moment it’s done.</p><p>In my live session I demonstrated this with two prompts about the same topic. “Tell me about hip fractures” got me a long, jargon-heavy wall of text. </p><p></p><p>The CARE version: “I’m a trauma surgeon, fewer than a third of my patients ever start bone-protecting treatment after a fracture, you’re a patient educator, write for families at a sixth-grade reading level, one-page handout, warm and non-alarmist, end with three questions to ask your doctor”</p><p>This prompt instead produced something I could physically hand to a patient that afternoon. Same model. Same topic. The difference was entirely in the briefing.</p><p>Your First Output Is the Input</p><p>The second principle, and the one that separates people who get compounding value from people who quit: <strong>the first output is not the final output. It’s the input for the next cycle.</strong></p><p>You will be very frustrated if you try to one-shot these tools. The entire power of a large language model is the compression of iteration cycles: you get unlimited at-bats, and each swing takes seconds. When my bone-health handout came back and I didn’t love it, I didn’t start over. I said what needed to change. Make it Duke-branded, add interactive components, also give me a PowerPoint I can click through. And the output became the raw material for something better. Later I dragged that same HTML into a fresh Cowork task and rebranded it for RevelAi in one prompt. Output becomes input. That’s the loop.</p><p>Two force multipliers on that loop. </p><p>First, <strong>speak instead of typing.</strong> Being verbose is usually a weakness of mine; it turns out it’s a superpower with these models, because descriptive, rambling, context-rich instruction is exactly what they reward. You’re not on a timer, and nobody’s grading your dictation.</p><p> Second, <a target="_blank" href="https://techysurgeon.substack.com/p/stop-writing-prompts-start-building?r=3adnor"><strong>meta-prompting</strong></a>: when the end product demands a better description than you can produce—a detailed image prompt, say—don’t write the prompt yourself. Ask the tool to write the best-practice prompt for you, then carry it wherever you need it. The model is better at describing what the model needs than you are.</p><p>The Step Most People Never Take</p><p>Everything above makes a single task go well. The better approach is making sure you never start from zero again. This is what I think of as building sustainable context systems.</p><p>The low-hanging fruit is Projects: a folder where your chats, files, and outputs accumulate so the tool carries the thread across sessions. I run my academic promotion tracker, cap table, and investor touchpoints this way connected with Live Artifacts. <strong>Learn more about Scheduled Tasks and Live Artifacts Below:</strong></p><p> But the foundation underneath all of it—the thing I do with every person I onboard one-on-one—is to <strong>have Claude interview you.</strong> Instead of laboring to write the perfect context document about yourself, you flip it: make the model ask you questions, one at a time, until it understands your role, your projects, your people, and your standards. Answering questions is cognitively cheap. Composing instructions is expensive. And in Cowork, the answers don’t evaporate when the chat ends—they become standing infrastructure, so every future task starts with the CARE already half-written.</p><p>The question is what the interview should cover. That’s the part most people improvise badly. Below the line are the exact packs I give people in one-on-ones—six prompts that stand up your workspace from nothing, and five that teach it your recurring workflows.</p><p></p><p>The two prompt packs below are for paid subscribers. Pack One stands up a Claude Cowork workspace from scratch in about thirty minutes—it’s the same starter kit I use when I onboard people one-on-one. Pack Two teaches your Cowork your writing voice, your calendar, and your definition of done. Copy, paste, answer the questions out loud and you’re all set.</p><p>As a bonus, in the paid section… It seems like many people are a fan of the <a target="_blank" href="https://substack.com/@techysurgeon/note/c-271385379?r=3adnor&utm_source=notes-share-action&utm_medium=web">one-shot video note</a> that I wrote recently. I also included a video of me installing the <a target="_blank" href="https://higgsfield.ai/mcp">Higgsfield MCP</a>.</p><p><p>Techy Surgeon is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></p><p>Prompt Pack One: The Cold Start Interview</p><p>Run these in order, in Claude Cowork, ideally in one sitting. Each prompt instructs Claude to interview you and then write what it learns to memory—so say “save this” when the summary looks right. Total time: about thirty minutes. Less if you dictate.</p><p><strong>1 — The Role Brief</strong></p><p>You’re setting up as my long-term work assistant, and right now you know nothing about me. Interview me, one question at a time, until you understand: what my job actually is day to day (not the title—the verbs), who I’m accountable to, what I produce, and what a great week versus a bad week looks like. Don’t accept vague answers—push for specifics. When you’re confident, write a one-page working profile of me, show it to me for corrections, and save it to memory.</p><p><strong>2 — The Project Map</strong></p><p>Interview me about everything I’m currently working on—projects, initiatives, recurring responsibilities, and the things that are stalled but still mine. One question at a time. For each, capture: what it is, current status, who else is involved, the next milestone, and what I’m most worried about. Then organize it into a project map ordered by what deserves my attention, show me, and save it to memory.</p><p><strong>3 — The People Directory</strong></p><p>I’m going to mention names, nicknames, and abbreviations constantly, and I never want to explain them twice. Interview me about the people and organizations in my work orbit: who they are, their role relative to me, how I refer to them in shorthand, and anything you should know before drafting something they’ll read. One question at a time, and prompt me with categories I might forget—boss, reports, clients, vendors, collaborators, the person I always forward things to. Save the directory to memory.</p><p><strong>4 — The Preference Card</strong></p><p>Interview me about my output preferences so you stop guessing. Cover: how long answers should be by default, bullet points versus prose, how formal my drafts should run, formatting pet peeves, words and phrases I’d never use, and how I want you to behave when you’re uncertain—guess, ask, or give options. Get concrete by showing me two short sample paragraphs in different styles and asking which is closer. Save the result as my standing preference card.</p><p><strong>5 — The Definition of Done</strong></p><p>For each type of deliverable I produce regularly—you have the list from my project map—interview me about what “finished” means. What does a ready-to-send email have that a draft doesn’t? What makes a document ready for my boss versus ready for a client? Build me a short rubric per deliverable type, confirm it with me, and save it. From now on, check your own work against these rubrics before showing me anything.</p><p><strong>6 — The Standing Orders</strong></p><p>Last one. Interview me about the rules of engagement: things you should always do without asking, things you should never do without asking, topics where I want pushback versus execution, and how proactive to be when you notice something off in my files or messages. Compress what you learn into a set of standing orders, read them back to me, and save them. Then summarize everything you now know about me from this whole setup in ten bullets—let’s see how well you listened.</p><p>Prompt Pack Two: The Workflow Interviews</p><p>Run these as needed, after the Cold Start. Each targets one recurring workflow and ends with a reusable asset.</p><p><strong>1 — The Voice Extraction</strong></p><p>I’m going to paste three pieces of writing that sound like me. Read them, then interview me—one question at a time—about the choices you noticed: sentence rhythm, how I open, how I handle disagreement, what I do instead of corporate phrasing. Challenge me where my samples contradict my self-description; trust the samples. Then write a style guide for drafting as me, test it by rewriting one paragraph of your own in my voice, and ask me to grade it. Save the final guide to memory.</p><p><strong>2 — The Weekly Rhythm</strong></p><p>Interview me about the shape of my typical week: recurring meetings and what I need before each, deliverables on a cycle, the days that are always crunched, and the prep work I always do in a rush at the last minute. Then propose three things you could take over on a schedule—drafts, briefings, summaries—with the day and time you’d deliver each. I’ll pick. Save the rhythm to memory and set up the scheduled tasks I approve.</p><p><strong>3 — The Triage Spec</strong></p><p>I want you to be able to look at my inbox or message backlog and know what matters. Interview me about how I triage: which senders always get same-day replies, what “urgent” actually means in my world, what I can safely ignore, and what I’m always afraid of missing. Turn my answers into a written triage rubric with named tiers, confirm it with me, and save it. Then, whenever I ask you to review my messages, apply it and show your sorting.</p><p><strong>4 — The Decision Brief</strong></p><p>When I bring you a decision, I don’t want a list of considerations—I want it framed for a verdict. Interview me about how I like decisions presented: how many options, how much detail per option, whether I want your recommendation up front or last, and what evidence earns my trust. Build my decision-brief template, run a real decision I’m facing through it right now as a test, and refine it based on my reaction. Save the template.</p><p><strong>5 — The Delegation Test</strong></p><p>Pick a task I do regularly—I’ll name one if you can’t. Interview me about it until you could execute it without me: inputs, steps, judgment calls, who it goes to, and what failure looks like. Keep asking until YOU are confident, not until I get tired. Then write the runbook, execute the task once with me watching, and incorporate my corrections. Save the runbook. This is the test of everything else we’ve set up.</p><p></p><p> As a bonus, it seems like many people are a fan of the <a target="_blank" href="https://substack.com/@techysurgeon/note/c-271385379?r=3adnor&utm_source=notes-share-action&utm_medium=web">one-shot video note</a> that I wrote recently. Here is a preview of something I’m working on to let people understand the workflow for creating AI videos on their own directly in Claude CoWork: the Higgsfield MCP! Higgsfield is a bit pricey, but if marketing is a part of your business, it seems like it is probably the best tool to rapidly create images and videos, taking advantage of the APIs from the best native tools, including Cadence and GPT’s image generator. Check it out below and let me know if you’d like a deeper dive on how to create AI videos </p><p>Video below lightly dunking on pathologists was made with ONE PROMPT. Wild.</p><p></p><p>Four Habits to Take With You</p><p>If you remember nothing else: <strong>prompt with CARE</strong>—context, audience, role, end product. <strong>Don’t accept the first output</strong>—it’s the input for the next cycle, and the iteration loop is the whole point. <strong>Speak over typing</strong>, however clunky it feels at first; you’re not on a timer. And <strong>watch other people prompt.</strong> I’m a little embarrassed it took me this long to do it deliberately. You’ll learn as much from seeing where someone else gets stuck as from any tutorial—including this one.</p><p>Your output is going to look different from mine. That’s not a bug. Don’t get frustrated. Just iterate.</p><p><strong>Like this article on Techy Surgeon? </strong></p><p><strong>Spread the word!</strong></p><p>The best part of this newsletter isn’t the tips. It’s the people reading them. Subscribers here have teamed up on projects, swapped workflows, and pushed each other’s work forward. I’ve collaborated with several of you myself.</p><p>If something here has saved you time or sparked an idea, share it with one person who’d benefit. That’s it! One person. Group subscriptions get a discount.</p><p>Christian Pean, MD, MS is CEO and Co-Founder of RevelAi Health, Executive Director of AI & IT Innovation at Duke Health, and Assistant Professor of Orthopaedic Surgery at Duke University. He writes the Techy Surgeon newsletter on clinical AI and health policy for surgeons and health system leaders.</p> <br/><br/>This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit <a href="https://techysurgeon.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_2">techysurgeon.substack.com/subscribe</a>
May 23, 2026
Claude CoWork Live Artifacts and Scheduled Tasks Tutorial
<p>If you want to go deeper and combine scheduled tasks and artifact with context from meetings. Check out the articles below:</p><p></p><p></p><p></p><p>How I use AI to create content that can be part of your “AI loops””</p> <br/><br/>This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit <a href="https://techysurgeon.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_2">techysurgeon.substack.com/subscribe</a>
May 2, 2026
The AI Content Flywheel: How I Build an Audience as a Surgeon Without Sounding Like a Robot
This is a free preview of a paid episode. To hear more, visit <a href="https://techysurgeon.substack.com?utm_medium=podcast&utm_campaign=CTA_7">techysurgeon.substack.com</a><br/><br/><p>Thank you <a target="_blank" href="https://substack.com/profile/445396101-doug-fullington-md">Doug Fullington, MD</a>, <a target="_blank" href="https://substack.com/profile/32407752-alex-rivero">Alex Rivero</a>, <a target="_blank" href="https://substack.com/profile/6308510-healthmind-insights">HealthMind Insights</a>, <a target="_blank" href="https://substack.com/profile/49261132-eric-burgh-md">Eric Burgh, MD</a>, and many others for tuning into my live video! Join me for my next live video in the app.</p><p>I can publish a paper in an upper-tier orthopedic journal and, if I’m being candid, a few hundred to maybe a few thousand people will read it. Some of those people will cite it in their own papers. A small number will change anything in their practice because of it.</p><p>Then I share an insight about CMS payment model mechanics on Substack, and a health system CFO I’ve never met emails me because she’s been trying to articulate that exact problem to her board. A policy researcher in Geneva follows the thread. Three orthopedic surgeons I’ve never spoken to start a conversation about what I wrote that turns into an ongoing dialogue that has genuinely shaped how I think.</p><p>That asymmetry in exposure is what motivated me to start writing in public. Not personal branding, not monetization, not the promise of newsletter revenue (though those have their own logic). The primary driver was reach and dialogue. The feeling that the ideas worth communicating in healthcare were reaching a fraction of the people who needed them, mostly because we’d built a science communication infrastructure that made academic publishing the gold standard and everything else secondary.</p><p>AI changes the equation a bit. Not by doing the thinking. The thinking is still yours, and it’s still the most important part. But by handling enough of the operational needs that someone running a clinical practice, a research agenda, and a startup can also maintain a consistent presence in public. That’s what I want to share here: how I’ve structured that system, in enough detail that you can build your own version of it if it seems useful.</p><p>What works for me may not work for you. I can’t promise to optimize your content calendar. But I wanted to describe infrastructure that has made the practice of writing in public sustainable for me, and that has produced a lot of unexpected good in the process.</p><p>Why This Isn’t Primarily About Content Creation</p><p>A minor but important framing note before the setup details: the value I’ve gotten from Techy Surgeon isn’t primarily the newsletter metrics.</p><p>It’s the policymakers who’ve reached out. The research collaborators who found me because of a piece on care coordination. The clinicians who wrote to say that an article crystallized something they’d been trying to explain to administrators for years. The people building interesting companies in healthcare who wanted to connect because we were apparently thinking about similar problems from different angles.</p><p>None of those connections would have happened if I hadn’t been willing to put my thoughts into a form that others could interact with. And it wasn’t a white paper or journal article that did that. It was something closer to a public conversation, where the format invites response and the distribution reaches people outside the academic bubble.</p><p>I think medicine, and clinical research more broadly, is underinvested in this kind of communication. Not because clinicians don’t have things worth saying (clearly they do), but because the infrastructure for saying them publicly has been either unavailable, considered taboo, or too costly in time. AI is changing that. The skill of generating multimodal media whether written, visual, or video, is becoming something a motivated clinician can build and maintain without a full production team. We probably need more of us doing this.</p><p>The Flywheel, Briefly</p><p>Before the setup details, the concept: a content flywheel is a system where each piece of output feeds the next, and where the marginal cost of producing content decreases over time rather than remaining constant.</p><p>The alternative is what most clinician-writers default to: the brute-force model, where every piece starts from scratch, involves a Sunday afternoon staring at a blank editor, and depends entirely on having energy left over from the clinical and research work. That’s a fragile system. It produces good work occasionally and nothing the rest of the time.</p><p>The flywheel I’ve built runs on five loops: <strong>Ideate</strong> (keep a backlog so you never start from nothing), <strong>Research</strong> (get sources before you start writing, not after), <strong>Write</strong> (use AI constrained by your voice, not AI in its default state), <strong>Distribute</strong> (publish once, distribute many times across platforms), and <strong>Repurpose</strong> (one strong piece seeds two weeks of downstream content).</p><p>The setup below is how I’ve operationalized each of those loops.</p>
26 total episodes available
Deep-dive analytics for Techy Surgeon Podcast
Frequently asked questions
Have a different question and can't find the answer you're looking for? Reach out to our support team by sending us an email and we'll get back to you as soon as we can.
- What is Techy Surgeon Podcast?
- How often does this podcast release new episodes?
This podcast updates daily.
- Where can I listen to this podcast?
This podcast is available on 4 platforms including Apple Podcasts, Spotify, and more. You can also use the RSS feed directly.
- Does this podcast accept guests?
Yes, this podcast regularly features guests.
Legal Disclaimer
Pod Engine is not affiliated with, endorsed by, or officially connected with any of the podcasts displayed on this platform. We operate independently as a podcast discovery and analytics service.
All podcast artwork, thumbnails, and content displayed on this page are the property of their respective owners and are protected by applicable copyright laws. This includes, but is not limited to, podcast cover art, episode artwork, show descriptions, episode titles, transcripts, audio snippets, and any other content originating from the podcast creators or their licensors.
We display this content under fair use principles and/or implied license for the purpose of podcast discovery, information, and commentary. We make no claim of ownership over any podcast content, artwork, or related materials shown on this platform. All trademarks, service marks, and trade names are the property of their respective owners.
While we strive to ensure all content usage is properly authorized, if you are a rights holder and believe your content is being used inappropriately or without proper authorization, please contact us immediately at hey@podengine.ai for prompt review and appropriate action, which may include content removal or proper attribution.
By accessing and using this platform, you acknowledge and agree to respect all applicable copyright laws and intellectual property rights of content owners. Any unauthorized reproduction, distribution, or commercial use of the content displayed on this platform is strictly prohibited.