Versions Compared

Key

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

...

  • Proactive identification of high-value opportunities

  • Consistent linkage to rationales and strategic responses

  • Improved transparency across strategic planning cycles

  • Enhanced auditability and traceability of decisions

Example

Trigger

Strategic Opportunity – Capability Enhancement

Description

Business planning process identifies need for workforce upskilling in AI analytics

Origin

Strategic planning

Time horizon

Anticipatory

Impact level

High

Linked rationale

To prepare the organisation for competitive positioning in data-driven decision making

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

...

The

...

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.

Linking to

...

rationales

Triggers can lead to multiple Rationales. Each Rationale references the originating trigger and justifies a different response path. This many-to-one structure allows a single trigger to influence several domains. See: Rationale

...

See https://orthogramic.atlassian.net/wiki/spaces/OM/pages/291242002 for reference cases.

Trigger and rationale linkage examples

See: https://github.com/Orthogramic/Orthogramic_Metamodel/blob/main/examples/trigger-rationale-links.md

Trigger JSON Schema

See: https://github.com/Orthogramic/Orthogramic_Metamodel

Schema properties

Field

Type

Required

Description

Example

triggerID

string (uuid)

Yes

Unique identifier for the trigger

"8f14e45f-ea4b-47b5-92e3-9d6bbd1e302f"

label

string

Yes

Short, human-readable name of the trigger

"New Safety Regulation"

description

string

No

Expanded explanation of the trigger's relevance

"Government introduces new safety rules affecting inspections"

primaryCategory

string (enum)

Yes

Primary classification of trigger context

"Regulatory_Compliance"

subCategory

string

No

More specific classification within the primary category

"Workplace Safety"

origin

string (enum)

Yes

Whether the trigger originates from inside or outside the organisation

"External"

timeHorizon

string (enum)

No

The temporal nature of the trigger

"Short_Term"

impactLevel

string (enum)

No

The potential significance of the trigger

"High"

status

string (enum)

No

The current status in the lifecycle of the trigger

"Ongoing"

detectionDate

string (date)

No

Date when the trigger was identified

"2025-04-20"

validUntil

string (date)

No

Expected end of relevance for this trigger

"2026-01-01"

sourceReference

string

No

Reference to source document or authority identifying the trigger

"https://gov.au/safety-act-2025"

relatedTriggers

array of uuid

No

References to other related triggers

["uuid-1", "uuid-2"]

strategicResponseReferences

array of uuid

No

References to related Strategic Response artefacts

["uuid-3", "uuid-4"]

This schema allows organizations to systematically capture and manage triggers that necessitate strategic responses, ensuring traceability and alignment across the enterprise architecture.

Enumeration Values

primaryCategory

  • "Regulatory_Compliance" - Changes in laws, regulations, or compliance requirements

  • "Strategic_Opportunity" - Forward-looking opportunities to create value

  • "Market_Shift" - Changes in customer preferences, competitive landscape, or market dynamics

  • "Technological_Change" - Emergence of new technologies or technical disruptions

  • "Risk_Management" - Response to identified risks or vulnerabilities

  • "Performance_Issue" - Internal operational or business performance challenges

  • "Stakeholder_Demand" - Requirements from stakeholders (customers, employees, shareholders)

  • "Resource_Constraint" - Limitations in financial, human, or material resources

  • "Capability_Enhancement" - Need to develop or improve organizational capabilities

  • "Innovation_Initiative" - Internal drive for product, service, or process innovation

origin

  • "Internal" - Trigger originates from within the organization

  • "External" - Trigger originates from outside the organization

  • "Strategic_Planning" - Trigger arises from deliberate strategic planning processes

  • "Hybrid" - Trigger has both internal and external components

timeHorizon

  • "Immediate" - Requires action within days or weeks

  • "Short_Term" - Requires action within months

  • "Medium_Term" - Requires action within 1-2 years

  • "Long_Term" - Requires action over multiple years

  • "Anticipatory" - Proactive planning for future conditions

impactLevel

  • "Low" - Limited impact on operations or strategy

  • "Medium" - Moderate impact requiring significant adjustment

  • "High" - Major impact requiring substantial response

  • "Critical" - Existential impact requiring immediate, comprehensive response

status

  • "Identified" - Trigger has been recognized but response not yet planned

  • "Analyzing" - Trigger is being assessed to determine appropriate response

  • "Responding" - Organization is actively responding to the trigger

  • "Monitoring" - Response has been implemented and effects are being tracked

  • "Resolved" - Trigger has been fully addressed

  • "Archived" - Trigger is no longer relevant but retained for reference

  • "Ongoing" - Trigger represents a continuing condition requiring sustained response

This schema allows organizations to systematically capture and manage triggers that necessitate strategic responses, ensuring traceability and alignment across the enterprise architecture.

...