It’s been a year of working from home. For some writers – parents, mostly – it’s been a year of zero focus. But for others, it’s been a revelatory year. One that showed them what work looks like when they control their interruptions. When no one can walk up to their desk to ask a […]
That dreadful moment (hour? day?) when the words won’t come. We think of writer’s block as something that is stopping a well formed image from settling into the right words. But in reality, a writer’s block happens when our mental image is a little hazy and abstract. We can’t put it into words because words […]
In a conversation about your user’s needs, it’s natural to start throwing out solutions almost immediately. Someone brings up an aspect of the user’s needs, and someone knows how to answer that aspect. But suddenly, that one aspect is all you’re talking about. You’ve just blinkered your view of the user to whatever can be […]
Writing begins with awareness of the single word, then moves up. What can a word mean, and what does it actually mean in its current context? Does the sentence make its point as clearly as possible? Does the paragraph come together as a single point? Is it in the right place Does the whole document tell […]
When users find a gap in your documentation – some jump from A to C that gets negative feedback – don’t just fix it. Ask yourself how it got there. Gaps happen because: Someone didn’t think users needed the topic. This demonstrates a misunderstanding of the audience. someone didn’t think about the topic at all. […]
When you start a new job, you can’t really work without a mental image of the job: “This is my role. This is what I should be doing and how I should be doing it.” But that image is about 90% wrong (yes, I made that number up), and you need to let go of it […]
As a technical writer, one of the most important questions you can ask yourself is “what are the default values of the choices a user can make, and why”. For example, if an option is disabled by default, what does that tell you about the average user and their workflow? Are you trying to protect […]
Oliver Burkeman reviews the basics of thinking about writing.
Agile got (at least) one thing right: stop writing documents no one’s ever going to read. If you want to honestly assess what will or won’t be read – and therefore what should or shouldn’t be written – you should answer some basic questions.
Tools of the trade, 2014. Everything from bug tracking to HR.
Tested Writing 
You must be logged in to post a comment.