Stakeholder Domain

The Stakeholder domain represents all individuals, groups, or organizations that either affect or are affected by the enterprise's strategies, activities, or outcomes. It provides the human and political context for all other enterprise architecture domains.

Schema Version: 2.1
Schema Location: /schemas/stakeholder.schema.json
Specification: JSON Schema Draft-07

Overview

What is the Stakeholder Domain?

The Stakeholder domain captures the essential context of who matters to the enterprise—from internal employees and executives to external regulators, customers, and the public. It focuses on classifying and documenting their:

• Roles and responsibilities within or toward the organization
• Interests and concerns regarding organizational outcomes
• Influence and power to affect decisions and strategy
• Engagement strategies for effective communication and management

Purpose and Value

The Stakeholder domain enables architects and planners to:

• Identify and classify key actors by systematically documenting all internal and external parties crucial to success
• Analyze influence and interest using models such as the Power–Interest Grid
• Define engagement strategies with tailored communication and engagement plans
• Prioritize initiative alignment by linking initiatives to the stakeholders they serve
• Manage expectations and risks by proactively addressing concerns and resistance
• Provide human context linking abstract architectural entities to accountable people

For Data Engineers

The Stakeholder domain maps directly to data governance roles:

• Stakeholders → Data Owners, Stewards, Consumers
• Engagement Strategies → Communication plans for data governance
• Requirements → Data quality requirements, SLAs
• Influence/Interest → Priority for data asset ownership

Domain Attributes

Core Attributes

Attribute	Type	Description	Required
title	String	Name/title of stakeholder	✓
tType	Enum	Position relation to organization	✓
description	String	Detailed explanation	✓
role	String	Responsibilities and interests
orgUnitTitle	String	Most closely linked org unit
stakeholderCategory	Enum	Broad stakeholder classification
influenceLevel	Enum	Degree of influence on organization
interestLevel	Enum	Level of interest in organization
engagementStrategies	String	Communication/interaction plans
engagementFrequency	Enum	How often engagement occurs
communicationChannels	Array[Enum]	Preferred communication methods
inputs	String	Resources/info provided by stakeholder
outputs	String	Benefits/outcomes received
expectations	String	What stakeholder expects from organization
dependencies	String	Required dependencies
relatedStakeholders	String	Related/linked stakeholders
geographicScope	Enum	Geographic scope of stakeholder
industry	Enum	Industry sector of stakeholder
organizationType	Enum	Type of organization stakeholder represents
performanceIndicators	String	Engagement effectiveness metrics
risks	String	Engagement risks
riskCategories	Array[Enum]	Categories of risks
improvementOpportunities	String	Enhancement areas
strategicAlignment	String	Goal alignment
stakeholderRequirements	Array[Object]	Specific requirements from stakeholder

Stakeholder Requirements Sub-Element

Attribute	Type	Description
title	String	Name/title of requirement
description	String	Detailed explanation
purpose	String	Intended purpose/benefit
owner	String	Responsible fulfiller
orgUnitTitle	String	Impacted organization units
priority	Enum	Requirement priority level
requirementType	Enum	Type of requirement
acceptanceCriteria	String	Acceptance criteria
timeline	String	Expected timeline for fulfillment
dependencies	String	Related dependencies
complianceFramework	Enum	Regulatory requirement framework
regulatoryCompliance	String	Regulatory requirements
measurementCriteria	String	How requirement success is measured
riskLevel	Enum	Risk level if not met

Enumeration Values

Stakeholder Type (tType)

Value	Description	Example
Primary Customer	Main customer or client	Enterprise software customers
Secondary Customer	Indirect or secondary customers	End users of customer's products
B2B Customer	Business-to-business customer	Corporate clients
B2C Customer	Business-to-consumer customer	Individual consumers
B2G Customer	Business-to-government customer	Government agencies
Internal Customer	Internal organizational customer	Internal departments
End User	Final user of product/service	Software application users
Regulatory Body	Government regulatory agency	Federal Railroad Administration
Government Agency	Government department or agency	Department of Transportation
Local Authority	Local government entity	City transportation department
International Body	International organization	United Nations, European Union
Standards Organization	Standards setting body	ISO, IEEE
Strategic Partner	Long-term strategic alliance	Joint venture partners
Supplier/Vendor	Goods or services provider	Equipment manufacturers
Distributor/Channel Partner	Distribution partner	Retail distribution networks
System Integrator	Technology integration partner	IT system integrators
Consultant/Advisor	Professional advisory services	Management consultants
Financial Institution	Banking or finance provider	Investment banks
Investor/Shareholder	Financial stakeholder	Equity investors
Board Member	Governance stakeholder	Board of directors
Employee/Staff	Internal workforce	Company employees
Trade Union	Labor organization	Railway workers union
Industry Association	Professional industry group	Railway industry association
Community Representative	Local community voice	Neighborhood associations
Environmental Group	Environmental advocacy	Environmental protection groups
Media/Press	News and media organizations	Industry publications
Academic Institution	Educational organization	Universities, research institutes
Competitor	Market competitor	Competing organizations

