| Table of Contents | ||
|---|---|---|
|
...
Triggers initiate the Strategic Response Model by identifying external or internal events that necessitate a strategic change. These are then elaborated through Rationales and linked to responsive changes across domains. See: Strategic Response Model
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.
...
The trigger catalogue provides a curated and expanding set of predefined triggers that can be used to initiate strategic responses. Each trigger is tagged to relevant business architecture domains, enabling efficient strategic response planning and alignment across organisational activities.
Trigger Category | Example Triggers |
Regulatory or compliance | New legislation, compliance audit mandate, data sovereignty changes |
Technological change | AI rollout, cybersecurity breach, platform deprecation |
Environmental & safety | Natural disaster preparedness, climate risk disclosures, workplace injury reform |
Operational transformation | Business process outsourcing, shared services implementation, lean redesign |
Strategic re-alignment | Mergers and acquisitions, board-level strategic pivot, budget realignment |
Customer & stakeholder | Community expectations shift, digital service demand surge, key account loss |
Workforce & skills | Critical skill shortage, union action, remote work policy adoption |
Performance response | KPI threshold breach, repeated incident occurrence, audit fail |
Political or social | Public inquiry, ministerial intervention, social licence erosion |
Innovation-led opportunity | Grant funding availability, pilot program success, ecosystem partnership offer |
...
Triggers are defined as a new open entity within the Orthogramic Metamodel, enabling them to be referenced independently and reused across strategic responses. Each trigger includes a unique identifier, category, description, and links to strategic responses in which it plays a role.
Attribute | Type | Description |
|---|---|---|
| UUID | Unique ID |
| Text | Short name (e.g. “Cybersecurity Incident”) |
| Enum | From defined set (e.g. Technological, Regulatory, etc.) |
| Text | Explanation of why this trigger matters |
| List of | Optional reverse reference |
...