Re: Confluence Usage

Subject: Re: Confluence Usage
From: Robert Lauriston <robert -at- lauriston -dot- com>
To: Laura Phillips <laurap -at- pluribusnetworks -dot- com>, TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 15 Jul 2015 09:48:07 -0700

Confluence's inline commenting, which did not exist when Rick had that
unfortunate experience, is much easier than commenting on PDFs. It
allows back and forth discussion with email alerts when someone
responds, pretty much like this discussion here only linked to the
relevant portion of the text (much like MS Word comments).

It sounds to me like Rick's problems stemmed from trying to do too
much at once. You have the advantage of a program manager who knows
how it works when it's done right.

On Wed, Jul 15, 2015 at 7:17 AM, Laura Phillips
<laurap -at- pluribusnetworks -dot- com> wrote:
> Thanks for that input, Rick. Thatâs exactly what I thought would be the make or break point for using the tool. Since I got pushback that commenting on PDFs was too hard, I donât think that this is the tool for us at this time.
>
> I will put this in my back pocket for use later when the topic comes up again.
>
> Thanks everyone, I sure appreciate the feedback.
>
> Laura
>
>
>
>
> On 7/14/15, 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
>>rapidly.
>>
>>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.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives


Follow-Ups:

References:
Confluence Usage: From: Laura Phillips
Re: Confluence Usage: From: Rick Lippincott
Re: Confluence Usage: From: Laura Phillips

Previous by Author: Re: Confluence Usage
Next by Author: public domain command syntax convention guide?
Previous by Thread: Re: Confluence Usage
Next by Thread: Re: Confluence Usage


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads