Urban Problems and Smart-City Choices · Lesson 2

Service journeys and stakeholders

5 min read

Lesson objectives

  • Map a service journey and responsible actors across digital and counter channels, identifying where a user without digital access is excluded.
Reading tools

Observe the whole journey

A dashboard may report that 90% of permit renewals were “processed digitally.” What happened to an application that never began because the owner could not read the form or pay through the available channel? That person is absent from the denominator. A service journey follows the steps from an emerging need to a verified outcome, across online, in-person and telephone channels. It records what residents do, what staff and systems do behind the interface, where people wait, repeat information or leave. The map is not decoration. It makes assumptions about failure points and responsibility visible so that a team can test them.

Start with a defined event, such as a shop permit nearing expiry. Separate discovery of requirements, gathering documents, application, verification, payment if required, decision, receipt of the result, and correction or appeal. Do not assume everyone takes one route. An owner with stable connectivity and a current device may finish online. Another may use a shared phone or need help uploading a document. Recording both routes changes the design question: have we reduced real effort or merely moved a counter queue to an upload page? UN-Habitat's people-centred work calls for attention to the digital divide and residents' participation in digital transition. Apply that principle to identify whose experience has not been heard; it does not establish a universal legal duty to offer any particular channel.

Who acts and who is affected?

Worked case: an attractive rate hides burden

In a fictional city, 200 people reach a permit renewal page each week. Of these, 160 start an application and 120 finish. Thirty people visit the service desk. The platform reports 120 ÷ 160 = 75% completion among started online applications. That is a valid answer to a narrow question, but it does not describe everyone trying to access the service: 40 page visitors did not start, and some desk visitors may have visited the page earlier. We cannot add 200 and 30 as distinct people without identifiers or a study that prevents double counting. The team inspects step records with identities removed where possible and asks a sample of desk visitors whether they tried the online route and why they left it. Reception notes suggest that many stop because the platform rejects an image format without explaining accepted formats.

A bounded first change is to show accepted formats before upload, check the file locally before submission, and offer phone or counter help. A new platform purchase is premature while this failure hypothesis can be tested cheaply. Measure completion among starters, but also monitor the share of page visitors who never start, staff time, and complaints from people using another route. If digital completion rises only because people facing difficulty stop starting, that is a denominator bias, not a demonstrated overall service gain. Stronger evidence would combine improved completion with fewer help requests and no new complaints concentrated in a particular group, while acknowledging the limits of this local trial.

Practice with checkable feedback

Lesson summary

A dashboard may report that 90% of permit renewals were “processed digitally.” What happened to an application that never began because the owner could not read the form or pay through the available channel? That person is absent from the denominator. A service journey follows the steps from an emerging need to a verified outcome, across online, in-perso