/stakeholders

IPAD Stakeholder Analysis

User Input

$ARGUMENTS

Prerequisites

Recommends: An ASSESS artifact (IPAD-{PID}-ASSESS-*.md) in the target project. The stakeholder analysis is enriched by assessment context (understanding the IPA's maturity level helps calibrate stakeholder data needs and engagement expectations), but it is not strictly required.

Instructions

Note: The IPAD Kit Project Context hook has already detected all projects, artifacts, and external documents. Use that context below.

Step 1: Identify Project

1. Parse $ARGUMENTS for a project ID (e.g., 001) or IPA name.
2. Check the project context (injected by the hook) for an existing project matching the input.
3. If a matching project exists:
   • Check if it already contains a stakeholder artifact (IPAD-{PID}-STKE-*.md).
   • If a stakeholder analysis already exists, inform the user and ask whether to create a new version or update the existing one.
4. If no matching project exists:
   • Create a new project directory under projects/ using the next available project number.
5. Record the resolved PROJECT_ID, PROJECT_NAME, and PROJECT_DIR.
6. If an assessment artifact exists in the project, read it to extract the IPA profile, maturity level, and key findings — these will inform the stakeholder analysis.

Step 2: Load Template

1. Check for a local template override at .ipad/templates/stakeholders-template.md.
2. If the local override exists, read it and use it as the output template.
3. If no local override exists, read the default template from ${CLAUDE_PLUGIN_ROOT}/templates/stakeholders-template.md.
4. If neither template is found, proceed using the built-in structure defined in these instructions.

Step 3: Load Reference Data

Read the following reference data files to inform the stakeholder analysis with IPA domain knowledge:

1. Business Domains: ${CLAUDE_PLUGIN_ROOT}/references/framework/investment-lifecycle/domains.md — the 5 IPAD business domains (Investment Climate, Investor Targeting, Investment Facilitation, Expansion & After-Care, Policy & Advocacy) and their associated entities. This helps map stakeholders to the data domains they interact with.
2. Promotion Lifecycle: ${CLAUDE_PLUGIN_ROOT}/references/framework/investment-lifecycle/promotion-lifecycle.md — the end-to-end investment promotion lifecycle phases (Image Building, Investor Targeting, Investment Facilitation, Aftercare & Expansion, Policy Advocacy). This maps stakeholder engagement to lifecycle stages.
3. Investment Growth Funnel: ${CLAUDE_PLUGIN_ROOT}/references/framework/investment-lifecycle/investment-growth-funnel.md — the funnel model (Outreach → Lead → Order → Delivery → Revenue → Loyalty) showing where stakeholders interact with the investment pipeline.
4. Governance Roles: ${CLAUDE_PLUGIN_ROOT}/references/framework/governance/roles-and-responsibilities.md — data governance roles and responsibilities that map to stakeholder tiers.
5. CDA Model: ${CLAUDE_PLUGIN_ROOT}/references/framework/governance/cda-model.md — the Create-Distribute-Act governance model for data stewardship.

Step 4: Read External Documents

1. Scan projects/000-global/external/ and projects/{PROJECT_DIR}/external/ for reference documents.
2. Look specifically for:
   • IPA organisation charts and mandate documents
   • Government structure documents showing the IPA's position in the public administration hierarchy
   • Partnership agreements or MoUs with other agencies
   • Annual reports listing key stakeholder interactions
   • Investor survey results or satisfaction reports
   • Strategy documents identifying target markets or priority sectors
3. Extract stakeholder information from these documents to pre-populate the analysis.

Step 5: Analyse Stakeholders Across 5 IPA-Specific Tiers

Conduct a structured stakeholder analysis across 5 tiers. For each tier, identify specific stakeholders and document their characteristics. Engage the user interactively to gather information about their specific stakeholder landscape.

Tier 1: Leadership & Governance

Description: Senior decision-makers who set strategy, approve budgets, and are accountable for IPA performance.

Typical stakeholders:

• Minister or Secretary of State responsible for investment
• IPA CEO / Director-General / Chairman
• Board of Directors or Governing Council
• Government sponsor (e.g., Prime Minister's Office, Ministry of Finance, Ministry of Economy)
• National investment council or advisory board

For each stakeholder, document:

• Name / Role / Organisation
• Power level (High/Medium/Low) — ability to influence IPA strategy and resources
• Interest level (High/Medium/Low) — degree of active engagement with data and analytics
• Key drivers: What motivates this stakeholder? (e.g., economic growth targets, job creation KPIs, political visibility)
• Data needs: What information does this stakeholder require? (e.g., FDI pipeline reports, economic impact dashboards, ROI metrics)
• IPAD framework touchpoints: Which business domains (D1-D5) and data layers (L1-L8) are relevant?
• Engagement frequency: Daily / Weekly / Monthly / Quarterly / Annual
• Current satisfaction: High / Medium / Low (if assessable)

Tier 2: Partners & Collaborators

Description: External organisations that collaborate with the IPA on investment promotion, share data, or co-deliver services.

Typical stakeholders:

• Other government agencies (trade, commerce, labour, immigration, customs, statistics)
• Trade promotion organisations (TPOs)
• Embassies and commercial attaches
• International organisations (WAIPA, UNCTAD, World Bank Group, OECD, regional bodies)
• Bilateral development agencies (USAID, GIZ, JICA, etc.)
• Chambers of commerce and business associations
• Academic and research institutions

For each stakeholder, document: (same fields as Tier 1, plus)

• Data sharing relationship: Provider / Consumer / Bidirectional
• Data exchange mechanism: Manual / Batch / API / Real-time
• Data shared: What specific datasets or reports are exchanged?
• Integration maturity: Ad-hoc / Structured / Automated

Tier 3: Entities & Zones

Description: Special economic zones, free zones, industrial estates, and development authorities that operate within or alongside the IPA's jurisdiction.

Typical stakeholders:

• Special Economic Zones (SEZs) / Free Trade Zones (FTZs)
• Industrial parks and technology parks
• Regional development authorities
• Export processing zones
• Innovation hubs and incubators
• State/provincial investment agencies (for national IPAs)

For each stakeholder, document: (same fields as Tier 1, plus)

• Jurisdictional relationship: Subsidiary / Partner / Independent
• Investor data overlap: How much of the IPA's investor pipeline flows through this entity?
• Data coordination: Shared systems / Separate systems / No coordination
• Relevant IPAD entities: Which entity types (E-001 through E-049) does this stakeholder produce or consume?

Tier 4: IPA Internal Teams

Description: Internal departments and teams within the IPA that produce, consume, and act on investment data.

Typical stakeholders:

• Investment Services / Facilitation team
• Marketing & Promotion team
• Research & Market Intelligence team
• Aftercare / Investor Relations team
• IT / Digital Transformation team
• Legal & Compliance team
• Finance & Administration team
• Human Resources team
• Policy & Advocacy team
• Regional / Sector desk officers

For each stakeholder, document: (same fields as Tier 1, plus)

• Data role: Producer / Consumer / Steward / All
• Systems used: Which IT systems does this team use daily?
• Data literacy level: Basic / Intermediate / Advanced
• Pain points: What data-related challenges does this team face?
• Self-service capability: Can they access and analyse data independently?
• Relevant lifecycle phase: Which promotion lifecycle phase(s) does this team operate in?

Tier 5: Investors & Clients

Description: External clients of the IPA — prospective investors, established investors, and intermediaries who interact with the IPA's services.

Typical stakeholders:

• Prospective investors (new FDI leads)
• Established investors (existing FDI with aftercare relationships)
• Site selection consultants
• Law firms and advisory firms (representing investors)
• Accounting / tax advisory firms
• Industry associations representing investor communities
• Diaspora investor networks

For each stakeholder, document: (same fields as Tier 1, plus)

• Investor lifecycle stage: Prospect / Lead / Active Project / Established / Expansion
• Data provided TO the IPA: What information do they provide? (applications, surveys, reports)
• Data received FROM the IPA: What information do they need? (market data, incentives, regulations)
• Service channel: In-person / Portal / Email / API
• Satisfaction data: Any survey or feedback data available?

Step 6: Create Power-Interest Grid

Based on the stakeholder analysis, create a Power-Interest grid that maps all identified stakeholders:

                        HIGH INTEREST
                            │
        ┌───────────────────┼───────────────────┐
        │                   │                   │
        │   KEEP SATISFIED  │  MANAGE CLOSELY   │
        │                   │                   │
  HIGH  │  • Board members  │  • Minister       │
 POWER  │  • Finance Min.   │  • CEO/DG         │
        │                   │  • Key partners   │
        ├───────────────────┼───────────────────┤
        │                   │                   │
        │   MONITOR         │  KEEP INFORMED    │
        │                   │                   │
  LOW   │  • Regulators     │  • Internal teams │
 POWER  │  • Int'l orgs     │  • Investors      │
        │                   │  • Intermediaries  │
        └───────────────────┼───────────────────┘
                            │
                       LOW INTEREST

Populate the grid with the actual stakeholders identified in Steps 5.1-5.5.

Step 7: Create Engagement Plan

For each quadrant of the Power-Interest grid, define the engagement strategy:

1. Manage Closely (High Power, High Interest): Regular executive briefings, co-design sessions, dashboard access, steering committee membership.
2. Keep Satisfied (High Power, Low Interest): Quarterly summary reports, escalation pathways, annual strategy reviews.
3. Keep Informed (Low Power, High Interest): Regular newsletters, training sessions, self-service data access, feedback channels.
4. Monitor (Low Power, Low Interest): Annual updates, standard reporting, ad-hoc engagement as needed.

For each stakeholder, recommend a specific engagement cadence, channel, and key messages related to the IPAD framework.

Step 8: Create RACI Matrix

Produce a RACI (Responsible, Accountable, Consulted, Informed) matrix for key IPAD framework activities:

| Activity | CEO/DG | CIO/CDO | Dept Heads | Data Owners | IT Team | Partners |
|----------|--------|---------|------------|-------------|---------|----------|
| Data Strategy | A | R | C | C | I | I |
| Data Quality | I | A | C | R | C | I |
| Analytics | I | A | R | C | R | I |
| Governance | A | R | C | R | C | I |
| Data Sharing | C | A | C | R | R | R |
| Training | I | A | R | C | C | I |

Map RACI assignments based on the stakeholders identified and the IPA's organisational structure. If an assessment exists, calibrate the RACI to the current and target maturity levels.

Step 9: IPAD Framework Touchpoint Summary

Create a summary table mapping each stakeholder tier to IPAD framework elements:

| Tier | Business Domains | Data Layers | Key Entities | Lifecycle Phases |
|------|-----------------|-------------|-------------|-----------------|
| T1: Leadership | D1-D5 (all) | L7-L8 | E-042, E-043 | All (strategic) |
| T2: Partners | D1, D4, D5 | L1-L2, L4 | E-001-E-009 | Phase 1, 4, 5 |
| T3: Entities | D3, D4 | L2, L4 | E-015, E-028-E-032 | Phase 3, 4 |
| T4: Teams | D1-D5 (varies) | L2-L6 | All (varies) | All (operational) |
| T5: Investors | D2, D3, D4 | L8 | E-021-E-035 | Phase 2, 3, 4 |

Step 10: Write Output Artifact

1. Generate the stakeholder analysis document using the template structure.
2. Write the output to: projects/{PROJECT_DIR}/IPAD-{PROJECT_ID}-STKE-v1.0.md
3. If a previous version exists, increment the version number.

IMPORTANT — Auto-Populate Document Information Fields: When writing the output artifact, automatically populate these fields without asking the user:

• Document ID: IPAD-{PROJECT_ID}-STKE-v{VERSION} (e.g., IPAD-001-STKE-v1.0)
• Project ID: The resolved project number
• Version: 1.0 for the initial stakeholder analysis, incremented for updates
• Date: Today's date in ISO format (YYYY-MM-DD)
• Status: DRAFT
• IPA Name: From the project context or user input
• Stakeholder Count: Total number of stakeholders identified across all tiers
• Based On: Reference to the assessment artifact if one was used (e.g., IPAD-001-ASSESS-v1.0)

Generation Metadata Footer:

---

**Generated by**: IPAD Kit `/ipad-kit:stakeholders` command
**Generated on**: {DATE}
**IPAD Kit Version**: {IPAD_KIT_VERSION}
**Project**: {PROJECT_NAME} (Project {PROJECT_ID})

Step 11: Suggest Next Steps

After writing the artifact, inform the user of recommended follow-on commands:

1. /ipad-kit:funnel {PROJECT_ID} — Map data requirements to the Investment Growth Funnel, informed by stakeholder needs at each tier.
2. /ipad-kit:roadmap {PROJECT_ID} — Generate an improvement roadmap that includes a stakeholder buy-in and change management strategy.
3. /ipad-kit:governance {PROJECT_ID} — Define the data governance framework with roles and responsibilities mapped to identified stakeholders.
4. /ipad-kit:assess {PROJECT_ID} — If not yet done, conduct a maturity assessment to calibrate stakeholder expectations to the IPA's current capability.