One could argue that the process that created your products (again widgets or services) should be as efficient as possible and should be able to gracefully handle unknown interruptions (jams in the production line). Furthermore, the process should also be able to handle feedback from your customers. Not just the positive (reviews, suggestions, improvements) but the negative as well (defects, issues, failures, etc). Consequently, the process should also be able to provide your team means to prioritize what to work on next: Improvements or Fixes. As you continue describing and designing the process that creates your products efficiently you will unequivocally come to the conclusion that there is complexity in creating and maintaining the production process efficiently.

In our current state of affairs because of the reasons stated above, you (as the idea creator or company CEO) will find yourself speaking with subject matter experts from multiple disciplines: Product, Finance, Projects, IT Application, IT Data, IT Infrastructure, IT Security, IT Operations etc. You may even speak to other companies producing services that you need to include in your production process (third parties, Google APIs, etc). You need to have a single language that describes specifically and without ambiguity business processes, business actors, business scenarios, IT processes, IT actors (components) and the relationships between them. Failure to do this, will only perpetuate the misunderstandings among business teams and IT teams. Furthermore, even within IT, it doesn’t take much to create ambiguities between say application developers, testers, security and operations.