Workflow is one of the first things you should do

Workflow shows how things are supposed to work at a high level. It is one of the first things that should be done in any system, not just Curam. The purpose of doing the workflow is to understand how the existing system works and find out places which can be improved upon and which of them are more important. However, do not fall into the trap of "analysis paralysis" either. Workflow should be done in concurrent with other tasks in Curam or non-Curam development. One caveat: Do not use Curam as your primary workflow modeling tool. Curam's workflow editor is a pain to use at best and hard to visualize change immediately. But it also does not mean you totally disregard it. So what tool should you use? Well there are tools like WebSphere Business Modeler which gives you a nice GUI, but I think the best visual modeling tool would be one of those "Smart Boards" which is a white board that can export to a file and redisplay it as well. The thing that should happen at the end of the day is a junior Curam workflow developer transcribes the workflow into the System Integration Test environment to make sure that it can be translated into Curam. The workflow developer just models manual task blocks and maybe some loops and routes. The customer can then validate the workflow as needed on the test environment by calling a UI that enacts the workflow process.