Chapter 38: Ethics and Responsibility in Technical Writing: The Power and Danger of Clear Communication

"It is not the critic who counts… the credit belongs to the man who is actually in the arena." — widely attributed to Theodore Roosevelt, "Citizenship in a Republic," 1910. Used here as illustration; the chapter's argument stands on its own.

Chapter Overview

For thirty-seven chapters, this book has treated clarity as an unambiguous good. Cut the bloat. Lead with the point. Make the figure interpret itself. Write so the reader cannot misunderstand you. Every page has assumed that the clearer your writing, the better off everyone is. This chapter complicates that assumption, and it does so on purpose, because you are now skilled enough that the assumption has become dangerous. A clear, well-structured, persuasive document is a powerful instrument. Like every powerful instrument, it can be aimed at the wrong target. The same techniques that help you explain a life-saving procedure can help someone sell a useless drug, bury a safety risk under reassuring prose, or make a reckless decision sound prudent. You have spent this book learning to be persuasive. Now you have to learn what you owe the people you are about to persuade.

That debt has a concrete shape, and it is the spine of this chapter: four obligations—accuracy, transparency, accessibility, and inclusivity—and one hard truth that sits underneath them, which is that clarity is a responsibility, not just a virtue. We will define each obligation, show how it fails in real documents, and fix the failures with the same before/after method you have used since Chapter 1. Then we will look the danger in the face through three cases drawn entirely from the public record: the Challenger O-ring memos you first met in Chapter 4 and analyzed as a data-display problem in Chapter 9; the Boeing 737 MAX and the documentation around its MCAS flight-control system; and the everyday, less famous, no-less-deadly category of medical-device and medication instructions you studied in Chapter 36. These are real events in which real people died, so we will be disciplined: only well-established, verifiable facts, attributed to the public investigations; no invented quotations, no embellished casualty figures, no fabricated internal text. Where the record is uncertain, we will say so. That discipline is not a disclaimer bolted onto the chapter—it is the chapter's subject, practiced in front of you.

This is a synthesis chapter, the opening of Part VIII, and it pulls threads from across the book. Theme 1 returns at full weight: writing is thinking, and a writer who refuses to think honestly about what the evidence actually shows has failed before the first sentence. Theme 2, audience is everything, becomes an ethical claim here—when you know more than your reader, that asymmetry is power, and power implies duty. And theme 7, the best writing is invisible, acquires a dark twin: invisible writing is also the most persuasive, which means a smooth, frictionless, beautifully designed document can slip a false claim past a reader's guard precisely because nothing about it looks like an argument. By the end of this chapter, you will be able to name the technical writer's core ethical obligations, diagnose how an accurate document can still lie, disclose uncertainty in a way that is honest and usable, and analyze a real communication failure to locate the choice that mattered.

In this chapter, you will learn to:

• Name and apply the four core obligations of ethical technical communication—accuracy, transparency, accessibility, inclusivity—and explain why each is a duty.
• Detect the ways a true document can still deceive: omission, framing, selective emphasis, burial, and false confidence—and revise to remove them.
• Disclose limitations, uncertainty, and conflicts of interest so the reader can actually use the disclosure, instead of hiding it or burying the reader in caveats.
• Recognize when clarity is being used to make a bad idea persuasive, and apply the standard that the better you write, the more careful you must be.
• Analyze the Challenger, 737 MAX, and medical-instruction cases against the verifiable record to find where communication helped cause—or could have prevented—harm.

📕 Engineering/Science track: This chapter is your professional-ethics core. The Challenger and 737 MAX cases are about engineering communication under pressure, and §38.6 (disclosing uncertainty) maps onto the limitations sections of every report, paper, and proposal you will ever write. Read §38.2 (accuracy) and §38.7 (the dark side) most carefully. 📘 Business/Professional track: Your highest-risk territory is §38.5 (the line between persuasion and spin) and §38.7. You are trained to advocate; this chapter is about where advocacy becomes deception. The "honest executive summary" pattern in §38.5 is your highest-leverage takeaway. 📗 Software/CS track: Accuracy and disclosure live in your changelogs, status pages, postmortems, and security advisories. "We are investigating reports of an issue" versus an honest incident disclosure is an ethics decision. §38.6 and the medical-instruction parallels in §38.8 apply directly to safety-critical software documentation.

38.1 Why a Writing Book Ends With an Ethics Chapter

Start with a question that sounds rhetorical but is not: why would a book about technical writing need a chapter on ethics at all? Plenty of writing courses never raise the subject. They treat writing as a neutral conveyor belt—ideas go in one end, prose comes out the other, and what the ideas are is somebody else's department. The engineer decides what is true; the writer just makes it readable. On that view, ethics belongs to the engineer, the scientist, the executive—not to the person who formats the sentences.

That view is wrong, and this whole book has been quietly dismantling it. Recall the central thesis from Chapter 1: writing is not the step where you write up what you already know; writing is how you figure out what you know. If that is true—and thirty-seven chapters have argued that it is—then the writer is not downstream of the thinking. The writer is doing the thinking. The choice of what to lead with, what to cut, what to call the result, which number to put in the caption, whether to say "proves" or "suggests"—these are not cosmetic. They determine what the reader will believe. A person who controls what a reader believes is making an ethical choice whether or not they admit it.

Consider a small, ordinary example before we reach the catastrophic ones.

❌ Before: "In testing, the new algorithm achieved 99.2% accuracy, dramatically outperforming the existing system."

✅ After: "On our internal test set, the new algorithm reached 99.2% accuracy versus the existing system's 98.7%—a 0.5-point gain. We have not yet tested it on production traffic, which is noisier; the real-world gain is likely smaller."

