What Is Science Writing and How Do You Make Technical Topics Readable for General Readers?

Updated

Science writing is the practice of translating research, technical findings, and expert knowledge into prose that non-specialists can follow without losing accuracy. It covers news reporting, features, editing, and explanatory articles. The core skill is not "dumbing down" but choosing the right level of detail, using concrete comparisons, and building a narrative that gives readers a reason to keep going. This guide explains what the work involves, how to make technical material readable, and how to get started.

What counts as science writing

Science writing is a broad label. The main forms differ in length, audience, and how much interpretation the writer adds.

Form Typical length Main job Example outlet type
News report 400–800 words Report a new finding accurately and quickly Wire services, daily news desks
Feature 1,500–5,000 words Tell a story around people, places, or a debate Magazines, long-form sites
Explainer 800–2,000 words Answer "how does this work" for a general reader Consumer magazines, blogs
Editing Varies Improve structure, accuracy, and clarity in someone else's draft Journals, magazines, institutional sites
Institutional / PR writing Varies Communicate an organization's research or mission Universities, agencies, nonprofits

Dan Drollette Jr, whose site dandrollette.com is the reference here, describes his work as stories on science, technology, and the environment "that appeal to both the experts and the general public." That dual-audience goal is the defining challenge of the field: an expert should not find errors, and a general reader should not get lost.

How to make technical topics readable

1. Find the one idea the reader must keep

Before drafting, write one sentence stating what changes in the reader's understanding. If you cannot, the piece is not ready. Everything that does not serve that sentence is a candidate for cutting.

2. Replace jargon with a comparison, not a synonym

Swapping a technical term for a vague everyday word usually loses precision. A comparison keeps the meaning:

  • Weak: "The protein regulates cell growth."
  • Better: "The protein acts like a brake on cell division — when it fails, cells keep multiplying."

The comparison should be checkable against the source. If a researcher says the analogy breaks down at some point, say so in the piece.

3. Put people and stakes in the first few paragraphs

Readers stay for consequences, not mechanisms. Lead with who is affected, what is at stake, or what is disputed, then explain the science. A useful sequence: hook → why it matters → how it works → what is still unknown.

4. Handle uncertainty explicitly

Science rarely delivers a clean answer. Name the type of uncertainty rather than hiding it:

  • Preliminary result, small sample, or single study
  • Correlation versus causation
  • Disagreement among researchers
  • Effect size, not just statistical significance

One sentence such as "This was a small trial, so the result needs replication" protects both accuracy and reader trust.

5. Control numbers

Round where rounding does not mislead, give one comparison for scale, and avoid stacking more than two figures in a sentence. "About the width of a human hair" is more useful to a general reader than "roughly 80 micrometres" unless the exact value matters.

What science journalists and editors actually do

A science journalist's day is mostly reporting, not writing: reading papers and press releases, checking whether a claim is new, contacting researchers, and verifying quotes and figures. Drollette's listed focus areas — nature, wildlife, natural history, wildlife biology, and adventure — show how a beat can combine field reporting with technical subjects.

A science editor's day is mostly triage and repair: deciding which stories are worth pursuing, checking that claims match sources, cutting structure that buries the point, and making sure a specialist reader will not find a factual error. Editors also manage the tension between a writer's narrative and a publication's accuracy standards.

Common skills across both roles:

  • Reading a primary paper and identifying its actual claim
  • Interviewing a researcher without letting them dictate the frame
  • Fact-checking names, numbers, and units
  • Writing a headline and standfirst that do not overpromise
  • Working to a word count and a deadline

A basic workflow from idea to finished piece

  1. Pick a question, not a topic. "Why did this species' population drop" is workable; "wildlife" is not.
  2. Read the primary source first. Note the claim, the method, the sample, and the limitations.
  3. Check what is new. Search for earlier coverage so you do not repeat it or miss context.
  4. Interview at least one independent expert who did not author the study, when possible.
  5. Draft to the one-sentence idea from step 1, leading with stakes.
  6. Verify every number and quote against your notes or the paper.
  7. Read it aloud to catch sentences that only make sense to someone who already knows the subject.
  8. Cut the first paragraph if it is throat-clearing; the real opening is often the second or third.

Getting started: portfolio, outlets, and routes in

There is no single entry path, but a few practical steps recur:

  • Build a portfolio of three to five clips. These can be student publications, personal blog posts that report and verify sources, or pieces for small outlets.
  • Pitch a specific story, not a beat. Editors respond to "here is a finding, here is why it matters now, here is who I will interview."
  • Start where the bar is lower. Trade magazines, regional outlets, university news offices, and nonprofit science sites publish more often than national desks.
  • Consider adjacent roles. Institutional writing, grant-adjacent communication, and editing are common first paid positions and build the same verification skills.
  • Keep a beat. Repeated coverage of one area — wildlife biology, for instance — makes you the person editors call.

Drollette's site structure (bio, resume, portfolio, book proposal excerpts, links, blog) is itself a usable template for a freelance science writer's online presence: a short bio, a resume, selected clips, and a place for ongoing work.

Common problems and how to handle them

Accuracy versus readability. When a simplification would create a false impression, add one qualifying clause rather than dropping the point. Precision and clarity conflict less often than writers assume.

A researcher who wants to control the frame. Ask what the finding means for people outside the field, and attribute interpretations to named sources rather than stating them as fact.

A study that contradicts earlier work. Report the disagreement as the story. Do not average two conflicting results into a false consensus.

No clear "so what." If you cannot state who is affected or what changes, the piece may be better as a short news item or may not be worth writing.

Jargon that keeps returning. Keep a running list of terms and their plain-language comparisons as you report, so you do not re-solve the same problem in every draft.