| Table of Contents | ||
|---|---|---|
|
...
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 |
...
See: https://github.com/Orthogramic/Orthogramic_Metamodel
Schema properties
Field | Type | Required | Description | Example |
|---|---|---|---|---|
| string (uuid) | Yes | Unique identifier for the rationale | "RAT-STR-005" |
| string | Yes | Title or summary of the rationale | "Ensure Regulatory Compliance" |
| string | Yes | A detailed explanation of the rationale supporting a strategic response | "To meet new safety regulations and avoid penalties" |
| string (uuid) | Yes | Reference to the trigger that prompted this rationale | "TRG-EXT-2025-01" |
| array of string (enum) | No | List of business architecture domains influenced or justified by this rationale | ["Policy", "Capabilities"] |
| string (enum) | Yes | Primary category for the rationale | "Compliance_Requirement" |
| string (enum) | No | The logical structure of the rationale | "Normative" |
| string (enum) | No | The foundation for the rationale | "Regulatory_Requirement" |
| string (enum) | No | How the rationale connects to organizational strategy | "Risk_Mitigation" |
| string (enum) | No | The nature of value creation or preservation | "Regulatory_Compliance" |
| string (date) | No | The date the rationale was first recorded | "2025-04-20" |
| string | No | The person or team who documented the rationale | "Regulatory Affairs Team" |
| string | No | The organizational unit that owns or authored the rationale | "Regulatory Affairs Unit" |
| array of string (uuid) | No | References to other related rationales | ["RAT-STR-006"] |
...