Why it's better: The "before" is not false. The algorithm did hit 99.2%. But "dramatically outperforming" hides that the baseline was already 98.7%, so the improvement is half a percentage point—and it conceals that the test was internal, not production. Every word is technically defensible; the overall impression is a lie. The "after" gives the reader what they need to judge for themselves: the comparison, the magnitude, and the limitation. It is less impressive and more honest, and the trade between those two is the entire subject of this chapter.

Notice what happened there. No one fabricated data. The deception lived in the writing—in a vague intensifier, an omitted baseline, a suppressed caveat. This is why a writing book needs an ethics chapter: because the most common technical lies are not invented numbers. They are true numbers, clearly written, arranged to mislead. The skills you have spent this book acquiring are exactly the skills required to do that well. The only defense is a writer who has decided not to.

🔄 Check Your Understanding The "before" sentence above contains no false statement, yet we called it a lie. Where, precisely, does the dishonesty live?

Answer

It lives in three places, all in the writing rather than the data: (1) the intensifier "dramatically," which characterizes a 0.5-point difference as large; (2) the omission of the baseline (98.7%), without which the reader cannot see how small the gain is; and (3) the suppression of a material limitation (results are from an internal test set, not production). Each choice is a writing choice. Accuracy is not only about whether each sentence is true—it is about whether the whole document leaves the reader with a true impression.

[📍 Good stopping point if you are reading in sessions—the next section begins the four obligations.]

38.2 Obligation One: Accuracy — Don't Overstate

The first duty is the most obvious and the most often violated in small ways: say what the evidence supports, and no more. Accuracy is not merely "don't state falsehoods." It is "don't create false impressions"—which, as §38.1 showed, you can do with entirely true sentences. The failure mode has a name worth learning: overstatement, the gap between what your data shows and what your prose claims.

Overstatement creeps in through a small vocabulary of words that quietly inflate. Watch them.

❌ Before: "This study proves that the supplement reduces fatigue. Participants who took it consistently reported feeling more energetic, demonstrating its clear effectiveness."

✅ After: "In this study, participants taking the supplement reported lower fatigue than the placebo group (a difference of 1.2 points on a 10-point scale, p = .04). The effect was modest, the sample was small (n = 40), and participants were not blinded to which pill they received, so we cannot rule out expectation effects. The result is suggestive and warrants a larger trial."

Why it's better: "Proves," "consistently," "clear effectiveness," and "demonstrating" are all overstatement. A single small study does not prove anything; it provides evidence. The "after" reports the actual magnitude (a point worth recalling from Chapter 9—the number must carry its own meaning), names the limitations honestly, and chooses a calibrated verb: suggestive, not proven. This is not weakness. Calibrated language—matching the strength of your claim to the strength of your evidence—is the mark of a writer the reader can trust. Chapter 7 introduced hedging as a tone choice ("may suggest" versus "proves"); here that choice becomes an ethical one. The hedge is not timidity; it is accuracy.

There is a counter-failure, and an honest chapter has to name it. You can understate too. A writer so terrified of overclaiming that they bury a real, important, well-supported finding under so many hedges that the reader cannot tell whether anything was found has also failed the reader—and, when the finding is a safety risk, failed them dangerously. The Challenger engineers, as we will see, did not overstate; if anything the decisive concern was hedged and fragmented into invisibility. Accuracy runs in both directions: claim exactly as much as the evidence supports—no more, and no less. The skill is calibration, not reflexive caution.

A practical test, usable on any draft: for every claim, ask "what is the strongest sentence the evidence actually licenses?" Then write that sentence. If your draft says more, you are overstating. If it says markedly less, you are hiding the finding. Either way you have misrepresented the evidence, and misrepresentation is the violation, regardless of direction.

A short field of common overstatements and their honest forms:

🔍 Why Does This Work? Why does naming a limitation increase a reader's trust rather than decrease it? You would think admitting "the sample was small" makes the result less convincing. It does make the result less convincing—appropriately so—but it makes the writer more credible. A reader who sees you disclose the weaknesses of your own evidence infers that you are not hiding others, and extends you the benefit of the doubt on the claims you do make. Concealment works the opposite way: the reader who later discovers a hidden limitation re-reads everything you wrote as suspect. Disclosure spends a little persuasive force to buy a lot of trust, and trust is the currency every technical document actually runs on. This connects to Chapter 14's lesson that a research paper is an argument: an argument that pre-empts its own objections is stronger, not weaker, than one that pretends it has none.

38.3 Obligation Two: Transparency — Disclose Limitations, Conflicts, and Uncertainty

Accuracy governs what you claim. Transparency governs what you reveal about the claim's foundations: its limitations, the uncertainty around it, and any conflict of interest that might be shaping it. The accurate writer states the finding correctly. The transparent writer also tells you what they did not measure, how confident they are, and who paid for the study.

Three things must be disclosed, and each has a characteristic failure.

Limitations. Every analysis has them—an unrepresentative sample, an untested edge case, an assumption that may not hold, a measurement that is noisier than you'd like. The failure is silent omission: the limitation is real, the writer knows it, and it simply does not appear. Chapter 13 taught that the Discussion section of a report exists partly to state limitations; Chapter 14 made the limitations paragraph a standard move in a research paper. Here is why those conventions are ethical and not merely formal: a limitation you don't disclose is a decision you've made on the reader's behalf without telling them. You have decided the caveat doesn't matter. That is the reader's decision, not yours.

Conflicts of interest. If a study showing a drug works was funded by the company selling the drug, that does not make the study wrong—but it is information the reader needs in order to weigh it. The failure is the buried or absent disclosure. The honest move is a plain statement, placed where the reader will see it, not in eight-point type on the last page.

❌ Before (conflict buried or absent): "An independent analysis confirms that our cloud platform reduces total cost of ownership by 40% compared to competitors."

