You know this as well as anyone. Processes cannot be a faster way to do more of the same. You cannot be designing processes that are not able to keep up with the change. Your processes have to have CHANGE built-in.

I'm sure you already have your own recipe. Allow me to share with you, mine:

1. Use Business Rules - remove from the process any ability to make decisions. Isolate the expert systems outside the process.

2. Use Human Workflow - if the expert system fails to return an answer, escalate to a human and allow them to lead the process execution

3. Use Business Activity Monitoring - the only way to know where you heading is by tracking where you are over time. BAM is your map towards your objectives. Please see the the entry "How to pick bullet proof KPIs for BPM design ".

4. Log Exceptions and incorporate resolution - don't just track exceptions. Exceptions are the only way by which your system is going to be able to learn. Ensure that your design forces the user to enter its knowledge into the expert system of choice.

5. Make it simple - avoid long and wide processes. If your process is longer than two pages, or wider than one, you are probably doing something not very efficient. Usually it is an indication that you are including too much expertise inside your process. Put it out!

There other ways to built-in change by using systemics . If you're only now starting, I suggest you design your processes with this in mind. If you ready for the next level, I suggest you contact us. You will be surprised!