It’s happened to me so many times, I should be used to it by now, but I’m not. I meet people who are involved in product development, and when I try to talk to them about user documentation I get brushed-off with “It’s OK, we do all our user documentation in-house.” “That’s great,” I say, “how many technical writers do you have on staff?”
“Oh no,” they reply, “we don’t have any technical writers, the programmers (or the engineers, or whoever) do it themselves.”
These are intelligent people, who wouldn’t allow anyone other than an experienced and qualified accountant to prepare their company’s balance sheet, or anyone other than a qualified and experienced lawyer to prepare their end-user licence agreement, but they’ll happily entrust preparing their user documentation to someone without any relevant experience or qualifications!
Top 10 TechComm Influencers 2011
Most Influential Tech Comm Bloggers 2010
Pages
Blogroll
- 2moroDocs
- A Techie Tech Writer
- Communication Cloud
- Conradiator
- CyberText Newsletter
- DITA XML org
- ffeathers
- Firehead Blog
- Gryphon Mountain
- I Heart Tech Docs
- I'd rather be writing
- Just Write Click
- Less Work, More Flow
- Mardahl.dk
- Michael Priestley
- One man writes
- Palimpsest
- RJ Jacquez
- RoboColum(n)
- Talks like a scientist
- techcommdood
- The Agile Technical Writer
- The Content Wrangler
- UAX (User Assistance)
Archives
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- May 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- 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
- July 2006
- October 2005
- September 2005
- August 2005

p>






This is a common issue that most of us face. Besides this, recently I was having tough time trying to make them understand the difference between Copy writing and Technical writing!
Another issue is to ask them how many hours it takes them to prepare a NON professional documentation and how they prepare it.
Answers become funny.
Hours ans hours, normally in the evening or on Saturday (sometimes payd, sometimes not depend on the level of the developer).
Then the authoring tool: you will discover how to manually enter a table of contents, or how manually number the pictures or other funny issues..
Then you can, just tell them the lower metric of your best manual, and show it…if you have the opportunity. Or, if you are a true sadist, tell them that even in Word you have something called “field” (oh..”field”!! As in a software code!!)…
Sometimes it works. Try it. And they will start to ask you “How it was possible…?”