✅ After: "An analysis we commissioned and funded (vendor: TCO Insights, methodology in Appendix A) estimated a 40% reduction in total cost of ownership versus three named competitors, under the workload assumptions in §2. Results depend heavily on those assumptions; readers with different workloads should re-run the model with their own inputs."

Why it's better: "Independent" was doing dishonest work—the analysis was paid for by the seller, which the "after" states plainly. It also surfaces the assumptions the 40% rests on, because a projected number with hidden assumptions is a number that can mean anything. The reader is now equipped to discount appropriately and to test the claim against their own situation. You have not killed the claim; you have made it honest, and an honest 40% is worth more than a suspicious one.

Uncertainty. This is the hardest of the three, because our writing instincts push against it. We are taught to sound confident—Chapter 7 noted that hedging can read as weakness—and confidence sells. But false confidence in a technical document is a quiet betrayal: the reader takes your certainty as information and acts on it. The skill is to convey uncertainty precisely rather than either hiding it or smearing it across the whole document. There is a real difference between "the bridge will hold," "the bridge should hold under the loads we modeled, with a safety factor of 2.0," and "we are not confident the bridge will hold under seismic loads, which we did not model." All three might be written by honest engineers. Only the last two let the reader act safely.

🧩 Productive Struggle Before reading on, try this. A data scientist—call her Dana—has finished a churn analysis. Her actual situation: the model predicts churn with about 70% accuracy on held-out data; it has only been validated on the last two quarters; and it performs noticeably worse for enterprise accounts, which are the most valuable. She needs one sentence for the executive summary that is confident enough to be useful but honest about the uncertainty. Write that sentence before you look.

One honest version

"The model correctly flags about 70% of churners on recent data and can prioritize outreach, but it is less reliable for enterprise accounts and has only been tested on the last two quarters, so treat its enterprise predictions as a starting point, not a verdict." Notice it leads with the usable finding (you can prioritize outreach), then bounds it (70%, recent data) and flags the specific weakness that matters most to this audience (enterprise accounts are both least reliable and most valuable). It is confident and honest—the two are not in conflict once you state the uncertainty precisely instead of vaguely.

The general principle: uncertainty is information, and withholding information the reader needs to act safely is a form of dishonesty even when every sentence you wrote is true. We will see in §38.8 that in medicine and safety-critical systems, this is not an abstraction—an undisclosed uncertainty is a hazard with a body count.

🔄 Check Your Understanding A colleague argues: "If I list every limitation, no one will believe my results, and a competitor who hides theirs will look stronger. Disclosure is professional suicide." What is the strongest honest response?

Answer

Two responses, one principled and one practical. Principled: the limitations are true whether or not you state them; hiding them doesn't make the work stronger, it makes the reader's belief unjustified, and you are responsible for that belief. Practical: the disclosure is what makes the rest credible. Sophisticated readers—reviewers, executives who've been burned, regulators—assume that work with no stated limitations is either naive or hiding something. And the competitor's hidden limitations don't stay hidden; they surface in production, in replication, in an audit, at which point the concealer's credibility collapses and yours stands. Disclose the limitations that matter, state them precisely, and don't drown the real ones in trivial ones (see §38.6 on usable disclosure).

38.4 Obligations Three and Four: Accessibility and Inclusivity

The first two obligations concern truth. The next two concern reach—who can actually receive the truth you are telling. A message that only a narrow group can understand, or that quietly signals to some readers that it was not written for them, has failed an ethical test even if every word is accurate and every limitation disclosed.

Accessibility means writing so the broadest appropriate audience can understand and use the document, and—because much technical writing is now digital—so that people using assistive technology can reach it. We have treated accessibility as a craft skill throughout: plain language in Chapter 3, header hierarchy and alt-text in Chapter 4 and Chapter 10, health-literacy levels in Chapter 36. Here it graduates to an obligation. The reason is exclusion: when comprehension is gated by unnecessary jargon, dense layout, or inaccessible formats, you have not just written badly—you have decided who is allowed to understand. Sometimes that exclusion is accidental, the curse of knowledge from Chapter 2 operating unchecked. The ethical writer treats accessibility as something they owe, not something they grant when convenient.

This is not the same as dumbing down. Chapter 3's lesson stands: clarity is not the enemy of precision, jargon is. Writing a consent form at an eighth-grade reading level (Chapter 36) does not make it less accurate; it makes it received by the patient who has to sign it. An API doc that defines its terms on first use (Chapter 25) loses nothing for the expert—whose eye skips the definition—and rescues the newcomer. Accessibility costs the skilled writer almost nothing and gives the marginal reader everything.

Inclusivity is the language-level cousin of accessibility: writing that does not unnecessarily exclude or alienate readers through its word choices and assumptions. Chapter 7 introduced inclusive language as a tone and word-choice skill. The ethical core is this: technical writing constantly makes assumptions about its reader—their gender, their physical abilities, their cultural defaults, their native language—and many of those assumptions are invisible to the writer and jarring to the reader who doesn't fit them.

❌ Before: "When the engineer reviews his code, he should check that the layman can follow the comments. A sanity check by a normal user catches most issues."

✅ After: "When you review your code, check that a non-specialist can follow the comments. A quick check by a typical user catches most issues."

Why it's better: "His" assumes every engineer is a man. "Layman" and "normal user" quietly mark some readers as abnormal. "Sanity check" is casual ableist idiom that a careful writer can replace at zero cost ("quick check," "validation"). The "after" loses nothing in clarity and excludes no one. Inclusivity is rarely about grand gestures; it is a thousand small defaults, chosen well. The test is cheap: would any reasonable reader feel, on reading this, that the document assumes they are not its audience? If so, and if you can fix it without loss of meaning—and you almost always can—then fixing it is the job.

