← All work AI Product · Government · FCDO

PropChecker

A propaganda monitor that lets non-Arabic-speaking analysts read the answer in minutes — not wait days for a translation queue.

Client
FCDO, via Faculty AI
My role
Senior Product Designer (UX)
Discipline
Research → UI · GOV.UK
Outcome
78% faster processing
PropChecker search interface showing keyword-searchable, auto-translated and summarised foreign-language content
78%
Less time to process foreign-language content
3 mo
From kickoff to a working, validated MVP
2 → ∞
From two seed sources to a multi-department dataset
The problem

A translation bottleneck on time-critical work.

An organisation within the FCDO monitors foreign-language propaganda to spot narratives that could threaten the UK. The catch: most of the staff doing that monitoring don't speak Arabic. Every piece of content had to go through translation services first — slow, costly, and a hard ceiling on how much an analyst could ever review.

The brief was to remove that ceiling: let analysts find relevant material and read an English summary of it themselves, without specialist database skills and without waiting in a translation queue.

User flow mapping the analyst journey from search to summarised insight
User flow — from search to summarised insight in minutes
Research

Designing for two very different analysts.

I led research through three interviews with stakeholders and end users, including a deep dive with our primary analyst. From that I built two personas — Emma, a counter-terrorism insights advisor, and Philip — and wrote the user stories that gave the team a shared, concrete picture of what we were solving and for whom.

Persona — Emma Takle, counter-terrorism insights advisor
Persona — Philip, analyst
Personas — Emma and Philip, grounding every design decision
Feature prioritisation workshop output
Prioritisation — agreeing what the MVP had to do, and what it didn't
The build · MVP

Search, scan, understand — in one place.

The three-month MVP let analysts search, scan and understand foreign-language content without reading hundreds of pages or waiting on translation. We seeded the dataset from two source websites, with entity recognition surfacing the key people, places and topics inside it.

Analysts ran keyword searches and instantly surfaced relevant material. Each result was auto-translated and summarised in English — with the search terms highlighted directly inside the summary, so the eye lands on what matters first.

Complex dataset interface with entity recognition for people, places and topics
Entity recognition surfaced people, places and topics across the dataset
The build · GenAI layer

Open questions — with the receipts.

Once the MVP was working well, two follow-on projects pushed it further. We added a GenAI layer so analysts could ask open questions of the dataset. Crucially, every response checked the source documents and highlighted exactly the ones it had consulted — building in the explainability a government accountability context demands.

A second follow-on brought in more UK government departments and a far larger, more complex dataset, extending the same search-and-summarise model across a much broader range of intelligence sources.

GenAI interface answering open questions while citing the source documents it consulted
Same dataset, GenAI addition — answers cite the sources they drew from
Craft

Built to public-sector standards.

Once the flows were aligned, I moved into low-fidelity wireframes and tested continuously with the champion group. We iterated quickly before moving to UI in the GOV.UK Design System — keeping the product accessible, clear and consistent with the standards analysts already trust.

The win wasn't a cleverer search box. It was giving an analyst who doesn't speak the language a way to read the answer — and see where it came from.

Impact

78% less time, per piece of content.

PropChecker cut the time FCDO analysts spent processing foreign-language content by 78% — and moved the team from depending on external translation to working directly, in English, against a live and growing dataset.

Impact — search interface in use
Impact — summarised results
Impact — highlighted keywords in summaries