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 don't entirely agree with you. There are a myriad of ways you can
verify your knowledge of subject-matter, and not all work in all
contexts and cultures (diagrammatic approaches included).
On 12/12/05, Tony Markos <ajmarkos -at- yahoo -dot- com> wrote:
> Excellent point! I would use behavioral based
> interviewing to find out where the writer stands on
> this critical issue. I would ask "How would you
> verify your product understanding with an SME?" If
> the writer say he/she would ask the SME to review the
> document he/she created - wrong answer! Requests for
> SME review of documentation is most often only going
> to get some minor (typically single-word) changes.
> Correct answer: Tech Writer would use a diagram
> technique specifically designed for effective
> multi-cycle reviews of product essentials.
HATT List Owner
WWP-Users List Owner
I support Char James-Tanny for STC Secretary.
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l