Stakeholder Map

Purpose

Stakeholder and decision-rights map for roles, interests, influence, engagement, RACI ownership, communication cadence, and escalation paths.

Example

Show a worked example of this artifact

---
ddx:
  id: example.stakeholder-map.depositmatch
  depends_on:
    - example.opportunity-canvas.depositmatch
    - example.compliance-requirements.depositmatch
    - example.risk-register.depositmatch
  review:
    self_hash: 7a1136a9797454fae7cd398a1eeded819f907aae48866461d6640c2bdcae892c
    deps:
      example.compliance-requirements.depositmatch: ec7fb87a927f7e53a9c323e9af8ee73d667e4520ab596c130077d332d2783c9f
      example.opportunity-canvas.depositmatch: 75303097bfeeed0272bd68f90ef887f9a5e646a1272f9a57ccd0d899ae17497a
      example.risk-register.depositmatch: 4cfb9a77765bfa4a63e8ad9d98a656bb5c9b9bfb5c5569389cb8cf73e8c1c3ba
    reviewed_at: "2026-05-15T04:11:24Z"
---

# Stakeholder Map

**Status**: Review
**Last Updated**: 2026-05-12

## Primary Stakeholders (High Influence, High Interest)

### Product Lead

- **Role**: Owns pilot scope, customer validation, and PRD readiness.
- **Interest**: Proving the core reconciliation workflow without expanding v1.
- **Influence**: High
- **Concerns**: Scope creep into bank feeds, ledger writeback, or broad
  accounting replacement.
- **Success Criteria**: PRD scope maps to pilot evidence and measurable success
  metrics.
- **Communication**: Weekly pilot readiness review.
- **Contact Channel**: Product review meeting / product planning issue.

### Engineering Lead

- **Role**: Owns technical feasibility, security requirements, and delivery
  design.
- **Interest**: Keeping CSV import, matching, and audit logs buildable in the
  three-month pilot.
- **Influence**: High
- **Concerns**: CSV variability, cross-firm data isolation, and support access
  controls.
- **Success Criteria**: P0 features can be designed and tested without hidden
  integration dependencies.
- **Communication**: Weekly design/risk review.
- **Contact Channel**: Engineering planning issue / architecture review.

### Compliance Officer / Legal Counsel

- **Role**: Owns regulatory applicability review and data-handling constraints.
- **Interest**: Confirming whether FTC Safeguards, state privacy, or contractual
  duties affect live-data pilot scope.
- **Influence**: High
- **Concerns**: Live financial data uploaded before controls and agreements are
  approved.
- **Success Criteria**: Compliance Requirements gaps closed before pilot
  onboarding.
- **Communication**: Counsel-review checkpoint before live-data pilot.
- **Contact Channel**: Compliance review issue / counsel checkpoint.

### Pilot Firm Reconciliation Lead

- **Role**: Primary user and evidence source for workflow validation.
- **Interest**: Reducing weekly reconciliation time without losing reviewer
  control.
- **Influence**: High for product fit; low for internal budget.
- **Concerns**: Match evidence, exception ownership, CSV setup burden, and
  auditability.
- **Success Criteria**: Weekly reconciliation below 3 minutes per client with
  trusted suggestions.
- **Communication**: Research interview, pilot onboarding, weekly feedback.
- **Contact Channel**: Pilot feedback session / customer interview notes.

## Secondary Stakeholders (Variable Influence/Interest)

### Operations Lead

- **Role**: Owns pilot support process and onboarding load.
- **Interest**: Keeping CSV mapping and support access manageable.
- **Influence**: Medium
- **Engagement Level**: Consult
- **Contact Channel**: Pilot operations review.

### Sponsor / Finance Lead

- **Role**: Owns investment continuation and pilot budget.
- **Interest**: Business Case confidence, willingness to pay, and cost to
  support.
- **Influence**: High
- **Engagement Level**: Inform / Consult at gates
- **Contact Channel**: Monthly sponsor review.

### Security Champion

- **Role**: Reviews security requirements, threat model, and security tests.
- **Interest**: Preventing cross-firm exposure and sensitive-data leakage.
- **Influence**: Medium
- **Engagement Level**: Collaborate on security artifacts
- **Contact Channel**: Security review issue.

## RACI Matrix

| Activity/Decision | Product Lead | Engineering Lead | Compliance/Legal | Pilot Firm Lead | Sponsor |
|-------------------|--------------|------------------|------------------|-----------------|---------|
| PRD scope approval | A | R | C | C | I |
| CSV import feasibility | C | A/R | I | C | I |
| Live-data pilot approval | C | R | A | I | I |
| Pilot success metrics | A/R | C | C | C | I |
| Budget continuation | R | C | C | I | A |
| Release readiness | A | R | C | I | I |

