Situation
The operating reality
The existing service estate was a patchwork of forms, PDFs, and call-center flows. Citizens routinely abandoned applications mid-flow, and call-center volume was outpacing budget.
Loading your next page…
Loading your next page…
Designed and launched a citizen-services portal handling 1.1M monthly active users, with offline tolerance, accessibility conformance, and a 4.2× drop in call-center load.
Every engagement is framed around the business situation, the constraint that made it hard, and the decision that turned delivery into a controlled path to value.
Situation
The existing service estate was a patchwork of forms, PDFs, and call-center flows. Citizens routinely abandoned applications mid-flow, and call-center volume was outpacing budget.
Constraint
The existing service estate was a patchwork of forms, PDFs, and call-center flows. Citizens routinely abandoned applications mid-flow, and call-center volume was outpacing budget.
Decision
Mapped citizen journeys end-to-end, including offline steps, before deciding what the portal should digitize.
Build
Each citizen journey was mapped end-to-end — including the offline steps — before any screen was drawn. The portal explicitly designed for the journeys it could not fully digitize.
WCAG 2.2 AA conformance was audited externally before launch. Forms worked on low-bandwidth mobile, were resumable across sessions, and degraded gracefully when JavaScript failed.
Outcome
Sustained 1.1M monthly active users within six months of launch.
Call-center load on the digitized services dropped 76%.
What changed after launch
Citizens could complete core services on low-bandwidth mobile, while the agency saw call-center pressure fall sharply.
“The service finally worked for citizens with older phones, patchy connectivity, and no patience for government complexity.”
The work was not abstract modernization. It changed day-to-day behavior, ownership, and the evidence leaders used to make decisions.
Before
After
The delivery plan made the system boundary explicit, then used rehearsals, gates, and telemetry to optimize safely before launch.
Delivery architecture
Government control loop
Discover
Each citizen journey was mapped end-to-end — including the offline steps — before any screen was drawn. The portal explicitly designed for the journeys it could not fully digitize.
Launch
WCAG 2.2 AA conformance was audited externally before launch. Forms worked on low-bandwidth mobile, were resumable across sessions, and degraded gracefully when JavaScript failed.
Each citizen journey was mapped end-to-end — including the offline steps — before any screen was drawn. The portal explicitly designed for the journeys it could not fully digitize.
WCAG 2.2 AA conformance was audited externally before launch. Forms worked on low-bandwidth mobile, were resumable across sessions, and degraded gracefully when JavaScript failed.
After launch
Citizens could complete core services on low-bandwidth mobile, while the agency saw call-center pressure fall sharply.
A similar problem?
A senior engineer will follow up within one business day with an opinionated take on the shape of the work.