Robert Walters — Case study · Tom Nicholls
← Tom Nicholls
Case study · Robert Walters Group

Managing your
candidate pipeline

Replacing an off-the-shelf CRM with one built for the job

Robert Walters ran their recruitment on an ageing off-the-shelf platform about to go out of support. The vendor's replacement was enormously expensive and still didn't do everything they needed — so they decided to build their own. I led the UX, working agency-side.

Role
Lead UX designer, agency-side
Team size
Me & a researcher
Platform
Web app, desktop & mobile
Industry
Recruitment
Users
Consultants and team supporters, UK, EMEA and APAC
Final design, live in the app
rw
Search candidates, clients, jobs etc.
JB
Finance Manager
Live ▾
London•Permanent•£60k – £85k•Financial Services•Exclusive
NW
Main contact
⋮
Filter candidates
SHARE
EDIT SPEC
EDIT JOB
{{ col.name }}
{{ col.count }}
{{ c.name }}
{{ c.employer }}
{{ c.flag }}
{{ c.salary }} {{ c.avail }}
{{ c.initials }}
{{ col.emptyText }}
{{ ghost.name }}
{{ ghost.employer }}
{{ ghost.flag }}
{{ ghost.salary }} {{ ghost.avail }}
{{ ghost.initials }}
Last activity 1 minute ago
{{ lv.selText }}
{{ lv.title }}{{ lv.countText }}
Tick candidates to change their stage together
CANDIDATE
SALARY
CURRENT EMPLOYER
AVAILABLE
STAGE
LAST CONTACT
{{ r.initials }}
{{ r.name }}
GBP {{ r.salary }} pa
{{ r.employer }}
{{ r.avail }}
{{ r.stage }}
{{ r.last }}
No candidates in {{ lv.title }}.
PublishedVersion 3 · updated Mon 2 Mar by Jo Bailey

Finance Manager, UK Corporate Banking

Barclays’ Group Finance team is hiring a Finance Manager to own monthly reporting and forecasting for UK Corporate Banking. You’ll lead a team of four and act as finance partner to the division’s senior leaders.

What you’ll do
  • Run month-end close and management reporting for the division.
  • Build the quarterly forecast and annual budget with business heads.
  • Explain variance to plan and turn it into decisions.
  • Lead, coach and develop a team of four analysts.
  • Automate recurring reporting in Power BI.
What you’ll need
Must-haves Used in screening
  • ACA, ACCA or CIMA qualified
  • Financial services background
  • Manages a team today
Nice to have
  • IFRS 9 experience
  • SAP or Oracle Financials
  • Power BI or similar
About the team

The role reports to Natalia Wilkins, Head of Finance. The team sits in Canary Wharf and works in the office three days a week.