Stakeholder Category (stakeholderCategory)

Value	Description	Example
Internal Stakeholder	Stakeholders within the organization	Employees, management, shareholders
External Stakeholder	Stakeholders outside the organization	Customers, suppliers, regulators
Primary Stakeholder	Direct impact on organization success	Key customers, investors
Secondary Stakeholder	Indirect influence on organization	Industry associations, media
Key Stakeholder	Critical to organization success	Major customers, key suppliers
Influential Stakeholder	High influence but varying interest	Government regulators, industry leaders

Influence Level (influenceLevel)

Value	Description	Example
High Influence	Significant power to affect organization	Major investors, key regulators
Medium Influence	Moderate power to affect organization	Important customers, suppliers
Low Influence	Limited power to affect organization	Individual consumers, small vendors

Interest Level (interestLevel)

Value	Description	Example
High Interest	Very interested in organization outcomes	Direct customers, employees
Medium Interest	Moderate interest in organization	Industry partners, community
Low Interest	Limited interest in organization	Distant suppliers, general public

Engagement Frequency (engagementFrequency)

Value	Description	Example
Daily	Multiple times per day or daily	Operations teams, key customers
Weekly	Once or multiple times per week	Project partners, regular suppliers
Monthly	Monthly engagement	Management reporting, board updates
Quarterly	Every three months	Investor relations, strategic reviews
Annually	Once per year	Annual shareholder meetings
Ad-hoc	As needed basis	Consultants, crisis communications
Continuous	Ongoing, always available	Digital platforms, customer support

Communication Channels (communicationChannels)

Value	Description
Email	Electronic mail communication
Phone/Call	Telephone communication
Video Conference	Online video meetings
In-Person Meeting	Face-to-face meetings
Digital Platform	Online platforms or portals
Newsletter	Regular newsletter communications
Reports	Formal reporting documents
Workshops	Interactive workshop sessions
Website	Public website communications

Risk Categories (riskCategories)

Value	Description	Example
Operational	Day-to-day operational risks	Service delivery issues, process failures
Financial	Financial and budget risks	Payment delays, cost overruns
Compliance/Regulatory	Regulatory compliance risks	Non-compliance penalties
Reputational	Reputation and brand risks	Negative publicity, brand damage
Strategic	Strategic planning risks	Misaligned objectives
Communication	Communication-related risks	Miscommunication, information gaps
Relationship	Relationship management risks	Relationship breakdown, trust issues
External/Environmental	External environmental risks	Market changes, political instability
Technology	Technology-related risks	System failures, cybersecurity threats
Legal	Legal and contractual risks	Contract disputes, legal violations

Requirement Priority (priority)

Value	Description	Example
Critical	Must be fulfilled for basic operation	Safety compliance requirements
High	Important for successful operation	Key performance requirements
Medium	Beneficial but not essential	Process improvement requirements
Low	Nice to have, future consideration	Enhancement requests

Requirement Type (requirementType)

Value	Description	Example
Functional	Specific functionality requirements	System features, capabilities
Non-Functional	Quality attributes	Performance, security, usability
Compliance	Regulatory or standards compliance	Legal requirements, certifications
Business	Business process requirements	Workflow, operational procedures
Technical	Technical specifications	System architecture, integration
User Experience	User experience requirements	Interface design, accessibility

Domain Relationships

The Stakeholder domain integrates with other metamodel domains:

Target Domain	Relationship Type	Description
Organization	Engagement	Organization units engage with stakeholders
Strategy	Influence	Stakeholders influence strategic direction
Policy	Compliance	Stakeholders subject to or creators of policies
Services	Consumption	Stakeholders consume or provide services
Products	Usage	Stakeholders use or influence product development
Information	Exchange	Stakeholders provide and consume information
Performance	Impact	Stakeholders affected by or affect performance
Initiatives	Involvement	Stakeholders participate in or are impacted by initiatives

Stakeholder Analysis Framework

The Stakeholder domain supports comprehensive stakeholder analysis using influence-interest matrices:

Quadrant	Strategy	Stakeholders
High Influence, High Interest	Manage closely	Key stakeholders requiring active management
High Influence, Low Interest	Keep satisfied	Influential stakeholders requiring attention
Low Influence, High Interest	Keep informed	Interested stakeholders to communicate with
Low Influence, Low Interest	Monitor	Minimal engagement required

Examples

Example 1: Regulatory Body

