Now, we can connect Actors, Flows, and Key Objectives into the MoSy’s High-Level System View. Basically, actors interact with the system through flows that allow them to achieve their key objectives. It’s a structured view that mixes and connect business goals with operational processes.
The diagram depicts the system at the center as the core value facilitator for the customers. On the right side, you place the customer actors along with their key objectives (which must directly map to the value propositions outlined in the business plan). On the left, you illustrate the key partners and resources (each associated with operational objectives). Then, you connect the system to the rest of the actors in pairs, using big arrows that serve as the baseline to add the different flows in your business.
A simple e-commerce example of a High-Level System View in MoSy
The flows illustrate the interactions between the system and its actors and are placed on the arrows. The start of the arrow indicates who initiates the flow, and the head of the arrow points to the recipient. Flows must not represent technical transactions but only business-driven functional interactions.
By visualizing these relationships, the High-Level View diagram serves as a strategic baseline for defining and optimizing how a technological system fulfills its role in the broader business ecosystem. It works well for documenting and evolving existing systems and designing new systems from scratch.
After filling in the Business Model Canvas, this diagram is a natural step in sketching how to connect the different pieces—customers, Partners, and Key *Resources—*to deliver your value proposition, especially when you plan to do it through an IT system.
In cases when you don’t have a visual representation of your business plan like the Canvas, using MoSy and this High-Level System view is even more helpful since it can be the first visual reference you use to enable valuable discussions.