<img alt="" src="http://www.qlzn6i1l.com/118942.png" style="display:none;">

Employee Training

Road maps and Roadblocks

Greg DeVore - Jan 5, 2012 7:59:00 AM

Without clear goals your software documentation is bound to fail. Recently we have started thinking of our documentation in two contexts:

  1. Documentation that provides a road map
  2. Documentation that removes roadblocks

Roadmaps vs. Roadblocks

A Road map tells someone where to start and what steps to take to arrive at a desired destination.

A Roadblock is something that keeps someone from continuing on the path they are already traveling.

The main difference is that someone who has encountered a roadblock already knows where they want to go. They are just stuck and need help getting unstuck.

Someone who needs a road map doesn't know where they are going yet. That is why they need the road map.

For example, a consultant setting up Salesforce in a new org who gets stuck with setting up single sign-on doesn't need a road map. They know what they want to do. They just need documentation that helps them remove the roadblock that is preventing them getting single sign-on working.

But a brand new Salesforce admin probably needs a road map that will help them implement Salesforce correctly and achieve product adoption. Removing roadblocks won't help them yet since they don't even know which road to take.

Customer Support vs. Customer Success

Our popular Plan not to Plan methodology is ideal for removing roadblocks. Someone gets stuck, they ask you a question and you answer it with crystal clear instructions. The next time someone asks the same question you have a ready-made answer.

But what about that person who needs a road map? Their needs are very different. They know the outcome they want. But they have no clue how to get there. The Plan not to Plan methodology doesn't meet the needs of these people because they don't even know which road they should be on. In providing a road map you need to address broader topics and best practices as opposed to just how-to's. This takes planning.

Were do Road maps and Roadblock apply

Road maps should be used for:

  • New customer onboarding
  • Establishing best practices
  • New user onboarding (when a new user is added to a plan or an account)

The goal with road maps is to give your customer a clear understanding of how they should be using your application.

Roadblock removal comes into play after the customer has the road map. The purpose of roadblock removal is to decrease customer support requests and keep your users sailing through their daily workflow.

Providing road maps will allow customers to adopt best practices which will ensure customer success.
Removing roadblocks will decrease customers support requests.

As you develop your documentation strategy you need to address both issues. In a future post we will explain how we are tackling this issue here at Blue Mango.

Topics: Software Documentation Tips- Customer Support- Customer Success- Documentation Managers

Greg DeVore

Greg DeVore

CEO of ScreenSteps

Previous Post

The Hidden Power of an Online Manual

Next Post

3 Tips for Keeping Your Documentation Up to Date

0 Comments

Free Training Tips

Subscribe For Employee Training Best Practices

We talk about rollout training, onboard training, and writing better standard operating procedures

Subscribe to Email Updates

100% Privacy. No Spam.