Writing Mistakes Explained: Why Professional Communication Fails
In 2003, the Columbia space shuttle broke apart during re-entry, killing all seven crew members. The subsequent investigation revealed a disturbing detail: NASA engineers had identified the foam strike damage that ultimately caused the disaster. They communicated this information to management. But they communicated it in a PowerPoint slide so dense and poorly organized that the critical risk data was buried in nested bullet points three levels deep.
Edward Tufte, the information design professor at Yale, later analyzed that slide in his essay The Cognitive Style of PowerPoint. He demonstrated that the same data, presented with clear writing, would have made the danger unmistakable. The writing did not cause the disaster. But it prevented the information from reaching decision makers in a form they could act on.
Most writing mistakes do not carry life-or-death consequences. They carry smaller costs that accumulate silently: rework from misinterpreted requirements, decisions delayed by unclear proposals, relationships strained by emails that sounded dismissive, and credibility eroded by careless errors. A 2019 study by Grammarly and Harris Poll found that 72% of business professionals experienced confusion from poor writing quality in their organization at least weekly.
This article catalogs the most damaging writing mistakes, explains why they persist even among experienced writers, and provides concrete techniques for eliminating them.
The Cardinal Sin: Burying the Main Point
The single most common writing mistake in professional communication is placing the conclusion at the end. Writers follow a natural thinking sequence: I encountered a problem, I analyzed options, I evaluated tradeoffs, and therefore I conclude...
The reader does not need to follow your thinking sequence. They need your conclusion first, then enough reasoning to evaluate it.
Why Writers Bury the Point
- Academic training: Schools teach thesis papers where arguments build toward a conclusion. This structure is wrong for professional communication.
- Psychological safety: Presenting the conclusion upfront feels exposed. What if the reader disagrees? Building up to it feels like building a case.
- Effort justification: "I spent 40 hours on this analysis and I want you to see my work" -- natural but counterproductive. The reader wants results, not process.
- Genuine uncertainty: Sometimes the writer is not sure of their conclusion and hopes the reader will reach it independently through the analysis. This almost never works.
The Fix
State your main point in the first sentence. Then provide supporting reasoning. Then provide evidence if needed. This is the Pyramid Principle structure developed by Barbara Minto at McKinsey.
Before: "We analyzed three vendors over six weeks, evaluating them on 12 criteria including cost, reliability, support, and scalability. Vendor A scored highest on reliability but was 40% more expensive. Vendor B offered the best pricing but had concerning support reviews. Vendor C balanced all factors effectively. We recommend Vendor C."
After: "We recommend Vendor C, which offers the best balance of reliability, cost, and support among three evaluated vendors. Vendor A's superior reliability does not justify its 40% premium. Vendor B's lower price comes with inadequate support."
Passive Voice: Hiding the Actor
Passive voice places the object of an action before the actor, often hiding who is responsible.
- Passive: "Mistakes were made in the deployment process."
- Active: "The operations team made mistakes in the deployment process."
- Passive: "The decision was approved."
- Active: "The VP of Engineering approved the decision."
The Quick Test
If you can add "by zombies" after the verb and the sentence still makes sense grammatically, it is passive: "The report was written by zombies." "Mistakes were made by zombies."
When Passive Voice Is Appropriate
- Actor unknown: "The server was compromised sometime overnight"
- Actor less important than action: "The data was encrypted using AES-256"
- Deliberate diplomatic softening: "Some concerns were raised about the timeline" (in contexts where naming the person would be counterproductive)
When Passive Voice Is Harmful
In accountability contexts: "The deadline was missed" avoids saying who missed it. If accountability matters -- and in project management it usually does -- use active voice.
In instruction: "The form should be submitted by Friday" is weaker than "Submit the form by Friday."
In recommendations: "It is recommended that..." by whom? Own your recommendation: "I recommend..."
Example: George Orwell identified passive voice as a tool of political evasion in his 1946 essay "Politics and the English Language": "Defenceless villages are bombarded from the air, the inhabitants driven out into the countryside, the cattle machine-gunned, the huts set on fire with incendiary bullets: this is called pacification." The passive voice obscures who is acting and why.
Unnecessary Complexity: The Curse of Sounding Smart
Many professionals unconsciously equate complex writing with intelligence. The opposite is true. Clear, simple writing requires more effort and demonstrates more mastery than complex writing.
Nominalization: Turning Verbs into Clumsy Nouns
| Nominalization | Plain Version |
|---|---|
| "Conduct an investigation into" | "Investigate" |
| "Make a determination about" | "Determine" |
| "Perform an assessment of" | "Assess" |
| "Provide a recommendation for" | "Recommend" |
| "Give consideration to" | "Consider" |
| "Reach a conclusion about" | "Conclude" |
Nominalizations inflate word count by 50-100% without adding meaning. They also sap energy from prose -- the verb, which should carry the sentence, is buried in a lifeless noun phrase.
Jargon Overload
Jargon is appropriate when writing for audiences that share your specialized vocabulary. It is harmful when:
- The reader does not share the vocabulary
- The jargon obscures meaning rather than adding precision
- Simpler words would communicate the same idea
- The writer uses jargon to signal expertise rather than to communicate
Before: "We need to leverage our core competencies to synergize cross-functional deliverables and optimize our go-to-market strategy."
After: "We need to use our strengths to improve collaboration and refine our sales approach."
The second version communicates the same idea in half the words, without requiring the reader to decode corporate jargon.
Hedging and Qualification
Writers weaken their prose with unnecessary hedges:
- "It could potentially be argued that..." -- just argue it
- "There seems to be some evidence suggesting..." -- present the evidence
- "It is perhaps worth noting that..." -- note it or do not
- "In many cases, it may be true that..." -- say when it is true and when it is not
Some qualification is appropriate when genuine uncertainty exists. But reflexive hedging signals either that the writer lacks confidence in their claims or that they are protecting themselves from criticism. Neither creates trust.
Ambiguous Pronouns: The "It" and "This" Problem
Vague pronoun references force readers to guess what you mean, creating misunderstanding.
Ambiguous: "The marketing team reviewed the proposal with the engineering team. They had concerns about the timeline."
Who had concerns? Marketing or engineering?
Clear: "The marketing team reviewed the proposal with the engineering team. Marketing had concerns about the timeline."
Ambiguous: "We need to update the API documentation, refactor the authentication module, and fix the performance regression. This should be our top priority."
Which one is the top priority? All three?
Clear: "We need to update the API documentation, refactor the authentication module, and fix the performance regression. Fixing the performance regression should be our top priority because it affects customer-facing reliability."
The Rule
Every time you write "it," "this," "that," or "these," check whether the reference is unambiguous. If a reader could plausibly attach the pronoun to more than one antecedent, rewrite for clarity.
Walls of Text: Formatting as Communication
Even well-written content fails when it is poorly formatted. A single-spaced, fully justified, 2,000-word block of text with no headings, bullet points, or visual breaks is functionally unreadable in a professional context.
Formatting for Scannability
Professional readers do not read linearly from start to finish. They scan, looking for the information relevant to them. Help them:
- Headings create entry points for different topics
- Bold text highlights key terms and conclusions
- Bullet points break complex lists into scannable items
- Short paragraphs (3-5 sentences maximum) create visual breathing room
- White space between sections signals topic transitions
Example: Jakob Nielsen, the web usability researcher, found through eye-tracking studies that 79% of web readers scan rather than read word-by-word. Professional documents are read the same way. His research at the Nielsen Norman Group demonstrated that scannable formatting improved comprehension by up to 124% compared to the same content in plain paragraph form.
Inconsistent Terminology: The Silent Confuser
Using different words for the same concept creates confusion about whether you are discussing one thing or multiple things.
Problematic: "The platform handles user authentication. The system also manages access control. The application provides login functionality."
Are "platform," "system," and "application" the same thing? Are "authentication," "access control," and "login functionality" the same thing? The reader cannot tell.
Clear: "The platform handles user authentication, which includes login, access control, and session management."
The Rule
Choose one term for each concept and use it consistently throughout the document. If you must introduce a synonym (to avoid repetitive prose), explicitly connect it: "The authentication platform -- also referred to as the auth service in our codebase -- handles all login and access control."
Why Even Experienced Writers Struggle with Conciseness
The Comfort of Over-Explanation
Adding qualifiers, context, and caveats feels safe. What if the reader misunderstands? What if they challenge my claim? Extra words feel like armor against criticism.
Reality: Extra words dilute your message. Every unnecessary word reduces the probability that the important words get read.
The Curse of Knowledge
Once you know something, you cannot imagine not knowing it. You skip steps that seem obvious, use abbreviations without defining them, and reference context that lives in your head but not the reader's.
The fix: Have someone unfamiliar with the topic read your draft. Where they get confused, you have assumed knowledge they do not have.
The Effort-Justification Trap
You spent three weeks on this analysis. Naturally, you want the reader to see all three weeks of work. Cutting feels like wasting effort.
The fix: Remind yourself that your job is not to display effort but to communicate effectively. The reader benefits from your three weeks of work by receiving a clear, concise conclusion -- not by wading through three weeks of analysis.
Practical Cutting Technique
After completing a draft, challenge yourself to cut 20% of the word count without losing any essential meaning. Most writers discover that not only is this possible, but the shorter version is better.
Example: William Strunk, author of The Elements of Style, made this the first rule: "Omit needless words." His student E. B. White expanded the book, but the first rule endured as perhaps the most important sentence ever written about writing.
Structural Problems vs. Editing Problems
Sometimes a document's problem is not sentences that need polishing but an underlying structure that does not work.
Signs of Structural Problems
- Multiple readers miss your main point
- You need many transitional sentences ("as discussed earlier," "to understand this, recall that...")
- The same information appears in multiple sections
- Cutting or moving sections seems impossible without breaking everything
- You cannot quickly outline the document's structure from memory
The Structural Fix
Stop editing sentences. Step back to outline:
- What is the single main point?
- What are the 3-5 supporting arguments?
- What evidence supports each argument?
- What is the logical order?
Rebuild from the outline. This feels like starting over, but it is faster than endlessly rearranging a document whose fundamental structure is wrong.
For broader guidance on organizing professional communication, see deep work explained for techniques on dedicating focused time to substantial writing tasks.
Technical Documentation: A Special Category of Mistakes
Technical documentation has its own failure modes:
1. Assuming reader knowledge: Using terms without definition, referencing undocumented concepts, skipping "obvious" steps.
2. Organizing by system architecture instead of user tasks: Users arrive thinking "How do I authenticate?" not "How does the auth module work?"
3. Outdated information: Even small discrepancies between docs and reality destroy trust. Users learn that the documentation lies and stop consulting it.
4. Missing working code examples: Abstract explanations without concrete implementations force users to guess.
5. No error documentation: Happy paths are documented; error states are not. When things fail, the user is abandoned.
6. Inconsistent terminology: The API calls it "user_id," the documentation calls it "account identifier," and the error message says "client reference." Is this one thing or three?
A Checklist for Better Professional Writing
Before sending any professional communication:
- Is the main point in the first paragraph? If not, move it there.
- Could a reader stop after the first paragraph and understand what I need? If not, rewrite the opening.
- Have I quantified wherever possible? Replace "significant" with actual numbers.
- Am I using active voice? Check for "was," "were," "been" -- are any hiding the actor?
- Are my pronouns clear? Could "it" or "this" refer to more than one thing?
- Is there a clear action requested? Does the reader know what to do next?
- Have I cut everything non-essential? Could I remove any paragraph without weakening the communication?
- Is the formatting scannable? Headings, bullets, bold text for key points?
- Is terminology consistent? Am I using the same words for the same things?
- Would someone unfamiliar with the context understand this? Or have I assumed knowledge they do not have?
References
Tufte, E. R. "The Cognitive Style of PowerPoint: Pitching Out Corrupts Within." Graphics Press, 2006.
Orwell, G. "Politics and the English Language." Horizon, 1946. https://www.orwell.ru/library/essays/politics/english/e_polit
Strunk, W. & White, E. B. "The Elements of Style." Pearson, 2019.
Minto, B. "The Pyramid Principle." Pearson Education, 2009.
Zinsser, W. "On Writing Well." Harper Perennial, 2006.
Nielsen, J. "How Users Read on the Web." Nielsen Norman Group, 1997. https://www.nngroup.com/articles/how-users-read-on-the-web/
Grammarly & Harris Poll. "The State of Business Writing." Grammarly, 2019. https://www.grammarly.com/business/learn/state-of-business-writing
Pinker, S. "The Sense of Style: The Thinking Person's Guide to Writing in the 21st Century." Penguin Books, 2015.
Clark, R. P. "Writing Tools: 55 Essential Strategies for Every Writer." Little, Brown Spark, 2008.
Williams, J. M. & Bizup, J. "Style: Lessons in Clarity and Grace." Pearson, 2016.
Garner, B. A. "Legal Writing in Plain English." University of Chicago Press, 2013.