How the operating model is structured
The distinct structural, assignment and occupancy views used to describe work.
A useful work model keeps several relationships separate. It distinguishes where work belongs, how accountability is assigned and who currently occupies a position.
Operational structure
The operational view places work in a hierarchy:
Department → Domain → Work Module → Work Unit
- A Department provides broad organisational context.
- A Domain groups a coherent area of responsibility.
- A Work Module keeps related work together around a shared object, interface, pattern or working context.
- A Work Unit describes meaningful recurring or when-required work.
Every valid Work Unit belongs to exactly one Work Module. A Work Module is a practical grouping for related work, not a claim that every organisation uses one universal technical boundary.
A Work Unit has a trigger, inputs, intended result and completion boundary. Its type may be a Responsibility, Automation or Agent Action.
Organisational assignment
The organisational view answers a different question:
Department → Position → Role → Work Unit
A Position is a seat in the organisation. One Person occupies exactly one Position at a time. A Position can hold multiple Roles, and a Role can be shared across Positions. The Work Unit is where the organisational and operational views meet.
Occupancy is not work definition
Person → Position describes occupancy. It does not define the work itself, change the structure or make the person the owner of every related record. Keeping these views distinct makes reassignment and redesign easier to reason about.