# UK Home Office

> During the Syrian refugee crisis I was design lead on a Government Digital Service team in the Home Office, helping build digital tools for the caseworkers, local authorities and charity groups running the resettlement process.

**Question:** How do you help caseworkers resettle refugees?  
**Tags:** Service Design, Public Sector  
**Focus:** Design Lead  
**Case study:** https://www.sebastian-nause-blueml.com/ukhomeoffice.html

---

## Resettlement off the spreadsheet.

Helping the Home Office build digital tools for the caseworkers resettling Syrian refugees in the UK.

*Cover image: Two young children at the entrance of a UNHCR refugee tent in a camp, an adult behind them and shoes lined up on the wet ground.*

## At a glance

- **Client:** UK Home Office - Syrian refugee resettlement
- **My role:** Design Lead on a Government Digital Service team in the Home Office
- **Users:** Caseworkers, local authorities, charity groups
- **The work:** Process mapping, user research, early prototypes for the resettlement programme

## The situation

### A national effort, run on Excel and Post-its.

When the UK committed to resettling refugees from Syria, the volume overwhelmed the existing process almost immediately. Cases, housing pledges and funding were tracked in spreadsheets and handwritten notes.

*Image caption: A real artifact of the process: housing addresses, passed around on a Post-it. (A caseworker holding a Post-it note with two handwritten housing addresses.)*

## Mapping the process

### Every decision maker described a different process.

Mapping the journey made the gaps visible: the process on the ground versus the one everyone imagined. The blueprint had senior stakeholders asking, for the first time, is that really how this works, and why are we doing it that way?

*Image caption: The anticipated process for the regional match-making model, mapped wall-size. (Detail of the wall map: "Making a Match" - putting together a batch of cases to match a region's capabilities.)*

## The research

### Built with the people doing the work.

Workshops, interviews and watching caseworkers, local authorities and charities at work. The people who line up pledges, match cases and receive families, to learn what they actually struggle with day to day.

*Image caption: Mapping activities and pain points with the people running the process. (A workshop table covered in activity and pain-point cards, with a participant writing.)*

## From findings to opportunities

### Pain points became a backlog of tools.

Each mapped pain point was turned into a concrete opportunity with the teams - what to automate, what to support, what to leave alone.

*Image caption: Opportunity worksheets: "...I would have a tool that could help me..." (A mapping worksheet being filled in.)*

## Early prototypes

### From paper worksheets to a working alpha.

The research fed straight into early digital prototypes for the resettlement service - built on GOV.UK patterns and tested with the caseworkers who'd use them.

*Image caption: The Syrian refugee resettlement service - in alpha, on GOV.UK rails. (A GOV.UK alpha of the Syrian refugee resettlement service, open on a laptop during testing.)*

## Where it landed

### Tools for the people helping people settle.

The mapping gave the programme a shared picture of its own process; the prototypes became the basis for digital tools the caseworkers actually used.

It shipped as a live service on GOV.UK, part of the Government Digital Service - used by caseworkers to resettle Syrian refugees, and to make that work faster and less error-prone.

## The quote

> "I had no hesitation in asking him to work on challenging and high-profile projects which he tackled confidently. He quickly took a lead role in the design of these new services, while building excellent relationships with colleagues and stakeholders."

**Stu Penny**
Senior User Researcher, UK Home Office

## Looking back

### What stays with me

It is rare to design something this consequential - a live service for families arriving with almost nothing - and that stays with you. So does the lesson: never assume you know how a process really works. Map what people actually do, and pay closest attention to where they do something you didn't expect.
