{"id":4872,"date":"2016-03-11T08:35:30","date_gmt":"2016-03-11T13:35:30","guid":{"rendered":"http:\/\/www.encoretechresources.com\/insights\/?p=4872"},"modified":"2016-03-11T08:46:16","modified_gmt":"2016-03-11T13:46:16","slug":"getting-out-there-matters-greatly","status":"publish","type":"post","link":"http:\/\/www.encoretechresources.com\/insights\/2016\/03\/11\/getting-out-there-matters-greatly\/","title":{"rendered":"Getting ‘Out There’ Matters Greatly"},"content":{"rendered":"

\"imgres\"<\/a>
\nOn his ‘I’d Rather Be Writing’ blog, Tom Johnson in California’s San Francisco Bay area takes the occasion of moving to a new job to reflect on<\/a> what he was pleased with, and not so pleased with, on his old one. His reflections reveal a conscientious, fully engaged technical writing style, although not a perfect one \u2013 on his old job, anyway.<\/p>\n

Tom’s first priority, a key resolve, seems to be getting out to where the work is done, to experience what’s happening before he prescribes procedures to keep it happening. <\/p>\n

“Understanding the scrum process and how it was implemented,” Tom notes, “allowed me to quickly understand what teams were working on and what documentation needed to be written or updated, and when.”<\/p>\n

Like a street-side reporter, you have to be on the street, rather than at your keyboard, to experience what’s actually happening before you start to describe it for others. There’s nothing like “being there” as a first step.<\/p>\n

“I like being a part of engineering teams,” Tom notes, “embedded right there alongside product managers, quality assurance engineers, and developers. I built a strong sense of trust and rapport with the teams. I don’t like it when writers are grouped in their own space and interact mostly with each other, separated from the engineers.”<\/p>\n

In getting to know the engineers he’s writing for, Tom is almost automatically in closer touch with them \u2013 they’re colleagues, not clients in their own “spaces”. <\/p>\n

“I learned,” Tom confides, “that you should never send blanket emails to the entire team asking for reviews of massive amounts of documentation, because it will never happen.”<\/p>\n

His goals for next time include trusting nothing, testing everything; keeping documentation systems as simple as possible and “diving deep into content, not doc tools.”<\/p>\n

This all gets down to becoming, and remaining, authentic in your approach to technical writing. It may seem initially comfortable to be sitting at a wide display with a slick keyboard, but, over time, it’s the content, more than the technique that matters. And you get that from your colleagues. After all, they’re doing the work you’re describing. \u2013 Doug Bedell<\/em> <\/p>\n","protected":false},"excerpt":{"rendered":"

On his ‘I’d Rather Be Writing’ blog, Tom Johnson in California’s San Francisco Bay area takes the occasion of moving to a new job to reflect on what he was pleased with, and not so pleased with, on his old one. His reflections reveal a conscientious, fully engaged technical writing style, although not a perfect […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,5],"tags":[],"class_list":["post-4872","post","type-post","status-publish","format-standard","hentry","category-technology","category-the-writing-life"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t