<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheet.css" type="text/css"?>
<?xml-stylesheet href="data:text/css,%3Aroot%7B--art%3Aurl%28%22https%3A%2F%2Fimg.transistorcdn.com%2F5MCVL1iYAk5fhn4QX-bswKMlhQA7wcgzw0cZim_F-wQ%2Frs%3Afill%3A0%3A0%3A1%2Fw%3A400%2Fh%3A400%2Fq%3A60%2Fmb%3A500000%2FaHR0cHM6Ly9pbWct%2FdXBsb2FkLXByb2R1%2FY3Rpb24udHJhbnNp%2Fc3Rvci5mbS9jZWYz%2FZjE4MTJjYjVlNWVm%2FNTJiMmI4ODkyOTNj%2FOTllMy5qcGc.webp%22%29%3B--art-scale%3A1%7D" type="text/css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:podcast="https://podcastindex.org/namespace/1.0">
  <channel>
    <atom:link rel="self" type="application/rss+xml" href="https://feeds.transistor.fm/human-factors-with-ken-catchpole-safety-and-performance-in-acute-care" title="MP3 Audio"/>
    <atom:link rel="hub" href="https://pubsubhubbub.appspot.com/"/>
    <podcast:podping usesPodping="true"/>
    <title>Human Factors with Ken Catchpole: safety and performance in acute care</title>
    <link>https://human-factors-with-ken-catchpole-safety-and-performance-in.transistor.fm</link>
    <generator>Transistor (https://transistor.fm)</generator>
    <itunes:new-feed-url>https://feeds.transistor.fm/human-factors-with-ken-catchpole-safety-and-performance-in-acute-care</itunes:new-feed-url>
    <description>How safety and performance in acute care really work, seen through human factors: teams, communication, technology, organizations and the methods used to improve them. Conversations get into specifics, from reading the rhythm of an operating room to tracking flow disruptions and learning a clinical team's language.

With Kenneth Catchpole PhD, the S.C. SmartState Endowed Chair in Clinical Practice and Human Factors. For clinicians and the teams who keep patients safe in acute care.</description>
    <copyright>© 2026 Aloudable Ltd</copyright>
    <podcast:guid>f622dc1a-cadd-56fa-a575-62dadb3f5365</podcast:guid>
    <podcast:locked>yes</podcast:locked>
    <language>en</language>
    <pubDate>Fri, 20 Nov 2026 16:39:54 +0000</pubDate>
    <lastBuildDate>Fri, 20 Nov 2026 16:40:04 +0000</lastBuildDate>
    <image>
      <url>https://img.transistorcdn.com/tHVbpx3iTeTHV1H59lXgVM8TFf5xqTSeyo5GOpB3KUg/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9jZWYz/ZjE4MTJjYjVlNWVm/NTJiMmI4ODkyOTNj/OTllMy5qcGc.jpg</url>
      <title>Human Factors with Ken Catchpole: safety and performance in acute care</title>
      <link>https://human-factors-with-ken-catchpole-safety-and-performance-in.transistor.fm</link>
    </image>
    <itunes:category text="Health &amp; Fitness">
      <itunes:category text="Medicine"/>
    </itunes:category>
    <itunes:type>episodic</itunes:type>
    <itunes:author>Ken Catchpole</itunes:author>
    <itunes:image href="https://img.transistorcdn.com/tHVbpx3iTeTHV1H59lXgVM8TFf5xqTSeyo5GOpB3KUg/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9jZWYz/ZjE4MTJjYjVlNWVm/NTJiMmI4ODkyOTNj/OTllMy5qcGc.jpg"/>
    <itunes:summary>How safety and performance in acute care really work, seen through human factors: teams, communication, technology, organizations and the methods used to improve them. Conversations get into specifics, from reading the rhythm of an operating room to tracking flow disruptions and learning a clinical team's language.

With Kenneth Catchpole PhD, the S.C. SmartState Endowed Chair in Clinical Practice and Human Factors. For clinicians and the teams who keep patients safe in acute care.</itunes:summary>
    <itunes:subtitle>How safety and performance in acute care really work, seen through human factors: teams, communication, technology, organizations and the methods used to improve them.</itunes:subtitle>
    <itunes:keywords></itunes:keywords>
    <itunes:owner>
      <itunes:name>Aloudable</itunes:name>
      <itunes:email>podcasts@aloudable.com</itunes:email>
    </itunes:owner>
    <itunes:complete>No</itunes:complete>
    <itunes:explicit>No</itunes:explicit>
    <item>
      <title>What a robot in the operating room changes for the team</title>
      <itunes:episode>4</itunes:episode>
      <podcast:episode>4</podcast:episode>
      <itunes:title>What a robot in the operating room changes for the team</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">c0deac40-cbbe-419a-aad7-0759195bfcaa</guid>
      <link>https://human-factors-with-ken-catchpole-safety-and-performance-in.transistor.fm/episodes/what-a-robot-in-the-operating-room-changes-for-the-team</link>
      <description>
        <![CDATA[<p>When the surgeon moves from the table to a console, team talk becomes remote and less shared. Ken explains why read-backs and requests by name matter more, why some teams never take them up, and what staff learned by sitting at the console themselves: the surgeon was not ignoring them, they could not hear. He describes docking as an obstacle course that needs a leader, who is not always the surgeon, and how counting flow disruptions points to fixes such as floor markings and camera warmers.</p><p>Listeners will come away with practical ideas for team training that feels like a game rather than a reprimand, including an inflatable obstacle course where teams worked out that docking is a three-person job. Ken also explains why the goal is systems that suit people rather than surgery without pauses, why blame for automation surprises should not land on the operator, and how informal tricks reveal the hidden expertise of experienced staff.</p><p>00:00 Intro<br>00:42 The surgeon disappears into the console<br>04:02 "They literally can't hear us"<br>05:54 Docking: the operation before the operation<br>09:38 What the little hiccups reveal<br>11:07 An obstacle course of inflatable robots<br>14:53 Pauses aren't the enemy<br>17:40 When the machine does more, who's responsible?<br>20:07 The hidden expertise in the room</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>When the surgeon moves from the table to a console, team talk becomes remote and less shared. Ken explains why read-backs and requests by name matter more, why some teams never take them up, and what staff learned by sitting at the console themselves: the surgeon was not ignoring them, they could not hear. He describes docking as an obstacle course that needs a leader, who is not always the surgeon, and how counting flow disruptions points to fixes such as floor markings and camera warmers.</p><p>Listeners will come away with practical ideas for team training that feels like a game rather than a reprimand, including an inflatable obstacle course where teams worked out that docking is a three-person job. Ken also explains why the goal is systems that suit people rather than surgery without pauses, why blame for automation surprises should not land on the operator, and how informal tricks reveal the hidden expertise of experienced staff.</p><p>00:00 Intro<br>00:42 The surgeon disappears into the console<br>04:02 "They literally can't hear us"<br>05:54 Docking: the operation before the operation<br>09:38 What the little hiccups reveal<br>11:07 An obstacle course of inflatable robots<br>14:53 Pauses aren't the enemy<br>17:40 When the machine does more, who's responsible?<br>20:07 The hidden expertise in the room</p>]]>
      </content:encoded>
      <pubDate>Thu, 19 Nov 2026 16:11:08 +0000</pubDate>
      <author>Ken Catchpole</author>
      <enclosure url="https://media.transistor.fm/b024b5d4/2001f8ae.mp3" length="21537151" type="audio/mpeg"/>
      <podcast:alternateEnclosure type="application/x-mpegURL" length="0" bitrate="3486045" height="1080" lang="en" title="HD Video Stream" rel="alternate">
        <podcast:source uri="https://media.transistor.fm/b024b5d4/2001f8ae.m3u8"/>
      </podcast:alternateEnclosure>
      <podcast:contentLink href="https://www.youtube.com/watch?v=r6QF-DJqMr4">Watch on YouTube</podcast:contentLink>
      <itunes:author>Ken Catchpole</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/pw9OhsERRuw4mtjOYMwoxxcVQ7FahKbPz4O7Kej7nXU/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8xYTc1/ZDVjYzgzZmU0OGI5/MjM0OGEzNDU2ZjNl/ZjdhMC5wbmc.jpg"/>
      <itunes:duration>1344</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>When the surgeon moves from the table to a console, team talk becomes remote and less shared. Ken explains why read-backs and requests by name matter more, why some teams never take them up, and what staff learned by sitting at the console themselves: the surgeon was not ignoring them, they could not hear. He describes docking as an obstacle course that needs a leader, who is not always the surgeon, and how counting flow disruptions points to fixes such as floor markings and camera warmers.</p><p>Listeners will come away with practical ideas for team training that feels like a game rather than a reprimand, including an inflatable obstacle course where teams worked out that docking is a three-person job. Ken also explains why the goal is systems that suit people rather than surgery without pauses, why blame for automation surprises should not land on the operator, and how informal tricks reveal the hidden expertise of experienced staff.</p><p>00:00 Intro<br>00:42 The surgeon disappears into the console<br>04:02 "They literally can't hear us"<br>05:54 Docking: the operation before the operation<br>09:38 What the little hiccups reveal<br>11:07 An obstacle course of inflatable robots<br>14:53 Pauses aren't the enemy<br>17:40 When the machine does more, who's responsible?<br>20:07 The hidden expertise in the room</p>]]>
      </itunes:summary>
      <itunes:keywords></itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/b024b5d4/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/b024b5d4/chapters.json" type="application/json+chapters"/>
    </item>
    <item>
      <title>What decides when a small slip in surgery escalates</title>
      <itunes:episode>3</itunes:episode>
      <podcast:episode>3</podcast:episode>
      <itunes:title>What decides when a small slip in surgery escalates</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">0f69eced-2ef1-4c70-9ccc-faf727be1005</guid>
      <link>https://human-factors-with-ken-catchpole-safety-and-performance-in.transistor.fm/episodes/what-decides-when-a-small-slip-in-surgery-escalates</link>
      <description>
        <![CDATA[<p>Ken explains why the same small error in surgery can fizzle out or snowball, depending on the system's design, the team and the patient. The question at the centre is what decides it. His answer is mostly the team's spare capacity to avoid, trap or mitigate small problems. He describes the early signs of drift, from micro miscommunications to people going quiet. He also explains why the Swiss cheese model suits heavily engineered systems better than surgery, which runs on constant adaptation.</p><p>Listeners will come away knowing how unresolved problems stack into a cascade and why preparing in advance, as pilots do, helps most. They will also see why followership, mutual support and over-communicating matter alongside leadership. Ken covers when silence in theatre is a warning and how team cohesion shapes the risk. He closes with a syringe of local anaesthetic that was stopped just in time.</p><p>00:00 Intro<br>00:42 The same error, nothing or a catastrophe<br>02:19 The first signs a team is drifting<br>04:10 Where the Swiss cheese model stops fitting surgery<br>05:23 Spare capacity: avoid, trap, mitigate<br>09:13 Leaders can't see everything<br>11:13 When two problems land at once<br>12:41 Why congenital heart surgery is less forgiving than a knee replacement<br>14:10 When silence in theatre is a warning<br>15:14 Frustration, friction and team cohesion<br>18:15 The syringe that wasn't saline</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Ken explains why the same small error in surgery can fizzle out or snowball, depending on the system's design, the team and the patient. The question at the centre is what decides it. His answer is mostly the team's spare capacity to avoid, trap or mitigate small problems. He describes the early signs of drift, from micro miscommunications to people going quiet. He also explains why the Swiss cheese model suits heavily engineered systems better than surgery, which runs on constant adaptation.</p><p>Listeners will come away knowing how unresolved problems stack into a cascade and why preparing in advance, as pilots do, helps most. They will also see why followership, mutual support and over-communicating matter alongside leadership. Ken covers when silence in theatre is a warning and how team cohesion shapes the risk. He closes with a syringe of local anaesthetic that was stopped just in time.</p><p>00:00 Intro<br>00:42 The same error, nothing or a catastrophe<br>02:19 The first signs a team is drifting<br>04:10 Where the Swiss cheese model stops fitting surgery<br>05:23 Spare capacity: avoid, trap, mitigate<br>09:13 Leaders can't see everything<br>11:13 When two problems land at once<br>12:41 Why congenital heart surgery is less forgiving than a knee replacement<br>14:10 When silence in theatre is a warning<br>15:14 Frustration, friction and team cohesion<br>18:15 The syringe that wasn't saline</p>]]>
      </content:encoded>
      <pubDate>Thu, 12 Nov 2026 16:06:08 +0000</pubDate>
      <author>Ken Catchpole</author>
      <enclosure url="https://media.transistor.fm/ed3c2f73/78f848ce.mp3" length="19325507" type="audio/mpeg"/>
      <podcast:alternateEnclosure type="application/x-mpegURL" length="0" bitrate="3502586" height="1080" lang="en" title="HD Video Stream" rel="alternate">
        <podcast:source uri="https://media.transistor.fm/ed3c2f73/78f848ce.m3u8"/>
      </podcast:alternateEnclosure>
      <podcast:contentLink href="https://www.youtube.com/watch?v=NrMD8t5W9zo">Watch on YouTube</podcast:contentLink>
      <itunes:author>Ken Catchpole</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/QUEXvVDDfcAtrwFJJ-KNyDi1t3DRddkCctI1vwCwL3E/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9kOGNk/YmVmNTc4MWExOWIw/ZTBkOWQxNDA3ZWVk/NWU3MS5wbmc.jpg"/>
      <itunes:duration>1206</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Ken explains why the same small error in surgery can fizzle out or snowball, depending on the system's design, the team and the patient. The question at the centre is what decides it. His answer is mostly the team's spare capacity to avoid, trap or mitigate small problems. He describes the early signs of drift, from micro miscommunications to people going quiet. He also explains why the Swiss cheese model suits heavily engineered systems better than surgery, which runs on constant adaptation.</p><p>Listeners will come away knowing how unresolved problems stack into a cascade and why preparing in advance, as pilots do, helps most. They will also see why followership, mutual support and over-communicating matter alongside leadership. Ken covers when silence in theatre is a warning and how team cohesion shapes the risk. He closes with a syringe of local anaesthetic that was stopped just in time.</p><p>00:00 Intro<br>00:42 The same error, nothing or a catastrophe<br>02:19 The first signs a team is drifting<br>04:10 Where the Swiss cheese model stops fitting surgery<br>05:23 Spare capacity: avoid, trap, mitigate<br>09:13 Leaders can't see everything<br>11:13 When two problems land at once<br>12:41 Why congenital heart surgery is less forgiving than a knee replacement<br>14:10 When silence in theatre is a warning<br>15:14 Frustration, friction and team cohesion<br>18:15 The syringe that wasn't saline</p>]]>
      </itunes:summary>
      <itunes:keywords></itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/ed3c2f73/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/ed3c2f73/chapters.json" type="application/json+chapters"/>
    </item>
    <item>
      <title>What the tiny hiccups in surgery reveal about safety</title>
      <itunes:episode>2</itunes:episode>
      <podcast:episode>2</podcast:episode>
      <itunes:title>What the tiny hiccups in surgery reveal about safety</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">b384ee4e-f70b-4df5-bf4d-2c04ef439246</guid>
      <link>https://human-factors-with-ken-catchpole-safety-and-performance-in.transistor.fm/episodes/what-the-tiny-hiccups-in-surgery-reveal-about-safety</link>
      <description>
        <![CDATA[<p>Ken explains what flow disruptions are: the small pauses and hiccups in an operation, from a struggle with packaging to a misheard request. He describes how observers build a picture of the ideal case by watching many procedures, why the observer is the instrument that has to be calibrated against an experienced colleague, and why rare events like a needle lost in the body cavity can say more than the numbers. The question at the centre is what these ordinary disruptions show about how surgery succeeds.</p><p>Listeners will come away knowing why almost every surgery Ken observes has missing or failing equipment, why small miscommunications are constant, and how room layout, acoustics and robotic consoles can pull sub-teams apart through nobody's fault. Ken also explains why severity is harder to judge than occurrence, and why the expertise that keeps surgery safe is hard to see, even for the clinicians who have it.</p><p>00:00 Intro<br>00:52 Hiccups, bumps and the drive home<br>03:22 The observer is the instrument<br>05:42 A phone call and a needle in the body<br>07:54 Every surgery has something broken<br>12:12 When teams drift apart<br>14:29 Small problems, big consequences<br>18:10 The expertise nobody can explain</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Ken explains what flow disruptions are: the small pauses and hiccups in an operation, from a struggle with packaging to a misheard request. He describes how observers build a picture of the ideal case by watching many procedures, why the observer is the instrument that has to be calibrated against an experienced colleague, and why rare events like a needle lost in the body cavity can say more than the numbers. The question at the centre is what these ordinary disruptions show about how surgery succeeds.</p><p>Listeners will come away knowing why almost every surgery Ken observes has missing or failing equipment, why small miscommunications are constant, and how room layout, acoustics and robotic consoles can pull sub-teams apart through nobody's fault. Ken also explains why severity is harder to judge than occurrence, and why the expertise that keeps surgery safe is hard to see, even for the clinicians who have it.</p><p>00:00 Intro<br>00:52 Hiccups, bumps and the drive home<br>03:22 The observer is the instrument<br>05:42 A phone call and a needle in the body<br>07:54 Every surgery has something broken<br>12:12 When teams drift apart<br>14:29 Small problems, big consequences<br>18:10 The expertise nobody can explain</p>]]>
      </content:encoded>
      <pubDate>Fri, 06 Nov 2026 12:24:30 +0000</pubDate>
      <author>Ken Catchpole</author>
      <enclosure url="https://media.transistor.fm/472cf7e7/3594be26.mp3" length="19557533" type="audio/mpeg"/>
      <podcast:alternateEnclosure type="application/x-mpegURL" length="0" bitrate="3487690" height="1080" lang="en" title="HD Video Stream" rel="alternate">
        <podcast:source uri="https://media.transistor.fm/472cf7e7/3594be26.m3u8"/>
      </podcast:alternateEnclosure>
      <podcast:contentLink href="https://www.youtube.com/watch?v=29HBtXSKLM0">Watch on YouTube</podcast:contentLink>
      <itunes:author>Ken Catchpole</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/gYWVY2S04DaVMTEpQdPLYZwTMQH8JpAyNDTuGeXNGsQ/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS85MDAw/YzM3NzNkNzg3NDFj/MWUwZjZjZTg1MGQ1/OTVkNi5wbmc.jpg"/>
      <itunes:duration>1220</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Ken explains what flow disruptions are: the small pauses and hiccups in an operation, from a struggle with packaging to a misheard request. He describes how observers build a picture of the ideal case by watching many procedures, why the observer is the instrument that has to be calibrated against an experienced colleague, and why rare events like a needle lost in the body cavity can say more than the numbers. The question at the centre is what these ordinary disruptions show about how surgery succeeds.</p><p>Listeners will come away knowing why almost every surgery Ken observes has missing or failing equipment, why small miscommunications are constant, and how room layout, acoustics and robotic consoles can pull sub-teams apart through nobody's fault. Ken also explains why severity is harder to judge than occurrence, and why the expertise that keeps surgery safe is hard to see, even for the clinicians who have it.</p><p>00:00 Intro<br>00:52 Hiccups, bumps and the drive home<br>03:22 The observer is the instrument<br>05:42 A phone call and a needle in the body<br>07:54 Every surgery has something broken<br>12:12 When teams drift apart<br>14:29 Small problems, big consequences<br>18:10 The expertise nobody can explain</p>]]>
      </itunes:summary>
      <itunes:keywords></itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/472cf7e7/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/472cf7e7/chapters.json" type="application/json+chapters"/>
    </item>
    <item>
      <title>What an engineer with no medical training saw in heart surgery</title>
      <itunes:episode>1</itunes:episode>
      <podcast:episode>1</podcast:episode>
      <itunes:title>What an engineer with no medical training saw in heart surgery</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">a291b393-2ef1-4ca1-84ed-8e5d4afb2df3</guid>
      <link>https://human-factors-with-ken-catchpole-safety-and-performance-in.transistor.fm/episodes/what-an-engineer-with-no-medical-training-saw-in-heart-surgery</link>
      <description>
        <![CDATA[<p>Ken explains what he saw when he joined a congenital heart surgery team at Great Ormond Street having barely been in a hospital. It took him six or seven months of observing before he knew what a case should look like and could spot the deviations. One moment made it clear: a trainee anaesthetist paused when the surgeon said "Shoot", and in that pause Ken saw missing preparation and no shared language. The question at the centre is why skilled people trying their hardest can still cause harm, and why that systems view remains hard for healthcare to accept.</p><p>Ken explains how he learned to read tension in a room and why he observes before asking. He describes building trust by learning each group's language, taking an interest the perfusionists had never had, and playing the student. He also outlines flow disruptions and the cues that show whether a case is going well or badly.</p><p>00:00 Intro<br>00:41 An engineer on day one at Great Ormond Street<br>02:57 "Shoot": the pause that showed the system<br>06:44 Not the people, the setup<br>10:20 Learning to speak surgery<br>13:56 Flow disruptions and the engineer's eye</p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p>Ken explains what he saw when he joined a congenital heart surgery team at Great Ormond Street having barely been in a hospital. It took him six or seven months of observing before he knew what a case should look like and could spot the deviations. One moment made it clear: a trainee anaesthetist paused when the surgeon said "Shoot", and in that pause Ken saw missing preparation and no shared language. The question at the centre is why skilled people trying their hardest can still cause harm, and why that systems view remains hard for healthcare to accept.</p><p>Ken explains how he learned to read tension in a room and why he observes before asking. He describes building trust by learning each group's language, taking an interest the perfusionists had never had, and playing the student. He also outlines flow disruptions and the cues that show whether a case is going well or badly.</p><p>00:00 Intro<br>00:41 An engineer on day one at Great Ormond Street<br>02:57 "Shoot": the pause that showed the system<br>06:44 Not the people, the setup<br>10:20 Learning to speak surgery<br>13:56 Flow disruptions and the engineer's eye</p>]]>
      </content:encoded>
      <pubDate>Fri, 30 Oct 2026 16:25:24 +0000</pubDate>
      <author>Ken Catchpole</author>
      <enclosure url="https://media.transistor.fm/b066495d/8364a66e.mp3" length="16287279" type="audio/mpeg"/>
      <podcast:alternateEnclosure type="application/x-mpegURL" length="0" bitrate="3473112" height="1080" lang="en" title="HD Video Stream" rel="alternate">
        <podcast:source uri="https://media.transistor.fm/b066495d/8364a66e.m3u8"/>
      </podcast:alternateEnclosure>
      <podcast:contentLink href="https://www.youtube.com/watch?v=dNSNLh8JENI">Watch on YouTube</podcast:contentLink>
      <itunes:author>Ken Catchpole</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/PaWvtDETE25UZ7Z8-odHlkZYvvs8xd-uUBGfGJhhjWc/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9iOTMx/MjU0ZmRjOTEwNTBk/NDdiNWYyYzZmNzBk/YjNlNi5wbmc.jpg"/>
      <itunes:duration>1016</itunes:duration>
      <itunes:summary>
        <![CDATA[<p>Ken explains what he saw when he joined a congenital heart surgery team at Great Ormond Street having barely been in a hospital. It took him six or seven months of observing before he knew what a case should look like and could spot the deviations. One moment made it clear: a trainee anaesthetist paused when the surgeon said "Shoot", and in that pause Ken saw missing preparation and no shared language. The question at the centre is why skilled people trying their hardest can still cause harm, and why that systems view remains hard for healthcare to accept.</p><p>Ken explains how he learned to read tension in a room and why he observes before asking. He describes building trust by learning each group's language, taking an interest the perfusionists had never had, and playing the student. He also outlines flow disruptions and the cues that show whether a case is going well or badly.</p><p>00:00 Intro<br>00:41 An engineer on day one at Great Ormond Street<br>02:57 "Shoot": the pause that showed the system<br>06:44 Not the people, the setup<br>10:20 Learning to speak surgery<br>13:56 Flow disruptions and the engineer's eye</p>]]>
      </itunes:summary>
      <itunes:keywords></itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/b066495d/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/b066495d/chapters.json" type="application/json+chapters"/>
    </item>
  </channel>
</rss>
