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.
Start small with a 10-user pilot instance, the program manager who's
had success with it before, and a few SMEs who are interested.
My review workflow's the same as was with FrameMaker, it's just more
automated. I ask the most likely SME to check a new or revised topic.
If they don't have all the answers, I ask someone who might. If I
include an @<username> in a comment the system automatically sends
them an email notice with a link. With built-in inline comments it's
much easier than it was previously (unless you used the Talk plugin).
You can still export Word or PDF and get comments from other SMEs that way.
On Tue, Jul 14, 2015 at 3:31 PM, Rick Lippincott <rjl6955 -at- gmail -dot- com> wrote:
> To go back to your original question:
>>Since it is collaborative, what is the buy in
>> necessary from the engineering group? Is that crucial to the success or
>> failure of using the tool?
> The buy in is significant, and it is critical to the success or failure.
> The last place where I worked, we started using Confluence. At first,
> it seemed like a perfect solution, we'd be able to get everyone to be
> able to see each other's comments and the updates could be done
> We never got buy in from the SME's. Many of them whined that they
> couldn't understand how this worked, and the navigation confused them.
> Even those who gave it a try, unfortunately the quality of the
> comments wasn't much improved. Yep, even in Confluence, I was getting
> "This is wrong, fix it" quite a bit. "Can you detail how it needs to
> be fixed?" I'd ask "Oh no, writing it down is your job. Let's have a
> meeting and I'll give you all the details there."
> So we gave it up.p://techwr-l.com/archives
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW