One of theme I constantly return to is that once you assume that you are building a solution for users, there are lot of issues you need to consider – even for workflow. Most BPM tools completely ignore these aspects – and many BPMS tools require that you get into relatively low level programming to do this kind of work.

That is why I am always happy to find simple best practices about usability that can easily be applied to applications built using a BPMS (or of course ACM). Jacob Nielsen wrote a good post on “Workflow Expectations: Presenting Steps at the Right Time” – it is about how to plan for user expectations when creating a workflow for users – in this case  it mostly about steps for a single user, but the thought process is applicable for workflow between users too.