CASE STUDY 01 / PUBLIC SECTOR RESEARCH + DESIGN

Digital Citizenship Program

Helping Hungary’s program in shaping a clearer unemployment service

Read the case study

CENTRAL DESIGN QUESTION

How could the service help a digital citizen understand the whole process while still in it?

For six months, I worked on the ‘becoming unemployed’ life event in Hungary’s Digital Citizenship Program (DÁP), covering jobseeker registration and the unemployment benefit application. Research showed that people struggled to see the process as a whole. Our response combined visible progress, questions relevant to each person’s situation, prefilled information and ways to get help or pause. The work reached a detailed prototype tested with users.

MY ROLE

Product designer in a multidisciplinary team, with substantial hands-on involvement in interviews and prototype development.

SCOPE

Six months on the unemployment life event: research, service concept, detailed prototype and usability testing.

DELIVERY

A research-informed, iterated prototype used in usability testing. The service’s subsequent rollout and scope is still ongoing.

Project scope and team

I worked in a multidisciplinary team of two product designers, a design lead, a product owner, a senior service designer, researchers, a legal specialist and a copywriter. Together we moved from desk research and interviews through synthesis and ministry discussions to a service blueprint and an iterated prototype.

My hands-on responsibility was the navigation, the organisation of questions and the detailed experience of moving through the service. I also conducted about half of the in-depth interviews. The aim was a journey citizens could follow, with information prepared digitally to support the staff handling their case.

FIG 1 · STARTING THE SERVICE

Establishing an early design direction

Desk research and social listening pointed to the same pattern: people knew they needed support, but not how registration, information requirements and the next administrative step fitted together. Before the interviews, we turned this into an early concept built on three principles.

Make progress understandable

People needed to see where they were in the process and how the current step related to the whole journey, so navigation and progress belonged to the core experience.

Ask screening questions

Early screening questions decided which later questions applied, so nobody had to work through questions irrelevant to their situation.

Use information already available

Data prefilled from DÁP turned entering every detail into checking it and adding only what was still missing.

The interviews that followed reinforced this direction and gave it a richer understanding of the people and working conditions it had to serve.

Understanding both sides of the service

We ran short interviews at employment offices, followed by in-depth interviews with citizens, caseworkers and office heads; I conducted about half of the in-depth ones. The range of people was broad and the stress around the process was clearly visible. Being comfortable with digital products did not mean someone understood the administrative journey.

The most important finding was a gap in perception. Citizens often described a poor experience, while staff saw the service more positively and pointed to the effort they invested in helping people. Both views were valid: providing a service and receiving it were simply not perceived the same way.

We synthesised the material together, grouping recurring patterns with the quotes behind them. For my product work, this translated into three priorities: make the relevant path understandable, organise the questions coherently and keep help within reach.

Understanding the process

Knew support was needed, but not how registration, information requirements and the next step fitted together

Comfortable with digital products, yet unsure about the administrative journey

Similar uncertainty raised in accounts outside the interviews

Effort and experience

Described a poor experience of the service

Regarded the service more positively

Pointed to the effort invested in helping people

Different starting points

People with very different backgrounds and life circumstances

The stress surrounding the process was clearly visible

Providing the service and receiving it were not perceived in the same way.

Design question: how could the service help a digital citizen understand the whole process while still in it?

FIG 2 · RESEARCH SYNTHESIS

Designing navigation and question flow

I developed the navigation across the prototype, together with the grouping of questions. Grouping shapes how a person understands the task in front of them, while navigation shows how that task relates to the rest of the journey. Both had to support the same understanding.

Screening questions at the start prevented unnecessary work later, and prefilled DÁP data reduced what people had to enter again. The design judgement was in fitting the process to each situation while keeping the information the administration needed.

FIG 3 · NAVIGATION

Navigation and progress information help the user see how the part they are completing relates to the wider journey.

Making help and interruption part of the journey

I advocated for help throughout the flow and treated interruption as an expected part of the experience. A long application is tiring, and stopping should not mean losing the work. If someone stopped partway, their answers went straight to the employment office and an appointment was booked to finish in person. If they completed every step online, only a short visit to sign remained.

This depended on the legal timing of information handling: when someone could start entering details, and when those details could reach the office. We worked through it in repeated discussions with ministry staff and in a service blueprint. It taught me to treat such conditions as design inputs from the start, because the timing of an action shapes the journey, the meaning of a button and what people expect to happen next.

Stopping partway does not discard the work already done.

The answers go straight to the employment office, and an appointment is booked to finish the registration in person.

Every step can be completed online, so the office receives the full application.

Only a short visit to sign remains.

FIG 4 · TWO WAYS TO FINISH

Testing the prototype and assessing the outcome

The prototype followed a common but complex case, giving us a connected journey for testing the navigation and question structure. As I recall, most usability sessions went well: participants generally welcomed handling the process digitally and also gave detailed feedback on individual elements. This was qualitative feedback on a prototype, not a measured improvement in a live service.

By the end of my involvement, the work had reached a detailed, iterated prototype grounded in research and service design. Later programme changes left the rollout and final scope uncertain, so I describe the result at the level reached: a researched and tested service concept, without live-service figures for processing time, completion rate or staff workload.

07 · WHAT THE WORK ACHIEVED

How could the service help a digital citizen understand the whole process while still in it?

08 · TAKEAWAY

The project deepened my understanding of how legal and institutional conditions shape a public service. Knowing when a user can prepare information and when an authority can receive it affects the experience as directly as navigation or content structure. A single life event can hide very different circumstances, and my part was turning that understanding into concrete product decisions.

NEXT CASE STUDY · 02 / 06

Forecastify

Making time and project data easier to compare

horvath.bertalan.andras@gmail.com · +36 30 311 8560