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 expert called to testify before the Columbia Accident Investigation Board, analyzed the slide and concluded that "the cognitive style of PowerPoint" had contributed to the disaster by allowing complex technical information to be expressed in fragments that concealed rather than revealed the underlying analysis. The engineers had done the analysis. The risk was identified. The communication failed.

This is not a story about bad intentions or incompetent analysts. The engineers who produced that slide were highly educated, technically sophisticated professionals under significant time pressure. They did what professionals under pressure do: they used familiar formats, relied on common conventions, and communicated in ways that felt adequate rather than ways that were adequate. The gap between "feels like communication" and "actually communicates" is the subject of this article.

Professional writing fails in predictable ways. Understanding the patterns allows writers to target the specific mistakes most likely to affect their own work, rather than applying generic writing advice that may not match their actual failure modes.

"The cognitive style of PowerPoint allows complex technical information to be expressed in fragments that conceal rather than reveal the underlying analysis." — Edward Tufte, testimony to the Columbia Accident Investigation Board, 2003

Writing Mistake What It Looks Like Why It Fails
Writer's process, not reader's need Analysis before recommendation, context before conclusion Reader must wait through everything they do not need
Egocentric writing Unexplained jargon, missing context, wrong level Reader does not have the writer's background
Passive construction "The decision was made," "errors were identified" Obscures who is responsible and what happens next
Bullet fragmentation Lists where prose reasoning is needed Connections and logic disappear; fragments replace argument
False completeness Long documents that say little Creates appearance of thoroughness while obscuring the key point

Mistake 1: Starting With the Writer's Process, Not the Reader's Need

The most fundamental mistake in professional writing is organizing the document around how the writer arrived at their conclusions rather than around what the reader needs.

Writers naturally think chronologically: they start with the problem, gather information, analyze it, consider alternatives, and arrive at a recommendation. This is a logical intellectual process. It is also a terrible document structure for most professional purposes.

The reader's need is almost always the opposite: what do you recommend, why, and what should I do about it? A document that provides the context before the recommendation, the analysis before the conclusion, the background before the finding makes the reader wait through everything they do not immediately need to reach the thing they do need.

The inversion principle: Start where the reader needs to end. State the recommendation, then provide the support. State the conclusion, then provide the evidence. State the decision required, then provide the context.

Example: The difference between a consultant's presentation that works and one that does not is often reducible to this single decision. A presentation that opens with "Here is the situation, here is what we analyzed, here is what we found" delays the audience's ability to engage with the central argument. A presentation that opens with "We recommend Option B, for three reasons: [reasons]" and then provides supporting analysis for each reason enables the audience to engage immediately with the argument and evaluate the evidence against the stated claim.

Mistake 2: Writing for Yourself, Not for Your Reader

Most bad professional writing is egocentric — it reflects what the writer knows and how the writer thinks rather than what the reader needs and how the reader approaches documents.

Egocentric writing manifests in several specific patterns:

Unexplained jargon: The writer uses technical vocabulary that is common in their domain without recognizing that the reader may not share that domain knowledge. The solution is not to avoid technical precision — it is to provide brief definitions when terms may be unfamiliar, or to substitute plain language equivalents that preserve the meaning.

Missing context: The writer assumes shared background that the reader does not have. Critical context that is obvious to someone who has been working on a project for months is not obvious to someone reading about it for the first time. The fix is the stranger test: ask "Would a competent professional with no background in this area understand this sentence?"

Writing to the wrong level: A document written for a technical audience being read by an executive; a document written for an executive being read by a technical team. The mismatch between the document's assumptions about the reader and the actual reader produces the same confusion as writing in the wrong language.

Burying the lede: The most important information is in the middle or at the end of the document. The reader who stops reading after the first page — as many busy readers do — misses the key message.

Mistake 3: Passive Construction and Ambiguous Agency

Passive voice constructions ("the decision was made," "errors were identified," "the analysis was conducted") obscure who did what. In professional contexts where accountability, clarity about roles, and specific attribution matter, passive voice produces specific failures.

The accountability problem: "The budget exceeded projections by $800,000" does not specify who is accountable for the overrun, what caused it, or what is being done about it. "The procurement team's vendor selection exceeded the approved budget by $800,000 because the winning bid was 25% above the estimate. The team is renegotiating the contract." The active version specifies actors, causation, and current state.

