DurhamRegion

A civic UX/UI redesign for myDurham 311, focused on clearer service discovery, payment paths, responsive behavior, and resident-first navigation.

Redesigned myDurham 311 homepage with primary action cards.
Role

UX / UI Designer

Service architecture, responsive interface direction, navigation, and civic page systems.

Focus

311 services

Help residents submit requests, find alerts, make payments, and track service status faster.

Principle

Findability first

Make the most common municipal tasks visible before users need to search.

Mission

Turn a civic portal into a calmer service gateway.

Durham residents needed a clearer way to reach high-demand services without parsing a heavy government website.

My contribution

I reorganized priority actions around resident intent.

The work focused on homepage hierarchy, service request entry points, payment paths, mobile behavior, and reusable UI patterns.

A calmer way into civic services.

The redesign shifted the page from a search-heavy municipal landing page into a resident task hub with three obvious starting points.

Older myDurham 311 homepage with large search hero and service alerts.
Previous directionSearch was doing too much of the work.

The earlier homepage relied heavily on one search bar and separated key actions across the page.

Refined myDurham 311 homepage with submit, track, and payment cards.
Refined directionPrimary services became the first visible decision.

Submit, track, and pay are elevated as direct entry points before secondary service content appears.

Navigation mapped around resident intent.

The sitemap clarified how broad civic categories could connect to high-demand request paths without making users understand internal departments first.

Durham Region sitemap showing home navigation into service request categories.
Task mapService requests connect to concrete resident needs.

High-frequency categories like transit, water, garbage, and regional inquiries sit behind a clearer service request model.

01

Put resident tasks before organization structure.

The interface stays civic, practical, and direct so residents can complete the task even when they arrive under pressure.

02

Use accessible contrast and large, readable action targets.

The interface stays civic, practical, and direct so residents can complete the task even when they arrive under pressure.

03

Keep service status, alerts, and payment paths easy to recover.

The interface stays civic, practical, and direct so residents can complete the task even when they arrive under pressure.

04

Make responsive behavior feel like the same civic product, not a separate mobile site.

The interface stays civic, practical, and direct so residents can complete the task even when they arrive under pressure.

Core paths became easier to scan.

The page system treats requests, tracking, and payment as sibling journeys, each with a direct entry point and supporting explanation.

Durham Region service request homepage with social alerts and service request cards.
01 / Service discoveryService cards bring common tasks forward.

Residents can scan alerts, requests, and topic cards before committing to search or a deeper navigation path.

Durham Region track service request screen with explanation steps and request list.
02 / Request trackingTracking becomes a guided status flow.

The track-request screen explains the service lifecycle and keeps reference search close to the result area.

Durham Region payment options page with payment categories.
03 / PaymentsPayment options are grouped by task, not department.

Water, tickets, permits, and waste payments are presented as direct choices with scannable descriptions.

Same civic product, smaller canvas.

Mobile and compact desktop states preserved the same service hierarchy, reducing the chance that residents would lose their place between devices.

Durham Region responsive home screen design.
HomeResponsive behavior keeps the service model intact.
Durham Region responsive service request screen.
RequestsResponsive behavior keeps the service model intact.
Durham Region responsive learn and help screen.
HelpResponsive behavior keeps the service model intact.
Design system

UI parts were treated as civic infrastructure.

Buttons, nav states, footer patterns, and service modules were organized so the portal could scale without each new page becoming a custom layout problem.

Durham Region design system board with buttons, navigation, footer, and color frames.
Outcome

A public service experience that feels easier to trust.

The Durham Region work brings hierarchy, accessibility, responsive consistency, and task-first navigation into one calmer 311 experience.