There’s Not An App For That November 30, 2009Posted by Chuck Musciano in Leadership, Technology.
Tags: Communication, Relationships, Technology, Users
I’ve been in a few CIO briefings of late that have revolved around the topic of business process management. There is little doubt that much value can be found in formally capturing, defining, and managing the hundreds of processes that keep our companies running. Even the simplest processes can have costly inefficiencies that can make a big difference in delivering good service and maintaining efficient operations. A good BPM exercise can find and eliminate those issues and yield a good return on the effort.
For many of these initiatives, much time is spent selecting and implementing the right tool. Certainly, having a sound workflow system to drive your processes helps. The right system can automate mundane tasks, track all sorts of things, and make sure people know who needs to do what when.
As with most tools, however, it is easy to get so wrapped up in the tool that you lose sight of the real goal: creating a better process. While it may be fun to connect lots of boxes with lots of lines, you’re creating a monster, not a better way.
I was once a party to just such a monster, several years ago. As part of a workflow design team, we were tasked to formalize and automate a process within our company. This process had several gates, at which point someone could reject the item and stop the process. This had been a bit of a sore point in the past, so we were careful to design in ways for rejected applicants to appeal their rejection.
This quickly escalated into a multi-level appeal process, with committees and advisors and automatic hearings. It looked great on paper and took seven pages to draw out all the various options and choices that could occur. We were pretty proud of this “better” way of doing things.
Finally, we all came to the same conclusion: this was a disaster in the making. First, it would be extremely difficult to implement. Second, it attempted to automate tasks that really needed to be handled by people. And third, it would cause confusion and chaos among the users.
The real answer to the problem was far simpler: when an item was rejected, the rejecting party was expected to call and explain the circumstances to the rejected party. The whole group realized that actual communication had an important place in the automated workflow.
That lesson hasn’t changed. Tools are useful, but they can only go so far. We cannot automate the most important part of any business: the interaction between team members as they get work done. We need to use tools to remove the drudgery so that people have more time for the high-value interaction that really counts. Freed from mindlessly shuffling paper (or email), people can actually discuss issues and work things out. Communication is the most important thing we do; unfortunately, there isn’t an app for that.
[tweetmeme source=”EffectiveCIO” alias=”http://bit.ly/cio137″ only_single=false]