Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 38 Next »

Strategic response model

Introduction

The Strategic Response Model provides a formalised structure for capturing how an organisation responds to external triggers and internal performance insights. It links these drivers to organisational reasoning (rationales) and defines the actions taken across strategic, policy, capability, and initiative domains. By making these relationships explicit, the model supports traceability, alignment, and accountability across the business architecture.

Each strategic response includes references to the triggers that prompted the change and the rationales that explain the basis for the response. Responses are associated with affected domains and are monitored through linked performance indicators, which define what success looks like and how progress is measured. These indicators support ongoing evaluation by including target values, baseline comparisons, timeframes, and data sources, enabling continuous assessment of strategic effectiveness.

This model supports continuous strategic alignment by documenting why a change occurred, how it was rationalised, and what was impacted and by how much—across strategies, capabilities, initiatives, policy, and organisational units.

Components of the Strategic Response Model

The Strategic Response Model (SRM) links observed conditions—both external and internal—to formal responses across Strategy, Capabilities, Policy, Initiatives, and other domains. It is comprised of three core elements:

This structured model enables traceable, auditable, and adaptive decision-making throughout the organisation.

Purpose

The SRM strengthens strategic governance by ensuring that:

  • Business responses are traceable to defined triggers

  • Rationales are explicitly captured and consistently structured

  • Impact across domains and organisational units is recorded

  • Organisational learning and auditability are enhanced

Structure

Each Strategic Response includes:

  • A trigger: drawn from the shared trigger catalogue

  • A rationale object: structured and detailed, replacing simple references

  • One or more affected domains: such as policy, initiatives, or capabilities

  • Impacted organisational units: using defined role types

  • Response actions: steps taken or planned

  • Expected outcomes: anticipated benefits or changes in performance

  • A performance indicator measuring a response

Trigger catalogue

Responses reference a trigger selected from a standardised catalogue of events, trends, or insights. This ensures consistency in classifying causes of change and enables systemic analysis across responses.

Affected domains

Strategic responses typically impact one or more of the following domains:

  • Strategy: adjustments to goals or strategic direction

  • Capabilities: development, enhancement, or decommissioning

  • Initiatives: programs or projects started or stopped

  • Policy: introduction or amendment of rules and frameworks

  • Performance: redefinition or reweighting of KPIs

  • Information: changes to how data is used or governed

  • Value Stream: refinements in end-to-end value delivery

Impacted organisational units

The impactedUnits array uses standardised relationship roles (as defined in the Inter-unit Domain Relationships model). See: https://orthogramic.atlassian.net/wiki/spaces/OM/pages/285016368

Relationship with Rationales

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.

Strategic Response Model JSON Schema

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

Schema properties

Field

Description

Example

responseID

A unique identifier for the strategic response.

SRM-2025-001

responseTitle

A concise title summarizing the strategic response.

Enhance Data Security Measures

responseType

The classification of the response (e.g., Initiative, Policy Change, Capability Development).

Policy Change

responseDescription

A detailed explanation of the strategic response, its objectives, and scope.

Implement new data encryption protocols to comply with updated regulations.

triggerReferences

An array of triggerIDs that initiated this strategic response.

["TRG-EXT-2025-01", "TRG-INT-2025-03"]

rationaleReferences

An array of rationaleIDs providing justification for this response.

["RAT-COMP-2025-02"]

performanceIndicatorReferences

Metrics or KPIs that will be used to measure the success of the strategic response.

["KPI-SEC-2025-01", "KPI-SEC-2025-02"]

affectedDomains

A list of business architecture domains impacted by this response (e.g., Capabilities, Services).

["Capabilities", "Services"]

implementationPlan

A reference or description of the plan outlining how the response will be executed.

Refer to Implementation Plan Document ID: IMP-2025-007

expectedOutcomes

A description of the anticipated results or benefits from implementing the response.

Improved compliance with data protection laws and reduced risk of data breaches.

responsibleOrgUnits

Organisation units accountable for executing the strategic response.

["Information Security Department"]

startDate

The planned start date for implementing the strategic response.

2025-05-01

endDate

The planned completion date for the strategic response.

2025-12-31

status

The current status of the strategic response (e.g., Planned, In Progress, Completed).

Planned

lastUpdated

The date when the strategic response record was last updated.

2025-04-19

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).

  • No labels