TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I need some advice on taxonomy development for a website knowledgebase.
My Google-research taught me that a taxonomy is a classification scheme
containing vocabulary and navigation to make content easier to find. It
will also help guide content development because 'holes' in the content
will have to be filled.
Building has its challenges. According to Gartner, someone
inexperienced in taxonomy development could take up to five times to get
it right. This could cause a few customers of the knowledgebase some
grief, "...why did they move that article again?!". The in-house
development boon is our understanding of our customers and the depth of
technological discourse.
Contracting might eliminate the repetition development, but only if the
contractor is well versed in our customer usability requirements and the
technology. Quite a bit of time and cost for the above.
Has anyone done Taxonomy development in-house or through a consultant?
What steps were taken? How long did it take? Are there any internet
resources to tap? What about skills I should be watching for in future
courses or perhaps in a consultant? Any information would be helpful.
