A patient-information team that runs a cardiology website has a recurring problem: someone new joins, learns how pages are drafted, reviewed and published, and within a month has forgotten half of it. We compared three common ways of fixing a new process in memory, namely rereading notes, shadowing a colleague and writing the process up for the next newcomer. This comparison looks at each on what they cost, what they reveal and how well the learning holds. It concerns editorial and administrative workflow only, not clinical content.<\/p>\n
Before comparing methods, it helps to separate recognising a process from being able to explain it. Recognition is the feeling that a step looks familiar when you see it. Explanation is the ability to state the step, give its reason and predict what happens if it is skipped. Teams often confuse the two, because a new colleague can follow along in a meeting and appear to understand. The real test is the quiet moment when nobody is prompting them.<\/p>\n
Learning research has described this gap for decades in general terms: material that feels familiar after rereading is often not the material you can retrieve unaided, and explaining something to another person forces retrieval. We are not citing a figure here, because we do not need one. The practical point is that the three methods below sit at different places on that spectrum.<\/p>\n
Cost:<\/strong> low. The notes already exist, and it takes only time.<\/p>\n What it reveals:<\/strong> very little. Rereading produces fluency, and fluency feels like knowledge. A reader can finish a review checklist feeling confident and then freeze the first time a reviewer asks why a step precedes another.<\/p>\n How well it holds:<\/strong> weakest of the three, in our experience. It is useful as a refresher once the basics are in place, but as a primary method it tends to leave gaps undiscovered until a live task exposes them.<\/p>\n Cost:<\/strong> moderate, and it falls on the colleague, who loses focus time.<\/p>\n What it reveals:<\/strong> a great deal about the texture of the work, the shortcuts, the judgement calls and the tone of conversations with reviewers. Shadowing shows how the process feels in motion.<\/p>\n How well it holds:<\/strong> good for context, uneven for detail. The shadow sees the process through the other person’s habits, which can include undocumented workarounds the newcomer then mistakes for rules. Without a second step that makes the learner reconstruct what they saw, much of it fades.<\/p>\n Cost:<\/strong> moderate. A page takes an hour or two, plus a senior colleague’s time to review it.<\/p>\n What it reveals:<\/strong> the most. The act of explaining the process to an imagined beginner immediately shows which steps you cannot justify, which words you use inconsistently and which handovers you never followed to the end. The gaps surface while the learner is still new enough to ask without embarrassment.<\/p>\n How well it holds:<\/strong> strongest, because it combines retrieval, organisation and a real audience. It also produces something that outlasts the learner: the next person starts from a page written by someone who remembers being confused.<\/p>\n We should be honest about limits. This is a comparison from one team’s experience plus well-established general principles, not a controlled study, and a different team may weigh the costs differently. The write-up method also carries a risk: a confident but wrong page can mislead the next reader. That is why every page is reviewed by someone senior before it is shared, and why each one is dated.<\/p>\n The methods are not rivals so much as stages. Our current routine runs like this: a newcomer shadows for a short period to absorb the context, writes a one-page explanation within a few days while confusion is still fresh, and then rereads that page at set intervals as a check on their own memory. A senior colleague reviews the page and answers the questions it raises. By the end, the learner has seen the process, explained it and verified it.<\/p>\n One surprise was how much the written page improved the shadowing. Once newcomers knew they would have to explain what they watched, they paid closer attention and asked sharper questions mid-task. Knowing you will teach changes how you learn.<\/p>\n Internal process pages belong in internal tools. But the same write-up habit travels well, and plenty of people publish their lessons as they go. MyBlogPad<\/a> is a blogging network that offers every blog its own subdomain, supports multiple contributors and has Discover and Latest pages for browsing, and it describes itself as free with no credit card. A team might use it to compare notes in public on anything outside patient confidentiality, such as general lessons about writing clearly.<\/p>\n On this site, the pieces we publish about heart conditions are written to explain terms to non-specialists, and each had to be understood by its writer before it could be explained to anyone else. For example, our overview of the way cardiologists grade everyday functional limits<\/a> and the companion note on how murmur grading is explained<\/a> are reference-style articles, informational only and never a substitute for a clinician’s judgement. Writing in that register is itself a lesson in teaching what you know: define the term, give its context, state its limits.<\/p>\n You do not need elaborate metrics. Three simple observations will tell you whether it is working. First, count how many questions a newcomer asks in their second week compared with the first, and note whether the questions have become more specific. Second, ask a reviewer whether the page still matches what the team actually does, and record every correction. Third, ask the next newcomer to rate how much of the page they needed to rewrite. A shrinking rewrite is a sign the team’s shared understanding is stabilising.<\/p>\n If you must choose one method with limited time, choose the write-up, and pair it with enough shadowing to give it substance. Rereading is a fine refresher but a poor foundation. The decisive advantage of explaining a process to a beginner is that it turns hidden uncertainty into visible questions, and visible questions can be answered. Whatever your team’s process is, try writing three paragraphs about it for a stranger this week and see what you discover you did not know.<\/p>\n","protected":false},"excerpt":{"rendered":" A comparison of three ways a patient-information team fixes a new workflow in memory, and why explaining it to the next newcomer exposes the most gaps.<\/p>\n","protected":false},"author":5,"featured_media":867,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[392],"tags":[],"class_list":["post-866","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-healthcare-it"],"_links":{"self":[{"href":"https:\/\/heartcareforyou.in\/blog\/wp-json\/wp\/v2\/posts\/866","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/heartcareforyou.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/heartcareforyou.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/heartcareforyou.in\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/heartcareforyou.in\/blog\/wp-json\/wp\/v2\/comments?post=866"}],"version-history":[{"count":1,"href":"https:\/\/heartcareforyou.in\/blog\/wp-json\/wp\/v2\/posts\/866\/revisions"}],"predecessor-version":[{"id":929,"href":"https:\/\/heartcareforyou.in\/blog\/wp-json\/wp\/v2\/posts\/866\/revisions\/929"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/heartcareforyou.in\/blog\/wp-json\/wp\/v2\/media\/867"}],"wp:attachment":[{"href":"https:\/\/heartcareforyou.in\/blog\/wp-json\/wp\/v2\/media?parent=866"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/heartcareforyou.in\/blog\/wp-json\/wp\/v2\/categories?post=866"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/heartcareforyou.in\/blog\/wp-json\/wp\/v2\/tags?post=866"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Method two: shadowing a colleague<\/h2>\n
Method three: writing it up for the next newcomer<\/h2>\n
Side-by-side summary<\/h2>\n
\n
Combining the methods<\/h2>\n
A public place for a lesson of your own<\/h2>\n
Applying it to a cardiology information site<\/h2>\n
What to measure if you adopt the write-up method<\/h2>\n
Conclusion<\/h2>\n