Explaining a Procedure in Plain English: Practice With The Good Doctor
You know the technical words. The problem is that the person listening does not. So you explain more, add three acronyms, throw in a passive sentence, and somehow make the explanation less clear. The fix is not “dumb it down.” It is to translate expertise into a sequence the listener can actually use.
The Procedure Translation Loop
- Permission: check that you may begin or examine.
- Purpose: say why the procedure or step is needed.
- Steps: give only the important actions, in order.
- Risk: name meaningful uncertainty and consequences honestly.
- Options: explain trade-offs or alternatives when relevant.
- Questions: make it easy to interrupt and clarify.
- Teach-back: check what the listener understood in their own words.
- Update: if something changes, give the headline first, then the details.
This loop works in healthcare, but it also transfers to IT support, banking, onboarding, repairs, safety briefings, and any situation where one person knows the process and the other person has to decide what to do next.
Start with permission, not momentum
Okay if we take a look?
This is short, ordinary English, but it does an important job: it checks permission before the examination. In high-pressure communication, clarity is not only about vocabulary. It is also about agency.
For practice outside medicine, the same move is easy to transfer: “Is it okay if I open the settings and check the account permissions?” or “Can I show you what I’m going to change before I change it?”
Purpose before detail
A weak explanation starts with machinery. A useful explanation starts with the reason.
If there's a cardiac issue,
The conditional sets up the problem. The next phrase gives the purpose of monitoring:
an early warning.
That is the plain-English payoff. The listener does not need a lecture on the device before understanding why it is there.
The AHRQ Health Literacy Universal Precautions Toolkit, Tool 4 recommends plain, nonmedical language, concrete explanations, slower delivery, encouragement of questions, and limiting the message to a small number of key points rather than unloading everything at once.
Give the steps in a human-sized sequence
We'll drain the abscess,
The useful feature is not the medical noun. It is the structure: we will + concrete action. The listener knows what is going to happen next.
which will allow us to remove
This links one step to the next by explaining what the first step makes possible. Procedure explanations become much easier to follow when every step answers either what happens? or why does that happen?
and we must be certain that
This is a safety-check frame. It tells the listener that the next information is not random detail; it is something that has to be confirmed before proceeding.
a full run-through.
A run-through is a complete rehearsal or step-by-step review. It is useful language whenever a process is complicated enough that the team should review it from beginning to end first.
Jargon is allowed. Untranslated jargon is the problem.
What's that?
This is the listener’s emergency brake. Learners often think they need a polished question such as “Would you mind elaborating on the terminology?” You usually do not. What’s that?, What does that mean?, and Could you say that in simpler words? are enough.
while I excise the tumor.
Excise is a technical verb. In a plain-English explanation, the useful repair is immediate: “excise — in other words, surgically remove or cut out.” If the medical term matters, you can keep it. Just do not mistake naming the term for explaining the term.
It's not cancerous, but it is
This is a strong communication shape because it avoids a common trap: reassurance that accidentally erases the remaining problem. The pattern is correct the feared interpretation + but + explain what still matters.
Risk language: precise without pretending to know the future
There's a high chance
This introduces probability rather than certainty. If you do not have a reliable number, do not invent one just to sound precise.
which could have
Could is doing important work: it marks a possible consequence. In professional explanations, modal verbs such as could, may, and might help keep the certainty level honest.
we could mitigate them.
Mitigate means reduce or manage the severity or likelihood of a problem. It is perfectly good professional English, but for a non-specialist listener, “we may be able to reduce the risk” is usually clearer.
This doesn't completely
Start by naming the limitation.
but it does reduce
Then name the narrower benefit. That two-part structure is much safer than saying a measure “makes it safe” when risk still remains.
Do not hide the trade-off after the recommendation
We need to remove the tumor,
This gives the proposed action clearly.
but to do that,
This signals the cost, condition, or consequence attached to that action. It is a very reusable bridge: Here is what we recommend — but to do that, here is what it involves.
You'll lose all feeling
In the fictional case, the line states a serious consequence directly. The transferable lesson is not to copy the medical claim. It is to state major consequences plainly and to match your certainty to the evidence you actually have.
The AMA Code of Medical Ethics on informed consent describes informed consent as a communication process and says physicians should explain the nature and purpose of recommended interventions, burdens and risks, expected benefits, and available options, including forgoing treatment, while supporting an independent voluntary decision. That is a useful communication boundary here; exact legal requirements still depend on jurisdiction and setting.
Empathy should sit beside information, not replace it
I know this hurts,
This acknowledges what the listener is experiencing.
but I really do need
This returns to the necessary step. Together, the pattern is: acknowledge discomfort → explain necessity → say what happens next. That is clearer than either cold instruction or vague reassurance.
I'm so sorry.
After difficult information, a simple expression of sympathy can be enough. It should not be followed by a promise you cannot make.
Questions are part of the explanation
Any other questions?
This opens a door. An even stronger writer-original version is “What questions do you have?” because it assumes questions are normal rather than asking for a yes/no response.
AHRQ’s Teach-Back Method, Tool 5 goes one step further: instead of relying on “Do you understand?”, ask the person to explain the key information back in their own words. The goal is to check how clearly you explained it, not to test the listener.
Teach-back practice
Writer-original: “I want to make sure I explained that clearly. Could you tell me what will happen first and what the main risk is?”
That question checks two concrete things: sequence and risk. If the answer is off, rephrase the explanation rather than repeating the same jargon louder. Medical communication does not improve through volume. Revolutionary concept, apparently.
After the procedure: headline first
There was a complication
This gives the headline before the mechanism. For a worried listener, that ordering matters: first say what changed; then explain what happened, what it means, what is being done now, and what remains uncertain.
It is her decision.
In the fictional discussion, this is an agency statement. Treat it as communication evidence, not a universal legal rule. In real healthcare, decision-making authority, capacity, surrogacy, emergencies, and consent rules depend on the situation and local law or policy.
The Plain-English Converter
Try these before opening the model answer.
Medical jargon: “We will excise the lesion and monitor you for postoperative complications.”
Writer-original plain English: “We’ll remove the abnormal area. Afterward, we’ll watch for problems that can happen after the procedure.”
Risk language: “This intervention significantly mitigates the primary risk but does not eliminate adverse-event potential.”
Writer-original plain English: “This can lower the main risk, but it cannot remove every risk.”
IT procedure: “We’ll rotate your credentials, revoke active sessions, and re-provision the account.”
Writer-original plain English: “First, we’ll change your sign-in credentials. Then we’ll sign the account out everywhere and set access up again. You may need to log back in on each device.”
A 30-second procedure explanation template
“Is it okay if I explain what we’re planning to do? The reason is ____. First, we’ll ____. Then we’ll ____. The main benefit we expect is ____. The main risk or limitation is ____. Another option is ____. What questions do you have? I want to make sure I explained it clearly — could you tell me what you expect to happen first?”
You do not need to force every procedure into exactly eight sentences. The loop is a diagnostic tool: if an explanation feels muddy, check what is missing. No purpose? Too many steps? Risk hidden behind jargon? No room for questions? No understanding check?
Practice the translation loop with FunFluen
After you can spot the structure, FunFluen can turn scenes into active practice: Smart Auto-Pause gives you time to reformulate a technical line, dual subtitles and the hover dictionary help isolate the blocking term, saved phrases let you collect explanation patterns, and speaking practice, AI Coach, or Live AI Talk can challenge you to explain the same procedure to a patient, a colleague, or a complete beginner.
The target is not “simple English” for its own sake. It is English that lets the listener understand the purpose, follow the sequence, see the real risk, ask back, and make the next decision without needing a decoder ring.
Current communication references: AHRQ — Communicate Clearly, Tool 4 · AHRQ — Use the Teach-Back Method, Tool 5 · AMA Code of Medical Ethics — Informed Consent.
Explore more language-learning guides in FunFluen Learn.