A practical note for the global reality of technical work: much of your audience reads English as a second or third language. Inclusivity and accessibility converge here. Shorter sentences, common words over rare ones, one idea per sentence, explicit connectives ("because," "therefore," "however") rather than implied logic, and consistent terminology (don't call it a "user" here and a "client" there for the same thing) all serve the ESL reader and, not coincidentally, every other reader too. Writing for the reader at the edge usually improves the document for the reader at the center.

🪞 Learning Check-In Pause and take your own inventory. Think of the last substantial document you wrote. (1) Did it state its real limitations, or did you quietly decide they didn't matter? (2) Would a smart non-specialist in your reader's position have understood it, or did the curse of knowledge win? (3) Did its language assume a default reader who looks like you? You are not being asked to feel guilty—you are being asked to notice. The whole of this chapter is the claim that these are not separate from "good writing"; they are good writing, seen from the reader's side.

38.5 The Dark Side: When Clarity Sells a Bad Idea

Here is the turn the chapter has been building toward, and it is uncomfortable. Everything you have learned makes you more persuasive. Persuasiveness is morally neutral. It serves whatever it is aimed at. A clear, well-structured, beautifully designed case for a bad idea is more dangerous than a muddled one, precisely because clarity lowers the reader's defenses. The muddled proposal gets questioned because it is hard to follow; the polished one slides through because it is easy. This is the threshold concept of the chapter, and it inverts an assumption you have held since page one.

🚪 Threshold Concept: Clarity is a responsibility, not a virtue.

How you have thought about clarity until now: clear writing is simply good. The clearer you write, the better—for you, for the reader, for everyone. Clarity is a virtue you cultivate, like honesty or diligence, and more of it is always better.

How to think about it after this chapter: clarity is power, and power is not automatically good—it takes the moral sign of whatever it serves. Clear writing in service of a true, beneficial message is a gift to the reader. Clear writing in service of a false or harmful message is a weapon, and a sharper one than muddled writing could ever be, because the reader cannot mount a defense against an argument they find effortless to accept. The frictionless document (theme 7—the best writing is invisible) is the most persuasive document, which means it is also the most dangerous when it is wrong. Once you cross this threshold, you can no longer treat your own skill as innocent. The question is never just "is this clear?" It is "is this clear, and is it true, and should it persuade?"

The everyday version of this is the gap between persuasion and spin. Both select and arrange information to move a reader toward a conclusion. The difference is whether the arrangement respects the reader's ability to judge or defeats it. Persuasion gives the reader what they need to agree with you, including the costs and risks, and lets a reasonable person reach your conclusion. Spin hides what would cause a reasonable person to disagree. The line is not always crisp, but it is real, and you usually know which side you are on—the tell is whether you are hoping the reader doesn't notice something.

❌ Before (a recommendation that hides its risk): "Migrating to the new platform will modernize our infrastructure, improve developer velocity, and position us for future growth. The transition is straightforward and the long-term benefits are substantial. We recommend proceeding immediately."

✅ After (the honest version of the same recommendation): "We recommend migrating to the new platform. Expected benefits: faster deploys (we estimate 20–30% based on two pilot teams) and a supported toolchain. Costs and risks the decision-makers should weigh: an estimated 6–9 engineer-months of migration work, a likely 2–4 week period of reduced velocity during cutover, and one hard dependency (the legacy billing integration) that we have not yet proven will port. On balance we think the benefits justify the costs, but the billing dependency is a real risk and should be prototyped before we commit."

Why it's better: The "before" is fluent, confident, and scannable—everything this book has taught you to produce—and it is spin. "Straightforward," "substantial," "modernize," "position us for growth" are content-free intensifiers (Chapter 3's "so what?" test guts them), and the costs and the one genuine risk are simply absent. The "after" is just as clear and more persuasive to a sophisticated reader, because it demonstrates that the recommender has thought about the downside. It leads with the recommendation (Chapter 4's BLUF), quantifies where it honestly can, and—crucially—surfaces the risk it would have been easy to hide. An executive summary that hides the risk is not a strong summary; it is a dishonest one. The skill you learned in Chapter 20 (lead with the ask) and the ethics you are learning now are the same move done with integrity.

A particularly seductive trap deserves its own name: the lie of omission. It is the favorite of skilled writers because it never requires a false sentence. You simply leave out the fact that would change the reader's mind—the failed pilot, the recall, the assumption that doesn't hold, the cheaper alternative you didn't mention. Every sentence survives a fact-check. The document still lies, because honesty in technical communication is a property of the whole, not the sentence. The defense is a question you ask of your own drafts: "what does the reader need to know that I have left out—and am I leaving it out because it's irrelevant, or because it's inconvenient?" Only the first reason is legitimate.

🔄 Check Your Understanding Distinguish persuasion from spin in one sentence, in a way that gives you a usable test.

Answer

Persuasion gives the reader everything a reasonable person needs to evaluate the claim—including the costs, risks, and counter-evidence—and trusts them to still agree; spin withholds whatever would make a reasonable person disagree. Usable test: if you are hoping the reader won't notice a fact you've buried or omitted, you've crossed from persuasion into spin. Persuasion survives the reader knowing everything; spin depends on them not.

38.6 How to Disclose Uncertainty Without Burying the Reader

There is a real practical objection to everything in §38.2–§38.5, and it deserves a real answer, not a slogan. If you disclose every limitation, every assumption, every uncertainty, you produce a document so hedged and caveated that the reader drowns—and a reader who drowns in caveats receives no message at all. Over-disclosure can be its own failure of communication, and sometimes its own dishonesty: a writer can bury the one limitation that matters under forty that don't, so that "technically we disclosed it" becomes a shield. Honest disclosure is not maximal disclosure. It is usable disclosure. The skill is to disclose what matters, prominently, and to keep the rest available without letting it swamp the message.

Four techniques make disclosure usable:

1. Prioritize the limitations by what would change the reader's decision. Not all caveats are equal. The limitation that could flip the recommendation goes in the summary, in plain sight. The minor methodological footnote goes in an appendix. Ask of each limitation: if the reader knew this, might they act differently? If yes, it is load-bearing—surface it. If no, it can go deeper. This is Chapter 4's inverted pyramid applied to honesty: the most decision-relevant caveat goes highest.

2. State the limitation and its consequence together. A bare limitation is hard for a non-expert to weigh. Pair it with what it means for the reader's decision.

❌ Before: "Limitations: the sample was non-random and the study period was short."

✅ After: "Limitations: because we surveyed only volunteers (a non-random sample), the results may overstate enthusiasm—people who opt in tend to be more positive. And because we measured over four weeks, we cannot speak to whether the effect lasts. Both mean: treat these numbers as an encouraging early signal, not a basis for a company-wide rollout."

Why it's better: The "before" lists limitations a non-specialist cannot interpret—so what if the sample was non-random? The "after" states the direction of each problem (it likely overstates enthusiasm) and the decision it bears on (don't roll out company-wide yet). The disclosure is now usable by the person who has to act, not just defensible by the person who wrote it.

