Skip to content
Fundamentals

Who's MoSy for?

Learn who can benefit from using the MoSy Framework and how different roles can leverage visual system modeling.

MoSy is designed for anyone involved in creating, designing, building, managing, or optimizing technological systems. From executives and businesspeople to technologists. Here’s how different professionals can use MoSy to drive alignment and success:

Business executives and strategists

  • Ensure the organization’s directional vision and strategy (the business plan) are understood by all the departments and aligned efficiently.
  • Get insights about how the different system flows work and map to other aspects (technical, KPIs, etc.), at a good enough level to make informed decisions.

Product Managers:

  • Define and visualize how customer journeys relate to product capabilities –system actions– and business objectives to ensure clear stakeholder communication. Then, leverage the same visuals to communicate the requirements to the engineering team.
  • Slice deliverables into multiple release iterations (e.g., figuring out MVPs) based on technical complexity inputs from engineering and must-haves from commercial teams.
  • Quickly identify the best system tweaks to improve the actor’s key objectives, pursuing the organization’s goals.

Product Designers:

  • Ensure User Journeys and UI/UX mock visualizations directly relate to Product, Engineering, and Business visualizations.
  • Map screens and user interactions to the technical system, identifying team ownership and removing UI/UX silos.
  • Model user feedback loops easily by creating or linking them to new goals.

Commercial Teams:

  • Understand how systems support customer and partner objectives.
  • Learn about the existing system capabilities to identify selling opportunities that leverage existing functionality.
  • Collaborate with product and technical teams to refine workflows and prioritize initiatives.

Software Architects:

  • Design technical components and APIs with a clear understanding of system functions (actions), goals, and flows.
  • Help Product people bridge the gap between the high-level organization strategy and the detailed implementation plans that can populate roadmaps, using simple tools to communicate with stakeholders.
  • Highlight the importance of addressing technical debt by connecting it to key metrics and business value.

Engineering Managers:

  • Evaluate technical complexity and plan resource allocation effectively.
  • Ensure alignment between development efforts and organizational objectives.

Engineers:

  • Gain clarity on system requirements and objectives to streamline development and boost creativity and motivation.
  • Use MoSy to propose experiments, pilots, or scalable solutions.
  • Advocate for technical debt remediation by aligning it with business objectives and measurable outcomes.
  • Find better ways to solve problems by gaining access to the complete context in a simple visualization.

Getting Started with MoSy

Since MoSy helps all these roles, anyone in the organization can promote organizing design sessions with this framework. Whether it’s for an existing system, a new product, or a project, you can suggest using these simple visuals and structures to ignite valuable discussions and create a concrete solution rather than relying on vague requirements and uncertainties.

You don’t need much—just time, a physical board with sticky notes (or an online diagramming tool), and most importantly, people. Bring representatives from all the above departments – commercial, product design, management, engineering/architects, etc. Try to keep the group as small as possible – six to eight people maximum.

It’s also a good idea to draft a version of the high-level system view and the most essential flows in one or two sessions and then involve other people so you can incorporate their feedback. Don’t try to perfect it the first time; it’s an iterative process. Most likely, you all see value from the first time and continue doing it until you have something from which you can make further plans: a project roadmap, setting up a team, implementing new metrics, improving existing flows, etc.