How to Explain Complicated Information Without Oversimplifying It
I have spent a lot of my career writing about subjects most people do not understand until they suddenly have to.
Healthcare. Mortgage underwriting. Regulatory compliance. Software. Financial products. Medical treatments with safety warnings longer than the actual explanation of what the treatment does.
The challenge is rarely that the information is impossible to understand. The challenge is that the person explaining it already understands it so well that they have forgotten what it feels like to encounter it for the first time.
You see this constantly in technical and regulated content. The writer includes every relevant fact, uses the correct terminology, gets approval from the subject matter expert, and still produces something the intended reader cannot use.
The usual response is to simplify it.
That often makes the problem worse.
Important details disappear. Qualifications get stripped out. Different concepts get collapsed into one vague explanation. The final content sounds easier to read, but the reader walks away with an incomplete or inaccurate understanding of what is happening.
Clear content should help readers understand the complexity. It should not hide the complexity from them.
Why Complicated Information Becomes Unclear
A lot of complicated content is written according to the structure of the subject instead of the needs of the reader.
Imagine someone is trying to understand whether a medication might be appropriate for them. The company has information about how the drug works, who participated in clinical trials, possible side effects, contraindications, dosing schedules, insurance requirements, and how long it may take to see results.
All of that information matters.
The reader probably starts with much more immediate questions:
What is this supposed to help with?
How is it different from what I am already taking?
What will I physically have to do?
What could go wrong?
How much is this going to cost me?
What happens if it does not work?
When we organize the page around the company’s internal understanding of the product, the reader has to dig through layers of information before reaching the part that matters to them.
That is where people get lost.
The same thing happens with mortgage content. A lender may want to begin by explaining loan types, underwriting standards, debt-to-income ratios, and documentation requirements. The reader may simply want to know why the lender asked for another bank statement after they already submitted three.
The information is connected, but the order matters.
Start With What the Reader Is Trying to Do
Before I explain a complicated subject, I identify the decision the reader is trying to make.
They may be deciding whether to:
Schedule an appointment
Apply for a service
Choose between two products
Continue reading
Gather documentation
Call customer support
Ask their doctor a question
Discuss an option with their employer
Take an immediate safety precaution
Once I know the decision, I can work backward and determine what the reader needs to understand before making it.
This helps me separate essential information from information that is merely available.
That does not mean the secondary details should disappear. It means they need to be placed where they support understanding instead of interrupting it.
A person comparing health plans may need a plain explanation of deductibles before they need the historical background of the insurance model. Someone troubleshooting software may need the two most likely fixes before they need a technical explanation of what caused the error.
Writers often worry that prioritizing the reader’s immediate question will make the content feel shallow. In practice, it gives the deeper information somewhere useful to go.
Build an Information Hierarchy
Readers can understand a great deal of complexity when the information arrives in a sensible order.
I usually think about complicated content in layers.
Layer One: What is happening?
Give the reader the basic situation in ordinary language.
For example:
A prior authorization is a requirement from your insurance company. Your doctor has to provide additional information before the company decides whether it will cover the treatment.
That explanation is incomplete, but it gives the reader a usable starting point.
Layer Two: Why does it matter?
Explain how the concept affects the reader.
Until the authorization is approved, the pharmacy may be unable to fill the prescription at the covered price.
Now the reader understands why the issue is delaying their care.
Layer Three: What happens next?
Give the reader a realistic process.
Your doctor’s office usually submits the request. The insurer may approve it, deny it, or ask for more documentation. You can contact both the insurer and the doctor’s office to check the status.
Layer Four: What are the exceptions or complications?
This is where the necessary nuance belongs.
Approval does not guarantee that the medication will be free. Your deductible, copayment, coinsurance, pharmacy network, and plan rules may still affect the final cost.
Each layer adds complexity without forcing the reader to absorb everything at once.
Define Terms When the Reader Needs Them
Glossaries can be useful, but I do not want readers to keep leaving the paragraph to look up the words I just used.
If a technical term is necessary, I define it at the point of use.
For example:
Coinsurance is the percentage of a covered medical bill that you pay after meeting your deductible.
That is more useful than writing an entire paragraph with the assumption that the reader already understands coinsurance, then adding a glossary definition at the bottom of the page.
I also avoid replacing every precise term with a vague synonym. Sometimes the reader needs to learn the real word because they will see it again on a bill, form, contract, medication guide, or customer portal.
The goal is to introduce the terminology without making the reader feel like they walked into the middle of a conversation.
Preserve the Details That Change the Meaning
This is where a lot of “plain language” content fails.
A writer removes the words that seem technical, and the sentence becomes less accurate.
Consider the difference between these two claims:
This treatment prevents migraines.
This treatment may reduce the number of migraine days for some patients.
The second sentence has more qualifications because the qualifications matter. Removing them would create a much stronger claim than the evidence supports.
The answer is not to bury the reader in disclaimers. The answer is to explain uncertainty clearly.
You can write:
The treatment does not work for everyone. In clinical studies, some patients experienced fewer migraine days, while others did not see a meaningful improvement.
That gives the reader a more realistic understanding without requiring them to decode statistical language.
The same principle applies outside healthcare.
A mortgage rate is not simply “the rate you will receive.” It may depend on credit, loan type, down payment, property details, market conditions, and lender requirements.
A software feature is not always “available to all users.” It may depend on the plan, region, device, permissions, or rollout schedule.
Those details should remain visible whenever they could change the reader’s decision.
Use Examples That Clarify the Rule
Examples are one of the best ways to explain complicated information, but they can also create false certainty.
Suppose you are explaining a deductible:
If your deductible is $2,000, you pay the first $2,000 of all healthcare expenses.
That sounds clear. It is also likely to mislead someone because many plans cover certain services before the deductible, and not every charge applies to it in the same way.
A better example would be:
Imagine your plan has a $2,000 deductible. You may have to pay the negotiated cost of many services until your deductible is met. Some services, such as preventive care, may be covered differently. Your plan documents explain which expenses count toward the deductible.
The example still helps the reader picture the process. It also shows where the example stops applying.
I try to make examples specific enough to be useful and limited enough to remain honest.
Write for the Reader’s Actual State of Mind
People rarely read complicated information under ideal conditions.
They are reading because something happened.
They received a medical diagnosis. Their loan was delayed. Their software stopped working. Their child needs treatment. Their insurance denied a claim. Their company has a compliance problem. Their bill is higher than expected.
Stress changes the way people process information. Readers scan more. They miss qualifications. They have less patience for background information. They may interpret neutral language as threatening because they are already worried.
This affects the structure of the content.
Important actions should be easy to locate. Deadlines should not be hidden in the sixth paragraph. Safety information should appear where the reader is likely to see it. The most common question should not require opening four accordions and downloading a PDF.
Empathy in content is often treated as a matter of tone. Tone matters, but organization is part of empathy too.
A calm voice does not help much when the reader still cannot figure out what to do.
Avoid Writing for the Subject Matter Expert
Subject matter experts are essential. They protect accuracy and catch mistakes that writers cannot always see.
They are also unusually familiar with the subject.
A sentence can feel perfectly clear to a healthcare executive, attorney, engineer, or product manager because they already know what every term means and how the concepts connect.
That does not make them a good proxy for the audience.
When I work with experts, I want them to answer questions such as:
Is this accurate?
What important qualification is missing?
Could this example create the wrong impression?
What would cause this process to work differently?
Which part of this explanation would concern you if a customer misunderstood it?
I do not want the final content to read like internal documentation simply because internal reviewers approved it.
Accuracy review and audience review serve different purposes. Good content needs both.
Test Whether the Content Is Actually Clear
Readability scores can identify long sentences and complicated words. They cannot tell you whether the explanation makes sense.
A page can earn an excellent readability score and still leave the reader confused.
I prefer questions that test understanding:
Can the reader explain the concept in their own words?
Can they identify what they need to do next?
Can they tell which parts apply to everyone and which depend on individual circumstances?
Can they recognize the most important limitation?
Can they find the answer again without rereading the entire page?
Would they know what question to ask a professional after reading?
When possible, I ask someone unfamiliar with the subject to read the content and tell me what they think it means.
I do not ask, “Was this clear?”
Most people will say yes.
I ask them to explain it back to me. That is where the gaps appear.
Example: Turning Technical Information Into Useful Information
Here is the kind of sentence you often see in financial or healthcare content:
Eligibility is contingent upon satisfaction of applicable underwriting requirements and verification of all requested documentation.
The sentence is technically respectable. It is also difficult to use.
A clearer version might be:
You are not fully approved until the company reviews the required documents and confirms that you meet its eligibility rules.
Depending on the context, I may add:
The company may ask for additional records before making a final decision.
The meaning remains intact. The reader now understands that an initial application or estimate is not a final approval, and that more paperwork may be required.
That is the work.
You identify what the sentence actually means, what the reader could misunderstand, and which details need to remain.
A Practical Process for Explaining Complicated Subjects
When I am working on a difficult topic, I use a process like this:
1. Learn the subject well enough to recognize what matters
I read primary sources, product documentation, regulations, studies, internal materials, and expert feedback. I do not start rewriting while I am still guessing.
2. Identify the reader’s decision or problem
The content needs a reason to exist beyond “we have information to share.”
3. List the facts that could change the reader’s decision
These are the details that cannot be removed for convenience.
4. Organize the information in the order the reader needs it
That order may be very different from the order in which the company stores or discusses the information internally.
5. Introduce technical terms with immediate explanations
Use the real terminology when it will help the reader navigate the subject later.
6. Add examples and identify their limits
Show the concept in practice without implying that every situation works the same way.
7. Review for misunderstanding, not just inaccuracy
A sentence can be factually correct and still lead readers toward the wrong conclusion.
8. Give the reader a next step
Complicated information becomes more manageable when the reader knows what to do with it.
Readers Can Handle Complexity
Writers sometimes underestimate readers.
People learn complicated systems all the time when those systems become relevant to their lives. They learn medication schedules, special education rules, mortgage requirements, tax forms, software platforms, legal processes, and insurance terminology.
They do not need us to pretend those systems are simple.
They need someone to guide them through the parts that matter, explain how the pieces connect, and warn them where the answer depends on individual circumstances.
That is what good content does.
It does not remove every difficult detail. It gives the reader enough structure to understand why the detail matters.
