Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
A Rationale provides the logical reasoning behind a strategic or operational response. It connects a specific condition (Trigger) to a reasoned explanation that guides actions across one or more business architecture domains. Rationales are formalized objects in the Strategic Response Model and are central to decision transparency and traceability. See: Strategic Response Model
Rationales help ensure that every action taken by the organization is grounded in strategic intent and can be clearly explained through a documented reasoning process.
Every Rationale must reference the Trigger that prompted it. This is represented by linking to a triggerID. This linkage ensures traceability from external condition through to internal response.
...
Each rationale bridges the gap between a trigger event and organizational action. While triggers explain what happened to prompt a response, rationales explain why we're responding in this specific way.
Rationale classification framework
Rationales in the Orthogramic Metamodel follow a structured classification system that supports analytics, reuse, and auditability. Each rationale is categorized according to:
Rationale Orientation: Whether the rationale is reactive to existing conditions or proactive to anticipated conditions
Rationale Type: The response category (Preventative, Remedial, Opportunistic, etc.)
Reasoning Pattern: The logical structure of the rationale (Causal, Comparative, Normative, etc.)
Evidence Base: The foundation for the rationale (Data-driven, Expert judgment, Industry best practice, etc.)
Strategic Objective Reference: Direct link to the strategic objective this rationale supports
Business Value Type: The nature of value creation or preservation (Cost reduction, Revenue growth, Market creation, etc.)
...
The Orthogramic Metamodel now explicitly distinguishes between reactive and proactive rationales:
Reactive Rationales: Respond to existing conditions, events, or triggers that have already occurred
Proactive Rationales: Anticipate future conditions or opportunities that have not yet materialized
...
It's important to understand the relationship between Triggers and Rationales:
Triggers represent external or internal events/conditions that prompt a response (what happened)
Rationales explain the reasoning behind a specific response to that trigger (why we're responding this way)
...
Preventative: "Implementing these changes will prevent future incidents"
Compliance-focused: "We must implement to meet regulatory requirements"
Opportunistic: "This gives us a competitive advantage in safety reputation"
Implementation guidance
Clarity: Each rationale should clearly articulate the reasoning that connects the trigger to the chosen response
Traceability: Rationales should link to the relevant trigger, strategic objective, and affected domains
Consistency: Use the defined rationale types to ensure consistent classification
Evidence: Document the evidence base that supports each rationale
Strategic Alignment: Always connect rationales to strategic objectives to maintain alignment
Alternatives: Document alternative approaches considered and reasons for their rejection
Orientation: Clearly classify rationales as reactive or proactive
Competitive Context: For market-facing rationales, document competitive positioning impact
...
Rationales bridge between Triggers and organizational responses across multiple domains:
Strategy: Rationales explain strategic adjustments based on triggers
Capabilities: Rationales describe why capabilities need to be developed or modified
Initiatives: Rationales provide the foundation for launching initiatives
Policy: Rationales explain policy changes in response to triggers
Performance: Rationales describe modifications to performance metrics
Rationale and Trigger linkage examples
See: https://github.com/Orthogramic/Orthogramic_Metamodel/blob/main/examples/trigger-rationale-links.md
Rationale Schema
Introduction
...
Customer: Rationales justify changes to customer approaches and experiences
Market: Rationales explain market-related decisions and competitive responses
Finance: Rationales support financial resource allocation decisions
Risk Management: Rationales document risk-based decision processes
Supply Chain: Rationales justify supply chain configuration choices
Innovation: Rationales explain innovation investments and experimental approaches
Sustainability: Rationales articulate the basis for environmental and social initiatives
People: Rationales document the reasoning behind workforce and cultural decisions
Technology: Rationales explain technology selection and architecture choices
Channel: Rationales justify distribution channel strategies and partnerships
Rationale and Trigger linkage examples
See: Orthogramic_Metamodel/examples/trigger-rationale-links.md at main ยท Orthogramic/Orthogramic_Metamodel
Rationale Schema
Introduction
A Rationale provides the logical reasoning behind a strategic or operational response. It connects a specific condition (Trigger) to a reasoned explanation that guides actions across one or more business architecture domains. Rationales are formalized objects in the Strategic Response Model and are central to decision transparency and traceability.
See: https://github.com/Orthogramic/OrthogramicGitHub - Orthogramic/Orthogramic_Metamodel
Core Schema Properties
The following core schema properties apply to all rationales, regardless of domain:
Field | Type | Required | Description | Example |
---|---|---|---|---|
rationaleID | string (uuid) | Yes | Unique identifier for the rationale | "7a98e34d-f2b4-4ad1-9ac9-ecda9f145d79" |
rationaleTitle | string | Yes | Title or summary of the rationale | "Responding to new safety regulation" |
description | string | Yes | Detailed explanation supporting a strategic response | "The new regulation requires immediate updates to inspection protocols" |
triggerReference | string (uuid) | Yes | Primary trigger this rationale responds to | "uuid-of-trigger" |
triggerReferences | array of uuid | No | Optional multiple triggers this rationale addresses | ["uuid-1", "uuid-2"] |
linkedDomains | array of enum | No | Business architecture domains influenced or justified by this rationale | ["Policy", "Performance"] |
rationaleType | string (enum) | Yes | The justification type for this rationale | "Compliance_Fulfillment" |
rationaleOrientation | string (enum) | Yes | Whether the rationale is responding to existing conditions or anticipating future conditions | "Proactive" |
anticipatedOutcomes | array of string | No | For proactive rationales, the expected benefits or outcomes | ["Market leadership", "20% cost reduction"] |
alternativesConsidered | array of objects | No | Other strategic options that were evaluated but not selected | See example below |
reasoningPattern | string (enum) | No | The logical structure of the rationale | "Deductive" |
evidenceBase | string (enum) | No | The foundation for the rationale | "External_Research" |
strategicObjectiveReference | string (uuid) | No | Reference to the strategic objective this rationale supports | "uuid-of-objective" |
businessValueType | string (enum) | No | The nature of value creation or preservation | "Risk_Reduction" or "Market_Creation" |
competitivePositioning | object | No | How this rationale advances competitive stance | See example below |
dateCreated | string (date) | No | The date the rationale was first recorded | "2025-04-20" |
lastReviewed | string (date) | No | The most recent date of rationale review | "2025-06-01" |
effectivenessRating | integer (1โ5) | No | Optional evaluation of rationale effectiveness | 4 |
author | string | No | The person or team who documented the rationale | "Business Architecture Team" |
orgUnitTitle | string | No | The organisational unit that owns or authored the rationale | "Regulatory Compliance Division" |
relatedRationales | array of uuid | No | References to other related rationales | ["uuid-1", "uuid-2"] |
relationshipTypes | array of enum | No | Type of relationship with each related rationale | ["supports", "supersedes"] |
Example of alternativesConsidered
...
Code Block |
---|
"competitivePositioning": { "positioningType": "Differentiation", "positioningDescription": "Position our products as uniquely responsive to emerging customer needs through superior predictive analytics capabilities", "competitiveTarget": "Premium segment currently dominated by competitors relying on retrospective analytics" } |
Domain-Specific Schema Extensions
The rationale schema can be extended with domain-specific properties to capture context-specific reasoning. The following sections describe these domain-specific extensions.
Customer Domain Extensions
When a rationale relates to the Customer domain, the following additional properties can be specified:
Field | Type | Description | Example |
---|---|---|---|
customerSegmentIDs | array of string | Customer segments this rationale relates to | ["CUST-SEG-001", "CUST-SEG-003"] |
customerInsightSource | string (enum) | Source of customer insights supporting this rationale | "Voice_of_Customer", "Customer_Behavior_Analysis", "Market_Research" |
reasoningPattern | string (enum) | Customer-specific reasoning patterns | "Customer_Needs_Based", "Journey_Friction_Based", "Segment_Value_Based" |
businessValueType | string (enum) | Customer-specific value types | "Customer_Retention_Value", "Customer_Experience_Value", "Brand_Loyalty_Value" |
Market Domain Extensions
When a rationale relates to the Market domain, the following additional properties can be specified:
Field | Type | Description | Example |
---|---|---|---|
marketIDs | array of string | Markets this rationale relates to | ["MKT-ENTSW-001", "MKT-CLOUD-002"] |
marketInsightSource | string (enum) | Source of market insights supporting this rationale | "Market_Research", "Competitive_Intelligence", "Industry_Analysis" |
competitiveImplications | object | How this rationale affects competitive position | {"implicationType": "offensive", "targetCompetitors": ["Competitor A"], "expectedResponse": "Price matching"} |
marketRisks | array of objects | Market risks associated with this rationale | [{"riskDescription": "Increased competition", "likelihood": 4, "impact": 3, "mitigation": "Accelerated innovation"} ] |
Finance Domain Extensions
When a rationale relates to the Finance domain, the following additional properties can be specified:
Field | Type | Description | Example |
---|---|---|---|
financeIDs | array of string | Financial elements this rationale relates to | ["FIN-INV-001", "FIN-BUD-002"] |
financialInsightSource | string (enum) | Source of financial insights supporting this rationale | "Financial_Analysis", "Budget_Analysis", "Investment_Review" |
financialImpactAssessment | object | Assessment of financial implications | {"impactType": "income_statement", "estimatedAmount": 1500000, "impactTimeframe": "Q3-Q4 2025"} |
financialRisks | array of objects | Financial risks associated with this rationale | [{"riskDescription": "Capital cost overrun", "financialExposure": 500000, "likelihood": 3, "mitigation": "Phased funding approach"}] |
Risk Management Domain Extensions
When a rationale relates to the Risk Management domain, the following additional properties can be specified:
Field | Type | Description | Example |
---|---|---|---|
riskIDs | array of string | Risks this rationale relates to | ["RISK-CYBER-001", "RISK-COMP-002"] |
riskInsightSource | string (enum) | Source of risk insights supporting this rationale | "Risk_Assessment", "Incident_Analysis", "Control_Monitoring" |
riskImpactAssessment | object | Assessment of risk implications | {"impactType": "operational", "impactSeverity": "significant", "impactLikelihood": "moderate", "confidenceLevel": 4} |
Supply Chain Domain Extensions
When a rationale relates to the Supply Chain domain, the following additional properties can be specified:
Field | Type | Description | Example |
---|---|---|---|
supplyChainIDs | array of string | Supply chain elements this rationale relates to | ["SC-MFG-001", "SC-MFG-002"] |
supplyChainInsightSource | string (enum) | Source of supply chain insights supporting this rationale | "Supply_Chain_Analytics", "Supplier_Feedback", "Market_Intelligence" |
supplyChainImpactAssessment | object | Assessment of supply chain implications | {"impactAreas": ["supplier_network", "inventory"], "impactSeverity": "significant", "impactTimeframe": "medium-term"} |
Enumeration Values
Core Enumerations
rationaleOrientation
"Reactive"
- Responding to existing conditions or events that have already occurred"Proactive"
- Anticipating future conditions or opportunities that have not yet materialized
rationaleType
(Core)
"Preventative"
- Aims to prevent potential negative outcomes before they occur"Remedial"
- Addresses existing problems or deficiencies that need correction"Opportunistic"
- Leverages an emerging situation to create value or advantage"Proactive"
- Initiates change in anticipation of future needs or conditions"Reactive"
- Direct response to a specific trigger or event"Compliance_Fulfillment"
- Ensures adherence to legal, regulatory, or policy requirements"Strategic_Advancement"
- Supports forward movement on strategic objectives or positioning
reasoningPattern
(Core)
"Causal"
- Based on cause-and-effect relationships between events or conditions"Comparative"
- Based on similarities or differences with other situations or organizations"Normative"
- Based on standards, best practices, or what should ideally be done"Predictive"
- Based on forecasts or projections of future conditions"Analogical"
- Based on parallels with similar situations encountered previously"Deductive"
- Based on applying general principles to specific situations"Inductive"
- Based on recognizing patterns from specific observations
evidenceBase
(Core)
"Data_Driven"
- Primarily supported by quantitative metrics or analysis"Expert_Judgment"
- Based on specialized knowledge or experience of subject matter experts"Industry_Best_Practice"
- Informed by recognized standards or approaches in the industry"Customer_Feedback"
- Derived from direct customer or user input"Internal_Analysis"
- Based on internal studies, assessments, or evaluations"External_Research"
- Supported by third-party research or market analysis"Competitive_Analysis"
- Informed by assessment of competitor strategies or positions
businessValueType
(Core)
"Cost_Reduction"
- Decreasing operational or production expenses"Revenue_Growth"
- Increasing income or sales volume"Risk_Reduction"
- Mitigating potential threats or vulnerabilities"Customer_Experience"
- Enhancing interactions and satisfaction for customers"Operational_Efficiency"
- Improving internal processes or productivity"Competitive_Advantage"
- Strengthening position relative to competitors"Brand_Perception"
- Enhancing how the organization is viewed in the market"Stakeholder_Trust"
- Building confidence among investors, partners, or regulators"Market_Creation"
- Developing entirely new markets or customer segments"First_Mover_Advantage"
- Gaining benefits from being first to market with an offering"Market_Disruption"
- Changing existing market structures or business models"Innovation_Leadership"
- Establishing recognized leadership in innovative practices"Ecosystem_Development"
- Building or expanding a network of partners or complementary offerings"Strategic_Positioning"
- Improving long-term strategic position or capabilities
competitivePositioning.positioningType
"Differentiation"
- Setting the organization apart based on unique attributes or capabilities"Cost_Leadership"
- Competing primarily on price or value through operational efficiency"Focus_Strategy"
- Targeting specific market segments with tailored offerings"Blue_Ocean"
- Creating uncontested market space rather than competing in existing markets"Industry_Leadership"
- Establishing the organization as a dominant force in the industry"Fast_Follower"
- Quickly adopting innovations after market validation by others"Niche_Dominance"
- Commanding a specialized market segment or application area"Strategic_Alliance"
- Leveraging partnerships or collaborations for competitive advantage
relationshipTypes
"supports"
- This rationale reinforces or enhances another rationale"contradicts"
- This rationale conflicts with or opposes another rationale"expands"
- This rationale builds upon or extends the scope of another rationale"duplicates"
- This rationale substantially overlaps with another rationale"supersedes"
- This rationale replaces or makes obsolete another rationale
Domain-Specific Enumerations
Customer Domain
customerInsightSource
"Voice_of_Customer"
- Direct feedback from customers"Customer_Behavior_Analysis"
- Analysis of customer actions and patterns"Market_Research"
- Structured research on customer segments and needs"Customer_Service_Data"
- Information from customer service interactions"Social_Media_Analysis"
- Insights from social media conversations"Customer_Journey_Mapping"
- Analysis of customer experience touchpoints"Customer_Feedback"
- Formalized feedback mechanisms"Competitive_Analysis"
- Understanding customer choices vs. competitors
Customer-specific reasoningPattern
"Customer_Needs_Based"
- Focused on addressing explicit customer requirements"Market_Trends_Based"
- Responding to changing customer behaviors"Journey_Friction_Based"
- Addressing pain points in customer experience"Segment_Value_Based"
- Prioritizing high-value customer segments"Experience_Gap_Based"
- Closing gaps in customer experience
Customer-specific businessValueType
"Customer_Retention_Value"
- Keeping existing customers"Customer_Acquisition_Value"
- Gaining new customers"Customer_Growth_Value"
- Expanding revenue from existing customers"Brand_Loyalty_Value"
- Strengthening customer commitment"Customer_Experience_Value"
- Enhancing interactions"Market_Share_Value"
- Increasing proportion of customer base
Market Domain
marketInsightSource
"Market_Research"
- Formal market studies and analysis"Competitive_Intelligence"
- Information about competitor moves"Industry_Analysis"
- Broader sector trends and patterns"Customer_Feedback"
- Customer input about market needs"Sales_Data"
- Patterns in market purchases"Partner_Network"
- Insights from business partners"External_Consultant"
- Third-party market expertise"Strategic_Planning"
- Internal market projections
Market-specific rationaleType
"Competitive_Response"
- Reacting to competitor actions"Market_Opportunity"
- Pursuing new market openings"Defensive_Position"
- Protecting market share"Industry_Adaptation"
- Adjusting to industry changes"Growth_Initiative"
- Expanding market presence"Market_Entry"
- Moving into new markets"Market_Exit"
- Leaving unprofitable markets"Innovation_Imperative"
- Responding to market innovation needs"Consolidation_Strategy"
- Optimizing market positions
Finance Domain
financialInsightSource
"Financial_Analysis"
- Analysis of financial metrics"Performance_Metrics"
- Operational performance indicators"Investment_Review"
- Analysis of investment opportunities"Budget_Analysis"
- Review of budget allocations"Cost_Structure_Assessment"
- Analysis of cost components"Revenue_Analysis"
- Review of revenue streams"Risk_Assessment"
- Financial risk evaluations"Capital_Planning"
- Long-term capital allocation planning
Finance-specific rationaleType
"Financial_Performance_Improvement"
- Enhancing financial metrics"Cost_Optimization"
- Reducing or reallocating costs"Investment_Justification"
- Supporting investment decisions"Capital_Allocation"
- Guiding resource allocation"Financial_Risk_Management"
- Mitigating financial risks"Resource_Prioritization"
- Determining resource priorities"Financial_Sustainability"
- Ensuring long-term viability"Funding_Strategy"
- Approaching funding decisions"Value_Creation"
- Generating financial value
Risk Management Domain
riskInsightSource
"Risk_Assessment"
- Formal risk evaluation process"Incident_Analysis"
- Review of past incidents"Control_Monitoring"
- Oversight of control effectiveness"Audit_Finding"
- Results from audit processes"Industry_Intelligence"
- Risk trends in the industry"Scenario_Analysis"
- Evaluation of potential risk scenarios"Expert_Judgment"
- Risk specialist opinions
Risk-specific rationaleType
"Risk_Prevention"
- Preventing risk events"Risk_Mitigation"
- Reducing risk impact"Risk_Transfer"
- Shifting risk to other parties"Risk_Acceptance"
- Acknowledging and allowing risk"Control_Enhancement"
- Improving risk controls"Response_Planning"
- Preparing for risk events"Opportunity_Exploitation"
- Leveraging positive risk"Compliance_Management"
- Meeting risk requirements
Supply Chain Domain
supplyChainInsightSource
"Performance_Metrics"
- Supply chain performance data"Supply_Chain_Analytics"
- Advanced supply chain analysis"Market_Intelligence"
- Market factors affecting supply chain"Supplier_Feedback"
- Input from suppliers"Customer_Requirements"
- Customer needs affecting supply chain"Risk_Assessment"
- Supply chain risk evaluation"Technology_Evaluation"
- Analysis of supply chain technologies"Compliance_Analysis"
- Regulatory compliance assessment
Supply Chain-specific rationaleType
"Disruption_Response"
- Addressing supply chain disruptions"Network_Optimization"
- Improving supply chain structure"Cost_Reduction"
- Decreasing supply chain costs"Service_Improvement"
- Enhancing service levels"Risk_Mitigation"
- Reducing supply chain risks"Capability_Development"
- Building supply chain capabilities"Sustainability_Enhancement"
- Improving environmental impact"Technology_Adoption"
- Implementing new technologies"Supplier_Change"
- Modifying supplier relationships
Relationship with Other Domains
The Rationale schema has relationships with multiple domains in the Orthogramic Metamodel:
Strategic Response Model: Rationales provide the reasoning component that connects triggers to responses.
Triggers: Each rationale must reference at least one trigger that prompted it.
Domain-Specific Elements: Rationales can reference elements from Customer, Market, Finance, Risk, and Supply Chain domains.
Performance Indicators: Rationales may link to performance indicators that measure their effectiveness.
This consolidated schema supports structured reasoning and traceability across strategy, policy, and initiative development, ensuring that every response is grounded in a documented rationale that bridges from trigger events to strategic objectives.
Innovation updates
Rationale Schema Updates
Add new Innovation domain rationaleType enum values:
Innovation_Advancement
- Developing new innovationsCapability_Enhancement
- Strengthening innovation capabilitiesPortfolio_Optimization
- Improving innovation portfolio balanceExperimentation_Need
- Supporting testing of conceptsInnovation_Culture
- Strengthening innovation mindsets
Add new Innovation-specific evidenceBase enum values:
Experiment_Results
- Based on innovation testingInnovation_Metrics
- Informed by innovation performance dataPrototype_Feedback
- Derived from prototype testing
Add new Innovation-specific businessValueType enum values:
Innovation_Leadership
- Establishing position as an innovation leaderTime_To_Market
- Accelerating innovation development cyclesInnovation_Capability
- Building organizational capability for innovation
Add Innovation domain-specific properties:
innovationInsightSource
: String (enum) - Source of innovation insightsinnovationImpactAssessment
: Object - Assessment of impact on innovation
Sustainability updates
Rationale Schema Updates:
Add sustainability-specific rationaleType values:
"Sustainability_Compliance"
"Environmental_Stewardship"
"Social_Impact_Enhancement"
"Governance_Improvement"
"Climate_Risk_Mitigation"
Add "Sustainability_Insight" to evidenceBase enum values
Add sustainability-specific businessValueType values:
"Environmental_Value"
"Social_Value"
"Governance_Value"
"Sustainability_Reputation"
Add a new
sustainabilityInsightSource
enum with values:"ESG_Assessment"
"Climate_Scenario_Analysis"
"Stakeholder_Materiality_Assessment"
"Sustainability_Reporting"
"External_ESG_Rating"
People updates
Rationale Schema Updates
Add people-specific
rationaleType
enum values:"Talent_Development" - Developing human capabilities
"Culture_Enhancement" - Strengthening organizational culture
"Knowledge_Management" - Preserving critical knowledge
"Workforce_Optimization" - Improving workforce structure
"Talent_Acquisition" - Addressing talent sourcing needs
Add "People_Insight" to
evidenceBase
enum valuesAdd people-specific
businessValueType
values:"Talent_Value"
"Culture_Value"
"Knowledge_Value"
Add a new
peopleInsightSource
enum with values:"Engagement_Assessment"
"Skills_Analysis"
"Cultural_Assessment"
"Competency_Evaluation"
"Knowledge_Audit"
Technology updates
Rationale Schema Updates
Add "Technology_Refresh" to the rationaleType enum values
Add "Legacy_Modernization" to the rationaleType enum values
Add "Security_Enhancement" to the rationaleType enum values
Add "Technology_Integration" to the rationaleType enum values
Add "Technology_Standardization" to the rationaleType enum values
Add new Technology-specific detectionMethod enum values:
"Technology_Assessment"
"Security_Monitoring"
"Vendor_Notification"
Channel updates
Rationale Schema Updates
...
Add Channel-specific rationale types:
"Channel_Optimization"
"Channel_Expansion"
"Partner_Management"
"Distribution_Efficiency"
"Omnichannel_Integration"
...
Add Channel-specific insight source enum values:
"Channel_Performance_Analysis"
"Partner_Feedback"
"Distribution_Network_Assessment"
"Customer_Channel_Preference"
...
Add Channel-specific reasoning patterns:
"Channel_Effectiveness_Based"
"Partner_Performance_Based"
"Distribution_Efficiency_Based"
...
Add Channel-specific business value types:
"Channel_Reach_Value"
"Distribution_Efficiency_Value"
"Partner_Network_Value"
Add Channel domain-specific properties:
...
channelIDs
: Array of string - Channels this rationale relates to
...
channelInsightSource
: String (enum) - Source of channel insights
...
Innovation Domain Extensions
When a rationale relates to the Innovation domain, the following additional properties can be specified:
Field | Type | Description | Example |
---|---|---|---|
innovationIDs | array of string | Innovation elements this rationale relates to | ["INN-DIGITAL-001", "INN-AI-003"] |
innovationInsightSource | string (enum) | Source of innovation insights supporting this rationale | "Experiment_Results", "Innovation_Metrics", "Prototype_Feedback" |
innovationImpactAssessment | object | Assessment of innovation implications | {"impactType": "acceleration", "affectedCapabilities": ["Experimentation", "Idea Management"], "timeframeChange": "35% reduction in cycle time"} |
Sustainability Domain Extensions
When a rationale relates to the Sustainability domain, the following additional properties can be specified:
Field | Type | Description | Example |
---|---|---|---|
sustainabilityIDs | array of string | Sustainability elements this rationale relates to | ["SUST-ENV-001", "SUST-SOC-002"] |
sustainabilityInsightSource | string (enum) | Source of sustainability insights supporting this rationale | "ESG_Assessment", "Climate_Scenario_Analysis", "Stakeholder_Materiality_Assessment" |
sustainabilityImpactAssessment | object | Assessment of sustainability implications | {"impactDimensions": ["Carbon Footprint", "Biodiversity"], "stakeholderExpectations": "Visible progress on emissions reduction", "complianceRelevance": "Supports anticipated regulatory requirements"} |
People Domain Extensions
When a rationale relates to the People domain, the following additional properties can be specified:
Field | Type | Description | Example |
---|---|---|---|
peopleIDs | array of string | People elements this rationale relates to | ["PEOPLE-WORKFORCE-001", "PEOPLE-CULTURE-002"] |
peopleInsightSource | string (enum) | Source of people insights supporting this rationale | "Engagement_Assessment", "Skills_Analysis", "Cultural_Assessment" |
peopleImpactAssessment | object | Assessment of workforce implications | {"impactAreas": ["Talent Development", "Organizational Culture"], "affectedRoles": ["Engineering", "Product Development"], "timeframeForChange": "6-12 months"} |
Technology Domain Extensions
When a rationale relates to the Technology domain, the following additional properties can be specified:
Field | Type | Description | Example |
---|---|---|---|
technologyIDs | array of string | Technology elements this rationale relates to | ["TECH-API-001", "TECH-CLOUD-002"] |
technologyInsightSource | string (enum) | Source of technology insights supporting this rationale | "Technology_Assessment", "Security_Monitoring", "Vendor_Notification" |
technologyImpactAssessment | object | Assessment of technology implications | {"impactAreas": ["System Architecture", "Security Framework"], "technicalDebt": "Significant reduction potential", "timeframeForImplementation": "3 release cycles"} |
Channel Domain Extensions
When a rationale relates to the Channel domain, the following additional properties can be specified:
Field | Type | Description | Example |
---|---|---|---|
channelIDs | array of string | Channel elements this rationale relates to | ["CHAN-RETAIL-001", "CHAN-DIGITAL-002"] |
channelInsightSource | string (enum) | Source of channel insights supporting this rationale | "Channel_Performance_Analysis", "Partner_Feedback", "Distribution_Network_Assessment" |
channelImpactAssessment | object | Assessment of channel implications | {"impactAreas": ["Partner Network", "Digital Touchpoints"], "customerJourneyEffects": "Improved cross-channel consistency", "implementationComplexity": "Medium"} |
Enumeration Values
Core Enumerations
rationaleOrientation
Reactive
- Responding to existing conditions or events that have already occurredProactive
- Anticipating future conditions or opportunities that have not yet materialized
rationaleType (Core)
Preventative
- Aims to prevent potential negative outcomes before they occurRemedial
- Addresses existing problems or deficiencies that need correctionOpportunistic
- Leverages an emerging situation to create value or advantageProactive
- Initiates change in anticipation of future needs or conditionsReactive
- Direct response to a specific trigger or eventCompliance_Fulfillment
- Ensures adherence to legal, regulatory, or policy requirementsStrategic_Advancement
- Supports forward movement on strategic objectives or positioning
reasoningPattern (Core)
Causal
- Based on cause-and-effect relationships between events or conditionsComparative
- Based on similarities or differences with other situations or organizationsNormative
- Based on standards, best practices, or what should ideally be donePredictive
- Based on forecasts or projections of future conditionsAnalogical
- Based on parallels with similar situations encountered previouslyDeductive
- Based on applying general principles to specific situationsInductive
- Based on recognizing patterns from specific observations
evidenceBase (Core)
Data_Driven
- Primarily supported by quantitative metrics or analysisExpert_Judgment
- Based on specialized knowledge or experience of subject matter expertsIndustry_Best_Practice
- Informed by recognized standards or approaches in the industryCustomer_Feedback
- Derived from direct customer or user inputInternal_Analysis
- Based on internal studies, assessments, or evaluationsExternal_Research
- Supported by third-party research or market analysisCompetitive_Analysis
- Informed by assessment of competitor strategies or positionsSustainability_Insight
- Based on environmental or social impact analysisPeople_Insight
- Derived from workforce or cultural assessmentsExperiment_Results
- Based on innovation testing outcomesPrototype_Feedback
- Derived from prototype evaluation
businessValueType (Core)
Cost_Reduction
- Decreasing operational or production expensesRevenue_Growth
- Increasing income or sales volumeRisk_Reduction
- Mitigating potential threats or vulnerabilitiesCustomer_Experience
- Enhancing interactions and satisfaction for customersOperational_Efficiency
- Improving internal processes or productivityCompetitive_Advantage
- Strengthening position relative to competitorsBrand_Perception
- Enhancing how the organization is viewed in the marketStakeholder_Trust
- Building confidence among investors, partners, or regulatorsMarket_Creation
- Developing entirely new markets or customer segmentsFirst_Mover_Advantage
- Gaining benefits from being first to market with an offeringMarket_Disruption
- Changing existing market structures or business modelsInnovation_Leadership
- Establishing recognized leadership in innovative practicesEcosystem_Development
- Building or expanding a network of partners or complementary offeringsStrategic_Positioning
- Improving long-term strategic position or capabilitiesEnvironmental_Value
- Creating positive environmental impacts or reducing negative onesSocial_Value
- Generating positive social outcomes or addressing social issuesGovernance_Value
- Improving organizational governance structures or processesTalent_Value
- Enhancing workforce capabilities or engagementCulture_Value
- Strengthening organizational cultureKnowledge_Value
- Preserving or enhancing organizational knowledgeChannel_Reach_Value
- Expanding access to customers through distribution channelsDistribution_Efficiency_Value
- Optimizing channel operations and costsPartner_Network_Value
- Strengthening relationships with distribution partners
competitivePositioning.positioningType
Differentiation
- Setting the organization apart based on unique attributes or capabilitiesCost_Leadership
- Competing primarily on price or value through operational efficiencyFocus_Strategy
- Targeting specific market segments with tailored offeringsBlue_Ocean
- Creating uncontested market space rather than competing in existing marketsIndustry_Leadership
- Establishing the organization as a dominant force in the industryFast_Follower
- Quickly adopting innovations after market validation by othersNiche_Dominance
- Commanding a specialized market segment or application areaStrategic_Alliance
- Leveraging partnerships or collaborations for competitive advantage
relationshipTypes
supports
- This rationale reinforces or enhances another rationalecontradicts
- This rationale conflicts with or opposes another rationaleexpands
- This rationale builds upon or extends the scope of another rationaleduplicates
- This rationale substantially overlaps with another rationalesupersedes
- This rationale replaces or makes obsolete another rationale
Domain-Specific Enumerations
Customer Domain
customerInsightSource
Voice_of_Customer
- Direct feedback from customersCustomer_Behavior_Analysis
- Analysis of customer actions and patternsMarket_Research
- Structured research on customer segments and needsCustomer_Service_Data
- Information from customer service interactionsSocial_Media_Analysis
- Insights from social media conversationsCustomer_Journey_Mapping
- Analysis of customer experience touchpointsCustomer_Feedback
- Formalized feedback mechanismsCompetitive_Analysis
- Understanding customer choices vs. competitors
Customer-specific reasoningPattern
Customer_Needs_Based
- Focused on addressing explicit customer requirementsMarket_Trends_Based
- Responding to changing customer behaviorsJourney_Friction_Based
- Addressing pain points in customer experienceSegment_Value_Based
- Prioritizing high-value customer segmentsExperience_Gap_Based
- Closing gaps in customer experience
Customer-specific businessValueType
Customer_Retention_Value
- Keeping existing customersCustomer_Acquisition_Value
- Gaining new customersCustomer_Growth_Value
- Expanding revenue from existing customersBrand_Loyalty_Value
- Strengthening customer commitmentCustomer_Experience_Value
- Enhancing interactionsMarket_Share_Value
- Increasing proportion of customer base
Market Domain
marketInsightSource
Market_Research
- Formal market studies and analysisCompetitive_Intelligence
- Information about competitor movesIndustry_Analysis
- Broader sector trends and patternsCustomer_Feedback
- Customer input about market needsSales_Data
- Patterns in market purchasesPartner_Network
- Insights from business partnersExternal_Consultant
- Third-party market expertiseStrategic_Planning
- Internal market projections
Market-specific rationaleType
Competitive_Response
- Reacting to competitor actionsMarket_Opportunity
- Pursuing new market openingsDefensive_Position
- Protecting market shareIndustry_Adaptation
- Adjusting to industry changesGrowth_Initiative
- Expanding market presenceMarket_Entry
- Moving into new marketsMarket_Exit
- Leaving unprofitable marketsInnovation_Imperative
- Responding to market innovation needsConsolidation_Strategy
- Optimizing market positions
Finance Domain
financialInsightSource
Financial_Analysis
- Analysis of financial metricsPerformance_Metrics
- Operational performance indicatorsInvestment_Review
- Analysis of investment opportunitiesBudget_Analysis
- Review of budget allocationsCost_Structure_Assessment
- Analysis of cost componentsRevenue_Analysis
- Review of revenue streamsRisk_Assessment
- Financial risk evaluationsCapital_Planning
- Long-term capital allocation planning
Finance-specific rationaleType
Financial_Performance_Improvement
- Enhancing financial metricsCost_Optimization
- Reducing or reallocating costsInvestment_Justification
- Supporting investment decisionsCapital_Allocation
- Guiding resource allocationFinancial_Risk_Management
- Mitigating financial risksResource_Prioritization
- Determining resource prioritiesFinancial_Sustainability
- Ensuring long-term viabilityFunding_Strategy
- Approaching funding decisionsValue_Creation
- Generating financial value
Risk Management Domain
riskInsightSource
Risk_Assessment
- Formal risk evaluation processIncident_Analysis
- Review of past incidentsControl_Monitoring
- Oversight of control effectivenessAudit_Finding
- Results from audit processesIndustry_Intelligence
- Risk trends in the industryScenario_Analysis
- Evaluation of potential risk scenariosExpert_Judgment
- Risk specialist opinions
Risk-specific rationaleType
Risk_Prevention
- Preventing risk eventsRisk_Mitigation
- Reducing risk impactRisk_Transfer
- Shifting risk to other partiesRisk_Acceptance
- Acknowledging and allowing riskControl_Enhancement
- Improving risk controlsResponse_Planning
- Preparing for risk eventsOpportunity_Exploitation
- Leveraging positive riskCompliance_Management
- Meeting risk requirements
Supply Chain Domain
supplyChainInsightSource
Performance_Metrics
- Supply chain performance dataSupply_Chain_Analytics
- Advanced supply chain analysisMarket_Intelligence
- Market factors affecting supply chainSupplier_Feedback
- Input from suppliersCustomer_Requirements
- Customer needs affecting supply chainRisk_Assessment
- Supply chain risk evaluationTechnology_Evaluation
- Analysis of supply chain technologiesCompliance_Analysis
- Regulatory compliance assessment
Supply Chain-specific rationaleType
Disruption_Response
- Addressing supply chain disruptionsNetwork_Optimization
- Improving supply chain structureCost_Reduction
- Decreasing supply chain costsService_Improvement
- Enhancing service levelsRisk_Mitigation
- Reducing supply chain risksCapability_Development
- Building supply chain capabilitiesSustainability_Enhancement
- Improving environmental impactTechnology_Adoption
- Implementing new technologiesSupplier_Change
- Modifying supplier relationships
Innovation Domain
innovationInsightSource
Experiment_Results
- Based on innovation testingInnovation_Metrics
- Informed by innovation performance dataPrototype_Feedback
- Derived from prototype testingIdea_Management_System
- Insights from idea collectionInnovation_Assessment
- Evaluation of innovation capabilitiesTechnology_Scouting
- Exploration of emerging technologiesPortfolio_Analysis
- Review of innovation portfolio balance
Innovation-specific rationaleType
Innovation_Advancement
- Developing new innovationsCapability_Enhancement
- Strengthening innovation capabilitiesPortfolio_Optimization
- Improving innovation portfolio balanceExperimentation_Need
- Supporting testing of conceptsInnovation_Culture
- Strengthening innovation mindsetsTechnology_Adoption
- Implementing emerging technologiesInnovation_Process_Improvement
- Enhancing innovation methods
Innovation-specific businessValueType
Innovation_Leadership
- Establishing position as an innovation leaderTime_To_Market
- Accelerating innovation development cyclesInnovation_Capability
- Building organizational capability for innovationDisruptive_Potential
- Creating market-changing innovationsExperimental_Learning
- Gaining insights through structured testingIdeation_Effectiveness
- Improving the generation of valuable ideas
Sustainability Domain
sustainabilityInsightSource
ESG_Assessment
- Evaluation of environmental, social, and governance factorsClimate_Scenario_Analysis
- Analysis of climate change impactsStakeholder_Materiality_Assessment
- Determination of key sustainability issuesSustainability_Reporting
- Insights from sustainability disclosure processesExternal_ESG_Rating
- Feedback from third-party sustainability ratingsEnvironmental_Impact_Analysis
- Evaluation of ecological footprintSocial_Impact_Assessment
- Analysis of effects on communities and society
Sustainability-specific rationaleType
Sustainability_Compliance
- Meeting sustainability regulations or standardsEnvironmental_Stewardship
- Protecting or enhancing natural resourcesSocial_Impact_Enhancement
- Improving impacts on communities and societyGovernance_Improvement
- Strengthening sustainability governanceClimate_Risk_Mitigation
- Addressing risks from climate changeStakeholder_Expectation_Management
- Meeting sustainability expectationsCircular_Economy_Advancement
- Moving toward regenerative business modelsResource_Efficiency_Improvement
- Optimizing use of natural resources
Sustainability-specific businessValueType
Environmental_Value
- Creating positive environmental impactsSocial_Value
- Generating positive social outcomesGovernance_Value
- Improving organizational governanceSustainability_Reputation
- Enhancing perception as responsible organizationResource_Security
- Ensuring long-term access to needed resourcesRegulatory_Resilience
- Preparing for evolving sustainability regulationsStakeholder_Trust
- Building confidence among sustainability-focused stakeholders
People Domain
peopleInsightSource
Engagement_Assessment
- Evaluation of employee engagementSkills_Analysis
- Assessment of workforce capabilitiesCultural_Assessment
- Evaluation of organizational cultureCompetency_Evaluation
- Assessment of role-specific abilitiesKnowledge_Audit
- Inventory of organizational knowledgeExit_Interviews
- Insights from departing employeesTalent_Analytics
- Data-driven workforce analysisLeadership_Assessment
- Evaluation of leadership effectiveness
People-specific rationaleType
Talent_Development
- Developing human capabilitiesCulture_Enhancement
- Strengthening organizational cultureKnowledge_Management
- Preserving critical knowledgeWorkforce_Optimization
- Improving workforce structureTalent_Acquisition
- Addressing talent sourcing needsEmployee_Experience_Improvement
- Enhancing work environmentLeadership_Development
- Strengthening leadership capabilitiesOrganizational_Alignment
- Improving structure and roles
People-specific businessValueType
Talent_Value
- Enhancing workforce capabilitiesCulture_Value
- Strengthening organizational cultureKnowledge_Value
- Preserving organizational expertiseEngagement_Value
- Improving employee commitmentProductivity_Value
- Increasing workforce effectivenessInnovation_Capacity
- Enhancing ability to generate ideasOrganizational_Agility
- Improving adaptability to change
Technology Domain
technologyInsightSource
Technology_Assessment
- Evaluation of technology capabilitiesSecurity_Monitoring
- Security system observationsVendor_Notification
- Information from technology providersTechnical_Debt_Analysis
- Assessment of technical debtArchitecture_Review
- Evaluation of technical architectureTechnology_Trend_Analysis
- Study of emerging technologiesSystem_Performance_Monitoring
- Operational technology metrics
Technology-specific rationaleType
Technology_Refresh
- Updating existing technologyLegacy_Modernization
- Transforming outdated systemsSecurity_Enhancement
- Improving technology securityTechnology_Integration
- Connecting disparate systemsTechnology_Standardization
- Harmonizing technology approachesArchitecture_Transformation
- Redesigning technology structureDigital_Capability_Building
- Creating new digital abilitiesTechnical_Debt_Reduction
- Addressing accumulated shortcomings
Technology-specific businessValueType
Technical_Agility
- Improving adaptability of technologySystem_Reliability
- Enhancing technology dependabilitySecurity_Posture
- Strengthening protection against threatsTechnical_Performance
- Improving system speed and efficiencyIntegration_Effectiveness
- Enhancing system connectionsTechnology_Cost_Efficiency
- Optimizing technology expensesDigital_Experience
- Improving technology interactions
Channel Domain
channelInsightSource
Channel_Performance_Analysis
- Review of channel metricsPartner_Feedback
- Input from channel partnersDistribution_Network_Assessment
- Evaluation of network structureCustomer_Channel_Preference
- Analysis of customer channel usageCompetitive_Channel_Analysis
- Study of competitor channel approachesChannel_Cost_Analysis
- Evaluation of channel economicsOmnichannel_Integration_Assessment
- Analysis of channel connections
Channel-specific rationaleType
Channel_Optimization
- Improving channel performanceChannel_Expansion
- Adding new distribution channelsPartner_Management
- Enhancing channel partner relationshipsDistribution_Efficiency
- Optimizing channel operationsOmnichannel_Integration
- Connecting multiple channelsChannel_Conflict_Resolution
- Addressing channel competitionDigital_Channel_Development
- Enhancing online distributionChannel_Mix_Rebalancing
- Adjusting relative channel importance
Channel-specific reasoningPattern
Channel_Effectiveness_Based
- Focused on channel performancePartner_Performance_Based
- Based on channel partner capabilitiesDistribution_Efficiency_Based
- Focused on operational optimizationCustomer_Access_Based
- Prioritizing customer reach considerationsChannel_Economics_Based
- Based on financial performance of channels
Channel-specific businessValueType
Channel_Reach_Value
- Expanding access to customersDistribution_Efficiency_Value
- Optimizing channel operationsPartner_Network_Value
- Strengthening channel relationshipsChannel_Integration_Value
- Creating seamless customer experiencesChannel_Innovation_Value
- Developing new distribution approachesCustomer_Access_Value
- Improving availability to customers
Relationship with Other Domains
The Rationale schema has relationships with multiple domains in the Orthogramic Metamodel:
Strategic Response Model: Rationales provide the reasoning component that connects triggers to responses.
Triggers: Each rationale must reference at least one trigger that prompted it.
Domain-Specific Elements: Rationales can reference elements from all domains including Customer, Market, Finance, Risk, Supply Chain, Innovation, Sustainability, People, Technology, and Channel domains.
Performance Indicators: Rationales may link to performance indicators that measure their effectiveness.
This consolidated schema supports structured reasoning and traceability across strategy, policy, and initiative development, ensuring that every response is grounded in a documented rationale that bridges from trigger events to strategic objectives.