Career Forums

There is great debate in my group about when it is appropriate to do a current state diagram. When we implement our software are are changing the processes of many roles and so trying to do a current state diagram for every process would be costly to the client.  If we did we'd probably end up with more than 200 and spend more time on this versus trying to figure out the future state.

Some have said that you do a current state diagram when multiple roles are involved. Others, say you should only do one if you are trying to solve a process problem.  if there isn't a problem, one is not needed.  

 So the question to the group is what factors should we consider when trying to judge when it is appropriate?