Who needs a rodmap?

When you're driving from your house to your office, do you whip out your cell phone and follow the navigation?

Probably not.

You've done it dozens or hundreds of times, and you know your way around.

If you were planning a cross-country drive with friends or family to a town you've never seen before, would you be more inclined to look at a map?

Probably so.

That is, unless you and your friends enjoy the adventure of getting lost and finding your way again. I admit, that can make for fun times if you're with the right people.

But when schedules are tight, or you just don't want to deal with getting lost, you might spend some time planning first.

You’d pull out the maps and made a clear plan that included starting times, alternate routes, allowances for meal and bathroom breaks, and maybe even a sightseeing detour or two.

Here's the thing:

When you're trying something new for your CRM, or your staff workflows, or your programs, there’s some effort involved in researching and thinking and making a very clear plan.

If you've done this kind of thing before, and the stakes are low, and you're not too concerned about when you'll get there or how much it will cost, just jumping in is a fine thing to do.

You'll probably learn a lot along the way, and have a good time while you're at it.

But if you've never done this kind of thing before, and if margins are tight and timely success is critical, it's probably worth investing in a little planning and roadmapping.

The road map itself does not get you the results that you're after.

But it goes a long way towards reducing risk and helping you to actually achieve your goals.

All the best,
A.