Strategic Response Model

The Strategic Response Model (SRM) provides a structured framework for capturing, documenting, and tracing how organizations respond to internal and external changes. It links triggers (what happened) and strategic intents (what we choose to pursue) to rationales (why we're responding) and strategic responses (what we're doing) across business architecture domains.

Schema: strategic-response-model.schema.json (composite)
Specification: JSON Schema Draft-07

Each of the four parts has its own schema, and the composite groups them for exchange:

Part	Schema	Composite list
Trigger	trigger.schema.json	triggers
Rationale	rationale.schema.json	rationales
Strategic Intent	strategic-intent.schema.json	strategicIntents
Strategic Response	strategic-response.schema.json	strategicResponses

The records reference each other by ID, so a composite document can hold any combination of them. See SRM JSON Schema for the composite and the Strategic Intent and Strategic Response attributes.

Overview

What is the Strategic Response Model?

The SRM is a governance extension that ensures organizational responses are:

• Traceable — Every action links back to a documented trigger or strategic intent
• Justified — Rationales explicitly capture the reasoning behind decisions
• Measurable — Performance indicators track success and enable adaptation
• Auditable — Complete chains from trigger to outcome support governance reviews

Why Use the Strategic Response Model?

Challenge	How SRM Helps
"Why did we start this initiative?"	Traces to documented trigger and rationale
"Is this aligned with strategy?"	Links responses to strategic objectives
"Who approved this change?"	Records accountability and decision points
"How do we know it's working?"	Connects to performance indicators
"What else was affected?"	Maps impact across domains

SRM Components

The Strategic Response Model comprises four parts — strategic intents, triggers, rationales and strategic responses — measured by performance indicators:

1. Strategic Intent

Proactive, forward-looking aspirations that drive organizational change. Unlike triggers (which are reactive), strategic intents represent deliberate choices to pursue opportunities. Each intent names the strategic objective it serves (strategicObjectiveReference), classifies the opportunity (opportunityType, e.g. growth, innovation, transformation), and lists the rationales that justify it and the responses that realise it (rationaleReferences, responseReferences).

Examples:

• "Become the market leader in sustainable products by 2027"
• "Achieve 50% digital channel adoption"
• "Build AI-first customer service capabilities"

→ See Strategic Intent for the attributes.

2. Triggers

Events, insights, or conditions that prompt a response. Triggers are categorized into families (primaryCategory) for consistent analysis, and list the specific records they affect in affectedEntities, each given by domain and ID ({ "domainType": "market", "entityID": "MKT-ENTSW-001" }).

Trigger Categories:

• Regulatory or compliance
• Technological change
• Environmental & safety
• Operational transformation
• Strategic re-alignment
• Customer & stakeholder
• Workforce & skills
• Performance response
• Political or social
• Innovation-led opportunity

→ See Trigger Schema for full documentation.

3. Rationales

The reasoned justification for responding to a trigger or pursuing a strategic intent. Rationales bridge the "what happened" (trigger) to the "what we're doing" (response). Each rationale names its trigger in triggerReference.

Rationale Elements:

• Description of reasoning
• Rationale type and orientation (reactive or proactive)
• Linked domains affected
• Alternatives considered
• Evidence base and reasoning pattern
• Related entities in any domain (relatedEntities, by domain and ID)

→ See Rationale Schema for full documentation.

4. Strategic Responses

The aligned changes or activities captured in other business architecture domains. A strategic response references the triggers, intents and rationales behind it (triggerReferences, intentReferences, rationaleReferences), lists the domains it affects in affectedDomains, and records the organization units involved in impactedUnits. Responses specify what is changing across:

• 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
• Performance — Redefinition or reweighting of KPIs
• Information — Changes to data usage or governance
• Value Stream — Refinements in end-to-end value delivery

→ See Strategic Response for the attributes.

5. Performance Indicators

Quantifiable metrics that evaluate success, efficiency, or impact of the response. Performance indicators close the loop by measuring whether the response achieved its intended outcome. They are separate records (performance-indicator.schema.json) that intents and responses reference in performanceIndicatorReferences.

→ See Performance Indicators for full documentation.

How the SRM Works

Example: Regulatory Compliance Response

Example: Proactive Strategic Initiative

Domain-Specific Responses

The SRM captures responses across all Triodian domains. A response is classified by responseType; typical types for each domain are:

Strategy and Market Domain Responses