Key facts
Salary
£60k – £85k
Bonus
Up to 10% discretionary
Location
Canary Wharf, London
Working pattern
Hybrid — 3 days in office
Reports to
Natalia Wilkins
Team
4 direct reports
Closing date
Fri 27 Mar
Package
Pension
8% employer contribution
Healthcare
Private, family cover
Holiday
28 days + bank holidays
Shares
Sharesave scheme
{{ g.day }}
{{ a.who }} {{ a.verb }} {{ a.subject }} {{ a.rest }}
{{ a.detail }}
{{ a.time }}
Nothing logged of this type yet.
Coming up
From the candidates on the board.
{{ u.flag }}
{{ u.name }} · {{ u.stage }}
Nothing booked.
Hiring pipeline
These stages are the columns on the Candidates board. Changes apply to this job only.
#
Stage
Type
On board
Order
{{ s.n }}
{{ s.name }}{{ s.lockNote }}
{{ s.kindLabel }}
{{ s.count }}
Stage name
Type
Add after
Long list and Placed are fixed. Removing a stage moves its candidates back one stage.
Interview plan
Pre-fills each interview when a candidate is moved into that stage.
{{ p.name }}
{{ p.when }}
{{ q.initials }}{{ q.name }}{{ q.role }}
{{ p.format }} · {{ p.where }}
Edit
There are no interview stages in the pipeline.
Job details
Reference
RW-FIN-10482
Consultant
Jo Bailey
Created
Mon 2 Mar
Job type
Permanent, full time
Salary
£60k – £85k + bonus
Location
Canary Wharf — hybrid
Exclusive
Yes, until Fri 27 Mar
Target start
Mon 4 May
Commercial terms
Fee
20% of first-year base
Rebate
12 weeks, sliding scale
Payment
30 days from start date
Terms signed
Thu 27 Feb
Hiring team
NW
Natalia Wilkins
Head of Finance
Hiring manager
RM
Raj Mehta
Financial Controller
Interviewer
HC
Helen Carter
CFO
Final approval
SD
Sam Doyle
HR Business Partner
Offers
Good morning, Jo
Monday 9 March · 5 things in the diary today
Add candidate
New job
{{ k.label }}
{{ k.value }}{{ k.unit }}
{{ k.sub }}
Today
{{ a.time }}
{{ a.type }}
{{ a.title }}
{{ a.sub }}
My live jobs
Job
Organisation
Pipeline
Candidates
Status
{{ j.title }}Open →
{{ j.ref }}
{{ j.total }}
{{ j.status }}
Tasks
{{ dash.tasksLeft }}
Recent activity
{{ r.who }} {{ r.verb }} {{ r.subject }} {{ r.rest }}
{{ r.time }}
Job vacancies
{{ jobsSub }}
Export
New job
Search jobs
Job
Organisation
Client
Location
Salary
Pipeline
Status
Consultant
Open
{{ j.title }}
{{ j.ref }}Open pipeline →
{{ j.loc }}
{{ j.salary }}
{{ j.total }}
{{ j.status }}
EXT
{{ j.openFor }}
No jobs match these filters.
Candidates
{{ candSub }}
Import CVs
Add candidate
No matches.
{{ cd.initials }}
{{ cd.name }}
{{ cd.title }} · {{ cd.employer }}
{{ cd.qual }} qualified{{ cd.salary }} paNotice: {{ cd.avail }}{{ cd.loc }}
Email
Call
Add to job
Summary

{{ cd.summary }}

Experience
{{ e.title }}
{{ e.org }}
{{ e.dates }}
Skills
{{ k }}
Applications
{{ a.org }}
{{ a.stage }}
Details
Phone
{{ cd.phone }}
Email
{{ cd.email }}
Location
{{ cd.loc }}
Source
{{ cd.source }}
Experience
{{ cd.years }}
CV
{{ cd.cvName }}
PDF · 2 pages · updated Tue 3 Mar
View
Clients
The people you hire for
Import
Add client
No matches.
{{ cl.initials }}
{{ cl.name }}
{{ cl.role }} ·
Client since {{ cl.since }}Owner: {{ cl.owner }}{{ cl.liveCount }}
Email
Call
Log meeting
Jobs
{{ j.title }}Open →
{{ j.ref }} · {{ j.salary }}
{{ j.total }}
{{ j.status }}
Interactions
{{ l.date }}
{{ l.type }}
{{ l.text }}
Contact details
Phone
{{ cl.phone }}
Email
{{ cl.email }}
Office
{{ cl.office }}
Prefers
{{ cl.preferred }}
Last contact
{{ cl.last }}
Hiring preferences
  • {{ p }}