The action problem: "Recommendations have been provided" does not specify who was given the recommendations, whether they were accepted, or what happens next. Passive constructions are often used to avoid commitment to specific action — which is sometimes politically convenient but always communicatively costly.

The credit problem: "The project was delivered on time and under budget" does not recognize who delivered it. Passive voice in recognition contexts produces the specific morale failure of un-attributed accomplishment.

Example: In UK Government Digital Service's plain language initiative, training materials for government writers specifically target passive constructions as one of the five most common clarity killers in government writing. The materials show before/after examples where converting passive to active produces documents that citizens can follow and act on, as opposed to documents that accurately describe what the government does without telling citizens what to do themselves.

Mistake 4: Bullet Point Fragmentation

Bullet points are a useful tool for genuinely list-like content: a sequence of steps, a set of independent options, a collection of specifications that do not have logical connections to each other. They are an overused escape from the intellectual discipline of constructing connected, logical prose.

When complex reasoning is expressed as bullet points, the logical relationships between points are removed. The reader sees items but not the argument that connects them. The writer who cannot construct a paragraph connecting these items typically has not yet thought through the argument fully.

The bullet point test: Take a bulleted list and attempt to write it as connected prose. If the paragraph writes easily and the logical connections are clear, the bullet points were a stylistic choice that prose serves equally well. If the paragraph is difficult to write — if you cannot construct sentences that connect the bullets — the difficulty is a signal that the underlying thinking requires more development.

This is the mechanism Bezos identified: PowerPoint bullet points allow fragmented thinking to appear organized. Narrative prose forces the connections to be explicit, which reveals gaps and inconsistencies that bullet points conceal.

When bullet points are appropriate:

  • Genuinely enumerable items that are parallel in structure
  • Step-by-step procedures where sequence is the only relationship
  • Comparison tables where items are evaluated against common criteria
  • Reference material where readers scan rather than read

When bullet points are inappropriate:

  • Arguments where the logical connection between points is essential to the argument
  • Analysis where the causal chain from evidence to conclusion matters
  • Any context where the relationship between items is more important than the items themselves

Mistake 5: Over-Hedging and Under-Committing

Professional writers, particularly in organizational contexts where being wrong has career consequences, hedge their conclusions to the point of meaninglessness.

"Based on the available data, it might potentially be worth considering the possibility that option B could represent a preferable alternative in some scenarios, depending on various factors."

This sentence communicates almost nothing except the writer's anxiety about being wrong. The hedge protects the writer while failing the reader, who needs an actual recommendation to make a decision.

The irony of over-hedging: it does not protect the writer as much as it seems to. Decision makers who read hedged recommendations identify them as hedged and adjust their evaluation of the writer accordingly — not as appropriately cautious, but as unwilling to commit. The reputational cost of over-hedging is similar to the cost of being wrong, because both mark the writer as someone whose judgments cannot be relied upon.

The appropriate commitment standard: Recommend what you actually believe, with the appropriate confidence level stated explicitly. "Based on three months of data, we recommend Option B. If usage data in Q2 shows that the assumed conversion rate does not hold, we should revisit this recommendation." This is commitment with explicit conditions — significantly more useful than a hedge that protects the writer at the cost of the reader's ability to act.

Mistake 6: Unclear or Absent Calls to Action

Professional documents that require a reader to do something — approve a request, make a decision, take an action, respond with feedback — frequently omit a clear specification of what they are asking for.

The writer knows what they want. They have thought about it, drafted the document around it, and feel that it is obvious. It is not always obvious to the reader, who encounters many documents and may interpret the purpose of any given document differently than the writer intended.

Common call-to-action failures:

  • No explicit request at all (the document describes a situation without specifying what should happen)
  • An implicit request that requires inference ("I thought we discussed doing this differently" as a way of requesting a change)
  • A vague request ("I'd love your thoughts on this" when specific approval or rejection is required)
  • A request buried in the last paragraph of a long document (the reader who stops reading partway through never encounters it)

The explicit request principle: Every professional document that requires action should specify, in a prominent location, what action is requested, from whom, and by when. "I am requesting your approval to proceed with the vendor contract by October 15" is a complete, actionable request. "Let me know what you think" is not.

Mistake 7: Inaccurate Confidence Levels

Professional writers often misrepresent their confidence in their conclusions — not necessarily through intentional dishonesty but through the social pressures that shape how professional communication is produced.

