Designing Municipal Services Around the Resident Journey

Start from the life event, not the service catalogue

People rarely think of themselves as users of 'municipal service number 452'. They experience events: a baby is born, they move to a new flat, a parent loses the ability to work, a heating claim is rejected. As the Nesta public innovation foundation has observed, governments organise themselves vertically into departments and catalogues, while residents live horizontally across all of them at once. If you begin your design from the catalogue, you build convenience for the administration, not for the person.

The practical starting point is to name the life event that triggers the need and the goal the resident wants to reach. In Russia's client-centric approach to public management, such bundles of measures are called life situations: having a child, retiring, losing health, looking for work, moving home. One life situation typically touches several municipal services and several channels, which is exactly why the map must be drawn around the event rather than around a single counter.

• Birth or adoption: registration, allowances, clinic and childcare enrolment.
• Loss of health: disability assessment, rehabilitation, care support.
• Moving home: re-registration, utilities, schooling and parking permits.
• Looking for work: benefits, retraining and job placement.

Research the 'as-is' journey with real evidence

Before drawing a single box, learn how the service actually works today. US federal teams that produced the TSA PreCheck passenger journey map started with a discovery session in which front-line staff identified every step a passenger passes through from check-in to boarding, then added passenger wait-time data, contact-centre records and a prior satisfaction survey. The result gave staff an overview they had never had and made simple improvements obvious.

Now capture the resident's experience. Interview people who recently went through the journey, observe them completing forms, shadow staff who answer the phone or run the counter, and add 'passive' signals such as complaints and social-media mentions, which often reveal the journey as people actually live it. Recruit a spread of residents: heavy users of the portal and people who can only come in person, older residents, people with disabilities, and users with limited digital literacy. Front-line staff see only their own leg of the route, so a joint session is what assembles the full picture.

• Interviews with recent service users across every channel.
• Observation of real form-filling and office visits.
• Contact-centre data, complaints, reviews and social media.
• A joint session with front-line staff to reconstruct the full route.

Build the map and find the moments that matter

Draw the timeline on the horizontal axis: from the moment the need appears through awareness, preparation, application, waiting, decision and follow-up — to the result the person actually wanted. On the vertical axis record the channel used at each step, the action taken, what the person is thinking and feeling, and where the file is handed between your teams. Creating a named persona with a concrete goal keeps the artefact human and helps every participant see where they fit.

Now walk the whole map and mark pain points, tagging each with the evidence behind it: an observation, a resident's quote, or a metric such as waiting time or repeat calls. Identify the few 'moments that matter' — a single painful step that, if fixed, removes the most friction across the journey. Treat the map as a living tool on the team's wall, kept current and visible, rather than an archived slide.

• Channel and action at every step of the route.
• What the resident is thinking and feeling at each point.
• Handoffs between teams and manual interventions.
• Pain points tagged with evidence: observation, quote or metric.
• Two or three highlighted 'moments that matter'.

Design the 'to-be' experience end-to-end

Redesign the journey as a whole problem, not step by step inside a department. Provide a joined-up experience across channels: the paper step should match the online step, and a resident should not be asked to repeat information they have already given the city. Reuse tested patterns and plain language, reveal choices progressively so anxious users are not overwhelmed, and confirm with your legal team what data you are actually required to collect again.

Make explicit trade-offs between the 'as-is' and 'to-be' maps. You may not fully automate every step: assisted digital support and in-person help remain part of the design, not an afterthought. For each proposed change name the channel owner, the department that must change its process, and the dependency on other systems. A 'to-be' map with no named owners is a wish list, not a design.

• One consistent description of the service on every channel.
• Reuse of data the city already holds about the resident.
• Progressive disclosure of detail to reduce anxiety.
• A clear offline route for residents who cannot or will not use the portal.

Pilot, measure and iterate with the teams who run it

Prototype the most painful step and test it with people who have real experience of the task and realistic data, rather than with colleagues. Invite front-line and policy staff to observe research sessions; they are the ones who will detect flaws early and champion the change. User-testing laboratories, like those planned within Russia's client-centric state project, let ordinary recent recipients try a redesigned service and report friction directly.

Define three to five success metrics before launch: time from request to result, number of visits or calls, drop-off or error rate, and resident satisfaction. Measure the same indicators before and after, then iterate. A redesign is never finished on launch day; schedule a re-check and keep the map and metrics visible in one place for the whole team.

• A prototype of the single most painful step.
• Tests with real users and realistic data, not colleagues.
• Before-and-after metrics: time, visits, drop-off, satisfaction.
• A scheduled re-check after launch.

Where journey mapping falls short

A journey map is an analysis tool, not an outcome. It is only as good as the evidence behind it and useless if no owner is assigned to act on it. Guard against 'design theatre' — workshops that produce a beautiful map but no change — and against mapping a single idealised persona while ignoring residents who are offline, older or less literate.

Legal, privacy, accessibility and security constraints may block what looks like an obvious fix; a map cannot repeal a regulation. Treat this material as general method guidance, not legal advice, and confirm requirements with your legal and data-protection teams in your own jurisdiction. Many client-centric action plans are deliberately advisory, so use the room they allow to tailor the redesign to your local conditions.