Hi, I just recently joined this group. I would like to know what your process is for the To-Be approach once you've completed the As-Is. Do you:

a) Create an initial To-Be as a starting point that is based on the As-Is, making improvements in the process as you go, having the customer provide input, etc.

b) Start from a clean slate and find out what the customer would like to see in a perfect world, then later once the functionality has been determined, help the customer (or let them tell you) what role will do what step (the swim lanes).

Please let me know for my own sanity!

Thanks!

The best approach I use is to determine what the business thinks is the problem(s) with the current (as-is) process. That gives you a starting point to look at the flow, understand what the pain points of the business are and to formulate more than one option to resolve the business need. Knowing what/how the providers of the solution (developers, platform, etc.) is something to keep in mind when presenting your options.

Chances are you are only making recommendations for solutions and the business (aka stakeholders) will determine which direction the new solutions will be. K

Keeping the business and the solution providers involved by asking questions and setting expectations will allow the to-be processes you come up with as potential solutions to the business needs allows all parties to set scope and further define the solution. Once a solution is decided upon, you will already have established a rapport with the people on both sides so the project to bring the future solution to fruition will be successful.