| Table of Contents | ||
|---|---|---|
|
...
The Strategic Response Model (SRM) allows organisations to capture and understand how internal or external triggers lead to deliberate, structured responses across the business. It provides traceability between cause and effect—connecting performance insights, regulatory changes, stakeholder demands, and other drivers triggers with the actions taken to realign business architecture domains.
...
Rationales play an important role in classifying and organising strategic responses. Ensure that the trigger catalogue—which lists common environmental or operational triggers prompting strategic responses—is up to date. Reference to the trigger catalogue within this page ensures that rationales are accurately categorised based on their initiating context, improving traceability from external or internal stimuli through to strategic objectives, initiatives, and performance metrics.
DriverType values for rationales
SRM trigger catalogue as an enumeration list of driverType values for rationales. For example:
"driverType": { "type": "string", "enum": [ "Regulatory change", "Customer demand shift", "Operational risk", "Technology obsolescence", "Performance shortfall", "Cost pressure", "Workforce change", "Stakeholder expectation", "Market opportunity" ], "description": "High-level driver category that provides the basis for the rationale."
}
Definition of strategicResponseModel as a composable artefact
This section formalises the strategic response model as composable within the Orthogramic Metamodel. It outlines the attributes required to define a model, including associated triggers, organisational roles, information dependencies, and KPIs, supporting reuse and integration across governance and planning tools.
...
Attribute
...
Type
...
Description
...
id
...
UUID
...
Unique strategic response model ID
...
responseTitle
...
Text
...
Human-readable name of the strategic response model
...
description
...
Text
...
Summary of the strategic response model’s purpose and scope
...
triggerID
...
Link to Trigger entity
...
Source event or condition
...
relatedDrivers
...
List of StrategyDriver
...
Strategy elements influenced
...
affectedCapabilities
...
List of Capability
...
Impacted capabilities
...
relatedValueStreams
...
List of ValueStream
...
Value streams engaged
...
impactedUnits
...
List of OrganisationUnit
...
Units with strategic response model-specific roles
...
servicesInScope
...
List of Service
...
Services required or affected
...
dataDependencies
...
List of InformationAsset
...
Key information entities involved
...
policiesInScope
...
List of Policy
...
Applicable rules or regulations
...
stakeholders
...
List of Stakeholder
...
Stakeholders affected or involved
...
kpis
...
List of PerformanceMetric
...
Metrics used to assess strategic response model success
...
linkedInitiatives
...
List of Initiative
...
Strategic Response Model JSON Schema
See: https://github.com/Orthogramic/Orthogramic_Metamodel
Schema fields
Field | Description | Example |
|---|---|---|
| A unique identifier for the strategic response. |
|
| A concise title summarizing the strategic response. |
|
| The classification of the response (e.g., Initiative, Policy Change, Capability Development). |
|
| A detailed explanation of the strategic response, its objectives, and scope. |
|
| An array of |
|
| An array of |
|
| A list of business architecture domains impacted by this response (e.g., Capabilities, Services). |
|
| A reference or description of the plan outlining how the response will be executed. |
|
| A description of the anticipated results or benefits from implementing the response. |
|
| Metrics or KPIs that will be used to measure the success of the strategic response. |
|
| Organisation units accountable for executing the strategic response. |
|
| The planned start date for implementing the strategic response. |
|
| The planned completion date for the strategic response. |
|
| The current status of the strategic response (e.g., Planned, In Progress, Completed). |
|
| The date when the strategic response record was last updated. |
|
This format ensures that the strategic response definition is:
Declarative (not procedural or UI-specific),
Traceable (everything points to reusable metamodel entities),
Reusable (across tools, audits, planning activities).
Strategic Response Model JSON Schema
See: https://github.com/Orthogramic/Orthogramic_Metamodel
Schema fields
...
Field
...
Description
...
Example
...
triggerID
...
A unique identifier for the trigger that initiates the strategic response
...
EXT-REG-001
...
triggerTitle
...
A short title describing the nature of the trigger
...
New Regulatory Mandate
...
triggerType
...
.
...
External
...
rationaleID
...
A unique identifier for the rationale linked to the trigger
...
RAT-STR-005
...
rationaleTitle
...
The reason for responding to the trigger in terms of organisational priorities
...
Ensure Compliance with Safety Regulations
...
rationaleDescription
...
A detailed explanation of the rationale
...
Adapting internal policies to meet updated regulations
...
affectedDomain
...
The business architecture domain(s) impacted by the rationale
...
Policy
...
responseEntityID
...
Identifier for the responsive change entity (e.g. Strategy, Initiative)
...
INI-2025-041
...
responseEntityType
...
The type of entity that represents the strategic response
...
Initiative
...
responseDescription
...
Description of how the organisation is responding
...