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: 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
stakeholderID	String	Unique identifier for the stakeholder, e.g. STK-001	✓
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
orgUnitID	String	ID of the organization unit (see orgUnitTitle)
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
relatedStakeholderIDs	Array[String]	IDs of related 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

A stakeholder record may not carry fields other than those listed above.

Stakeholder Requirement (stakeholderRequirement)

Attribute	Type	Description	Required
requirementID	String	Unique identifier for the requirement, so other records can reference it
title	String	Name/title of requirement	✓
description	String	Detailed explanation	✓
purpose	String	Intended purpose/benefit	✓
owner	String	Responsible fulfiller
orgUnitTitle	String	Impacted organization units
orgUnitID	String	ID of the organization unit (see orgUnitTitle)
priority	Enum	Requirement priority level (shared priority list)
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 (shared four-point risk scale)

Enumeration Values

Stakeholder Type (tType)

Value	Description	Example
primaryCustomer	Main customer or client	Enterprise software customers
secondaryCustomer	Indirect or secondary customers	End users of customer's products
b2bCustomer	Business-to-business customer	Corporate clients
b2cCustomer	Business-to-consumer customer	Individual consumers
b2gCustomer	Business-to-government customer	Government agencies
internalCustomer	Internal organizational customer	Internal departments
endUser	Final user of product/service	Software application users
regulatoryBody	Government regulatory agency	Federal Railroad Administration
governmentAgency	Government department or agency	Department of Transportation
localAuthority	Local government entity	City transportation department
internationalBody	International organization	United Nations, European Union
standardsOrganization	Standards setting body	ISO, IEEE
strategicPartner	Long-term strategic alliance	Joint venture partners
supplierVendor	Goods or services provider	Equipment manufacturers
distributorChannelPartner	Distribution partner	Retail distribution networks
systemIntegrator	Technology integration partner	IT system integrators
consultantAdvisor	Professional advisory services	Management consultants
financialInstitution	Banking or finance provider	Investment banks
investorShareholder	Financial stakeholder	Equity investors
boardMember	Governance stakeholder	Board of directors
employeeStaff	Internal workforce	Company employees
tradeUnion	Labor organization	Railway workers union
industryAssociation	Professional industry group	Railway industry association
communityRepresentative	Local community voice	Neighborhood associations
environmentalGroup	Environmental advocacy	Environmental protection groups
mediaPress	News and media organizations	Industry publications
academicInstitution	Educational organization	Universities, research institutes
competitor	Market competitor	Competing organizations
other	Any other stakeholder type

Stakeholder Category (stakeholderCategory)

Value	Description	Example
internalStakeholder	Stakeholders within the organization	Employees, management, shareholders
externalStakeholder	Stakeholders outside the organization	Customers, suppliers, regulators
primaryStakeholder	Direct impact on organization success	Key customers, investors
secondaryStakeholder	Indirect influence on organization	Industry associations, media
keyStakeholder	Critical to organization success	Major customers, key suppliers
influentialStakeholder	High influence but varying interest	Government regulators, industry leaders

Influence Level (influenceLevel)

Value	Description	Example
highInfluence	Significant power to affect organization	Major investors, key regulators
mediumInfluence	Moderate power to affect organization	Important customers, suppliers
lowInfluence	Limited power to affect organization	Individual consumers, small vendors

Interest Level (interestLevel)

Value	Description	Example
highInterest	Very interested in organization outcomes	Direct customers, employees
mediumInterest	Moderate interest in organization	Industry partners, community
lowInterest	Limited interest in organization	Distant suppliers, general public

Engagement Frequency (engagementFrequency)

engagementFrequency uses the shared frequency list from common.schema.json.

Value	Description	Example
continuous	Ongoing, always available	Digital platforms, customer support
realTime	As events occur	Incident response partners
hourly	Every hour	Operations control centres
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
semiAnnually	Twice a year	Half-yearly reviews
annually	Once per year	Annual shareholder meetings
eventDriven	Triggered by a defined event	Regulator notification after an incident
onDemand	When the stakeholder requests it	Information requests
adHoc	Irregular, as needed	Consultants, crisis communications

Communication Channels (communicationChannels)

Value	Description
email	Electronic mail communication
phoneCall	Telephone communication
videoConference	Online video meetings
inPersonMeeting	Face-to-face meetings
digitalPlatform	Online platforms or portals
socialMedia	Social media channels
website	Public website communications
newsletter	Regular newsletter communications
reports	Formal reporting documents
surveys	Questionnaires and feedback surveys
workshops	Interactive workshop sessions
conferences	Conferences and industry events
mobileApp	Mobile applications
traditionalMail	Letters and printed mail

Risk Categories (riskCategories)

riskCategories uses the shared risk category list from common.schema.json.

