Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

...

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"}

Here's the updated Enumeration Values section with properties in code font, which will be suitable for Confluence:

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

JSON Schema Reference

...

Relationship with Other Domains

...