As a technical writer, what does it mean to make your writing interesting? It’s a question you perhaps have never pondered—and understandably so: you spend your time ensuring that your docs are correct and easy to understand for users—not so much that the work is interesting to read.
It’s a comfortable approach to technical writing that’s easy to get stuck in—however, to the detriment of our work. Enter Anne Janzer: this epsiode’s guest and author of, well, several great books, but as we’ll highlight today,
Writing to be Understood.
In her book, Anne discovered the essential techniques to making nonfiction writing more interesting for readers, including how to use analogies effectively to illustrate unseen concepts, appeal to readers’ innate curiosity, and balance humility with credibility.
In this episode, Anne shares takes her research on making nonfiction writing more interesting and shifts the focus to how technical writers can apply the concepts as well. We discuss:
- where technical writers may currently miss the mark in their writing
- how technical writers can use cognitive science to make their writing more interesting
- small steps technical writers can take today to make their writing more interesting.
Show Notes:
What is The Not-Boring Tech Writer?
All technical writers have one thing in common: their peers outside of the industry believe technical writing is a boring career. They think we lack creativity; they think we only eat tuna salad for lunch; and they think our work is reserved to instructional manuals that they don't even use.
This podcast gives you the tools to prove them wrong! In each episode we talk to the humans behind the docs, sharing stories, experience and expertise to inspire, entertain, and give you knowledge and skills you can use in your life as a not-boring tech writer.