Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
stylenone

...

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 domainsrepresenting a change in context, observation, or external condition that warrants attention. Each Trigger may lead to one or more Rationales, each providing a specific justification for change. Triggers ensure that organisational decisions are not made in a vacuum, but are grounded in evidence or obligation.See: Strategic Response Model

...

  • Trigger is a supporting artifact, not a domain.

  • It is only relevant in the context of a strategicResponseModel.

Trigger

...

Catalogue

Triggers are classified using the Trigger Catalogue, which defines accepted types of triggers.

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

...

...

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

Each strategic response triggered using this catalogue links back to relevant Orthogramic Metamodel domains—such as capabilities, services, initiatives, and stakeholders—to produce a dynamic view of organisational readiness and response.

Definition of trigger as a new open entity

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

...

triggerID

...

UUID

...

Unique ID

...

label

...

Text

...

Short name (e.g. “Cybersecurity Incident”)

...

category

...

Enum

...

From defined set (e.g. Technological, Regulatory, etc.)

...

description

...

Text

...

Explanation of why this trigger matters

...

examplestrategicResponseModels

...

List of strategicResponseModel

...

.

Common Trigger Catalogue types include:

  • Regulatory: New or updated legislation or compliance obligations.

  • Performance Insight: Metrics indicating deviation from expected outcomes.

  • Risk: Identified operational, financial, or strategic risks.

  • Opportunity: Market, partnership, or innovation opportunities.

  • Mandate: Governmental or internal directives.

  • Stakeholder Need: Explicit demand from a stakeholder or stakeholder group.

Each trigger includes:

  • triggerID: Unique identifier

  • title: Human-readable label

  • description: Detailed summary

  • triggerType: From the Trigger Catalogue

  • dateDetected: Date the trigger was recognised

Trigger JSON Schema

{
"$schema": "http://json-schema.org/draft/2020-12/schema",
"$id": "https://orthogramic.org/schema/trigger.json",
"title": "trigger",
"type": "object",
"required": ["triggerID", "label", "category"],
"properties": {
"triggerID": {
"type": "string",
"format": "uuid",
"description": "Unique identifier for the trigger"
},
"label": {
"type": "string",
"description": "Short, human-readable name of the trigger"
},
"category": {
"type": "string",
"enum": [
"Regulatory or compliance",
"Technological change",
"Environmental & safety",
"Operational transformation",
"Strategic re-alignment",
"Customer & stakeholder",
"Workforce & skills",
"Performance response",
"Political or social",
"Innovation-led opportunity"
],
"description": "Classification of trigger context"
},
"description": {
"type": "string",
"description": "Expanded explanation of the trigger’s relevance"
},
"examplestrategicResponseModels": {
"type": "array",
"items": {
"type": "string",
"format": "uuid"
},
"description": "Optional references to related strategicResponseModel artefacts"
}
}
}