Process Mapping Saves the Day
Project success demands close IT and business partnerships. It takes partnerships that go beyond a routine business requirements definition followed by IT design. Improving business results now often requires the involvement of technology experts in the development of the business approach, long before requirements. For example, an enterprise architect may need to help the business understand new or emerging opportunities that must be considered before plunging into conceiving programs or projects.
What is needed is a formal way for IT and the business to interact effectively--a structured method for the important discussions to occur, building trust, bringing about understanding and minimizing controversy. The successful tactic must allow business representatives to visualize how the workflow will change using new technologies so that benefits such as cost savings and increased speed-to-market are clear.
Can any interaction technique ever do all that?
Process Mapping to the Rescue
There is a way to structure conversations around displaying and designing new processes. Call it process mapping or developing business process flows or workflows, it doesn’t matter. What matters is that process maps give you a visual representation at a level of detail appropriate to the management level in discussions.
High-Level Design & Decision-Making
Please log in or sign up below to read the rest of the article.
|
If Stupidity got us into this mess, then why can't it get us out? - Will Rogers |