Value	Description	Example
strategic	Strategic planning risks	Misaligned objectives
operational	Day-to-day operational risks	Service delivery issues, process failures
financial	Financial and budget risks	Payment delays, cost overruns
market	Market risks	Loss of customer demand
economic	Economic conditions	Recession affecting a partner
political	Political risks	Change of government policy
compliance	Regulatory compliance risks	Non-compliance penalties
legal	Legal and contractual risks	Contract disputes, legal violations
technology	Technology-related risks	System failures, obsolescence
security	Cybersecurity risks	Breach of a shared system
privacy	Personal data risks	Mishandling of stakeholder data
dataQuality	Data quality risks	Inaccurate data exchanged with a stakeholder
supplyChain	Supply chain risks	Supplier failure
people	Workforce, skills, capacity and labour risks	Industrial action, loss of key contacts
reputational	Reputation and brand risks	Negative publicity, brand damage
relationship	Relationship and communication risks	Relationship breakdown, miscommunication, information gaps
changeManagement	Risks of resistance to change	Stakeholder opposition to a programme
environmental	Natural-environment and climate risks	Community concern over environmental impact
external	Other outside events beyond the organization's control	Market shocks, political instability
other	Any other risk

Requirement Priority (priority)

priority uses the shared priority list.

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 Risk Level (riskLevel)

The risk if a requirement is not met uses the shared four-point risk scale.

Value	Description
low	Minor consequences if not met
medium	Noticeable consequences that can be managed
high	Serious consequences, such as regulatory or contractual breach
critical	Severe consequences that threaten operations or licences

Requirement Type (requirementType)

Value	Description	Example
functional	Specific functionality requirements	System features, capabilities
nonFunctional	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
userExperience	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

{
  "stakeholderID": "STK-001",
  "title": "Federal Railroad Administration",
  "tType": "regulatoryBody",
  "description": "Federal agency responsible for railroad safety oversight",
  "role": "Establish and enforce railroad safety standards and regulations",
  "orgUnitTitle": "Regulatory Compliance Division",
  "stakeholderCategory": "externalStakeholder",
  "influenceLevel": "highInfluence",
  "interestLevel": "highInterest",
  "engagementStrategies": "Regular compliance reporting, safety audits, policy consultations",
  "engagementFrequency": "monthly",
  "communicationChannels": [
    "email",
    "inPersonMeeting",
    "reports"
  ],
  "expectations": "Full compliance with safety regulations, timely incident reporting",
  "geographicScope": "national",
  "industry": "government",
  "organizationType": "governmentAgency",
  "riskCategories": [
    "compliance",
    "reputational"
  ],
  "strategicAlignment": "Critical for maintaining operating licenses and safety compliance"
}

Example 2: Technology Partner

{
  "stakeholderID": "STK-002",
  "title": "Railway Technology Solutions Ltd",
  "tType": "strategicPartner",
  "description": "Technology company providing AI-powered track monitoring solutions",
  "role": "Develop and maintain predictive maintenance technology systems",
  "stakeholderCategory": "externalStakeholder",
  "influenceLevel": "mediumInfluence",
  "interestLevel": "highInterest",
  "engagementStrategies": "Joint product development, regular technical reviews, innovation workshops",
  "engagementFrequency": "weekly",
  "communicationChannels": [
    "videoConference",
    "digitalPlatform",
    "workshops"
  ],
  "inputs": "Technical expertise, software development, system integration",
  "outputs": "Licensing fees, partnership opportunities, market access",
  "geographicScope": "multinational",
  "industry": "technology",
  "organizationType": "privateCompany",
  "strategicAlignment": "Enables digital transformation and predictive maintenance capabilities"
}

Example 3: Local Community Group

{
  "stakeholderID": "STK-003",
  "title": "Downtown Residents Association",
  "tType": "communityRepresentative",
  "description": "Local community group representing residents near railway operations",
  "role": "Advocate for community safety and noise reduction concerns",
  "stakeholderCategory": "externalStakeholder",
  "influenceLevel": "lowInfluence",
  "interestLevel": "highInterest",
  "engagementStrategies": "Community meetings, public consultations, safety briefings",
  "engagementFrequency": "quarterly",
  "communicationChannels": [
    "inPersonMeeting",
    "newsletter",
    "website"
  ],
  "expectations": "Minimal noise disruption, advance notice of maintenance activities",
  "geographicScope": "local",
  "industry": "nonProfit",
  "organizationType": "communityGroup",
  "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": "governmentRegulation",
      "riskLevel": "medium"
    }
  ]
}

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:

Triodian 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.get("stakeholderCategory") == "internalStakeholder":
        return {
            "type": "user",
            "id": stakeholder["stakeholderID"],
            "displayName": stakeholder["title"],
            "email": f"{stakeholder['title'].lower().replace(' ', '.')}@company.com"
        }
    else:
        return {
            "type": "team",
            "id": f"external_{stakeholder['stakeholderID']}",
            "displayName": stakeholder["title"],
            "teamType": "Group"
        }

Schema Reference

• Repository: Triodian/Triodian_Metamodel
• Schema: stakeholder.schema.json
• Specification: JSON Schema Draft-07
• License: Apache License 2.0

---

Previous: Organization Domain | Next: Capabilities Domain