As a Lombardi partner, I have been asked numerous times what I think of Blueprint. I hadn't gotten a chance to really play with it until last week. The first release was a Beta so I have lots of expectations for the future versions, and so far, all the suggestions that I have made seem to have already been on the roadmap.
It is a very easy to use tool. It didn't take any training to just jump in and get started. The functionality is basic today, but it allows you to create a pictorial image of your processes simply by typing an outline. The idea of having a shared, collaborative environment for process design that can be used by anyone is a good idea. The fact that it then creates a Powerpoint presentation right from the tool is an unexpected benefit.
It is built upon a SIPOC framework which is a Six Sigma process framework which stands for Suppliers, Inputs, Process, Outputs, and Customers. Capturing this information is a great first step for process analysis. Once all the functionality is there, this tool would make a lot of sense for people to use in the initial stages of a project.
You can go do a tour online which is where these images are from.
So, where do you take it from here:
* Add more process mapping functionality (e.g., decision points) - this is a planned functionality that is already in the demo for the GA version
* Allow the process to be BPMN compliant (I believe this is in process)
* Allow the process to be imported right into TeamWorks (in process)
* Add process analysis to make the tool more like the BPA tools (e.g., Mega) - this is also in process and part of the original plan
I have heard and read lots of skeptical comments about this tool, but I think it is a nice front end tool for starting a process discussion and capturing the critical data points. Yes, it doesn't execute today and isn't solving all your problems, but what is.
Comments