The pressures work in both directions. Overconfidence is produced by the social expectation that leaders and experts project certainty, by the incentive structure that rewards decisive-sounding recommendations, and by the discomfort of acknowledging the limits of analysis. Under-confidence is produced by the hedging habit described above, by genuine uncertainty that the writer has not resolved, and by political caution.

The accurate expression of confidence matters because decision makers calibrate how much evidence they require before acting based on their assessment of the writer's confidence. A writer who expresses high confidence in recommendations that frequently turn out to be wrong loses credibility. A writer whose confidence levels accurately predict the precision of their recommendations builds credibility over time.

Practical guidance: Express confidence levels through specific language choices that correspond to actual probability estimates. "Our analysis strongly supports" should correspond to genuine high confidence. "The data suggests" should correspond to directional evidence without strong certainty. "One possibility is" should correspond to speculation. Consistency between the language and the actual evidence level builds the trust that makes professional writing influential.

For related frameworks on how to construct the underlying argument that these mistakes distort, see structure in writing explained and writing for decision makers.

The Neuroscience and Psychology of Writing Failure

Research into why professionals produce unclear writing has moved beyond stylistic critique into cognitive science, revealing that writing mistakes are often predictable consequences of how the human brain processes information rather than evidence of carelessness or poor education.

George Miller's foundational 1956 paper "The Magical Number Seven, Plus or Minus Two," published in Psychological Review, established that working memory can hold approximately seven items simultaneously -- a limit that was later refined to four chunks of complex information by Nelson Cowan at the University of Missouri in his 2001 paper "The Magical Number 4 in Short-Term Memory: A Reconsideration of Mental Storage Capacity," published in Behavioral and Brain Sciences. The writing implication is direct: writers who draft sentences while simultaneously managing technical content, audience awareness, and organizational structure routinely exceed their own working memory limits, producing output that is internally coherent to them (because they have off-loaded context into long-term memory) but opaque to readers who lack that context.

David Kaufer and Brian Butler at Carnegie Mellon University studied professional writing failure empirically in Designing Interactive Worlds with Words (2000), analyzing 400 documents from corporate, legal, and governmental contexts. Their central finding: the most common professional writing failures were not grammatical or stylistic errors but failures of what they termed "audience simulation" -- the writer's inability to accurately model what the reader already knew and what they needed to be told. Documents written by subject-matter experts for non-expert audiences showed audience simulation failures in 71% of cases -- the experts consistently over-estimated shared background and under-estimated the amount of explanatory context required.

Roy Peter Clark at the Poynter Institute for Media Studies analyzed over 3,500 pieces of professional non-fiction writing in Writing Tools (2006) and identified "the over-stuffed sentence" as the single most prevalent structural failure: sentences attempting to carry more information than their grammatical architecture could support. Clark found that writers under deadline pressure produced sentences averaging 35 words compared to 18 words when writing without time constraints -- and that the longer sentences were rated by blind readers as significantly less comprehensible despite containing identical information. The research confirms that cognitive load during writing directly degrades writing quality, an effect magnified when writers mistake verbosity for thoroughness.

Timothy Wilson and Jonathan Schooler at the University of Virginia published research in 1991 in the Journal of Personality and Social Psychology demonstrating that attempting to verbalize knowledge in unfamiliar domains actively disrupts the expert's performance -- a phenomenon they called "verbal overshadowing." For professional writers, this explains a paradox frequently observed in organizations: the most technically expert professionals often produce the least comprehensible written explanations of their domains. The act of writing forces tacit, procedural knowledge into explicit, declarative form -- a translation that degrades fluency because expert performance is not stored in the brain in the form that written language requires. This is a cognitive constraint, not a skill deficit, and it explains why subject-matter expert review without a writing mediator so rarely improves professional documentation quality.

Britt Andreatta, learning researcher and former University of California Santa Barbara faculty member, studied writing behaviors in professional settings through observation studies at 14 organizations and reported in Wired to Learn (2017) that 63% of professionals reported spending less than 10 minutes revising professional documents before sending -- despite research consistently showing that revision is where clarity improvements are concentrated. The gap between revision behavior and revision need explains a large portion of the professional writing quality deficit: the cognitive work of clarity editing is systematically skipped not because writers are lazy but because they underestimate how much their unrevised drafts differ from how they will be read.

