Scott Francis from BP-3 recently posted a great, objective review of the Blueprint Summer ‘08 release. He does a thorough and insightful job covering the entire product. For example, here’s his take on the Visio import functionality we recently introduced:
Visio importing has long been the “holy grail” for process modeling tools. If I had a dollar for every time someone asked me if a particular BPM product could import Visio models directly I would be rich! However, Visio import into a process execution environment isn’t always all its cracked up to be. Visio diagrams tend to be quite unstructured, whereas BPMN is very structured, and executable BPMN is even more structured in form. Moreover, Visio models don’t have enough information attached to them to be immediately executable. It is possible to run into issues of “who owns this model” once you import the Visio (the business may have the expectation that they can keep making modifications and “reimport” into Teamworks, for example). At some point, the implementors must take over the model and own it to produce something executable. I’ve been working on some models for OMG certification and I thought they would be a fun (albeit simple) set of examples to import into Blueprint for a test drive. Blueprint imports these easily and accurately. I went back to the archives and tried importing some really awful process diagrams circa 2004. The results weren’t pretty (the original wasn’t pretty), but Blueprint imported the models nicely (a visio diagram with 10 tabs and one process per tab). Going to the Diagram View I was able to sort out the diagram into swimlanes and go from there. Interestingly, when I imported a diagram WITH swimlanes defined, Blueprint created those swimlanes and participants for me.
But my favorite quote had to be:
I actually like the diagramming portion better than Teamworks! And collaborating on the same process isn’t just possible, its actually cool. You almost look for an excuse to try to be logged into the same process at the same time so you can try to step on each other. Blueprint handles all the conflicting edits really well. I’m impressed!
We’re very proud of Blueprint’s collaboration and diagramming capabilities as well because we believe that there’s no tool that’s easier to use or can make you more productive, online or off.
Take a look at Scott’s full review when you get a chance.
Today I’m proud to announce the availability of the Summer ‘08 Update release of Blueprint! One of the great benefits of delivering Blueprint in SaaS model is that we’re able to stay nimble and quickly add functionality that improves the value of the product for everyone. So following shortly on the heels of our main Summer ‘08 release, we’ve added features to address some of the most common requests we hear from our customers.
Let’s take a look at them in detail:
Microsoft Word Export: Blueprint now gives you the ability to automatically generate a Microsoft Word document containing all the details of your process. This is a great way to communicate your process to stakeholders that don’t have a Blueprint account. For example, we’ve been using this feature internally to generate “specifications” for our processes when we need to interact with outside vendors.
Ross Mayfield noted today that one of the biggest challenges with collaboration among distributed teams is actually agreeing on who is actually part of the team. Larry Irons quotes research from Distributed Work to that effect:
Of the twenty-four teams surveyed, not a single team was in complete agreement on its boundary: who was and who was not a member of the team. In fact, the average level of agreement within the sample was only 75 percent, such that any given team member was likely to disagree with the rest of his or her team on one-quarter of potential team members.
We see this all the time in real world BPM projects. Agreeing on what the process is is often the easy part. Identifying the who is can seem nearly impossible, especially if a single team is attempting to define a process that is executed in many different locales all over the world.
A distributed, collaborative environment such as Lombardi Blueprint is key to solving this challenge. Having a structured repository to identify and maintain the players and relationships involved in a business process promotes visibility and knowledge sharing among those involved. Discovering the who in a process becomes far easier when all those that are involved can both document their own role and see how where they fit inside the grand scheme of things regardless of what office or time zone they happen to be working in at the particular moment.
We just wanted to check in and report on the first day of our annual Driven User Conference here in sunny Austin, TX.
The day began with CEO Rod Favaron’s keynote, which was all about how we are now at “the end of the beginning.” The secret is out about BPM, attention and visibility are soaring to new heights, and we are now entering a new phase of adoption and maturity.
A big part of this progression is the move from Project to Program to Culture, as Rod put it — in the early days of course it was all about getting your first BPM project up and running successfully, and then it became all about growing that project into a full-fledged program. But the next phase that Lombardi customers and partners are moving into right now is one in which BPM begins to truly impact the culture of any and every part of the organization that it touches, indeed the organization as a whole. This is the true value proposition of BPM ultimately — the idea that BPM becomes part of your DNA, that process becomes an integral part of what your company does every day.
Today I’m proud to announce the availability of the Summer ‘08 release of Blueprint! In the Spring ‘08 release, we delivered what we feel is the best process diagramming tool on the market, online or off. Over the last two months we’ve focused on improving the “other half” of process documentation — the standards and procedures, narratives, and data that make up the details that live behind the picture of the process. Let’s take a look at the improvements in depth:
Rich Wiki Editing Of Process Documentation: Blueprint now provides a rich, wiki-style experience for filling out the details of your process. You can link to external documents, embed images, and format your documentation any way you please. Already have something written up in Microsoft Word? No problem. Just paste it in and we’ll leverage what you’ve already done.
By now, you’ve probably experienced how simple it is to document a process with Blueprint. But we know creating detailed diagrams takes a significant portion of your time. So, we made Blueprint even better! The Spring ‘08 Release of Blueprint is here and it is the next evolution of diagramming. Based on user feedback, we’ve streamlined diagramming and added many requested features to make it even easier & simpler to document your process.
Effective utilization of the process map for simplicity and clarity
Fast and efficient techniques for diagramming
Using subprocesses to reduce complexity and encourage reuse
Leveraging existing work that you’ve done in Microsoft Visio
Update: The webinar is now available on demand. Check it out now. For the Blueprint veterans out there, the webinar focuses on the features we just introduced and I’ll think you’ll find it very informative. But if you don’t have an account yet, don’t feel left out! Sign up for one now and join us on Tuesday.
When you’re tasked with documenting your department’s processes, it can be overwhelming. Often times the project is so hard to approach that the gut reaction is to rely on everyone’s favorite method for doing anything: start at the beginning, and take it one step at a time.
Unfortunately, this approach just doesn’t work when documenting business processes. It’s not the processes themselves that present a problem — it’s the people. When you try to document each step chronologically, the inevitable result is a trip down rat-hole lane. Rat-holing is when you get caught up with the minor details and exceptions that occur in any process. I’ve seen documentation sessions go on for hours with little to show for the effort because each stakeholder in the room was preoccupied with the subtle exceptions to the steps that they themselves were most passionate about.
I’m very happy to announce that the Spring ‘08 release of Blueprint is now live. A quick rundown of the new features is below. But don’t take my word for it: log in now and check it out. Sign up for a your own account now if don’t have one yet.
Improvements in the Spring ‘08 release:
Improved usability in the diagram view : Significant ease of use and productivity improvements have been made in the diagram based upon customer feedback and testing. The toolbar in the diagram view has been replaced by the Blueprint “plus sign”, which allows you to click where you want to insert an item and have it show there immediately. New Blueprint users will be able to get started quicker and experienced users can get their job done a lot faster.
I’m happy to announce that the Spring release of Blueprint is nearly here. We’ve been working on this one for a while and I think it makes Blueprint hands down the best process modeler on the block, online or off. We’re really excited about it and I think you will be too.
Improved usability in the diagram view : Significant ease of use and productivity improvements have been made in the diagram based upon customer feedback and testing. The toolbar in the diagram view has been replaced by the Blueprint “plus sign”, which allows you to click where you want to insert an item and have it show there immediately. New Blueprint users will be able to get started quicker and experienced users can get their job done a lot faster.
Improved drawing functionality in the diagram view : Based upon customer feedback, we’ve closed the remaining gaps in Blueprint’s diagramming functionality. Blueprint now supports multiple end points inside a single diagram as well as loops and parallel flows beginning and ending at any activity. Blueprint should now be able to represent nearly any process flow that you can dream up.
Last month Blueprint’s Director of Engineering, Alex Moffat, spoke at the GWT: Voices That Matter conference. Alex talked about how we built the product and the tradeoffs we made along the way. His talk was really interesting and provides a great peek behind the veil into the development process.
Google was nice enough to record the presentation. It’s embedded below.
When you click the Print button, Blueprint generates a PDF version of your diagram. The great part about the PDFs is that they’re extremely scalable–you can view them on screen or print them on any sized printer (or plotter!). Here are a few tips for working with them:
Viewing Diagrams On Screen Zooming
By default, Adobe Reader scales the diagram so that the entire picture fits on one screen. If you’re going to present your diagram to other people, you’ll want to zoom in:
Choose Actual Size from the zoom menu to view the diagram as it will appear when printed.
Need to reorganize your processes? Over the weekend, we added a feature that a lot of people have been asking for: the ability to move processes between projects.
To take advantage of it, go to the Projects page and find the process that you’d like to move:
Then just click the Change Project link and pick the project you’d like to move it to:
The Blueprint product team is continuously improving the product based upon customer feedback. We’ve recently made some exciting usability improvements and introduced some new features that we’d like to tell you about…
Multi-level Undo
Made a mistake? Blueprint views include a new action toolbar with a one-click access to easily undo your recent changes. You can also print your process diagrams and export to Powerpoint for sharing with others.
It Should be Easy
We’ve made numerous changes to improve the ease of use and usability of Blueprint. These changes include improved help, guided wizards for creating processes, search capabilities, improved process lists, and easier navigation.
Diagram Labels
Gateways and splits now include text labels for improved readability and legibility of diagrams. Blueprint also supports having labels on flow lines as shown below.
Ever make a mistake and wish you could go back in time and fix things? I do. All the time. That’s why we’re adding the ability to undo changes in the next version of Blueprint.
Soon you’ll be only a control-Z away from making amends for that accidental touch of the delete key. Eagle-eyed readers may also notice a few other user interface improvements we have on tap for the next release in the video…
As the Blueprint community has grown, we’ve gotten many requests for a place to interact with other people that are discovering and documenting their processes. People have asked for a place not only to ask questions about Blueprint, but to also share best practices and find solutions to common problems when undertaking a process improvement project.
We’ve heard your requests, so we’ll be opening up The Blueprint Forums very soon. Here’s a quick screenshot to whet your appetite…
When we were initially researching Blueprint, we saw one thing over and over again: process diagrams hanging on the walls. If you’re trying to teach the details of a process to someone or just trying to get a bird’s eye view of things, it’s hard to beat a big printout pinned to the wall. We even had one customer tell us that they measured the complexity of their process in terms of the length of butcher paper required to draw it!
Then again, once it comes time to change what you’ve got drawn out on the wall, things get a little hairier. That’s why we recently added the ability to print scalable versions of the diagrams you create in Blueprint. Now you’ll be able to utilize the collaboration and change history features in Blueprint to keep your processes up to date easily and quickly, while still retaining the ability to create over sized diagrams to put on the wall. Better yet, since we generate a PDF version of your process, it’s your choice whether you want your process to fit in your Moleskine or on 30 feet of butcher paper.
Since Blueprint was launched on April 30th, I’m excited to say that we’ve signed up thousands of customersso far all across the world, and we’re growing every day. The earlyreviews of Blueprint were excellent and it’s great to see over a thousand people enjoying Blueprint’s benefits each day. For the team here, this is validation of all the hard work and long hours spent researching the difficulties customers run into while documenting their processes and building the solution to them.
Unfortunately, this approach just doesn’t work when documenting business processes. It’s not the processes themselves that present a problem — it’s the people. When you try to document each step chronologically, the inevitable result is a trip down rat-hole lane. Rat-holing is when you get caught up with the minor details and exceptions that occur in any process. I’ve seen documentation sessions go on for hours with little to show for the effort because each stakeholder in the room was preoccupied with the subtle exceptions to the steps that they themselves were most passionate about. 
Watch a preview video now.
Watch a demo
Posts