Phase 02
Stakeholders, discovery and accountability
Identify who experiences, operates, governs and approves the service so requirements and controls reflect the full system.
Inspect the evidence
Case workers, supervisors, technology, executive sponsor
Program policy, privacy and security
Applicants, intake clerks, accessibility advisor, data team
Community partners
Selected RACI decisions
| Decision | Responsible | Accountable |
|---|---|---|
| Validate AS-IS | Business Analyst | Operations |
| Approve business rules | Business Analyst | Program Policy |
| Approve requirements | Business Analyst | Sponsor |
| Approve privacy/accessibility controls | Technology | Privacy / Accessibility |
| Own data definitions | Business Analyst | Data Team |
| Execute simulated UAT | Business Analyst | Operations |
| Go / no-go | Operations + Technology | Sponsor |
Listen
- Applicant interview
- Assisted-intake observation
Understand
- Caseworker and supervisor interview
- Technology and data interview
Align
- Cross-functional workshop
- Decision and assumption log
My analysis and method Why this phase matters
Stakeholder analysis protects the project from designing only for the loudest group. RACI makes approval and delivery accountability explicit.
Capability demonstrated
What this work shows
Assessed influence, impact, interest, stance and engagement needs.
Used interviews, observation and cross-functional workshops to test hypotheses.
Distinguished responsible delivery roles from accountable decision owners.
Fictional municipal scenario, synthetic data, simulated discovery and validation. No City of Toronto affiliation or claimed production outcome.