How is technical communications evolving?

In the few short years I’ve been in the biz, I’ve seen a drastic push for online help in replacing traditional text outputs. The bible-length manuals we used to print were often seen as an afterthought for products. While each doc set has a particular purpose and audience, companies are now looking to social collaboration to drive customer satisfaction. Wikis with embedded social help features offer real-time customer feedback about a product, crucial from a developer’s standpoint and marketing teams post launch.

Microsoft SharePoint: ‘Yammer’ is a social media tool fostering collaboration, knowledge and efficiency. There are endless possibilities with  apps and open APIs to be explored. Naturally Yammer is paired with Microsoft products; which means, a Microsoft Dynamics integration supersedes Salesforce CRM.

Mindtouch: ‘A social help system that includes a knowledge base, help center, ticketing integration and a help button.’ Enough said.

Atlassian Confluence Wiki: A robust system designed with JIRA users in mind. Some key features are: Embed Google docs, Scroll Version, and team calendars. Want a slimmer version, perhaps on a diet? Try Confluence Blueprints.

MadCap Flare: ‘Pulse’ is a social collaboration platform in conjunction with the Help Authoring Tool. While pricey, MadCap serves the purpose in finding one software to do five, ten, fifty, one hundred tasks in one.

Want to read more about wikis?: Follow the discussion on LinkedIn.

The next generation of wikis

Did you know the origin of the word wiki is Hawaiian, meaning quick, fast? Wikis are website portals that are open for anyone to edit content. I use the word portal precisely as wikis are not static webpages. You can navigate from any one given point and easily be redirected to other sources for PDF files, video links, etc. It is meant to be on the cloud, meaning anyone can contribute, but there are also precautions that can be made in order to manage user’s views and permissions of content.

In tech writing, wikis are replacing the traditional user manual. No longer will you have to print out a ten-page quick start guide for a product, but instead enjoy a much more friendly user experience. Wikis are interactive, intuitive and visible throughout the organization.

Some of the top wiki providers are Mediawiki, Confluence, and Dokuwiki. One company offering an alternative solution to Confluence Wiki, however, is Mindtouch.

There are a few key features that beats the rest:
– Mindtouch’s product is context-sensitive
– Offers a robust reporting feature (aka Google Analytics for Marketing)
– Integrates CRM (Salesforce) data for real-time product feedback
– Bug tracking system that can replace or used in conjunction with JIRA
– More outputs and even offers an easy Flare-to-Mindtouch wiki migration
– and did I mention Agile friendly?

So get on board with Mindtouch, because they are redefining the user manual with a more impressive wiki.