The year 2005 is upon us, and the odds are pretty good that you'll be shopping for some software to remodel your own operation. Here are the steps we use to make sure that our clients' shiny new software doesn't become next year's “shelfware.”
Map it first. “Process mapping” is just a fancy term for drawing flow charts to show how information (or work) moves through your company. It's a critical step in selecting and implementing software of any kind, because you can't automate something you don't fully understand. Process mapping can uncover bottlenecks and inefficiencies that will derail your software project or force you into systems that are more expensive and complicated than they need to be. Analyze and simplify your operation first, and your software project will go more smoothly.Cut the paper. Don't assume every paper report you use today needs to be duplicated in your new software. For example, the schedule you now print out and fax might be better distributed on a password-protected Web site, or the information buried in a financial statement might be more understandable in a “digital dashboard” you can view at a glance.No next version. Always evaluate technology based on what is available now, not promises of the “next release.” Even if the missing features actually make it into the software, they may not work as expected or could conflict with something else you're already using.Best of show. Finally, it's trade show season. Always schedule one-on-one time with key product development people — not salespeople — before you leave for the show. When you arrive, leave your checkbook in your room. Today's trade shows are a great opportunity to meet the people behind the software. —Joe Stoddard is a process/technology consultant to the building industry. Contact him at jstoddard@smaconsulting.net.