Empirical Studies on the Cost of Specific Writing Mistakes

The quantification of writing mistake costs has become more precise as organizations have begun tracking the downstream consequences of communication failures with the rigor they apply to software bugs and operational incidents.

Josh Bernoff and Shawn Ryan at Forrester Research conducted a landmark 2016 survey of 547 business professionals in companies with more than 1,000 employees, published as "Bad Writing Costs Businesses Billions." Respondents estimated spending an average of 25.5 hours per week reading work-related writing, of which they rated 81% as only "somewhat effective" or less. Scaling this estimate across the U.S. workforce and adjusting for wage rates, Bernoff and Ryan calculated that poor business writing cost American businesses $396 billion annually in lost productive reading time -- the time spent by readers working to extract meaning from writing that failed to communicate clearly. The estimate excluded downstream costs from misunderstanding: errors, rework, delays, and failed decisions caused by miscommunication.

Phillip Clampitt at the University of Wisconsin-Green Bay studied the organizational costs of ambiguous professional communication through a decade of research summarized in Communicating for Managerial Effectiveness (multiple editions since 1991). His most specific finding: ambiguous instructions and unclear assignments were the primary cause of what he termed "communication noise" in organizations -- work completed incorrectly because the initial communication was unclear. Across the organizations he studied, he estimated that 30-40% of project rework was attributable to unclear initial communication, with the majority of those failures traceable to specific writing mistakes: undefined terms in requirements, passive voice that obscured ownership, and hedged instructions that left scope undefined.

Alan Manning and Nicole Amare at the University of Southern Alabama published a 2007 study in the Journal of Business and Technical Communication examining passive voice specifically in professional writing. Analyzing 200 business emails, 50 internal reports, and 50 technical specifications across five companies, they found that 34% of sentences in business emails used passive construction, rising to 47% in internal reports and 58% in technical specifications. Reader comprehension tests showed that passive-heavy documents required 23% longer to read and produced 31% more comprehension errors than equivalent documents rewritten in active voice -- confirming Flesch's earlier consulting observations with controlled experimental data. The researchers also found a counterintuitive pattern: writers who produced the most passive-heavy documents reported the highest confidence in the clarity of their writing, suggesting that passive voice obscures the writer's perception of their own clarity problems as much as it obscures meaning for readers.

Laura Gurak at the University of Minnesota and John Lannon at UMass Dartmouth studied over-hedging in professional communication in Strategies for Technical Communication in the Workplace (multiple editions). Their survey of 320 technical professionals found that 78% reported having added hedging language to recommendations "to protect themselves professionally," and 61% reported that this hedging had "definitely or probably" resulted in their recommendations being ignored or misinterpreted. The irony that Gurak and Lannon identified: over-hedged recommendations were significantly more likely to prompt follow-up questions than clear recommendations, meaning the writer who hedged to reduce professional risk actually increased it by generating more scrutiny and consuming more of their own time in subsequent clarification.

Nielsen Norman Group researchers Jakob Nielsen and John Morkes published findings in 1997 from a controlled study of web-based professional writing in which they tested five variants of the same content -- standard marketing prose, concise text (58% shorter), scannable layout (using bullet points and headers), objective language (instead of promotional writing), and a combined version using all three techniques. The combined version produced a 124% improvement in usability score compared to the standard marketing version. When tested in isolation, objectivity improvements produced a 27% usability improvement -- a larger gain than either concise writing (58% shorter text, 58% improvement) or scannable layout alone (47% improvement). The finding directly quantified the cost of the over-stating mistake: promotional, confidence-inflating language reduced comprehension and usability more than excessive length.

The Corporate Executive Board, in a 2012 study of executive communication practices across 78 large organizations, found that executives who were rated by peers as "poor communicators" shared a specific pattern distinguishing them from high-rated communicators: they used significantly more hedging language, vague quantifiers, and nominalized verb constructions in written communication, and their written recommendations were accepted at rates 40% lower than recommendations from high-rated communicators making equivalent proposals. The study controlled for the quality of the underlying recommendation by having subject-matter experts rate the analytical quality of proposals independent of their writing quality. The finding: writing quality produced a 40% difference in acceptance rates independent of analytical quality -- making writing mistakes the most powerful lever available for improving professional communication outcomes.