Response Type	Description
repositioning	Fundamental change in strategic direction or market position
marketEntry / marketExit	Entering or leaving a market
competitiveResponse	Reacting to competitor action

Capability Domain Responses

Response Type	Description
capabilityDevelopment	Creating or improving a capability
processImprovement	Improving how a capability is performed
technologyImplementation	Implementing technology that enables a capability

Initiative Domain Responses

Response Type	Description
initiativeLaunch	Starting a new program or project
portfolioAdjustment	Accelerating, re-scoping or stopping work in a portfolio

Policy Domain Responses

Response Type	Description
policyChange	Introducing, amending or retiring a policy
complianceProgram	Coordinated program to meet obligations

Finance Domain Responses

Response Type	Description
budgetReallocation	Shifting financial resources
investmentStrategy	New capital expenditure or investment approach
costOptimization	Reducing operational costs

Risk Management Domain Responses

Response Type	Description
riskMitigation	Implementing controls
riskAcceptance	Documented risk tolerance
riskTransfer	Insurance or outsourcing

The full list of 75 response types is in strategic-response.schema.json.

Impacted Organizational Units

The SRM tracks which organizational units are affected by a strategic response in its impactedUnits, naming each unit and the role it plays:

{
  "impactedUnits": [
    {
      "orgUnitTitle": "Retail Banking",
      "orgUnitID": "OU-RB",
      "relationshipRole": "owningUnit",
      "relationshipStrength": 5
    },
    {
      "orgUnitTitle": "Enterprise Technology",
      "orgUnitID": "OU-TECH",
      "relationshipRole": "providingUnit",
      "relationshipStrength": 4
    },
    {
      "orgUnitTitle": "Legal and Compliance",
      "orgUnitID": "OU-LEGAL",
      "relationshipRole": "governingUnit",
      "relationshipStrength": 3
    },
    {
      "orgUnitTitle": "Branch Network",
      "orgUnitID": "OU-BRANCH",
      "relationshipRole": "dependentUnit",
      "relationshipStrength": 2
    }
  ]
}

The roles are owningUnit, providingUnit, consumingUnit, utilisingUnit, custodianUnit, dependentUnit, supportedUnit and governingUnit. For relationships between units and other domain entities, see the Inter-Unit Relationships model.

Monitoring and Review

Responses should be reviewed on a cadence that matches their urgency:

Cadence	Use Case
Monthly	High-priority regulatory responses
Quarterly	Strategic initiative progress
Six-monthly	Capability development programs
Annual	Long-term strategic alignment review

The schemas record monitoring through the records themselves rather than a separate monitoring element: a response's status and lastUpdated, the assessmentFrequency and statusHistory of its performance indicators, and domain-specific monitoring such as riskMonitoring and competitiveMonitoring. A rationale's lastReviewed and effectivenessRating record when its reasoning was last reviewed and how well it held up.

Integration Points

The SRM connects to other Triodian extensions:

Extension	Integration
Cross-Domain Relationships	Responses use cross-domain verbs (enables, transforms, etc.)
Inter-Unit Relationships	Units' relationships to domain entities use standardized roles
Performance Domain	KPIs link to domain performance indicators
Initiatives Domain	Response initiatives reference the Initiatives domain

Usage Guidelines

When to Create an SRM Entry

• Regulatory or compliance changes requiring organizational response
• Significant market shifts affecting strategy
• Performance threshold breaches requiring intervention
• Technology changes enabling new capabilities
• Strategic planning decisions requiring traceability

Modeling Best Practices

1. Start with the trigger — Clearly document what prompted the response
2. Justify with rationale — Explain the reasoning, not just the action
3. Specify affected domains — Map all impacted areas
4. Define success criteria — Link to measurable performance indicators
5. Assign accountability — Record impacted units and their relationshipRole
6. Set review cadence — Ensure ongoing monitoring

For Data Engineers

The SRM maps well to data lineage and impact analysis patterns. Triggers can be connected to data quality alerts, rationales to business impact assessments, and responses to data pipeline changes. Consider integrating SRM entries with your data observability platform.

Related Documentation

• Trigger Schema — Detailed trigger documentation
• Rationale Schema — Detailed rationale documentation
• Performance Indicators — KPI schema and usage
• SRM JSON Schema — Composite schema, Strategic Intent and Strategic Response reference
• Trigger and rationale walkthrough — Worked examples in the composite form