**R** = Responsible | **A** = Accountable | **C** = Consulted | **I** = Informed

## Power/Interest Grid

```
High Power  | Keep Satisfied      | Manage Closely
            | - Sponsor           | - Product Lead
            |                     | - Engineering Lead
            |                     | - Compliance/Legal
            |---------------------|-------------------
Low Power   | Monitor             | Keep Informed
            | - Support Ops       | - Pilot Firm Leads
            |                     | - Security Champion
            Low Interest          High Interest
```

## Communication Plan

| Stakeholder Group | Channel | Frequency | Content | Owner |
|-------------------|---------|-----------|---------|-------|
| Product + Engineering | Pilot readiness review | Weekly | Scope, risks, import findings, security work | Product Lead |
| Compliance/Legal | Counsel checkpoint | Before live-data pilot, then as needed | Applicability gaps, data handling, vendor review | Compliance Officer |
| Pilot Firm Leads | Interview / pilot feedback session | During research and weekly pilot | Workflow pain, CSV samples, time saved, trust concerns | Product Lead |
| Sponsor / Finance | Sponsor review | Monthly or gate-based | Business Case confidence, pricing signal, pilot cost | Product Lead |

### Escalation Path

1. Artifact owner resolves routine disagreements.
2. Product Lead decides scope tradeoffs within approved pilot boundaries.
3. Compliance/Legal has stop authority for live-data use.
4. Sponsor decides funding continuation or project stop when risk exceeds pilot
   appetite.

Reference

Activity	Frame — Define what the system should do, for whom, and how success will be measured.
Default location	`docs/helix/01-frame/stakeholder-map.md`
Requires	None
Enables	None
Informs	PRD Risk Register
Generation prompt	Show the full generation prompt # Stakeholder Map Generation Prompt Map the stakeholders who matter most to the project and how to engage them. ## Reference Anchors Use this local resource summary as grounding: - `docs/resources/atlassian-raci-chart.md` grounds responsibility assignment, accountability, consultation, and informed stakeholders. ## Focus - Identify primary and secondary stakeholders. - Keep influence, interest, and communication needs clear. - Note escalation paths without overexplaining them. - Use roles when names or contact details are unknown. Do not invent people or emails. ## Role Boundary Stakeholder Map is not a communication log or org chart. It names who has influence, who needs input or updates, who is accountable for decisions, and where unresolved decisions escalate. ## Completion Criteria - Stakeholders are named and categorized. - Communication is actionable. - The map stays compact. - Every critical decision has exactly one accountable role in the RACI matrix.
Template	Show the template structure --- ddx: id: stakeholder-map --- # Stakeholder Map Status: [Draft \| Review \| Approved] Last Updated: [Date] ## Primary Stakeholders (High Influence, High Interest) ### [Stakeholder Name/Role] - Role: [Position/title] - Interest: [What they care about] - Influence: [Power to affect project] - Concerns: [Main worries] - Success Criteria: [What success looks like to them] - Communication: [Preferred engagement method] - Contact Channel: [Slack group / meeting / ticket queue / role alias] ## Secondary Stakeholders (Variable Influence/Interest) ### [Stakeholder Name/Role] - Role: - Interest: - Influence: - Engagement Level: [Inform \| Consult \| Collaborate] - Contact Channel: ## RACI Matrix \| Activity/Decision \| [Stakeholder 1] \| [Stakeholder 2] \| [Stakeholder 3] \| \|-------------------\|-----------------\|-----------------\|-----------------\| \| Project Vision \| A \| R \| C \| \| Requirements \| A \| R \| C \| \| Technical Decisions \| I \| C \| R/A \| \| Budget Approval \| A \| C \| I \| \| Release Decision \| A \| R \| C \| R = Responsible \| A = Accountable \| C = Consulted \| I = Informed ## Power/Interest Grid ``` High Power \| Keep Satisfied \| Manage Closely \| - [Stakeholder] \| - [Stakeholder] \|---------------------\|------------------- Low Power \| Monitor \| Keep Informed \| - [Stakeholder] \| - [Stakeholder] Low Interest High Interest ``` ## Communication Plan \| Stakeholder Group \| Channel \| Frequency \| Content \| Owner \| \|-------------------\|---------\|-----------\|---------\|-------\| \| [Group] \| [Channel] \| [Frequency] \| [What] \| [Who] \| ### Escalation Path 1. [Team Lead] -> [PM] -> [Sponsor] -> [Executive]