The systematic study of professional writing failures has identified causes that are more structural and cognitive than they are about individual skill deficits. Deborah Tannen's research on workplace communication, documented in Talking from 9 to 5 (1994), found that the most common source of writing failure is not ignorance of writing rules but a mismatch between what the writer assumes the reader knows and what the reader actually knows. Writers who have worked on a problem for weeks write as though their readers share three weeks of context; readers who encounter the document cold supply their own context, which may differ substantially from the writer's.

George Orwell diagnosed a root cause of bad professional writing that remains as accurate in the twenty-first century as when he published "Politics and the English Language" in 1946: writers use complex language not to express complex ideas but to avoid the intellectual discipline of having a clear idea. "Our company is committed to delivering innovative, customer-centric solutions that drive value across the ecosystem" contains no analyzable claim -- it is a phrase that sounds purposeful while communicating nothing. Orwell identified this pattern in political writing of the 1940s; Tannen, Steven Pinker, and Josh Bernoff have documented the same pattern in corporate writing of recent decades.

Joseph Williams at the University of Chicago analyzed patterns of professional writing failure across thousands of student and professional documents in developing Style: Lessons in Clarity and Grace. His most significant finding: the majority of clarity failures in professional writing stem from a small set of grammatical patterns that writers can learn to identify and correct. Nominalizations (converting verbs to abstract nouns: "conduct an investigation" instead of "investigate"), unnecessary passive voice, and misplaced modifiers account for a disproportionate share of the ambiguity and vagueness in professional prose. Williams' research demonstrated that targeted training on these specific patterns produces larger improvements in writing clarity than general writing instruction.

Rudolf Flesch identified passive voice as the most prevalent single cause of reading difficulty in his readability research, a finding consistent across the several decades of his consulting work with American corporations, newspapers, and government agencies. Flesch's consulting records, analyzed posthumously by readability researchers, show that documents revised to remove passive constructions showed an average Flesch Reading Ease score improvement of 8-12 points -- equivalent to reducing the required reading level by approximately one to two years of schooling. The implication: passive voice is not a stylistic choice with neutral effects on readability; it is a structural impediment with measurable costs.

Edward Tufte's analysis of organizational communication failures, including his study of the Columbia shuttle accident presented to the Columbia Accident Investigation Board in 2003, identified a category of writing mistake that is uniquely modern: the bullet-point fragmentation of complex reasoning. Tufte's research showed that converting an engineering analysis to PowerPoint bullet points systematically strips the logical relationships between claims. The engineer who wrote "foam strike damage: no safety concern" in a bullet point was not lying -- the full analysis, expressed in complete sentences, showed that the confidence interval around the claim was wide and the implications of a worst-case outcome were severe. The bullet point format eliminated these qualifications, not through dishonesty but through structural incapacity.

Case Studies: Writing Mistakes That Had Documented Consequences

The Columbia Shuttle: When Bullet Points Obscured Risk

Edward Tufte's analysis of the Boeing engineering slide shown to NASA management during the Columbia mission -- the slide that failed to communicate the severity of the foam strike risk -- remains the most extensively analyzed example of bullet-point fragmentation in professional communication history.

Tufte reconstructed what a competent engineer with the same data would have written in prose: a clear statement that the foam strike was of a type not previously tested, that the model used to assess damage was being applied outside its validated range, and that the confidence interval on the safety assessment was wide enough to include outcomes that would be catastrophic. The slide as presented compressed this information into a hierarchy of bullet points in which the critical uncertainty appeared at the third level of nesting -- structurally invisible to anyone who did not read every sub-bullet of every bullet on the slide.

The writing mistake was not a failure of the individual engineers. It was a failure of the organization's communication format to support the expression of complex, conditional reasoning. Tufte's recommendation to the Investigation Board -- that organizations adopt prose narrative rather than bullet-point slides for safety-critical communications -- was accepted and became part of NASA's revised communication standards following the investigation.

McKinsey's Internal Standards for Hedged Language

McKinsey's internal writing standards, documented by former associates in various accounts including Ethan Rasiel's The McKinsey Way (1999), specifically target the over-hedging mistake. Partners reviewing work product are trained to identify hedged recommendations -- "it might be worth considering whether option B could potentially represent a more favorable alternative" -- and return them for revision. The standard is that a recommendation must state, in the affirmative, what the writer believes is the right course of action, with explicit confidence level stated separately from the claim.

