Map stakeholders and decision owners in a small project

Projects stall when everyone is “involved” but nobody can approve scope, access or acceptance. Map decisions, not only job titles.

Inspect three fictional decisions

The delivery lab separates scope, data access and UAT ownership.

from delivery_cases import stakeholder_case

result = stakeholder_case()
assert result["one_accountable_each"] is True
assert result["fde_not_accountable_for_all"] is True
assert len(result["rows"]) == 3
assert result["fictional"] is True

Identify sponsor/value owner, process users, data/system owners, security/legal, platform operations and acceptance owner. For each material decision name one accountable person, the responsible worker, consulted experts and informed groups.

Add influence, impact, availability and preferred communication. Revisit when scope changes. The FDE can facilitate decisions but should not accept the client’s business or data risk on their behalf.

The FDE for Freshers course practises stakeholder trust alongside engineering.

Exercise

Create a decision-owner table for ten capstone decisions. Highlight gaps and simulate one escalation when the accountable owner is unavailable.

Continue learning

This article is part of the FDE career entry and client-delivery practice sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Write a one-page scope with explicit exclusions.
• Continue with Estimate a project when external access is uncertain.

Reference: GOV.UK service assessment roles.