Organisations
The companies with vacancies
Add organisation
{{ og.ini }}
{{ og.name }}
{{ og.industry }} · {{ og.size }}
{{ og.status }}Since {{ og.since }}Account owner: {{ og.owner }}
Log meeting
New job
{{ k.label }}
{{ k.value }}
Jobs
{{ j.title }}Open →
{{ j.ref }} · {{ j.owner }}
{{ j.total }}
{{ j.status }}
Contacts
{{ p.initials }}
{{ p.role }}
Last contact {{ p.last }}
Terms
Fee
{{ og.fee }}
Rebate
{{ og.rebate }}
Payment
{{ og.payment }}
Supplier status
{{ og.status }}
Offices
{{ x }}
Head office
{{ og.address }}
Consultants
Robert Walters consultants and the external partners who work our jobs
Teams
Invite partner
Consultant
Company
Team
Office
Live jobs
Placed YTD
{{ cs.initials }}
{{ cs.name }}
{{ cs.role }} · {{ cs.company }}
{{ cs.typeLabel }}{{ cs.team }}{{ cs.office }}
{{ cs.extNote }}
{{ k.label }}
{{ k.value }}
Placements against annual target{{ cs.targetText }}
Specialisms
{{ k }}
Jobs
{{ j.title }}
{{ j.orgName }}
{{ j.status }}
No jobs at the moment.
Recent placements
{{ p }}
No placements yet.
Phone
{{ cs.phone }}
Email
{{ cs.email }}
{{ toast }}
{{ fabLabel }}
{{ m.title }}
{{ m.initials }}
{{ m.name }}
{{ m.employer }} · {{ m.salary }} · {{ m.avail }}
{{ m.fromName }} {{ m.toName }}
{{ f.label }}
{{ p.initials }} {{ p.name }} · {{ p.role }}
+ Add
{{ f.v }}
{{ m.note }}
{{ cm.title }}
{{ cm.sub }}
{{ f.label }}
{{ p.initials }} {{ p.name }} · {{ p.role }}
+ Add
{{ f.v }}
{{ cm.note }}
{{ cq.initials }}
{{ cq.name }}
{{ cq.title }} · {{ cq.employer }}
{{ cq.qual }} qualified{{ cq.salary }} paNotice: {{ cq.avail }}{{ cq.loc }}
Email
Call
This job
Finance Manager · Barclays PLC
{{ cq.stage }}{{ cq.flag }}{{ cq.inStage }}
{{ p.label }}
Salary vs band
{{ cq.salary }}
{{ cq.salNote }}
Notice → start
{{ cq.avail }}
{{ cq.noticeNote }}
Must-haves
? {{ k.text }}To confirm
On this job
{{ a.who }} {{ a.verb }} {{ a.subject }} {{ a.rest }}
{{ a.detail }}
{{ a.day }} · {{ a.time }}
Nothing logged against this job yet.
Summary

{{ cq.summary }}

Experience
{{ e.title }}
{{ e.org }}
{{ e.dates }}
Skills
{{ k }}
Details
Phone
{{ cq.phone }}
Email
{{ cq.email }}
Location
{{ cq.loc }}
Source
{{ cq.source }}
Experience
{{ cq.years }}
Other applications
{{ a.job }}
{{ a.org }}
{{ a.stage }}
Only this job.
CV
{{ cq.cvName }}
PDF · 2 pages
View

The same pipeline as a board. Drag a candidate to another stage and the move asks only for what that stage needs, already filled in from the job's setup.

01

Aim

Change the way recruitment agents at Robert Walters manage their clients, jobs and candidates. The existing system was outdated and inefficient — cumbersome processes and an overload of information nobody needed, which frustrated the people who had to live in it all day.

The goal was a modern CRM that streamlines those tasks, improves productivity and matches the company's brand and long-term objectives — built on user research, iterative design and continuous feedback rather than a feature list.

Why build, not buy

The legacy platform was about to go out of support. The vendor's upgrade cost a fortune and still missed functionality the business depended on.

Building their own was the cheaper option and the only one that could fit how Robert Walters actually recruits — so the design work had to earn that decision.

02

Process

Stakeholder and user input feeding an iterative build: define objectives, research, ideate, scope, test, build, then learn and adapt. I laid it out linearly to explain Agile to non-digital stakeholders — the product itself was designed and built iteratively.

01 — Objectives

Agree with stakeholders what the product has to achieve.

02 — Research

Shadowing, interviews, card sorting and surveys with the real user base.

03 — Ideation

Hypotheses against each stated user problem.

04 — Scoping

What goes into this slice, against real resource.

05 — User testing

Benchmarked against the legacy system, not against nothing.

06 — Build

Alpha environments so tasks could be tried in real scenarios.

07 — Learn & adapt

Feed the findings back in and go again.

The process diagram shown to stakeholders

The seven stages I used to explain Agile to stakeholders who'd never worked in it.

03

User research

