Key Lessons from Google’s Technical Writing Course

Google offers a concise four‑hour technical writing course that covers fundamental writing concepts useful for developers and other technical audiences.

Clarity is emphasized as the top priority; writers should avoid ambiguous pronouns and idioms that may confuse non‑native speakers. Examples illustrate how replacing vague pronouns with explicit nouns improves readability.

Succinctness encourages removing unnecessary words such as "there is"/"there are" and limiting adjectives and adverbs that add fluff. Shorter sentences and tighter phrasing make documentation easier to read and maintain.

Active voice is preferred over passive constructions because it is clearer, more familiar, and generally shorter. The guide provides side‑by‑side comparisons of active and passive sentences to demonstrate the benefit.

Effective list usage includes choosing the appropriate list type (numbered vs. bulleted), keeping list items parallel in grammar and punctuation, and using lists to break up long sentences for better readability.

Additional advice covers paragraph structure (opening sentence stating the main point), jargon reduction, simple word choice, and tailoring content to the audience. The article also stresses the importance of a clear introduction, consistent style, and a concise conclusion.

Practical code illustration demonstrates how to embed code snippets in documentation: garp() returns the delta between a dataset's mean and median, helping readers assess whether extreme values skew the mean.

The summary reiterates the core takeaways: maintain consistency, avoid ambiguous pronouns, prefer active voice, be succinct, focus each sentence on one idea, use lists wisely, eliminate unnecessary words, avoid complex jargon, keep lists parallel, open paragraphs with overviews, and adapt the document to the intended audience.