Phase 07

Testing, change and executive recommendation

Validate the proposed design, preserve defect evidence and plan a phased, reversible implementation with clear stop/go gates.

12 / 12simulated scenarios executedRequirements and rule coverage
14 / 14assertions passedAfter correction and retest
3defects correctedCritical, high and medium
0open simulated defectsReal assurance still required

One defect, from failure to retest

One defect, from failure to retest
Test / cycleExpectedActual resultDecision
UAT-006 · Cycle 1Public status excludes internal risk notes.EX-007 / EVD-007: internal risk note was exposed.Fail · DEF-002 Critical
UAT-006 · Cycle 2Only allow-listed status, next action and update time.EX-008 / EVD-008: allow-list passed the simulated retest.Pass in model · formal privacy assessment still required

Historical simulation executed 1 September 2026. Seeded defects demonstrate correction and retest; these are not production incidents or acceptance of the current public website.

Defects preserved as evidence

Defects preserved as evidence
IDSeverityObserved findingOutcome
DEF-001MediumConditional document rule omitted declared circumstanceClosed after retest
DEF-002CriticalInternal note appeared in applicant-facing statusClosed after retest
DEF-003HighNotification retry created duplicate deliveryClosed after retest
0
4 weeksMobilize & validate

Confirm sponsor, scope, discovery, controls and pilot cohort.

1
10–14 weeksQuality at entry

Guided intake, validation, one case ID, routing and audit events.

2
8–12 weeksVisibility & management

Safe status, communications, alerts, reporting and workload views.

3
ControlledPilot & scale

Compare baseline, benefits, guardrails, workload and unintended effects.

Go-live gates

  • Requirements and rules approved
  • Privacy, accessibility and security approval
  • Data reconciliation and recovery passed
  • Training, support and rollback ready

Do not automate

  • Unreviewable final eligibility decisions
  • Removal of assisted service routes
  • Exposure of internal notes or risk flags
  • Benefit claims before pilot evidence
Executive recommendation

Run one program/team pilot with controlled volume. Scale only when service, equity, privacy, accessibility, defect and operational-readiness evidence supports the decision.

My analysis and method Why this phase matters

A portfolio solution is not complete because the diagram looks convincing. Testing, risk, change and governance determine whether a pilot is safe.

Capability demonstrated

What this work shows

Validation planning

Linked scenarios to requirements, owners, expected outcomes and evidence.

Change delivery

Defined mobilization, two releases, pilot, hypercare and adoption workstreams.

Executive recommendation

Separated pilot gates, strategic targets, risks and evidence still required.

Portfolio boundary

Fictional municipal scenario, synthetic data, simulated discovery and validation. No City of Toronto affiliation or claimed production outcome.

Municipal Housing Service Transformation · Independent portfolio case study

OverviewLinkedIn