The rationale is practical: clients pay for judgment, not for catalogues of possibilities. A hedged recommendation forces the client to do the analytical work of extracting a conclusion from a list of possibilities -- which is the work the consultant was hired to do. McKinsey found that clients who received clear recommendations, even when those recommendations turned out to be wrong, rated the engagement more highly than clients who received hedged analyses that were technically correct but required the client to reach their own conclusion.

UK Government Plain Language Reform: Measuring Writing Mistake Costs

When the Government Digital Service undertook its comprehensive review of UK government digital content beginning in 2010, its research team documented specific costs attributable to specific writing mistakes. The research methodology involved user testing of existing government documents against revised versions, measuring task completion rates, error rates, and time to completion.

The findings attributed specific failure modes to specific writing mistakes. Passive constructions -- "Your application will be processed within 28 days" instead of "We will process your application within 28 days" -- reduced reader certainty about who was responsible for the stated action, producing higher rates of follow-up calls. Buried calls to action -- the what-to-do paragraph appearing at the end of a long explanatory section -- were missed by 43% of readers in user testing. Jargon-heavy sections produced comprehension failures even among educated readers unfamiliar with the specific domain terminology.

The GDS team calculated that writing mistakes in high-volume government documents had cumulative costs in the hundreds of millions of pounds annually in unnecessary contact center calls, incorrectly completed forms, and delayed citizen action. The calculation provided an economic justification for the significant investment in content redesign -- and established a model for measuring the organizational cost of writing mistakes that has since been adopted by government digital services in Australia, Canada, and New Zealand.

References

Tags

writing mistakes improvement professional-writing work-skills

Frequently Asked Questions

What are the most common writing mistakes that undermine professional communication?

The most common professional writing mistakes are burying the main point, using unnecessarily complex language, and writing without clear purpose. Burying the main point means starting with background, context, or methodology before stating what you actually want readers to know or do—this forces busy readers to hunt for your message or give up entirely. Always lead with your conclusion, recommendation, or key takeaway. Using unnecessarily complex language—jargon when plain words would work, convoluted sentence structures, passive voice—makes comprehension harder without adding value. Complexity should reflect idea complexity, not effort to sound important. Writing without clear purpose means producing content that could be informational or action-seeking, leaving readers uncertain what to do with it. Every document needs a clear function: inform, persuade, instruct, request, or document. Other major mistakes include inconsistent terminology that confuses readers about whether you're discussing the same thing or different things, walls of text without visual hierarchy making scanning impossible, vague language ('improve performance,' 'significant impact') when specific numbers would be more useful, and ambiguous pronouns that force readers to guess what 'it' or 'this' refers to. Poor formatting decisions like justified text that creates awkward spacing, tiny fonts, or missing headings also undermine otherwise good writing. Writing from your perspective rather than the reader's—organizing by your thinking process rather than their needs—ensures your carefully crafted content doesn't get used. The underlying pattern is usually prioritizing what's convenient for the writer over what's useful for the reader.

How do you identify and fix passive voice in your writing?

Passive voice puts the object of an action before the actor, often obscuring who's responsible: 'Mistakes were made' (passive) versus 'The team made mistakes' (active). To identify passive voice, look for forms of 'to be' (is, are, was, were, been, being) combined with past participles, and check whether the sentence subject is acting or being acted upon. If you can add 'by zombies' after the verb and the sentence still makes grammatical sense, it's passive: 'The report was written (by zombies)' is passive; 'The manager wrote the report' is active. Look for phrases like 'was completed,' 'were approved,' 'has been decided,' 'will be implemented'—these signal passive construction. To fix passive voice, identify who or what is performing the action and make that the sentence subject. 'The feature was implemented' becomes 'The engineering team implemented the feature.' 'Mistakes were made in the analysis' becomes 'We made mistakes in the analysis.' Sometimes passive voice is appropriate: when the actor is unknown ('The server was compromised'), when the object is more important than the actor ('The president was elected by a narrow margin'), or when you deliberately want to avoid assigning responsibility. But these are exceptions—default to active voice because it's more direct, clearer about responsibility, and typically more concise. Active voice forces you to specify who does what, which prevents ambiguity and makes writing more concrete. If you find yourself writing passive frequently, it may signal that you're uncomfortable stating clearly who's responsible for actions and outcomes—sometimes passive voice is a symptom of organizational cultures that avoid accountability.

