When I was out at Cloud Connect, I met Dan Woods who writes the Jargon Spy column for Forbes.com. Turns out Dan has a particular soft spot in his heart for BPM and I was able to give him a quick demo of Lombardi Blueprint. The result was his piece that came out yesterday, “Stalking and Capturing a Business Process — We need a process for creating business processes.”
Be vewy, vewy quiet, we’re hunting pwocesses
Dan is clearly sold on the value of business processes and BPM:
“For large and small firms, the business process is the right way to think of what to do and how to do it better, whether or not it is automated or supported with technology. BPM puts the focus where it should be–on what you must do to make your company successful, not on the capabilities you happen to have.”
What he wants to know however is how are these processes captured in the first place? If the processes being submitted aren’t of quality, how can you expect the BPM results to be? Garbage in, garbage out.
Incremental and Collaborative…that’s the ticket
Dan argues that developing the processes incrementally is the only way you can be assured of solid inputs. The three approaches he advocates are: Wiki-based process discovery, Task-based process discovery and Mash-up based process discovery. And this is where the Blueprint shout out comes in:
Lombardi Software has recognized this trend and recently launched a Web-based service called “Blueprint” that allows for collaborative brainstorming and definition of processes. Using this service, you start with a bunch of ideas and can end up with a nice diagram. The JargonSpy imagines such a system could be used as the scratch pad for capturing and refining the processes that emerge in the other three methods.
Thanks for the mention Dan, and thanks for pointing out the importance of iterative and broadly inclusive input collection up front. For without that, are we not building our BPM castles on diagrams of sand?
Pau for now…