🦆
D.U.C.K. - Knowledge Base
  • D.U.C.K. Knowledge Base
    • 🦆Introduction
    • 🤝Contributors
    • 🎯Journey ahead
    • ℹ️Structure Overview
  • Risk Framework
    • ℹ️Risk Framework
    • Risks
      • Slashing (SLS)
      • Downtime (DOW)
      • Key Compromises (KEC)
      • General Infrastructure (GIR)
      • Service Partner Specifics (SPS)
      • Reputation (RER)
    • Risk Management Procedures
    • Risk Assessment Procedures
    • Review & Audit Procedures
    • Templates
      • Risk Register
      • Incident Response Plan
  • Mitigation & Controls Library
    • ℹ️Mitigation & Controls Library
    • Mitigation Strategies
    • Controls Catalog & Best Practices
    • Implementation Guidelines
    • Collection of Tools, Scripts & Templates
  • Communications Toolkit
    • ℹ️Communication Toolkit
    • Stakeholder Strategy
      • Stakeholder Overview
      • Ecosystem Touchpoints
      • Stakeholder Management
    • Incident Communication Protocols
    • Templates & Toolkits
      • Stakeholder Map
      • Stakeholder Register
      • Post-Mortem Analysis
      • Tools
    • Ecosystem Blueprint
      • Large Node Operator
Powered by GitBook
On this page
  • General Procedures
  • Stakeholder Map
  • Manage Closely
  • Keep Satisfied
  • Keep Informed
  • Monitor
  • Stakeholder Register

Was this helpful?

Edit on GitHub
  1. Communications Toolkit
  2. Stakeholder Strategy

Stakeholder Management

PreviousEcosystem TouchpointsNextIncident Communication Protocols

Last updated 1 year ago

Was this helpful?

General Procedures

The following procedures shall ensure appropriate consideration and management of relevant stakeholders:

  1. Define all stakeholders that are relevant to your organization (Reference: Stakeholder Overview)

  2. Define and align communciation channels that you intend to use for engagement with your stakeholders (Reference: Ecosystem Touchpoints)

  3. Perform a stakeholder mapping and define your individual ways of engagement with the different stakeholder groups (Reference: Stakeholder Map)

  4. Document all defined stakeholders with the respective management measures in the stakeholder register (Reference: Stakeholder Register). Also take best practices covering incident communication into account (Reference: Incident Communication Protocols).

  5. Define appropriate intervals to review accuracy and relevance of documented contents in the stakeholder register

Stakeholder Map

The Stakeholder Map provides guidance when categorizing the individual stakeholders into different communication groups. It can be used as an initial assessment for further review and adaption to your individual stakeholder landscape.

Only use the Communication Map below as a reference! Review each your stakeholder individually and assess needed means of contact! You can find the template here: Stakeholder Map

Manage Closely

  • Establish direct communication channels (e.g., Telegram, Slack or similar)

  • Individual status reporting and communications

  • Perform immediate alignment in case of incidents

Keep Satisfied

  • Establish public communication channels (e.g., Telegram, Discord, X)

  • Regular status reporting and engagement

  • Provide summary and updates in case of incidents

Keep Informed

  • Establish direct or public communication channels depending on need for responsiveness (e.g., Mail, Discord, Telegram, Slack, X)

  • Provide summary and updates in case of incidents

Monitor

  • Monitor activities and react to activities and requests

Stakeholder Register

The Stakeholder Register is a key management document, listing all stakeholders with details about their roles, interests, and impact on the organization. It is essential for understanding and managing stakeholders, ensuring tailored and effective communication.

You can download the spreadsheet here:

https://docs.google.com/spreadsheets/d/1ovBZbYhR5c-l83F4KKgNKam8igAKPASS/edit?usp=sharing&ouid=117284374075970906179&rtpof=true&sd=true
Stakeholder Register
Stakeholder Map