eDMS Roshambo Part 5 | Moving Gradually Towards Wiki
Continuing from eDMS Roshambo Part 4 | Feedback with the wiki versus the MadPak with Feedback Service.
Wikis clobber eDMS when it comes to collaboration. Wikis are great but getting the end result into a user manual format still requires an external tool.
Rock Paper Scissors (RoShamBo): Wiki vs the MadPak, Analyzer, and Feedback Service
There are strengths to not having a Wiki model introduced right away into a corporation. Dan Ortega mentions corporate policy holding back the anarchy, however it helps considerably when there is a gradual move towards the Wiki model.
MadCap is halfway through the Wiki model already with just the MadPak. Add to that the Analyzer and Feedback Server/Service’s Web 2.0 features, you’ve got yourself a good step past Wiki as far as maintaining positive control over the content.
With Analyzer you’re looking at a Documentation Manager’s dream package.
I think the key element is… how much time would this all save each role a Technical Communicator has. Let alone the workflow’s editing search and correction time.
Cost - $1200 for the MadPak and $400/quarter for the Feedback Service ($1600/year) so you don’t even need to host a server and stress the IIS configuration. No pricing on Analyzer is yet available. I really should get some sort of Amazon Buy-now button for this stuff.
As far as the industry tools are currently set, MadCap Analyzer could save upwards of $50k - $80k a year in tech writer time and other software. That’s pretty hefty, although at the time I’m writing this MadCap hasn’t set a price for the Analyzer.
Note: Pricing for Analyzer is pretty cheap, as I edit this article I find that it’s only about $200 or so to upgrade.
Posted by Charles in Software, Technical Communication, Web 2.0, Workflow Collaboration, wiki |