I shadowed recruitment team members, looked at the paper and digital tools they actually use, ran as-is interviews across a large slice of the future user base, and used card sorting surveys to find which candidate information genuinely matters.

Participants spanned London (14 consultants, 3 team supporters), Milton Keynes (4 consultants, 1 team supporter) and a business working group of around ten APAC and ten EMEA consultants.

One consultant kept their candidate hotlist in a paper notebook, because the digital platform wasn't trusted and was "not as versatile as a piece of paper".

The paper hotlist referenced in the quote above

That actual notebook — pages of candidates nobody else in the team could see.

Six insights that shaped everything after
Paper preference
Many recruiters preferred paper, for flexibility and reliability.
Information overload
The legacy system buried people in irrelevant detail and slowed them down.
Varied workflows
Recruiters work in genuinely different ways, so the system had to be customisable.
Data prioritisation
Job titles and skills mattered enormously; social profiles barely registered.
Resistance to change
Long-term users feared a new system would disrupt work that was paying their bills.
Distrust in automation
Automated candidate suggestions were treated with suspicion — people trusted their own judgement.
How frustrated are people with the existing system

Three-quarters of the people we surveyed were at least quite frustrated — the case for change wasn't a hunch.

Card sort results — candidate data ranked by importance

The card sort behind the data-prioritisation insight above — CV and salary mattered most; social profiles barely registered.

04

What users told us

The verbatims were unusually consistent — and they became the left-hand column of the solution table.

"Registering candidates is a painful process."
"Search is clunky and you have to enter exactly the right information, which is time consuming."
"A lot of information is off the system, so we end up annoying candidates by ringing them again."
"A lot is done over email, which gets lost easily."
"I wish I could access the application wherever I am — in a coffee shop, on the bus, wherever."
"It takes so long to learn how to use the old system — I want to learn it myself."
05

Segmentation, personas & jobs to be done

We segmented the recruitment staff on the qualities that actually changed their behaviour — profile usage, placement performance, tenure, discipline and how full their candidate pool was.

Distinct user qualities used to segment recruitment staff

Starred rows are the qualities that changed behaviour enough to shape a persona.

Three personas came out of it. Each had its own jobs to be done, on the system and off it — collating potential candidates, reviewing them with the team — which we turned into specific tasks with a pass mark, then ran in an alpha environment so we knew they held up in real use.

Three personas — high profiler consultant, low profiler consultant, high profiler supporter

The personas, split by role and how heavily they used the old platform.

Jobs to be done mapped to alpha testing tasks, methods and success criteria

Every job to be done became an alpha task with a testing method and a success bar.

06

Journeys & the object model

I mapped the high-level to-be journeys for finding suitable candidates for a role — the key steps, and the emotions and thoughts at each one — so the team could see the recruitment experience from the consultant's side and spot where the workflow hurts.

Alongside that, an entity-relationship diagram covering client contacts, organisations, job vacancies and everything they connect to. It was drawn deliberately so business stakeholders could read it — which is how we got useful feedback on the structure of the system rather than just the screens.

The journey map showed feeling dropping hard at one step in particular — entering a candidate into the system. That dip is what the whole quick-create flow was built to fix.

High-level to-be journey for finding suitable candidates for a job role

Search to interviews, with what the consultant is feeling and thinking at each step.

Entity-relationship diagram covering candidates, client contacts, organisations and job vacancies

Every record type written in plain definitions and examples, so stakeholders could argue with the model itself.

07

Solution hypotheses

I ran the UX team as a laboratory: every stated user problem got a hypothesis about what would make it better, and every hypothesis got tested rather than assumed.

User problem Hypothesis Solution
"Registering candidates is a painful process" Prioritising ease of entering candidate information will cut time and raise satisfaction. A quick-create modal carrying only the vital fields, and nothing else.
Re-typing what's already on the CV Letting users upload a CV and auto-populating the fields will cut time and raise satisfaction. Add a CV to the quick-create modal, parse it into the fields, and let the user review before saving.
"A lot is done over email which gets lost easily" Bringing that part of the workflow inside the product will stop information going missing. Candidate records as drafts that stay out of search, assignable to a team supporter to finish.
08

