返回 Papers
AI 扩展计划 / Playbooks

ABPA 模板 02:Stakeholder Evidence Map

Questions:

108abpa/templates/02-stakeholder-evidence-map.md

Stakeholder Evidence Map

Use this to avoid building for a fake average user. Each stakeholder needs a different evidence path.

1. Stakeholder Summary

StakeholderRole in workflowDecision powerSuccess definitionMain concernEvidence needed
Frontline userhigh / medium / low
Team leadhigh / medium / low
Compliance / riskhigh / medium / low
Data ownerhigh / medium / low
IT / platformhigh / medium / low
Securityhigh / medium / low
Legal / privacyhigh / medium / low
Executive sponsorhigh / medium / low

2. Interview Cards

Frontline User

FieldAnswer
What they do today
What slows them down
What they distrust
What they must control
What would make them adopt
What would make them reject

Questions:

Compliance / Risk

FieldAnswer
Regulatory responsibility
Evidence required
Non-negotiable controls
Review cadence
Incident escalation

Questions:

Technology / Data

FieldAnswer
Systems involved
Integration constraints
Data quality known issues
Access / identity constraints
Operational support constraints

Questions:

Executive Sponsor

FieldAnswer
Strategic objective
Funding threshold
Risk appetite
Time horizon
Decision criteria

Questions:

3. Conflict Map

ConflictStakeholdersWhy it mattersResolution path
Efficiency vs control
Automation vs human accountability
Data access vs privacy
Vendor speed vs lock-in
Model quality vs cost

4. Evidence Plan

Claim to validateEvidence sourceMethodOwnerDeadline
interview / log analysis / prototype / eval / pilot