| Table of Contents | ||
|---|---|---|
|
...
A trigger is defined as a catalyst event—internal or external—that compels an organisation to adapt. It is not a standalone structural element but a contextual stimulus that prompts changes to strategy, activates capabilities, or demands cross-functional coordination. Triggers may include legislative changes, customer demands, or performance breaches.
A Trigger is not a standalone structural element of an organisation but an external or internal event, condition, or hypothesis that causes the organisation to:
Mobilise capabilities,
Evaluate policies,
Adjust strategies,
Initiate new initiatives,
Coordinate across services and information flows.
In the Orthogramic Metamodel:
...
Trigger is a supporting artifact, not a domain.
...
Trigger Taxonomy
Triggers in the Orthogramic Metamodel follow a standardized classification system that enables consistent categorization, improved searchability, and enhanced analytics. Each trigger is classified according to:
Primary Category: The main classification of the trigger (e.g., Regulatory, Technological, Strategic)
Subcategory: A more specific classification within the primary category
Origin: Whether the trigger is internal or external to the organization
Time Horizon: The temporal nature of the trigger (immediate, short-term, long-term)
Impact Level: The potential significance of the trigger (low, medium, high, critical)
This taxonomy provides a framework for organizing triggers consistently, allowing organizations to:
Track patterns in strategic responses across similar trigger types
Analyze the distribution of triggers by source, timeframe, and impact
Identify which categories of triggers most frequently drive strategic changes
Maintain a trigger registry that can be referenced across multiple strategic response models
The standardized taxonomy also supports governance and auditability by ensuring that triggers are documented according to consistent criteria, making it easier to trace decision-making patterns over time.
Trigger Catalogue
Triggers are classified using the Trigger Catalogue, which defines accepted types of triggers.
...
See https://orthogramic.atlassian.net/wiki/spaces/OM/pages/291242002 for reference cases.
Trigger
...
Triggers in the Orthogramic Metamodel follow a standardized classification system that enables consistent categorization, improved searchability, and enhanced analytics. Each trigger is classified according to:
Primary Category: The main classification of the trigger (e.g., Regulatory, Technological, Strategic)
Subcategory: A more specific classification within the primary category
Origin: Whether the trigger is internal or external to the organization
Time Horizon: The temporal nature of the trigger (immediate, short-term, long-term)
Impact Level: The potential significance of the trigger (low, medium, high, critical)
This taxonomy provides a framework for organizing triggers consistently, allowing organizations to:
Track patterns in strategic responses across similar trigger types
Analyze the distribution of triggers by source, timeframe, and impact
Identify which categories of triggers most frequently drive strategic changes
Maintain a trigger registry that can be referenced across multiple strategic response models
The standardized taxonomy also supports governance and auditability by ensuring that triggers are documented according to consistent criteria, making it easier to trace decision-making patterns over time.
Trigger JSON Schema
See: https://github.com/Orthogramic/Orthogramic_Metamodel
Schema properties
Field | Type | Required | Description | Example |
|---|
| string (uuid) | Yes | Unique identifier for the |
trigger | " |
TRG-EXT- |
2025- |
01" |
| string | Yes |
Short, human-readable name of the |
trigger | " |
New Regulatory |
Mandate" | |
| string |
No |
Expanded explanation of the |
"To meet new safety regulations and avoid penalties"
triggerReference
string (uuid)
Yes
Reference to the trigger that prompted this rationale
"TRG-EXT-2025-01"
linkedDomains
array of string (enum)
No
List of business architecture domains influenced or justified by this rationale
["Policy", "Capabilities"]
trigger's relevance | "Mandate issued by the national regulator requiring compliance with new safety standards" | |||
| string (enum) | Yes | Primary classification of trigger context | "Regulatory_Compliance" |
| string | No | More specific classification within the primary category | "Safety Standards Update" |
| string (enum) | Yes |
Primary category for the rationale
"Compliance_Requirement"
Whether the trigger originates from inside or outside the organization | "External" | ||
| string (enum) | No | The |
temporal nature of the |
trigger | " |
evidenceBase
string (enum)
No
The foundation for the rationale
"Regulatory_Requirement"
strategicAlignment
string (enum)
No
How the rationale connects to organizational strategy
"Risk_Mitigation"
businessValueType
Medium_Term" | |||
| string (enum) | No | The |
"Regulatory_Compliance"
potential significance of the trigger | "High" | |
| string (date) | No |
Date when the |
trigger was |
identified | "2025-04- |
19" |
| string | No |
The person or team who documented the rationale
"Regulatory Affairs Team"
orgUnitTitle
string
No
The organizational unit that owns or authored the rationale
"Regulatory Affairs Unit"
Reference to source document, report, or authority identifying the trigger | ||||
| array of string (uuid) | No | References to other related triggers | ["TRG-EXT-2025-02"] |
| array of string (uuid) | No | References to |
related |
| [" |
...
SRM-2025-001", "SRM-2025-002"] |
This schema allows organizations to systematically capture and manage triggers that necessitate strategic responses, ensuring traceability and alignment across the enterprise architecture.
...