Last week, I wrote about the importance of understanding user roles and how a successful UI allows each user to focus on what s/he does best, especially with regards cross-functional process teams (Rule #1).

It’s crucial to get these groups aligned from the very outset of a project, to get them walking lock-step with each other as soon as possible. This is Rule #2.

But how is this accomplished through the UI?

The most important thing we’ve learned about aligning cross-functional interests from a UI perspective has to do with the early discovery and documentation phases of the project. This is the first (and potentially only) opportunity to get everyone’s interests on the same page, and is exactly why we created Lombardi Blueprint.

Read the rest of this entry »

In my BPM career, I’ve encountered a broad cross section of approaches when it comes to staffing an initial BPM implementation. I have found that some approaches function better than others, and that there are some clear mistakes to avoid.

One of the key points to recognize is that not all BPM projects are created equal. It is critical that you recognize whether or not your BPM project is a ‘point project’ or a ‘transformational initiative.’ If you start with a project approach and the first BPM projects are successful, it is highly likely that you will have a transformational initiative on your hands. Good news.

Read the rest of this entry »