What writing mistakes make technical documentation confusing or unusable?

Technical documentation becomes confusing through several common mistakes. First is assuming reader knowledge: using technical terms without definition, referencing concepts not yet explained, or skipping steps that seem obvious to experts but aren't to users. Second is organizing by system architecture rather than user tasks: documenting what the system does instead of how users accomplish their goals. Users arrive thinking 'I need to integrate authentication' not 'I wonder how the auth service works.' Third is outdated or inaccurate information: even minor discrepancies between docs and reality destroy trust, causing users to verify everything through trial and error. Fourth is missing working code examples: abstract explanations without concrete implementations force users to guess at details and debug inevitable mistakes. Fifth is lack of error documentation: explaining happy paths but not what errors mean or how to fix them leaves users stuck when things fail. Sixth is poor discoverability: organizing information in ways that make sense to writers but not to readers trying to find specific answers. Seventh is inconsistent terminology: calling the same concept different names in different sections or using the same term for different things. Eighth is walls of text without visual hierarchy: no headings, bullet points, or code formatting makes content unscannable. Ninth is writing once without testing: documentation that hasn't been used by actual users inevitably has gaps, unclear sections, and wrong assumptions. Tenth is missing context about when information applies: stating rules without conditions, edge cases, or version constraints. The pattern is usually documentation written to check a box rather than serve users—treating docs as obligation rather than product.

Why do even experienced writers struggle with conciseness?

Experienced writers struggle with conciseness because being comprehensive, showing your work, and sounding professional often feel at odds with brevity. There's psychological comfort in over-explaining—adding qualifiers, background, and caveats feels safer than making direct statements that could be misunderstood or challenged. Writers add 'really,' 'very,' 'quite,' and 'actually' thinking they strengthen statements, when they usually weaken them ('this is important' is stronger than 'this is really quite important'). Attempting to sound professional leads to nominalization—turning verbs into noun phrases ('conduct an investigation into' instead of 'investigate')—that inflates word count without adding meaning. Fear of seeming too simple or obvious drives writers to add complexity, mistaking length for depth or sophistication. Academic and corporate cultures often reward verbosity, training people that longer means more thorough. The curse of knowledge makes writers over-explain because they've forgotten what's genuinely unclear versus what's just unfamiliar at first. Emotional attachment to writing makes cutting feel like destroying valuable work—every sentence took effort, so deleting it feels wasteful, even when it's redundant or tangential. Writers also struggle to distinguish essential context from interesting background: they know why they included something, so they assume readers need it too. Conciseness requires being confident that direct, simple statements are sufficient—that readers are smart enough to understand without extensive scaffolding, that brevity doesn't equal shallowness, and that saying less usually means saying more effectively. The editing instinct is often to add rather than subtract, but concise writing usually requires ruthless cutting of anything not pulling its weight.

What are signs that your writing needs structural revision, not just editing?

Signs your writing needs structural revision rather than just line editing include readers consistently missing your main point, having to reread sections to understand flow, and finding that different sections contradict or don't connect logically. If multiple readers ask 'what are you actually recommending?' or 'why are you telling me this?' your structure has failed—the purpose and conclusion should be obvious. If you find yourself writing many transitional sentences explaining how sections relate ('as discussed earlier,' 'to understand this, we must first...'), that often signals sections are out of logical order or missing connective tissue that should be inherent in the structure. If major points are scattered across multiple sections rather than presented together, or if the same information appears in multiple places because no single location works, reorganization is needed. If you can't quickly outline your document's structure or different readers take away different main points, the underlying organization is unclear. If readers need to read linearly because jumping to middle sections leaves them confused, you may need better signposting or more self-contained sections. If your introduction is mostly 'in this paper I will discuss' statements about structure rather than actually introducing ideas, the organization probably needs work. If you notice pattern breaks—most sections follow one structure but some are organized differently without reason—consistency may need attention. If cutting or moving sections seems impossible without breaking everything, there's too much implicit dependence between parts. Structural problems feel different from editing problems: editing feels like polishing and tightening; structural revision feels like rebuilding. If you're constantly rearranging paragraphs or sections looking for the 'right' order, that's a structural issue. The solution is often stepping back to outline what you're really trying to communicate and rebuilding around that clear purpose rather than continuing to edit a fundamentally flawed structure.

Share this article