I recently wrote a corporate blog and came upon some interesting considerations. It’s one thing to write a blog for one’s own site, but to write on behalf of someone else (i.e., a company) is another matter. There’s of course the matter of style and tone, but what is appropriate especially if there are no clear guidelines.
You may have to spin things slightly to represent the best interests of your employer, but don’t be insincere—people sense it. The story I wrote, Iridium satellites not affected my recent solar storms, concerned the effects of recent solar storms on the company’s GPS location-based tracking services. I realized that it was important not to represent their technology as vulnerable or the solar storms as alarmist.
Here’s what I came up with:
- Focus on the positive – plays down concerns in the title
- In first sentence, I use end focus to draw attention to reliability of products/services of company “…has had no affect on Iridium satellites”.
- I chose a beautiful and re-assuring image of the aurora borealis, instead of something that might cause concern.
- I was given permission to use images found on the internet (always something to consider), but because I didn’t think the site where I found this image was one I wanted to highlight, I buried the source credit in the code for the image.


Discussing Style and Tone in technical documentation in the technical writing field is usually a one-minute conversation that really doesn’t even address core issues. Usually, the conversation is about style guides or templates (which has nothing to do with style) and tone hardly even enters into it.