Strategy Domain
The Strategy domain defines the organization's long-term vision, goals, and priorities that guide efforts to achieve mission and connect aspirations to actionable initiatives. It provides a structured framework for strategic planning, execution, and performance monitoring across the enterprise.
Schema: strategy.schema.json
Specification: JSON Schema Draft-07
Overview
What is Strategy?
Strategy represents the deliberate choices about how to achieve objectives through coordinated actions and resource allocation. It encompasses the direction, scope, and priorities that guide decision-making and resource deployment to achieve desired outcomes.
The domain emphasizes:
- Performance integration — KPIs embedded directly into strategic objectives
- Data-driven insights — Rapid scenario analysis and strategic planning
- Agile response — Model different scenarios and respond to changing conditions
Purpose and Value
The Strategy domain enables architects and planners to:
- Align initiatives to objectives by linking projects and programs to strategic goals
- Track strategic performance through embedded KPIs and success metrics
- Model scenarios by defining responses to different business conditions
- Communicate direction with clear, structured strategic documentation
- Enable governance through traceable strategy-to-execution linkages
The Strategy domain maps directly to analytics and governance concepts:
- Strategic Objectives → Business outcomes driving data priorities
- KPIs → Metrics to track in dashboards and reports
- Time Horizons → Planning cycles for data projects
- Risk Categories → Risk dimensions for data quality monitoring
Core Components
The Strategy domain includes essential elements that work together:
- Strategy Objectives: Specific measurable targets that support strategic goals
- Strategic Empathy: Elements that integrate human insight into strategy formulation
Domain Attributes
Core Attributes
| Attribute | Type | Description | Required |
|---|---|---|---|
strategyID | String | Unique identifier for the strategy, e.g. STR-001 | ✓ |
title | String | Name/title of strategy | ✓ |
description | String | Detailed explanation | ✓ |
purpose | String | Intended function | ✓ |
owner | String | Responsible individual/team | ✓ |
orgUnitTitle | String | Most closely linked organizational units | |
orgUnitID | String | ID of the organization unit (see orgUnitTitle) | |
strategyCategory | Enum | Broad categorization of strategy type | |
strategyType | Enum | Specific type of strategy | |
strategicFocus | Enum | Primary focus area | |
timeHorizon | Enum | Strategy time frame (shared time horizon list) | |
scopeLevel | Enum | Organizational scope | |
objectives | String | Specific measurable targets | |
keyActivities | String | Critical implementation actions | |
resources | String | Allocated resources | |
timeline | String | Achievement timeline | |
keyPerformanceIndicators | String | Success metrics | |
dependencies | String | Required dependencies | |
relatedStrategies | String | Related/linked strategies | |
relatedStrategyIDs | Array[String] | IDs of related strategies | |
risks | String | Associated risks | |
riskCategories | Array[Enum] | Categories of risks | |
mitigationStrategies | String | Risk mitigation approaches | |
improvementOpportunities | String | Enhancement areas | |
strategicAlignment | String | Goal alignment | |
businessObjective | String | Supporting business goal | |
competitiveAdvantage | String | How strategy creates competitive advantage | |
marketPosition | Enum | Desired market position | |
investmentLevel | Enum | Required investment level | |
successCriteria | String | Criteria for measuring success | |
stakeholderImpact | String | Impact on key stakeholders | |
changeManagement | String | Change management approach | |
parent | String | Parent strategy | |
parentStrategyID | String | ID of the parent strategy | |
child | String | Child strategy | |
childStrategyIDs | Array[String] | IDs of child strategies | |
strategyObjectives | Array[Object] | Specific objectives supporting the strategy |
The strategic empathy attributes are listed under Strategic Empathy Elements. A strategy record may not carry fields other than those listed on this page.
Enumeration Values
Strategy Category (strategyCategory)
| Value | Description | Example |
|---|---|---|
military | Armed forces and defense strategy | Defensive positioning, deterrence |
political | Political power and governance | Electoral campaigns, coalition building |
diplomatic | International relations | Treaty negotiations, alliance building |
economic | Economic competition and development | Market manipulation, trade strategy |
intelligence | Gathering and using intelligence | Competitive intelligence programmes |
corporate | Corporate, business-unit, functional and operational strategy | Overall company direction, marketing strategy, process improvement |
geopolitical | Positioning among states and regions | Regional influence strategy |
socialMovement | Social and cultural change | Advocacy campaigns, activism |
technological | Technology development and control | Innovation races, cyber strategy |
resourceControl | Control of critical resources | Energy, water or raw-material strategy |
information | Shaping information and narratives | Public communication campaigns |
legalJudicial | Use of law, regulation and courts | Litigation strategy, regulatory challenges |
Strategy Type (strategyType)
| Value | Description | Example |
|---|---|---|
offensive | Aggressive action to gain advantage | Market attack, hostile takeover |
defensive | Protecting existing position | Market defense, fortification |
containment | Limiting opponent's expansion | Competitive blocking |
deterrence | Preventing action through threat | Sanctions threat, legal warning |
attrition | Wearing down an opponent over time | Sustained price competition |
blitzkrieg | Rapid, concentrated action | Fast market entry with heavy investment |
asymmetric | Using unconventional means against a stronger opponent | Niche entrant against incumbents |
coalitionBuilding | Creating alliances | Strategic partnerships, trade blocs |
divideAndConquer | Splitting opponents to weaken them | Separate deals with members of a group |
encirclement | Surrounding an opponent's position | Covering all segments around a competitor |
infiltration | Gaining position inside a target area | Entering a market through a local partner |
scorchedEarth | Destroying assets an opponent could use | Aggressive defensive measures |
flanking | Attacking from an unexpected direction or differentiating | Market disruption from new angle, premium positioning |
preemption | Acting first to prevent opponent | First-mover advantage |
escalation | Increasing intensity | Expanding a price war |
deEscalation | Reducing intensity | Negotiated settlement |
provocation | Inducing an opponent to act | Public challenge to a competitor |
deception | Misleading an opponent | Feints and decoy announcements |
accumulation | Building up power, resources or market share | Market expansion, M&A |
disruption | Changing the rules through innovation or transformation | Digital transformation, new business models |
withdrawal | Pulling out of a position | Market exit |
retrenchment | Cutting back to a core | Cost reduction, divestment |
transition | Moving from one state to another | Handover of control, organizational transition |
abandonment | Giving up a position entirely | Discontinuing a business line |
appeasement | Making concessions to avoid conflict | Concessions to a regulator or rival |
capitulation | Conceding to an opponent | Accepting acquisition terms |
Strategic Focus (strategicFocus)
| Value | Description | Example |
|---|---|---|
powerAccumulation | Gaining power or influence | Building political support |
powerPreservation | Keeping existing power | Defending an incumbent position |
powerTransfer | Handing power to another party | Succession, sovereignty transfer |
powerReduction | Reducing an opponent's power | Weakening a rival coalition |
territoryControl | Controlling territory or markets | Holding a region or market |
territoryWithdrawal | Leaving territory or markets | Exiting a region |
resourceDominance | Control of critical resources | Supply chain control, raw materials |
resourceDenial | Preventing others' access to resources | Exclusive supply agreements |
informationControl | Controlling information flows | Narrative and data control |
allianceBuilding | Forming alliances | Partnership networks |
allianceDissolution | Breaking up alliances | Separating partners from a rival |
opponentNeutralization | Removing an opponent's ability to act | Acquiring a competitor |
conflictAvoidance | Avoiding confrontation | Choosing uncontested markets |
systemDisruption | Disrupting an existing system | Platform disruption of an industry |
statusQuoMaintenance | Keeping things as they are | Stability programmes |
influenceProjection | Extending influence | Market expansion, new segments |
influenceWithdrawal | Reducing involvement | Scaling back international presence |
survival | Ensuring continued existence | Turnaround, crisis response |
hegemony | Achieving dominance | Market dominance |
legitimacy | Gaining or keeping recognised authority | Regulatory standing, licence to operate |
innovationLeadership | Leading through new capabilities | Technological superiority, product and technology leadership |
economicDominance | Economic superiority | Cost or scale leadership |
culturalHegemony | Dominance of ideas and culture | Setting industry norms |
Time Horizon (timeHorizon)
timeHorizon uses the shared time horizon list from common.schema.json.
| Value | Description | Example |
|---|---|---|
immediate | Now to 3 months | Crisis response |
shortTerm | Up to 1 year | Annual operational improvements |
mediumTerm | 2 to 3 years | Technology implementation projects |
longTerm | 4 to 5 years | Major transformation programs |
extended | Beyond 5 years | Generational technology shifts |
Scope Level (scopeLevel)
| Value | Description | Example |
|---|---|---|
global | Worldwide scope | International expansion |
continental | A continent | European strategy |
regional | Geographic region | EMEA strategy |
national | Single nation | National market strategy |
stateProvincial | A state or province | State transport strategy |
local | A city or locality | Municipal strategy |
sector | An industry sector | Rail sector strategy |
organization | One organization, or a division, department or function within it | Corporate strategy, marketing department strategy |
coalition | A coalition of parties | Alliance strategy |
bilateral | Two parties | Bilateral agreement |
multilateral | Several parties | Multilateral treaty |
asymmetric | Parties of very different size or power | Small entrant against a dominant player |
Market Position (marketPosition)
| Value | Description | Example |
|---|---|---|
marketLeader | Dominant market position | Largest market share |
marketChallenger | Strong competitive position | Challenging the leader |
marketFollower | Following market trends | Adapting to leader strategies |
nichePlayer | Specialized market focus | Focused on specific segments |
disruptor | Disrupting existing markets | New business models |
emergingPlayer | New entrant to market | Startup, new participant |
defensivePositioning | Protecting an existing position rather than seeking share | Holding a defended niche or territory |
Investment Level (investmentLevel)
| Value | Description | Example |
|---|---|---|
highInvestment | Significant capital allocation | Major technology overhaul, M&A |
mediumInvestment | Moderate resource commitment | System upgrades, process improvements |
lowInvestment | Limited resource requirement | Minor enhancements, efficiency gains |
minimalInvestment | Very low resource needs | Process optimization, reorganization |
Risk Categories (riskCategories)
riskCategories uses the shared risk category list from common.schema.json, plus diplomatic.
| Value | Description | Example |
|---|---|---|
strategic | Strategic planning and execution risks | Market shifts, competitive threats |
operational | Operational execution risks | Implementation delays, resource constraints |
financial | Financial and investment risks | Budget overruns, ROI shortfalls |
market | Market and competitive risks | Market changes, competitive response |
economic | Economic conditions | Recession, inflation |
political | Political risks | Change of government, sanctions |
compliance | Regulatory and compliance risks | Regulatory changes, compliance issues |
legal | Legal and contractual risks | Litigation, contract disputes |
technology | Technology-related risks | System failures, obsolescence |
security | Security and cyber risks | Data breaches, cyber threats |
privacy | Personal data risks | Privacy breaches |
dataQuality | Data quality risks | Decisions based on poor data |
supplyChain | Supply chain risks | Supplier failure |
people | Workforce, skills and capacity risks | Capability gaps, key-person loss |
reputational | Brand and reputation risks | Public perception, stakeholder confidence |
relationship | Relationship risks | Partner or alliance breakdown |
changeManagement | Change and adoption risks | Resistance to change |
environmental | Natural-environment and climate risks | Extreme weather |
external | Other outside events beyond the organization's control | Supplier issues, external shocks |
other | Any other risk | |
diplomatic | Risks to relations between states or major parties | Breakdown of negotiations |
Strategy Objective Elements
Strategy Objective (strategyObjective)
| Attribute | Type | Description | Required | Example |
|---|---|---|---|---|
objectiveID | String | Unique identifier for the objective, so other records can reference it | "OBJ-001" | |
title | String | Name/title of objective | ✓ | "Zero Highway-Rail Grade Crossing Accidents" |
description | String | Objective explanation | ✓ | "Eliminate all accidents at highway-rail grade crossings" |
purpose | String | Intended purpose/function | ✓ | "Protect public safety at rail crossings" |
owner | String | Responsible individual/team | ✓ | "Grade Crossing Safety Director" |
orgUnitTitle | String | Aligned organization units | "Highway-Rail Grade Crossing Division" | |
orgUnitID | String | ID of the organization unit (see orgUnitTitle) | "OU-001" | |
objectiveType | Enum | Type of objective: powerAcquisition, powerPreservation, powerTransfer, powerReduction, destruction, neutralization, control, influence, access, denial, intelligence, disruption, legitimacy, survival, growth, efficiency, innovation, alliance, withdrawal, transition | efficiency | |
priority | Enum | Priority level (shared priority list: low, medium, high, critical) | critical | |
metrics | String | Success assessment indicators | "Crossing incidents per million train-miles" | |
targetValue | String | Specific target to achieve | "100% reduction in fatal crossing accidents" | |
currentValue | String | Current baseline value | "12 fatal accidents in 2024" | |
timeline | String | Achievement timeframe | "Q4 2027" | |
milestones | String | Key milestones and checkpoints | "50% reduction by 2026" | |
resources | String | Required resources | "$20M crossing upgrade budget" | |
dependencies | String | Critical dependencies | "Track monitoring systems, public awareness campaigns" | |
constraints | String | Limitations and constraints | "Local authority approvals" | |
stakeholders | String | Involved/affected stakeholders | "Road authorities, local communities" | |
riskFactors | String | Key risks to achievement | "Driver behaviour" | |
successCriteria | String | Criteria for success measurement | "No fatal crossing accidents for 12 months" | |
reportingFrequency | Enum | How often progress is reported (shared frequency list) | monthly | |
parentStrategy | String | Parent strategy this objective supports | "Zero Accident Initiative" | |
parentStrategyID | String | ID of the strategy this objective supports | "STR-006" |
Strategic Empathy Elements
The Strategy domain supports strategic empathy—the intentional use of emotional insight, stakeholder awareness, and political acuity to lead through complexity. These are optional top-level attributes of a strategy record.
| Attribute | Type | Description |
|---|---|---|
empathyFocus | Enum | Primary stakeholder group for empathy: customer, employee, partner, community, shareholder |
empathyIntegrationLevel | Enum | Maturity of empathy integration: adHoc, definedProcess, systemic, coreCapability |
stakeholderEmotionalInsight | Boolean | Whether strategy incorporates stakeholder emotional states |
politicalAcuity | Boolean | Whether strategy navigates power dynamics |
trustBuildingMandate | Boolean | Whether strategy includes trust-building mechanisms |
fearNavigationCapability | Boolean | Whether strategy addresses stakeholder fears during change |
unspokenDynamicsAwareness | Boolean | Whether strategic leadership reads unstated concerns, cultural nuances or hidden agendas that could affect adoption |
relationshipCentricity | Enum | How central relationships are to strategic success: transactional, collaborative, partnership |
empathyDrivenKPIs | Array[String] | KPIs linked to empathetic outcomes |
culturalContextIntegration | Boolean | Whether the strategy is designed with a deep understanding of organizational and external cultural nuances |
Domain Relationships
The Strategy domain integrates with other metamodel domains:
| Target Domain | Relationship Type | Description |
|---|---|---|
| Organization | Governance | Organization units govern and execute strategies |
| Capabilities | Enablement | Capabilities enable strategy execution |
| Initiatives | Implementation | Initiatives implement strategic objectives |
| Performance | Measurement | Performance metrics track strategic success |
| Stakeholder | Influence | Stakeholders influence and are impacted by strategy |
| Policy | Alignment | Policies align with strategic direction |
| Value Stream | Delivery | Value streams deliver strategic outcomes |
| Customer | Focus | Customer needs drive strategic priorities |
| People | Enablement | People execute and enable strategy |
| Intelligence | Insight | Intelligence informs strategic decisions |
Examples
Example 1: Digital Transformation Strategy
{
"strategyID": "STR-004",
"title": "Predictive Track Maintenance Program",
"description": "Implementation of AI-powered track defect prediction system across the national rail network",
"purpose": "Reduce track-related accidents by 35% through early detection and predictive maintenance",
"owner": "Director of Track Technology Innovation",
"orgUnitTitle": "Technology Innovation Division",
"strategyCategory": "corporate",
"strategyType": "disruption",
"strategicFocus": "innovationLeadership",
"timeHorizon": "mediumTerm",
"scopeLevel": "organization",
"objectives": "Deploy sensors on 85% of mainline track by 2026",
"keyActivities": "Sensor installation, data integration, model development",
"resources": "$145M budget, 23 technical staff, 4 AI systems",
"timeline": "36 months: 2024-2026",
"keyPerformanceIndicators": "Defect prediction accuracy: 92%, False positive rate: <3%",
"dependencies": "Track geometry systems, weather monitoring network",
"relatedStrategies": "Digital Track Inspection, Rail Stress Monitoring",
"risks": "Sensor reliability in extreme weather, data quality issues",
"riskCategories": [
"technology",
"operational",
"financial"
],
"mitigationStrategies": "Redundant sensor deployment, enhanced data validation",
"strategicAlignment": "Directly supports 25% accident reduction goal",
"businessObjective": "Reduce unplanned track maintenance by 40%",
"competitiveAdvantage": "Industry-leading predictive maintenance capabilities",
"marketPosition": "marketLeader",
"investmentLevel": "highInvestment",
"successCriteria": "25% reduction in track-related incidents, ROI > 15%",
"stakeholderImpact": "Improved safety for passengers, reduced costs for operators",
"changeManagement": "Phased rollout with extensive training and communication",
"parent": "FRA Technology Modernization Plan",
"child": "Rail Temperature Monitoring Strategy"
}
Example 2: Safety Compliance Strategy
{
"strategyID": "STR-006",
"title": "Zero Accident Initiative",
"description": "Comprehensive safety strategy to eliminate preventable accidents across all operations",
"purpose": "Achieve zero preventable accidents through systematic safety improvements",
"owner": "Chief Safety Officer",
"orgUnitTitle": "Safety and Compliance Division",
"strategyCategory": "corporate",
"strategyType": "defensive",
"strategicFocus": "legitimacy",
"timeHorizon": "longTerm",
"scopeLevel": "organization",
"keyPerformanceIndicators": "Lost-time injury rate, safety incident frequency, near-miss reporting rate",
"investmentLevel": "mediumInvestment",
"riskCategories": [
"operational",
"compliance",
"reputational"
],
"trustBuildingMandate": true,
"empathyFocus": "community",
"strategyObjectives": [
{
"objectiveID": "OBJ-001",
"title": "Zero Highway-Rail Grade Crossing Accidents",
"description": "Eliminate all accidents at highway-rail grade crossings",
"purpose": "Protect public safety at rail crossings",
"owner": "Grade Crossing Safety Director",
"orgUnitTitle": "Highway-Rail Grade Crossing Division",
"objectiveType": "efficiency",
"priority": "critical",
"targetValue": "100% reduction in fatal crossing accidents",
"timeline": "2027",
"parentStrategy": "Zero Accident Initiative",
"parentStrategyID": "STR-006"
}
]
}
Implementation Guidelines
Strategy Development Best Practices
- Start with outcomes — Define what success looks like before determining activities
- Align vertically — Ensure department strategies cascade from corporate strategy
- Embed measurement — Include KPIs at objective level for traceability
- Consider stakeholders — Use strategic empathy elements for human-centered strategy
- Plan for change — Include change management approach from the start
Strategy Cascade Pattern
OpenMetadata Integration
When integrating with OpenMetadata, map Strategy entities as follows:
| Triodian Element | OpenMetadata Entity | Notes |
|---|---|---|
| Strategy | Glossary Term | Strategic vocabulary |
| Strategy Objectives | Custom Entity | Track strategic objectives |
| KPIs | Data Quality Tests | Link metrics to data assets |
| Risk Categories | Tags | Apply to data assets |
| Time Horizon | Custom Property | Planning context |
# Example: Link strategic objectives to data assets
def link_strategy_to_data(strategy, data_assets):
"""
Tag data assets with strategic alignment information
"""
strategy_tag = {
"tagFQN": f"Strategy.{strategy['strategyID']}",
"description": strategy["purpose"],
"source": "Triodian"
}
for asset in data_assets:
if asset_supports_strategy(asset, strategy):
asset["tags"].append(strategy_tag)
asset["extension"] = {
"strategicAlignment": strategy["strategicAlignment"],
"timeHorizon": strategy["timeHorizon"],
"priority": get_priority(strategy)
}
return data_assets
Schema Reference
- Repository:
Triodian/Triodian_Metamodel - Schema: strategy.schema.json
- Specification: JSON Schema Draft-07
- License: Apache License 2.0
Previous: Capabilities Domain | Next: Products Domain