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 am creating a project plan. The template for my project says I need to have various sorts of documentation as deliverables from certain steps--I need a business case, functional specs, design specs, test specs, user doc, and marketing collateral, for example.
I need resources (people) to create the documents. I can get the right people if I can match the skills required to create the documents with the people who have those skills.
At this point I am looking for success in meeting project needs; I am not looking forward to the day when I have to hold someone accountable for failure. So a skills matrix is not for beating you about the head with a stick.
Basically, I need to know if the team I put together can, among them, understand the technology; write, edit, and produce engineering documents; and write, edit, and produce user documents and marcomm.
So those are the interesting skills:
Research and write
Research and write
I would not drill down to the tools level. If someone is identified as having production skills, presumably that token refers to production skills within your company's tools environment.
>I've been asked to contribute to our a company wide skills matrix. Each area
>will have it's own matrix with one being 'general' attributes such as time
>planning, business awareness etc etc. Each 'skill' is broken into two levels
>(or three if required).
>So (and this is probably more of a check) what should I put down for
>My main concern is missing something obvious and making a rod for our backs
>later on (not sure how this matrix is going to be used, just that it MUST
>been done... ho hum)
Purchase RoboHelp X3 in April and receive a $100 mail-in
rebate, plus FREE RoboScreenCapture and WebHelp Merge Module.
Order here: http://www.ehelp.com/products/robohelp/
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.