Everyone knows what Roshambo is – rock, paper, scissors. It’s a quick to learn children’s game with its basic roots in human psychology. Apply this to an area, say Policy and Procedure.
Documentation Management or What’s with all this stuff on the H Drive?!?
The existing concepts – eDMS with separate DMS documents, implementing and overseeing a corporate wiki, or the RoboHelp Server each have different strengths.
There’s a great article pointing out the pros and cons of eDMS vs Wikis that I have planned for Part 2.
With Part 3 I’ll go into the history and technology of the RoboInfo Server – a/k/a RoboEngine a/k/a RoboServer a/k/a RoboHelp Enterprise
So now we have a nice easy Roshambo with strengths and weaknesses in each. I’ll also wrap up with where I will be recommending my clients to improve their procedures.
Existing Paradigm: eDMS
Within an eDMS Word documents, disparate help files, PDFs are all available yet siloed with content that cannot yet be single sourced. Editing workflows vary from product to product but none are core technology and are stagnant in quality. The eDMS price point is upwards from $10,000 for the India-based developers into the mid five or low six figures for top of the line eDMS integration.
So cost is a weakness. It’s also risky for a middle manager to have to make recommendations on adopting usage. Editing is normally either a multi-desktop tool evolution or some sort of half-baked internal editing tool within the eDMS.
Proposed use: Wikis.
Wikis are easy for multiple users to use, however dealing with recommended corrections tends to lead towards anarchy without consistent management and oversight. Not a lot of corporations are thrilled about the open-editing functionality and that limits Wiki adoption currently.
I’ve not seen much to change my views from the research I did last year, How Wikipedia Works (Or Doesn’t) | Can Corporations Use Wikis?
Dan from Astoria has a great position contrary to mine. He feels that existing corporate controls will tend to triumph over the anarchy.
So if you take the notion of a corporate blog and loosen the filters to “evolve” it to a wiki, is this the equivalent of letting a pack of hyenas into your living room?
A lot of pundits seem to think so, however, with the proper review and approve mechanisms there is no reason to assume you can’t maintain the same level of control. The benefits of a wiki as an input mechanism to a documentation process that had previously been behind an information firewall are vast.
My response is in the comments and basically states that if a corporation is willing to listen to the unvarnished truth without punishing the contributors, they will be able to get the wiki job done.
I personally am skeptical about corporations not killing the messenger.
Yesterday’s Faded Glory: RoboInfo Server / RoboHelp Enterprise
RoboHelp / RoboInfo with the RoboServer is one method I’ve used for the past few years. RoboHelp can import content in, but it’s siloed and wrapped in proprietary format once it’s in. With the RoboServer other source information can be indexed. The Adobe Technical Communications Suite (Adobe TCS) brings things to ‘almost single source’.
In my opinion the Adobe TCS strategy with bundling the Acrobat 3D is that people will start drawing all of their documentation instead of writing it. Sort of like IKEA furniture instructions. I am beginning to believe that Adobe doesn’t know the true definition of Technical Communication, or they are attempting to change that definition.
Disrupting the Doc Management Roshambo – Analzyer and MadPak
MadCap’s solution set of the MadPak with their Feedback Server has been making a debut with its innovative Web 2.0 interface. Now, with the addition of the soon to release MadCap Analyzer, we’re looking at a true Roshambo contest for data management and documentation managers.
After sitting down to take a sneak peek at the MadCap Analyzer, I’m realizing that workflows as we know them for documentation are about to make an abrupt shift upwards in efficiency. As far as I know, MadCap’s Analyzer will release sometime this January.
Analyzer is breaking that rock-paper-scissors deadlock with a wrecking ball.
Since keeping documentation as simple as possible is the hardest task to accomplish, Analyzer allows a Documentation Manager the capability to review consistency quickly, a task that would normally take hours or days to complete is now a matter of minutes and can be run on a daily basis.
I’ll post a review of Analyzer shortly, having first seen its close to release version just this week.
What I’m guessing is that the MadPak will fit nicely into an existing eDMS solution, bringing Web 2.0 capabilities and advanced authoring assistance directly into the documentation team’s grasp.
My proposed adoption: For managers who have eDMS, use of the MadPak with the new Analyzer will make their doc teams sing their praises louder than Vikings sending heros off to Valhalla.
For small companies who have data silos and have a need for single sourcing that data, FrameMaker, Word, and RoboHelp content can all be aggregated with MadPak. That’s if you’re planning on spending less money later on by having all the information in one place.
For Wiki proponents, read my article How Wikipedia Works (Or Doesn’t) | Can Corporations Use Wikis? because the quoted Harvard Business School professors do the Wiki adoption point much better justice than I could in one or two paragraphs.