3. Separate "what we found" from "what we don't know," structurally. A short, clearly headed "Limitations" or "What this analysis can't tell you" section lets confident findings read as confident and uncertainties read as uncertain, instead of hedging every sentence into mush. Chapter 13's IMRaD structure already gives you this slot; use it as an ethical instrument.

4. Calibrate the language, then stop. Once you have chosen the right verb—"suggests," "is consistent with," "we estimate," "we did not test"—you do not also need to apologize three times. Say it once, precisely, and move on. Over-hedging ("it may possibly perhaps be the case that results could potentially suggest…") is not more honest than a single calibrated "suggests"; it is just unreadable, and unreadable is its own failure of the reader.

The synthesis: honesty and usability are not in tension once you treat disclosure as a writing problem rather than a confession. You are not dumping everything you know about the weaknesses of your work onto the reader. You are deciding, as carefully as you decided the structure, which uncertainties the reader needs and how to deliver them so they land. That is the same editorial judgment you have practiced all book, pointed at the truth.

📚 Going Deeper: the "reasonable reader" standard. A useful frame borrowed from law and ethics is to imagine a reasonable reader in your actual audience—not the most expert, not the most naive, but a competent member of the group you are writing for—and ask what that person would need in order to make an informed judgment, and what impression your document would leave them with. Accuracy asks: would the reasonable reader be left with a true impression? Transparency asks: have I given the reasonable reader the limitations, conflicts, and uncertainties they'd need? Persuasion-versus-spin asks: could a reasonable reader, given everything I've written, still disagree—or have I engineered the document so they can't? The "reasonable reader" is the same construct as Chapter 2's audience analysis, now doing ethical work.

38.7 Three Cases Where Communication Mattered: The Stakes Are Real

Abstract obligations become vivid at the scale of consequence. The three cases that follow are real, and people died in all three. We will treat them with the citation discipline this book demands (Chapter 11): only well-established, publicly documented facts, attributed to the official investigations, with no invented quotations, internal text, or casualty figures, and explicit hedging wherever the record is contested. These are not parables to be decorated. They are the public record, and the public record is sobering enough.

The Challenger O-ring memos (1986)

