mike's web log

 

Blog Search


(Supports AND)

 

Google Ads

 

Feed

Subscribe to the RSS feed for this blog.

See this post for info on full versus truncated feeds.

 

Quote

My favorite piece of writing advice: Be explicit.

Mark Allen



 

Navigation






<May 2013>
SMTWTFS
2829301234
567891011
12131415161718
19202122232425
2627282930311
2345678


 

25 Most-Visited Entries

 

Categories

  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
 

Blogs I Read

 

Contact

Email me
 

Blog Statistics

Dates
First entry - 6/27/2003
Most recent entry - 4/9/2013

Totals
Posts - 2293
Comments - 2463
Hits - 1,527,211

Averages
Entries/day - 0.63
Comments/entry - 1.07
Hits/day - 423

Update every 30 minutes. Last: 2:19 PM Pacific

 
   |  Golden Rules of Technical Writing

posted at 10:32 PM | | |

I've been working on some thots about what we do and how and why. I'm trying to come up with some Golden Rules for technical writing. Here are 12 to get started.

Planning
  1. Produce the information that your customers need. Forget everything else.

  2. To learn what customers need, talk to them.

  3. Take advantage of what's already available in your community, and work only on something where you add value.

  4. Know your audience. Understand what they know (and don't) and how they work.

  5. Know your product. Understand what it's for and explain to users how it solves their problem(s).

  6. Consider that the best "documentation" might not be documentation. It might be good product design instead.

  7. Don't assume producing documentation means writing. It might mean producing video, audio, or some interactive something-or-other.

  8. Prioritize. You can't produce everything, so produce the content that has the highest impact.


Writing

  1. Remember that people turn to documentation only as their last choice, and write accordingly.

  2. Focus on 3 C's (in order): correct, clear, concise.

  3. Know what you need to say, and say only that.

  4. Get yourself reviewed/edited.
Agree? Disagree? Items to add? Remove?

[categories] ,