Why Your History Content Reads Like A Textbook (And How To Fix It)
I spent three years building a history newsletter before anyone actually finished reading past the first paragraph. The problem wasn't the research. The research was solid. The problem was that I was writing like I had just finished a dissertation and everyone else had too. That's the default mode most history writers fall into, and it kills engagement faster than anything else. History In Plain Language is basically the practice of taking actual historical events and explaining them the way you would explain them to someone at a bar who asked a casual question. Not dumbed down. Just not written for academics. There is a meaningful difference between those two things that most people conflate until their audience bails.
The Core Principle Behind History In Plain Language
The rule is simple: if you had to explain a footnote to make your point land, you're doing it wrong. A footnote exists because the detail is either too tangential or too technically specific for the main narrative. When you start including footnotes in your actual prose, you're admitting that your explanation depends on academic scaffolding rather than standing on its own. I learned this the hard way during a piece about the Treaty of Westphalia. I had about fourteen pages of background context ready to go, mostly because every source I read assumed the reader already understood the broader Thirty Years War framework. The draft ended up being something like 6,000 words of context-setting before I even mentioned the treaty itself. My editor told me to cut it down to under 1,200 words or it was going nowhere. So I spent two days stripping out everything that required prior knowledge and rewriting each section so that the concept introduced itself without assumptions. The workaround I use now is the rubber duck test. I read my draft out loud to an empty room. If I catch myself saying something like "as you know" or "clearly" or "obviously," that's where I've relied on assumed knowledge. Those words are red flags. Replace them with the actual explanation you were implicitly skipping over.
Common Mistakes That Make History Sound Boring
The biggest mistake is date stacking. When you load three dates into one sentence, the reader's brain stops processing the actual event and starts treating the text like a spreadsheet. "In 1347, 1348, and 1349, the plague spread across Europe" is factual but it reads like a database export. Pick the most important year. Mention the others only if they fundamentally change the story. Another mistake is treating historical figures like they're your contemporaries in a modern workplace. Calling Henry VIII a "toxic boss" isn't plain language. It's lazy. It's also inaccurate because it maps a modern management concept onto a sixteenth-century monarch whose entire political reality was different. Plain language doesn't mean anachronistic shorthand. It means using clear, specific terms that actually describe what happened without translating everything into modern corporate-speak. Terminology is a minefield too. Words like "feudalism," "mercantilism," and "absolutism" carry specific academic meanings that most general readers won't have. If you use them, you have to define them in the moment, not in a glossary at the end. I've seen entire articles skip definitions entirely and just assume the reader knows what "feudal obligation" entails. That assumption costs you readers every single time.
Get the Full Details
What Actually Works In Practice
Start with the event, not the context. Lead with what happened and why it mattered to someone living through it, then layer in the background information as you go. This is the reverse of how history papers are structured, and that's exactly why it works better for general audiences. Use active voice consistently. Passive constructions are where ambiguity hides. "Mistakes were made" tells the reader nothing useful. "Louis XVI signed the edict despite his ministers advising against it" tells them exactly what happened and who was responsible. Specificity builds trust faster than vague hedging ever will. Paragraph length matters more than people realize. When your paragraphs run past four or five sentences, readers tend to drift. I keep my paragraphs to roughly 80 to 120 words. That's not a rule carved in stone, but it's a target that forces me to break ideas into digestible chunks instead of dumping entire arguments into one block of text.
When I need to explain something dense, like the succession crisis after Edward the Confessor's death, I map it out visually first. A quick timeline or relationship diagram on paper helps me identify which details are essential and which are noise. What I usually find is that about 60 percent of my initial research is background fluff that the reader doesn't actually need to understand the core story. Cutting that fluff is where the real work happens.
The Uncomfortable Truth About History In Plain Language
It does not scale to every topic. Complex subjects with overlapping causes, numerous actors, and contested interpretations resist simplification without becoming misleading. The Protestant Reformation, for example, cannot be accurately summarized in a thousand words without losing critical nuance. In those cases, the honest move is to acknowledge the complexity upfront and guide the reader toward longer-form resources rather than pretending a short piece can do justice to the subject. There is also a tension between accuracy and readability that rarely gets discussed. Sometimes the plain-language version of a historical claim is slightly less precise than the academic version. If you say "the Romans built roads to move troops faster," you've captured the general idea. But you've also omitted the logistical networks, provincial administration, and economic factors that made road building a sustained imperial project rather than a simple military decision. The tradeoff is real. You need to decide which level of precision your audience actually needs, and be honest about what you're leaving out. The alternative when plain language fails you is structured depth. Instead of compressing a complex topic, link to a well-researched long-form piece and write a focused companion article that explains one specific angle in accessible terms. This is what most successful history writers end up doing. They pick a narrow entry point into a broader subject and let the reader decide how deep they want to go.