You have met this case twice: in Chapter 4 as a structure failure (the decisive fact was buried and fragmented) and in Chapter 9 as a data-display failure (Edward Tufte's analysis showed that the relationship between temperature and O-ring damage was scattered across many exhibits and never isolated into one clean figure). Here we meet it a third time, as an ethics case, and the three readings reinforce one another.

The verifiable core: the Space Shuttle Challenger broke apart shortly after launch on January 28, 1986, killing its seven crew members. The Presidential commission that investigated the disaster (the Rogers Commission) traced the physical cause to the failure of rubber O-ring seals in a solid rocket booster joint, whose resilience was degraded by the unusually cold temperature at launch. The night before, engineers and managers held a teleconference in which concerns about cold-temperature O-ring performance were raised; the launch proceeded. Tufte later analyzed the charts used to argue the engineering case and concluded that they failed to make the critical temperature-damage relationship visible to the decision-makers. Those are the established facts; the internal dynamics of the teleconference have been described from multiple perspectives and we will not put words in anyone's mouth.

What does this case teach an ethics chapter that the structure and data-display chapters did not? This: the engineers who raised the concern were, on the public record, technically right and ethically trying—and that was not enough, because being right while being unreceived is a communication failure with a moral weight. The lesson is not that anyone lied; the documented record does not support a claim of deception, and we will not invent one. The lesson is subtler and harder: when you hold information that bears on whether people live or die, the duty of accuracy and transparency includes the duty to be received. A correct conclusion that is buried, fragmented, or rendered invisible by its own presentation has not discharged the writer's responsibility. Chapter 4 framed this as craft ("being correct is not the job; being received is"). At the scale of seven deaths, the craft and the ethics are the same thing. Communicating a safety-critical risk so that it cannot be overlooked is not a nicety. It is the obligation.

The Boeing 737 MAX and MCAS (2018–2019)

The second case is more recent and concerns documentation as much as design. Two Boeing 737 MAX aircraft crashed within five months—Lion Air Flight 610 in October 2018 and Ethiopian Airlines Flight 302 in March 2019—killing everyone aboard both flights, 346 people in total. Following the second crash the type was grounded worldwide. Official investigations (including by the relevant national air-safety authorities and a U.S. congressional committee) examined the causes at length.

We will state only what those investigations established and is widely reported, and we will stay general where details remain technical or contested. A central factor was a flight-control feature known as MCAS (Maneuvering Characteristics Augmentation System), which could automatically push the aircraft's nose down under certain conditions. Investigations and reporting documented that information about MCAS was limited in the materials provided to pilots and in the flight manuals, so that many pilots were not fully aware of the system, how it could activate, or how to respond when it behaved unexpectedly. The investigations identified a combination of engineering, certification, organizational, and communication factors; the communication and documentation gaps around MCAS are the part relevant to this chapter.

For a technical writer, the 737 MAX is a case about the ethics of omission and audience at the highest stakes. Recall §38.5's lie of omission and Chapter 2's principle that audience is everything. Pilots are an expert audience with a specific, safety-critical task; documentation that does not give them what they need to understand and respond to a system that can move the controls is documentation that has failed the most important audience analysis imaginable. We are not claiming that a writer caused the crashes—the investigations describe a complex, multi-factor failure spanning design and regulation, and it would be both false and disrespectful to reduce it to a documentation problem. The narrow, defensible lesson for this book is that what is left out of safety-critical documentation is an ethical choice with potential consequences as grave as anything that is put in, and that "the experts will figure it out" is not a safe assumption when the experts have not been told what exists. Where the technical and organizational specifics exceed what is firmly established, we defer to the official reports rather than embroider.

Medical-device and medication instructions (the everyday case)

The third case is not a single famous disaster but a whole category, and it is the one most technical writers will actually touch. You studied it in Chapter 36: clinical and patient-facing writing where, as that chapter's threshold concept put it, ambiguity is a safety hazard. A medication label that can be read two ways, a device instruction that omits a critical warning or places it after the step it should precede (Chapter 22), a dosage written so that "0.5 mg" can be mistaken for "5 mg"—these are writing problems, and in healthcare, writing problems injure and kill people. The patient-safety literature has documented for decades that unclear instructions, ambiguous abbreviations, and poorly designed labels contribute to medication errors; this is a well-established finding, even where any single incident's details are private.

This is the case that should land hardest, because it is the most ordinary. Most readers of this book will never write a flight manual or argue a rocket launch. Many will, at some point, write or edit an instruction that someone follows in a moment of stress, illness, or inexperience—a discharge instruction, a device manual, a dosing chart, a safety procedure, an emergency runbook. The obligations of this chapter are not reserved for catastrophes. They live in the caption, the warning placement, the unit of measurement, the word that can be read two ways. Accuracy, transparency, accessibility, and inclusivity are not abstractions for the safety-critical writer; they are the difference between an instruction that protects the reader and one that harms them. Chapter 36's safety imperative and this chapter's ethics are one subject.

🔄 Check Your Understanding Across all three cases, what is the common thread—stated as a single principle a technical writer could carry into their next document?

Answer

In each case, the content needed to prevent harm existed somewhere—an engineering concern, knowledge of a flight-control system, a correct dose—but a communication choice (burial and fragmentation in Challenger; omission and audience failure in the 737 MAX; ambiguity and design in medical instructions) prevented the right reader from receiving and acting on it. The principle: possessing the truth is not discharging your duty; the duty is to communicate it so the right reader receives it, in time, unmistakably. Being right is necessary and nowhere near sufficient. This is themes 1, 2, and 7 converging—writing is thinking, audience is everything, and the most consequential writing is judged not by how it reads but by whether it was received and acted on.

38.8 When the Document Is Wrong and You Know It: Duty of Care and Speaking Up

The cases raise a question this chapter cannot dodge: what do you do when you are the writer, and you believe the document you are being asked to produce—or sign, or stay silent about—is misleading or unsafe? This is the point where writing ethics becomes professional ethics, and it would be dishonest to pretend the answer is simple.

Start with the concept of a duty of care: the idea, familiar from many professions, that when your work can foreseeably affect others' safety or important interests, you owe those others reasonable care, not merely obedience to whoever is paying you. For a technical writer this means your loyalty is not only to the manager who assigned the document or the organization that employs you. It is also, in some measure, to the reader who will rely on what you wrote—the pilot, the patient, the user, the public. When those loyalties conflict, the duty of care says the reader's safety has weight that does not evaporate because a deadline or a boss says otherwise.

In practice this rarely arrives as a dramatic ultimatum. It arrives as small pressures: soften that warning, it's scaring customers; drop the limitation, it weakens the proposal; we don't need to mention the failed pilot; just say "industry-leading," everyone does. Each is minor. Each is a small step from persuasion toward spin, from disclosure toward omission. The skill the working writer needs is not heroism but a clear internal line and a repertoire of proportionate responses before the heroic version is the only one left:

• Raise it in writing, early, and constructively. "I want to flag that the summary as written omits the billing-integration risk; here's a version that includes it without weakening the recommendation." You are not accusing anyone; you are doing your job, and you are creating a record.
• Frame it as risk to the organization, not just principle. Most omissions that are wrong are also dangerous to the people asking for them—an overstated security claim that fails in production, an undisclosed limitation that surfaces in an audit. Honest writers often win the argument on prudence, not ethics.
• Know what you will not do. Decide in advance where your line is—what claim you will not write, what warning you will not delete, what you will not put your name to. A line decided in calm is one you can hold under pressure.
• Escalate proportionately. Most disagreements resolve a level up or with a second reviewer. The dramatic options—formal objection, refusal, in extreme and well-documented cases of serious danger, whistleblowing—exist, and the public record (including the Challenger and 737 MAX investigations) shows they are sometimes the only thing that surfaces a danger. But they carry real personal cost and real complexity; this book will not pretend they are easy or counsel them lightly. What it will say is that the small, early, in-writing version of speaking up prevents most situations from ever reaching the dramatic one.

⚠️ A note on scope and humility. Whistleblowing, professional liability, and the law surrounding them are serious matters that vary by country, industry, and contract, and they are beyond what a writing textbook can responsibly advise. If you find yourself believing a document you're involved with could cause real harm, that is the moment to seek guidance from a qualified person—an ethics office, a professional body, a regulator, a lawyer—not from a textbook chapter. What this chapter can give you is the upstream skill: write honestly enough, and raise concerns early enough and in writing, that you are far less likely to face the downstream crisis at all.

The reassuring truth underneath all of this is that the everyday practice of the four obligations is what keeps you out of the dramatic dilemmas. The writer who habitually states limitations, calibrates claims, surfaces risks, and refuses small omissions builds documents—and a reputation—that make the catastrophic version unlikely. Ethics in technical writing is mostly not a matter of grand stands. It is a thousand honest small choices, made under mild pressure to do otherwise.

📐 Project Checkpoint

You are nearing the end of the Communication Portfolio. By now you have drafted and revised most of your seven pieces—a technical report, a proposal, user documentation, a data memo, an email chain, a presentation, and a blog post. This chapter does not add an eighth piece. It adds an ethics pass across the pieces you already have.

Take your most persuasive piece—most likely the proposal or the data memo, the ones built to move a decision-maker. Read it once as the writer, then read it again as a skeptical, informed member of your target audience, applying this chapter's four tests in order:

1. Accuracy. Find every claim. For each, ask: what is the strongest sentence the evidence actually licenses? Mark every place your prose claims more than your evidence supports—every "dramatically," "proven," "significant" with no number, every projection stated as a fact. Recalibrate the language. Mark, too, any place you've underclaimed a real finding into invisibility.
2. Transparency. List the limitations, assumptions, and any conflict of interest behind the piece. Which are currently disclosed? Which did you silently decide didn't matter? Add the load-bearing ones—the ones that could change the reader's decision—using §38.6's "state the limitation and its consequence" pattern. Don't add the trivial ones; usable disclosure, not maximal.
3. The dark side. Hunt for one lie of omission: a fact you left out that a reasonable reader would want. Ask honestly whether you omitted it because it's irrelevant or because it's inconvenient. If inconvenient, put it back—and notice whether the piece is now more credible, not less.
4. Accessibility and inclusivity. Run the §38.4 checks: would a smart non-specialist in your audience understand it? Does its language assume a default reader who looks like you? Fix what you can fix at no cost to meaning.

Write a short note—half a page—to accompany the piece in your portfolio: what an ethics review changed, and what you decided to leave honest even though a less scrupulous version would read as stronger. This note is itself a portfolio asset. It demonstrates to any reader of your portfolio—an employer, a reviewer—that you treat clarity as a responsibility. Next chapter (Chapter 39) turns from the documents to the writer: how to keep this practice alive after the book ends.

38.9 Common Mistakes and Practical Considerations

The ethics of technical writing fail in patterned, recognizable ways. Knowing the patterns is most of the defense.

Mistake 1 — Treating accuracy as "no false sentences." The most common technical lie is a set of true sentences arranged to mislead—the omitted baseline, the suppressed limitation, the intensifier doing the deceiving. Fix: judge honesty at the level of the impression the whole document leaves, not the sentence. Ask what a reasonable reader would believe after reading, and whether that belief is true.

Mistake 2 — Confusing confidence with credibility. Writers fear that hedging looks weak, so they overstate. With sophisticated readers the effect reverses: uncalibrated confidence reads as naive or untrustworthy, and precise calibration reads as expertise. Fix: calibrate the verb to the evidence, once, and trust the reader to value it.

Mistake 3 — Over-disclosure as a shield. Burying the one limitation that matters under forty that don't, then claiming "we disclosed it." Fix: prioritize by decision-relevance (§38.6); the load-bearing caveat goes high, the trivia goes to an appendix.

Mistake 4 — Assuming the expert audience will fill the gap. "Pilots will know"; "engineers will figure it out"; "the doctor will catch it." The 737 MAX and the medication-error literature both warn against this. Fix: write the safety-critical thing explicitly, where it will be seen, before the step it governs—never rely on the reader supplying what you left out.

Mistake 5 — Thinking ethics is only for catastrophes. Most writers will never write a flight manual, so they file "writing ethics" under "not my problem." But the discharge instruction, the dosing chart, the security advisory, the status page, and the executive summary are where these obligations actually live. Fix: apply the four tests to ordinary documents, every time.

Mistake 6 — Mistaking your loyalty as solely to the assigner. Forgetting the reader who will rely on the document. Fix: hold the duty of care—the reader's safety and interests have weight—and raise concerns early, in writing, and constructively (§38.8), long before the only option left is a dramatic one.

It depends — the legitimate gray areas. Not every omission is a lie; you cannot include everything, and editorial selection is the job. Not every persuasive frame is spin; advocacy is legitimate and often required. The honest distinction is intent and effect: are you arranging information so a reasonable reader can judge, or so they can't? Reasonable professionals will disagree about specific cases—how much uncertainty to surface to a non-technical board, how much detail a patient leaflet can bear before it stops being read. The mark of an ethical writer is not certainty about every case; it is asking the question at all, and resolving genuine ambiguity in the reader's favor.

💡 Tip: Keep one question taped to your monitor for any consequential document: "If the reader knew what I know, would they feel I'd been straight with them?" It folds accuracy, transparency, and the persuasion/spin line into a single check you can run in ten seconds.

Frequently Asked Questions

Is it really unethical to write persuasively? Isn't persuasion the whole point of a proposal?

Persuasion is legitimate and often the job. The chapter's claim is narrower: persuasion crosses into spin when you arrange or omit information specifically so a reasonable reader can't reach a conclusion they'd otherwise reach with the full picture. Advocating for a recommendation while honestly surfacing its costs and risks is persuasion. Hiding the costs so the recommendation looks unopposed is spin. The usable test (§38.5): if you're hoping the reader doesn't notice something you've buried or left out, you've crossed the line.

How do I disclose limitations without making my work look weak?

Three moves (§38.6). First, prioritize: surface only the limitations that could change the reader's decision, and put the rest in an appendix—don't bury the important one under trivia. Second, pair each limitation with its consequence ("non-random sample, so this likely overstates enthusiasm; treat it as an early signal, not a basis for rollout") so the reader can weigh it. Third, calibrate once and stop—precise hedging reads as expertise, while over-hedging reads as mush. Disclosed limitations make the writer more credible, not less; concealed ones, once discovered, make everything you wrote suspect.

What's the difference between accuracy and transparency?

Accuracy governs what you claim—say exactly what the evidence supports, no more and no less. Transparency governs what you reveal about the claim's foundations—its limitations, the uncertainty around it, and any conflict of interest. You can be accurate and non-transparent (every sentence true, but you hid that the study was industry-funded), and the result still misleads. The ethical document is both: true claims and an honest account of what stands behind them.

Can I use the Challenger or 737 MAX examples in my own writing or teaching?

Yes, with discipline. Both are extensively documented in official investigations (the Rogers Commission for Challenger; national air-safety authorities and a U.S. congressional committee for the 737 MAX). Use only well-established facts, attribute them to those public records, and resist the urge to invent quotations, internal document text, or precise dramatic detail. Reducing a complex, multi-factor engineering and organizational failure to a single "the writer caused it" claim is both false and disrespectful to the people who died. Stay general where the record is technical or contested, and hedge explicitly. That citation discipline (Chapter 11) is itself part of the ethics.

Where does responsibility sit if I'm "just" the writer and someone else owns the content?

The chapter rejects the "neutral conveyor belt" view (§38.1). Because writing is thinking (Chapter 1), the writer's choices—what to lead with, what to cut, which verb to use, what to leave out—shape what the reader believes, which makes them ethical choices regardless of who "owns" the content. You hold a duty of care to the reader who will rely on the document (§38.8). That doesn't make you solely responsible for a complex outcome, but it does mean "I just wrote it the way I was told" is not a complete defense. The constructive form of that responsibility is to raise concerns early and in writing, before the only option left is a dramatic one.

Chapter Summary

Key Takeaways

• Technical writing is not ethically neutral. Because writing is thinking (Chapter 1), the writer's choices determine what the reader believes—and that makes them moral choices.
• The four obligations: accuracy (claim exactly what the evidence supports—no more, no less), transparency (disclose limitations, conflicts, and uncertainty), accessibility (write so the broadest appropriate audience can understand), inclusivity (don't unnecessarily exclude readers through language or assumptions).
• The most common technical lie is true sentences arranged to mislead—omission, framing, burial, false confidence. Judge honesty by the impression the whole document leaves, not by the truth of each sentence.
• Clarity is a responsibility, not a virtue (threshold concept). Persuasiveness serves whatever it is aimed at; a clear case for a bad idea is more dangerous than a muddled one, because clarity disarms the reader.
• Honest disclosure is usable, not maximal: prioritize the limitation that could change the decision, pair it with its consequence, separate findings from uncertainties structurally, and calibrate once.
• Three real cases converge on one lesson: possessing the truth is not the same as discharging your duty—the duty is to communicate it so the right reader receives and acts on it, in time, unmistakably.

Action Items

• Add the ten-second check to your editing routine: "If the reader knew what I know, would they feel I'd been straight with them?"
• On your next consequential document, run the four-test ethics pass from the Project Checkpoint before you send it.
• For every claim, write the strongest sentence the evidence licenses—then make sure your prose says neither more nor less.
• Decide your line now: what claim you won't write, what warning you won't delete, what you won't sign. A line decided in calm holds under pressure.

Common Mistakes

• Treating accuracy as "no false sentences" (it's about the whole impression).
• Overstating because hedging "looks weak" (calibration reads as expertise).
• Over-disclosing to create a shield (bury the real caveat under trivia).
• Assuming an expert audience will fill the gap you left.
• Filing ethics under "catastrophes only" instead of applying it to ordinary documents.

Decision Framework: Is This Document Honest?

Spaced Review

A few questions reaching back, to strengthen retention.

1. (From Chapter 36) That chapter's threshold concept was "in medicine, ambiguity is a safety hazard." Give one concrete writing choice in a medication or device instruction that turns ambiguity into a hazard—and how you'd fix it.
2. (From Chapter 9) Why did Tufte conclude the Challenger charts failed, even though they were accurate—and what single figure would have made the critical pattern unmissable?
3. (From Chapter 4 / bridging to this chapter) Chapter 4 said "being correct is not the job; being received is." How does this chapter raise the moral stakes of that craft principle—what turns "unreceived" from a quality problem into an ethical one?

What's Next

This chapter turned the book's tools back on the person wielding them and found that clarity is power and power is a responsibility. Chapter 39, Your Writing Life, turns from the document to the writer over the long run: how a writing practice grows or atrophies, how to keep learning after this book, how reading as a writer compounds your skill, and how the writing you do over the next five years will shape your career more than almost any technical skill you could name. If this chapter was about the weight of getting it right, the next is about staying in the arena long enough for that weight to become second nature.

Practice: Exercises · Quiz Go deeper: Case Study · Case Study 2 Review: Key Takeaways · Further Reading