online collaboration,workflow collaboration,web 2.0,technical support,technical writing,technical communication,madcap flare,madcap feedback server,robohelp server,adobe robohelp,blogging
Update: Feedback Review Part 2 is now available
First looks for the MadCap Feedback Server: Front-end
Wow. In a nutshell, MadCap has managed to streamline their Feedback Server and in doing so, they win my personal 2007 KISS software award.
How simple can you keep everything? Don’t overcomplicate what you know to be core, and develop based off of what the users want.
In this reference KISS has nothing to do with Gene Simmons, by the way. It’s more like the Staples Office Supply Easy Button: "That was easy".
How Madcap is MadCap?
You must understand, a visit to MadCap is like going to Seaworld; you know there’s going to be a show and even if you miss it, there is plenty to see. If you want a taste of innovation, arrange for a tour.
While waiting in their lobby I even ran into the model for their recent Tech Support ad campaign. She’s not so uptight in real life, but can really play it for the cameras.
I was actually running a bit late but that worked to my benefit. I was able to also meet Sharon Burton, key influencer and Product Manager for the new Blaze product which is in the works from MadCap.
This is a bit off topic, but apparently MadCap has big things in store for FrameMaker users, an area I seldom delve into strictly out of personal prejudice against the FM UI. Sharon made it sound compelling enough for me to think I might want to look into implementation of this product.
Oh yeah, another thing about Sharon – while she’s been around the industry for years it hasn’t dulled her sharp wit. She’ll fit right in with the MadCap crew. She even gave me her two cents about corporate wikis, compelling enough that I asked her for a sit down chat in a few weeks to talk about some industry stuff.
MadCap’s Technical Support: Eating Their Own Dog Food
I stole ten minutes of company time from Var Galpchian, MadCap’s Support Manager who told me the easiest way to see the Feedback Server was to check out their Knowledge Base. After all, all companies should dogfood whenever possible. From Wikipedia:
To say that a company "eats its own dog food" means that it uses the products that it makes. For example, Microsoft emphasizes the use of its own software products inside the company. "Dogfooding" is a means of conveying the company’s confidence in its own products.
Var’s a savvy support veteran who knows the value of eating ones own dog food. I would expect ASPOnline judges to be checking her team out this year for the small business category of online support.
Of course I was there to see her laugh out loud when she brought up the Feedback Server example on their Zombie Avoidance System a/k/a the Knowledge Base:

I always enjoy a good joke and clearly so does MadCap’s Tech Support staff. I think it’s refreshing to trust one’s employees in today’s corporate fortresses.
They’re a cheeky lot, to steal a term from the Brits, as the above title combined with the October pumpkin color theme for the Knowledge Base shows:

By the way, that’s the rating system for their Feedback Server. Users can rate the articles. Comes in handy when people use it.
Check the Feedback Server out yourself!
Var told me about their online presentation but I couldn’t make it because I’m doing my SIP Panel construction today and tomorrow up in NorCal as part of the 21st Century Farm Project, which is why I stopped by MadCap’s corporate office (late, I was supposed to go in September) to get the scoop before I got out of town.
If you have time tomorrow, check out their online presentation. Here’s the url to their Friday, October 5 10:00 am PST invite. Click the link, it should, at the very least, be entertaining – after all, you can ask about how the Zombie Avoidance System can help your documentation.
Why Use Server Based Help?
Of course the magic behind any server based help file all happens behind the scenes in the user statistics just like Adobe RoboHelp Server, you get to know what people are looking at so you can focus your resources on restructuring those hot spots.
Additionally, your engineering team knows where best to look at fixing the GUI issues they may be guessing at.
The problems that eHelp started having were in keeping the server going, and supporting all the Enterprise installations which had issues. Adobe inherited those problems and fixed them by axing the Natural Language Search component in their Adobe RoboHelp Server. My beef was that Adobe didn’t tell anyone this for weeks until there were complaints.
KISS principle defined
I first became acquainted with the KISS principle through my grandmother, a woman whose organizational abilities were legendary in my family. Definition from Wikipedia:
The term KISS is an acronym of the phrase "Keep It Simple, Stupid", and the KISS principle states that design simplicity should be a key goal and unnecessary complexity avoided. It serves as a useful and frequent verbal exhortation (or even dedicated policy) in software development, animation, engineering, and in strategic planning (especially military operations).
Later on, the Navy had a great deal to do with my adoption of this quite obviously, I still follow it with my rules of planning. If I can make something simpler I will do it to avoid complications. Climbing has this rule in making knots, you keep it simple because less can break.
KISS in Online Documentation
How simple can you keep everything? Use the KISS principle:
- Don’t overcomplicate what you know to be core, and develop your help based off of what the users really need.
- Crush the workflow logjams. Show people that you really need their subject matter expertise.
- Find out what’s broken from analyzing where people are going within your help documentation.
What I found at MadCap by talking to Var and looking at the Server in action exemplified the KISS principle. It also goes a great deal towards revolutionizing workflow collaboration, my primary focus for this blog.
Quick Look: Web 2.0 Meeting Technical Support
Unobtrusive.Yet compelling when users are used to the Blogging sort of Web 2.0 interface. This is why I enjoy the simple aspects of this server technology:

What happens within the Topic Comments area will be revealed in my continuation of the review.