Gleanings of the WfMC Thought Leadership Summit
Some reflections about the WfMC Thought Leadership Summit that I was invited to attend.
Suddenly I felt like in a lively discussion about what I thought for some time about the inflexibility of BPM models (what if the approver is on leave?), the ad-hoc nature of real processes (like in a court trial) and the small amount of system support for these.
Yes, Business Process Modeling to a degree rests on the assumption, that there are repetitive procedures that are triggered by a business transaction, and which is described in terms of which steps to execute as a result of it. Like a machine.
Did you ever wonder why there is so little standard software for startups – or business process models? If it where a standard process, it were not a startup. The driver in the seat hopefully is the founder of the startup, not a process.
I agree to the observation, that there are much more processes like this all over the place. And maybe there should be even more again, reverting the feeling to be but a cogwheel in the engine, but a responsible contributor – even for the benefit of the whole.
Still, what we need to work effective is system support for
- our information
- Collaboration and Communication over the information
- a clear status of all of the process and all parts of it
- Decide about next steps as you go
- Decide about required information as you go
- Decide about groups and access policies as you go
- Decide about information structure as you go.
- Overview and Tracking
Only to mention the most important ones.
This is not what you can to with BPM . Therefore we need a new breed of software which is not BPM, even if it is related to it.
I want to mention two things, that were not or not deeply discussed in the meeting as an additional contribution and defence of what I said.
First: Even with all the ad-hoc type of processes it is clear that over time some of them evolve in standard processes, which is a good thing. Because that is the time to earn money for the process owner. So there must be ways to
- pick best practices and develop them into standard processes
- re-design a bunch of local best practices into a global standard process.
- impose constraints of a standard process on the business
All of that as you go – i.e. without interfering the running processes.
Which is easily said – sounds a little like marketing buzz – but certainly challenging in terms of technology. But I wouldn’t say it, if I didn’t think it’s possible.
In Process design and re-design I disagree here with Max J. Poucher’s more philosophical statements about evolution. I do not believe as much in evolution as an unguided process as he seemingly does. I believe that redesigning processes as a whole makes them more effective, and more rewarding to everybody if done right.
Second, I think that we need is a seamless integration (A word that you first learn in marketing) with structured processes – be they classical workflows or classical ERP processes. In my opinion there is much ROI to be found.
Related Blog Posts
Adaptive Case Management by Max J. Pucher

Social Links