{
  "title": "Federal Railroad Administration",
  "tType": "Regulatory Body",
  "description": "Federal agency responsible for railroad safety oversight",
  "role": "Establish and enforce railroad safety standards and regulations",
  "orgUnitTitle": "Regulatory Compliance Division",
  "stakeholderCategory": "External Stakeholder",
  "influenceLevel": "High Influence",
  "interestLevel": "High Interest",
  "engagementStrategies": "Regular compliance reporting, safety audits, policy consultations",
  "engagementFrequency": "Monthly",
  "communicationChannels": ["Email", "In-Person Meeting", "Reports"],
  "expectations": "Full compliance with safety regulations, timely incident reporting",
  "geographicScope": "National",
  "industry": "Government",
  "organizationType": "Government Agency",
  "riskCategories": ["Compliance/Regulatory", "Reputational"],
  "strategicAlignment": "Critical for maintaining operating licenses and safety compliance"
}

Example 2: Technology Partner

{
  "title": "Railway Technology Solutions Ltd",
  "tType": "Strategic Partner",
  "description": "Technology company providing AI-powered track monitoring solutions",
  "role": "Develop and maintain predictive maintenance technology systems",
  "stakeholderCategory": "External Stakeholder",
  "influenceLevel": "Medium Influence",
  "interestLevel": "High Interest",
  "engagementStrategies": "Joint product development, regular technical reviews, innovation workshops",
  "engagementFrequency": "Weekly",
  "communicationChannels": ["Video Conference", "Digital Platform", "Workshops"],
  "inputs": "Technical expertise, software development, system integration",
  "outputs": "Licensing fees, partnership opportunities, market access",
  "geographicScope": "International",
  "industry": "Technology",
  "organizationType": "Private Company",
  "strategicAlignment": "Enables digital transformation and predictive maintenance capabilities"
}

Example 3: Local Community Group

{
  "title": "Downtown Residents Association",
  "tType": "Community Representative",
  "description": "Local community group representing residents near railway operations",
  "role": "Advocate for community safety and noise reduction concerns",
  "stakeholderCategory": "External Stakeholder",
  "influenceLevel": "Low Influence",
  "interestLevel": "High Interest",
  "engagementStrategies": "Community meetings, public consultations, safety briefings",
  "engagementFrequency": "Quarterly",
  "communicationChannels": ["In-Person Meeting", "Newsletter", "Website"],
  "expectations": "Minimal noise disruption, advance notice of maintenance activities",
  "geographicScope": "Local",
  "industry": "Non-Profit",
  "organizationType": "Community Group",
  "riskCategories": ["Reputational", "Operational"],
  "stakeholderRequirements": [
    {
      "title": "Noise Level Compliance",
      "description": "Maintain railway noise levels within city ordinance limits",
      "purpose": "Ensure community quality of life standards",
      "priority": "Medium",
      "requirementType": "Compliance",
      "acceptanceCriteria": "Noise levels below 65dB during nighttime hours",
      "complianceFramework": "Government Regulation",
      "riskLevel": "Medium Risk"
    }
  ]
}

Implementation Guidelines

Global Deployment Considerations

1. Cultural Adaptation: Select appropriate stakeholder types and engagement strategies for local contexts
2. Regulatory Alignment: Choose relevant compliance frameworks based on jurisdiction
3. Communication Preferences: Include culturally appropriate communication channels
4. Industry Specificity: Use industry-relevant stakeholder categories and requirements
5. Risk Assessment: Adapt risk categories to local business and regulatory environment

Data Quality Best Practices

1. Stakeholder Mapping: Systematically identify and categorize all stakeholders
2. Engagement Planning: Define clear engagement strategies and frequencies
3. Requirement Tracking: Document and track stakeholder requirements comprehensively
4. Relationship Management: Maintain current stakeholder contact and relationship data
5. Performance Monitoring: Track stakeholder satisfaction and engagement effectiveness

OpenMetadata Integration

For Data Platform Teams

When integrating with OpenMetadata, map Stakeholder entities as follows:

Orthogramic Element	OpenMetadata Entity	Notes
Stakeholder (Internal)	User	Map to user profiles
Stakeholder (External)	Team (External)	External stakeholder groups
Owner role	Owner	Data ownership assignment
Requirements	Custom Properties	Track on data assets
Engagement Strategies	Description/Tags	Document in asset metadata

# Example: Map stakeholder to OpenMetadata owner
def map_stakeholder_to_owner(stakeholder):
    if stakeholder["stakeholderCategory"] == "Internal Stakeholder":
        return {
            "type": "user",
            "id": stakeholder["title"].lower().replace(" ", "_"),
            "displayName": stakeholder["title"],
            "email": f"{stakeholder['title'].lower().replace(' ', '.')}@company.com"
        }
    else:
        return {
            "type": "team",
            "id": f"external_{stakeholder['title'].lower().replace(' ', '_')}",
            "displayName": stakeholder["title"],
            "teamType": "Group"
        }

Schema Reference

• Repository: Orthogramic/Orthogramic_Metamodel
• Schema Location: /schemas/stakeholder.schema.json
• Version: 2.1
• Specification: JSON Schema Draft-07
• License: Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0)

---

Previous: Organization Domain | Next: Capabilities Domain