Domain
Process
How value streams, capabilities, use cases, and steps describe the movement of work.
BOS Domain Model
The map of how the business actually works.
The domain model defines the relationships between people, process, information, and technology.
Four Domains
The model organizes the business into four connected views.
Domain
Information
How flow object templates, flow objects, and flow items describe the information moving through work.
Domain
People
How functions, departments, employees, roles, and responsibilities define ownership and accountability.
Domain
Technology
How system domains, systems, and integrations support execution across the operating model.
Process Model
Process describes how the business creates and delivers value.
The process model moves from the highest-value flow of the business down to the specific steps required to execute. It gives leaders a practical way to see where work starts, where it changes state, and where it reaches an outcome.
Process
Value Streams
The major paths through which the business creates value for customers, operators, partners, or internal teams.
Process
Capabilities
The abilities the business needs in order to support each value stream and operate consistently.
Process
Use Cases
The operational scenarios where roles, systems, data, decisions, and workflows come together.
Process
Steps
The executable units of work, including sequencing, conditions, approvals, and handoffs.
Information Model
Information describes what moves through the work.
The information model defines the operational entities and supporting items that carry context through the system. It keeps the business from treating every tool record as a separate version of reality.
Information
Flow Object Templates
The reusable definitions for operational objects, including expected fields, states, relationships, and rules.
Information
Flow Objects
The main business entities moving through workflows, such as opportunities, projects, deliverables, approvals, and invoices.
Information
Flow Items
The tasks, data points, documents, approvals, notes, events, and artifacts that live inside those objects.
People Model
People describes ownership, accountability, and governance.
The people model connects how the company is organized to how work is performed. It clarifies which function owns a capability, which department participates, which employee fills a role, and which responsibilities are assigned to that role.
People
Business Functions
The major areas of business accountability, such as sales, delivery, finance, operations, and customer success.
People
Departments
The organizational groups responsible for operating, supporting, and improving specific capabilities.
People
Employees
The people assigned to roles and involved in execution, review, governance, or escalation.
People
Roles
The operating seats that perform, decide, approve, govern, or improve work across the system.
People
Responsibilities
The accountabilities attached to each role, including decision rights, task ownership, review duties, and governance.
Technology Model
Technology describes the systems that enable execution.
The technology model defines where the operating model is supported by systems, data movement, integrations, and applications. It keeps technology tied to business logic instead of letting tools define how work should happen.
Technology
System Domains
The categories of technology capability, such as CRM, finance, documents, delivery, identity, or analytics.
Technology
Systems
The specific platforms, applications, databases, and internal tools used to execute and govern work.
Technology
Integrations
The connections that move context, trigger work, synchronize objects, and coordinate execution between systems.
How the Model Works Together
The domain model connects what the business does, who does it, what information moves, and which systems support it.
A use case is not only a process. It depends on roles, responsibilities, flow objects, flow items, systems, integrations, and business rules. The domain model shows those relationships so the business can design operations as a system rather than a collection of disconnected practices.
Operating Logic
Business meaning comes first
The model starts with value streams, capabilities, use cases, objects, roles, and responsibilities.
Execution Layer
Systems support the model
Technology is mapped to the work, information, and accountability structure the business has defined.
Next Model
See how business objects become executable.
The business object model explains how flow objects and flow items become the runtime layer for workflows, dashboards, integrations, and AI.