| Table of Contents | ||
|---|---|---|
|
...
Initiatives and Strategies that require justification.
Policies, Capabilities, and Value Streams being introduced or adjusted.
Performance goals or KPIs in the Performance domain.
Rationale object
Each response includes a rationale object that captures the justification for action. It replaces previous references to rationaleId and allows richer traceability and reasoning.
...
Field
...
Description
...
rationaleTitle
...
A short name for the rationale
...
description
...
A detailed explanation of the reasoning behind the response
...
driverType
...
.
...
sourceDocument
...
Reference to the originating insight, regulation, or analysis
...
...
KPIs that the response is intended to influence or improve
...
priorityLevel
...
(Optional) Indicates urgency or importance (e.g. High, Medium, Low)
Relationship to strategic response model
...
The Strategic Response Model defines the following categories of drivers:
Driver Type | Description | Common Triggers | Example Rationales | Related Domains |
|---|---|---|---|---|
Regulatory change | Changes in legal or regulatory requirements | New legislation, audits | Align with safety standards; address compliance risks | Policy, Initiatives, Capabilities, Performance |
Customer demand shift | Shifting customer expectations or behaviours | Feedback, usage patterns | Improve onboarding; redesign mobile services | Strategy, ValueStream, Capabilities, Stakeholders |
Operational risk | Threats to continuity or operational efficiency | System failure, safety incidents | Enhance cyber resilience; strengthen recovery plans | Capabilities, Performance, Information, Organisation |
Technology obsolescence | Legacy or unsupported systems impacting operations | End-of-life systems, innovation lag | Modernise tech stack; enable data interoperability | Information, Capabilities, Initiatives |
Cost pressure | Financial constraints requiring efficiency or cost optimisation | Budget cuts, benchmarking | Consolidate platforms; automate manual processes | Performance, Capabilities, Initiatives, Organisation |
Workforce change | Evolving workforce dynamics | Hybrid work, attrition | Reskill staff; adapt HR policies | Organisation, Policy, Capabilities |
Stakeholder expectation | Pressure or concern from internal or external stakeholders | Board expectations, ESG concerns | Increase transparency; implement ethical compliance | Stakeholders, Policy, Performance |
Market opportunity | New market trends or emerging business opportunities | Competitor gap, new segment demand | Launch services; localise products | Strategy, ValueStream, Capabilities, Initiatives |
...
Classification: Each rationale must include a driver type. Multiple drivers may be selected if appropriate.
Traceability: Rationales should link to the relevant strategy, initiative, or performance goal.
Consistency: Use the https://orthogramic.atlassian.net/wiki/spaces/OM/pages/290914315/Triggers#Trigger-Catalogue Trigger to guide classification.
Relationship to Triggers
...
For further details on how triggers are defined, classified, and managed, see: Triggers Trigger and the associated https://orthogramic.atlassian.net/wiki/spaces/OM/pages/290914315/Triggers#Trigger-Catalogue Trigger, which outlines recognised types such as Regulatory, Risk, Opportunity, and Performance Insight.
...
Risk
Compliance
Opportunity
Mandate
Performance Insight
Stakeholder Need
Other
Schema reference
The trigger property in the Rationale schema is now defined using a JSON Schema $ref to the Trigger schema, which includes details such as:
...
triggerID
...
title
...
Rationale JSON schema
See: https://github.com/Orthogramic/Orthogramic_Metamodel
Rationale – schema fields
Field | Description | Example |
|---|---|---|
| A unique identifier for the rationale |
|
| A short title describing the purpose or intent of the rationale |
|
| Classification of the rationale (e.g. |
...
Rationale JSON schema
...
, Compliance, Risk Reduction, Innovation) |
| |
| A detailed explanation of why the organisation is taking action |
|
| List of associated trigger IDs that support or initiate this rationale |
|
| The business architecture domain influenced or justified by the rationale |
|
| The identifier of the entity (e.g., strategy, initiative) that is justified |
|
| The organisation unit responsible for acting on the rationale |
|
| Summary of the expected impact or outcome of acting on the rationale |
|
This schema supports structured reasoning and traceability across strategy, policy, and initiative development, ensuring that every response is grounded in a documented justification.