Organizational mixer board – requirements model

OMB Requirement Catalog (ORC)

A requirements model helps the organization translate strategy and mission into clear expectations regarding structure, roles, working methods, competencies, and support. As part of the organizational mix board, the model enables the organization to describe what the business needs to function well, both today and in the next phase of development. The requirements can be used to analyze the current situation, identify gaps, and prioritize changes without losing the overall perspective. For a Chief of Staff, the working method creates a common basis for dialogue between management, managers, and teams. It becomes easier to distinguish between real needs, desired solutions, and temporary symptoms. The article shows how the requirements model can be built, used, and monitored, as well as how it is linked to the other controls in the organizational mix board. With clear requirements, the organization can make more consistent decisions, allocate resources better, and create an organization that is efficient, adaptable, and ready to deliver over time. The model supports collaborative learning, responsibility, and continuous improvement throughout the entire organization in a sustainable way.

OMB 1–10 Governance and corporate governance

Comment on the level of security

OMB 11–20 Accounting and financial reporting

OMB 21–30 Tax and VAT

OMB 31–40 Labour Law

OMB 41–50 Occupational safety and health

OMB 51–60 Data protection and GDPR

Important uncertainty marker

This OMB catalog is still:

• A = High security: verified against the law/regulation.
• B = Reasonably verified: rule/regulation but simplified mapping.
• C = Standard/Governance.
• D = Not verified or organization-specific.

The following groups will be evaluated according to the following principle:

• Legal requirements = law, EU regulation, regulatory order or other normative requirement.
• Standard/governance requirements ISO, COSO, COBIT, NIST, GRC practice or any other established governance principle.
• Not verified = where no clear primary source can be directly linked to the requirement.

OMB 61–70 Occupational safety and health

OMB 71–80 Data protection

OMB 81–90 Information security

OMB 91–100 Information security continues.

OMB 101–110 Contracts and Law

OMB 111–120 Business ethics

OMB 121–130 ESG, sustainability and the environment

OMB 131–140 ESG continuation

OMB 141–150 Quality management

OMB 151–160 Operational management

OMB 161–170 Strategy and business development

OMB 171–180 Supplier management and purchasing

OMB 181–190 Physical security

OMB 191–200 Continuity and resilience

OMB 191–200 Continuity and resilience

Important final note

The OMB catalog should be seen as a Preliminary reference model. Approximately:

• 35–40 % of the lines are clear legal requirements.
• 20–30 % are regulatory or prescriptive requirements.
• 30–40 % is the standard, governance or best-practice requirement.

Go to the summary page->

Read more about the requirements model->

Rolf Olsson Partner

Rolf Olsson is one of the founders of Chief of Staff Platform and specialist in business transformation, strategy implementation, and management support. Rolf has worked more than 40,000 hours as a consultant and writes about how the Chief of Staff role, modern governance, AI, and change management can help organizations increase their execution capabilities and create sustainable business results. Rolf has a degree in civil engineering, a master's degree in IT Management, and a PhD in Computer Science. Comments or remarks on this article can be emailed to: glossary@chiefofstaff.se

See Full Bio

Artificial Intelligence Risk & Compliance Enterprise Architecture Organizational resilience Merger & Acquisition Innovation management ESG Leadership Project management Frameworks, methods and models Board work Command & Control