Guide Origin: Official | ArcKit Version: [VERSION]
/arckit:stakeholders analyzes stakeholder drivers, goals, and measurable outcomes to establish project foundation.
Heading into a gate, a procurement or a board? ArcKit FDE puts a senior architect in your team for five days to produce your principles, requirements, risk register and stakeholder map, at a fixed price. See how ArcKit FDE works.
| Artefact |
Purpose |
| Project brief |
Initial context and objectives |
| Organization charts |
Identify key stakeholders |
| Existing documentation |
Current state understanding |
| Interview notes |
Stakeholder perspectives |
Command
/arckit:stakeholders Analyze stakeholders for <project>
Output: projects/<id>/ARC-<id>-STKE-v1.0.md
Stakeholder Analysis Structure
| Section |
Contents |
| Stakeholder Catalog |
List of all stakeholders with roles |
| Stakeholder Profiles |
Detailed profile per stakeholder |
| Drivers & Concerns |
What motivates and worries each group |
| Goals & Outcomes |
What success looks like |
| Power/Interest Grid |
Prioritization matrix |
| Communication Plan |
Engagement approach per stakeholder |
| RACI Matrix |
Responsibility assignment |
| Field |
Description |
| Name/Role |
Who they are |
| Organization |
Where they sit |
| Interest |
What they care about |
| Influence |
Power to affect project |
| Drivers |
What motivates them |
| Concerns |
What worries them |
| Goals |
What they want to achieve |
| Success Metrics |
How they measure success |
Power/Interest Grid
|
Low Interest |
High Interest |
| High Power |
Keep Satisfied |
Manage Closely |
| Low Power |
Monitor |
Keep Informed |
RACI Matrix
| Role |
Description |
| Responsible |
Does the work |
| Accountable |
Ultimately answerable (one per task) |
| Consulted |
Input required before decision |
| Informed |
Notified after decision |
One-Page Workflow
| Phase |
Key Activities |
ArcKit Commands |
| Discovery |
Identify and analyze stakeholders |
/arckit:stakeholders |
| Requirements |
Capture requirements from stakeholders |
/arckit:requirements |
| Planning |
Plan based on stakeholder needs |
/arckit:sobc, /arckit:plan |
| Execution |
Regular stakeholder engagement |
Governance meetings |
| Closure |
Validate outcomes with stakeholders |
/arckit:story |
Review Checklist
- All relevant stakeholders identified.
- Each stakeholder has documented drivers and concerns.
- Goals are specific and measurable.
- Power/interest mapping completed.
- RACI matrix covers key decisions.
- Communication plan appropriate for each group.
- Conflicting interests identified and addressed.
- Executive sponsor clearly identified.
Common Stakeholder Types
| Type |
Typical Concerns |
| Executive Sponsor |
Budget, timeline, business value |
| Product Owner |
Features, user needs, prioritization |
| Technical Lead |
Architecture, quality, feasibility |
| Operations |
Supportability, reliability, handover |
| Security |
Risk, compliance, data protection |
| Users |
Usability, training, change impact |
| Finance |
Cost, ROI, budget approval |
UK Government Digital Roles (GovS 005)
For UK Government projects, also consider the mandatory digital governance roles defined by GovS 005:
| Role |
Typical Concerns |
| SRO (Senior Responsible Owner) |
Accountability, spend control, outcomes |
| Service Owner |
End-to-end service quality, user satisfaction |
| Product Manager |
Feature prioritisation, user needs, policy alignment |
| Delivery Manager |
Delivery cadence, risks, dependencies |
| CDDO |
Spend control thresholds, cross-government standards |
| CDIO |
Departmental digital strategy, technology oversight |
| DDaT Profession Lead |
Capability framework, recruitment, career paths |
Key Principles
- Early Engagement: Identify stakeholders before requirements.
- Active Listening: Understand concerns, not just stated needs.
- Balanced Representation: Don't let loudest voice dominate.
- Clear Accountability: One accountable person per decision.
- Continuous Engagement: Stakeholder management is ongoing.