Prototypes, testing & benchmarking

Wireframes and prototypes were tested head-to-head against the legacy system, so improvement was a number rather than an opinion. That mattered with a user base nervous about change — and it gave the business hard evidence that building their own was working.

9.5/10
speed of editing candidate info — legacy scored 6/10
9.3/10
speed of creating a candidate — legacy scored 3.5/10
Four changes that came straight out of testing
Add a CV and let the information parse itself into the form.
Send a candidate — with a priority rating — to a team supporter to complete.
'Home location' became 'work locations' — candidates will often work away from home for the right job.
An 'add more' button revealing the secondary fields — aspirational role, qualifications, visa.
Prototype job details screens annotated with where test participants tapped

Test taps recorded step by step through the rate and contract fields — where hesitation showed up, the field changed.

The form that came out of it

Vital fields only, the CV doing the typing, and everything secondary folded behind 'add more'. Notes sit at the bottom because that's where consultants put the context a CV never carries.

Prototype of the quick-create candidate form on mobile
09

Brand & personality

I surveyed consultants on how they saw the company's personality, and read that against the Robert Walters brand guidelines and accessibility requirements. Three traits came back clearly, and they set the look and feel — and the tone of voice — for each type of record in the application.

Modern Professional Extroverted
A colour per record type

Candidates, client contacts, consultants, organisations and jobs each got their own gradient and mark, so a consultant knows what they're looking at before they read a word of it.

Candidate record header

Candidate

Client contact record header

Client contact

Consultant record header

Consultant

Organisation record header

Organisation

Job vacancy record header

Job vacancy

10

Detailed journeys, IA & accessibility

Detailed journeys captured every step a user takes through candidate management, down to the screen flows, so the interface stayed intuitive rather than merely complete.

The information architecture gave every piece of functionality a natural home without loading any one page with options — the direct answer to the information overload people hated in the legacy system. Accessibility was worked in alongside the brand guidelines rather than checked at the end.

Every field, empty state and validation message was drawn at screen level — so the build team never had to guess what a half-finished candidate record looks like.

Detailed screen flow for filling in a candidate record

The fill-in-the-form flow, screen by screen, from the candidate list through to a saved record.

11

Design system

A consistent set of colours, icons and typography, with page states defined, so the interface holds together across the platform and can be extended without re-deciding the basics every time.

What it covered
Record theme colours Icons at three sizes Type scale & case rules Feedback states
Design system — atoms, colours, icons and typography

Colour, icons and type documented as atoms — including sentence-case versus title-case, which settles a lot of arguments.

12

Final visual design

A modern, intuitive interface for managing candidates with streamlined workflows on desktop and mobile — one experience across devices, answering the consultants who wanted to work from a coffee shop or a bus.

Final design — desktop

Desktop — the pipeline, stripped to what consultants said they actually use.

Final design — mobile

Mobile — the same record and activity log, away from the desk.

13

Change management

Research had told us plainly that long-term users were resistant, so we designed for the transition as well as the product. A promotional and educational video showed the features and the benefits, and helped staff fold the new system into their working day — it turned out to be one of the most valuable things we made.

Cut and animated in-house — one scene per benefit, in the language consultants use. Watch on YouTube →

14

Results

−40%
task completion times
+20%
self-reported productivity
3.5→8
user satisfaction, out of 10
65%
of UK users fully moved across in month one
"The new CRM system has transformed how our team works — tasks that used to take hours now take minutes. The user-friendly design has been a game-changer."
Senior recruitment manager, Robert Walters
"The onboarding materials, especially the video, made the changeover much easier than we anticipated. The team was able to hit the ground running."
Stakeholder, Robert Walters
15

What I took from it

Anticipate resistance early

Change management — communication and training materials — needs planning from the start, not bolting on at release.

Involve users even earlier

If I ran it again I'd bring users in before the initial concepts, not just to react to them.

Benchmark, don't assert

Scoring prototypes against the system they replace made the case for the build in a language the business could act on.

More work, or a chat?
London SE9 · 07736 048842
← All case studies Get in touch →