- We design and build extraordinary applications for companies looking to make the next great idea a reality.
- learn more
The Ten Commandments for Technical Requirements: VII: Presentation: The Art of Gladness
I learned the first secret rule of technical writing in my first week. It floored me.
Content and organization are not the most important thing. Presentation is the most important thing.
Why?
Your readers assume you know more about the subject than you do right at the beginning! They need to be able to decode it and make the information their own as quickly as possible.
The first way of making it accessible is to make sure everything's properly and consistently spelled. You can't rely on spell check. Only 'Romantic' will show as an error in an unmodified spell checker:
And Honestly, what Is on the Rise that is taking the Reading world by storm, are these Romantic thug Books about the Boyfriend that lives the life of Crime and the girlfriend that is trying to deal with It. Or The Cheating man etc.
Here are the rules:
1. Make sure everything's spelled correctly- have at least one other set of eyes go over it before presenting it.
2. Keep the grammar gaffs to a minimum- if use a reader's pet grammar or word error, s/he will look much more closely at your work. Things that set me off include:
- 'entitled' for ''titled' (a book or CD isn't entitled to anything).
- Using a plural pronoun for a group (such as The City Council.... they voted against it, it should be it voted).
- Your for You're (jeez people!)
- Hidding behind or pompusly using big words- it's start- not initialize; it's end- not terminate; You know what the definition of orientate is? To orient; defer action means wait. Any writer has a bunch of favorites- just ask.
3. Use color when it makes sense. Always use color if part of your audience includes executives. One time a little inconsequential bar graph using three colors saved one of my projects. Go figure.
4. Use graphics when it makes sense and when it aids in understanding. If the graphic doesn't speak for itself, don't use it.
5. In print- make sure you use the paper-wasting one inch margins and stick them. I know. It is stupid. I can't tell you how manyt times the word 'dense' came up with a moved it down to half inch margins.
6. If you don't have a graphics designer:
- Follow the old newspaper typology rule- make the header font san serif and the body serif or vice versa.
- Use the serif font for captions in 8 point or less.
- Use the san serif for table headers in bold.
- Don't ever use more than two fonts- and be conservative in your selection. Times New Roman and Arial (Helvetica) are my friends in print. I go a little crazy and use Verdana is on-line publications when I have a choice.
7. Always use a title page.
8. Make sure the title page has all of the logos of companys involved.
Powered by ScribeFire.
Leave a comment
About Pathfinder
Recent
- Pimp my jQuery: Five plugins to replace the features Prototype and Scriptaculous users expect
- Thanksgiving 2008: What We’re Thankful For (In Rails)
- iPhone SDK: Testing with TextMate & GTM
- GWTQuery - JQuery-like Syntax in GWT
- Ask the readers: How do I fire native browser events in Prototype.js?
- News Rollup for the Week of November 17, 2008
- Rails ThreatDown!
- Automated Deployments Rock
- Bandwidth profiling Flex projects and more with Charles
- iPhone SDK: UIViewController Testing & TDD
Archives
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006

