Business Plan Blog: Business Plan Writing Made Simple header image 2

How do you measure technical documents? What metrics do you use?

November 21st, 2009 · View Comments · Career

One of our tech docs team was fired yesterday. Why? Technical documents provide no value.

This is how Management sees it.

Tech docs are nice to have but NOT essential.

Tech docs are useful but LESS important than development, user interface and marketing.

Are they right?

It’s hard not to get defensive in these situations. But maybe they have a point.

I was asked – “what metrics do you use to tell if the documents are successful?”

I did.

But they didn’t like (or agree) with my interpretation.

Do you even have any metrics?

How can you tell (objectively) that your documents are worth the money?

If not, maybe you next to be called into the office.

“Look , your documents are great but…”

Related posts:

  1. Are technical documents a waste of time? “Don’t worry” she said. “No one reads this stuff anyway....
  2. 5 Reasons Why Women Are Better Technical Writers Than Men? Technical Writing attracts women. They’re very good at it and...
  3. What kind to Technical Documents should I write for Java projects? What kind to technical documents should I write for Java...
  4. XML has won! All major office suites now save their documents in zipped XML by default For Microsoft®, the nightmare of a younger, nimbler competitor overtaking...
  5. Is a Degree In Technical Writing Worth The Effort? Do you have a degree in technical writing or technical...

Tags: ······

  • KaranSachar
    Hi Ivan,

    What are these success metrics? Kindly explain.

    Karan
  • Hello Karan,

    There are different ways of approaching this.

    For example, how can you tell how successful users are when reading your documents?

    Do they understand the instructions?

    Are they able to follow the material without getting lost?

    Do they know where to find the material? I.e. indexes, sitemaps.

    The reason I ask this is two-fold.

    1. Companies have approached me to test how ‘efficient’ their documents really are. There is a growing concern that ‘documentation’ needs to be tested more rigorously – otherwise, it’s a luxury.

    2. The more I move into consultancy and away from day to day tech writing, the more these type of questions come up. How can we save money with our tech docs? How can we use them to generate sales, leads, endorsements etc.

    So, it’s an open question.

    How do you test documents and how do you justify their use?

    If you don’t test them…

    Regards,

    Ivan
blog comments powered by Disqus