Why pre-screen service design leads before the portfolio review panel
Pre-screening service design leads protects the two hours your panel spends on a portfolio review. Applicants arrive from UX, product, business analysis, and consulting, and every resume lists blueprints, journey maps, and workshops. What it cannot show is whether the redesign shipped, whether backstage processes and policy actually changed, or whether they have ever led designers. A ten minute screen surfaces one real service they changed, the research behind it, and how they handled the operation saying no.
What actually matters when screening Service Design Lead candidates
- 01
Portfolio
Check services they redesigned end to end, and what changed for users and for the organisation behind the counter.
- 02
Craft and rationale
Test whether their research and journey work is grounded in real users or in workshop assumptions.
- 03
Feedback and iteration
Assess how they handle a design that tests well with users but the operation genuinely cannot deliver.
- 04
Working with the brief
Judge how they lead designers and bring operations, policy, and technology along with a service change.
Pre-screening questions to ask Service Design Lead candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Service portfolio
2 questions01Walk us through the service design projects you have worked on, and tell us which ones actually launched.
Listen forNamed sectors and services, their specific role on each, and a clear line between concepts that stayed on paper and changes that reached live users and staff.
Every project is described as a strategy or discovery phase with no evidence anything was implemented.
02Describe a time your service design significantly improved an aspect of the business, including what changed behind the counter.
Listen forA before and after with numbers (handling time, drop-off, repeat contacts, staff steps) plus a backstage change such as a new process, script, or policy.
Only front-end improvements described, or benefits stated as "better experience" with no measure and no operational change.
Research and blueprints
4 questions03Take a couple of minutes to walk us through one of your service blueprints or customer journey maps on screen.
Listen forFrontstage actions, backstage processes, supporting systems, and pain points shown as connected layers, with them explaining what decision the artefact drove.
A decorative journey map with no backstage or systems layer, or an artefact they cannot explain their own contribution to.
04What techniques do you use for identifying and understanding user needs on a service project?
Listen forNamed methods such as contextual enquiry, service safaris, diary studies, or frontline staff shadowing, with detail on recruitment and sample size.
Only internal workshops, personas, and stakeholder interviews, with no direct contact with actual service users.
05How familiar are you with running user research and analysing behaviour data yourself?
Listen forEvidence they have moderated sessions personally and triangulated findings with analytics, contact centre logs, or complaint data rather than relying on a research team.
They have only briefed researchers or read reports and cannot describe a session they ran.
06What methodologies do you use when designing services, and where have you had to adapt them?
Listen forA working grasp of double diamond, jobs to be done, or lean service creation, plus a concrete example of trimming the method to fit a real timeline.
Reciting a framework diagram with no example of applying or adapting it under constraint.
Prototyping and trade-offs
3 questions07How do you prototype and test a service concept before anyone builds it?
Listen forConcrete low-fidelity methods: role play with frontline staff, paper forms, Wizard of Oz pilots, or a single-branch trial, with what the test changed.
Prototyping described only as Figma clickthroughs, with no test involving real staff or real transactions.
08How do you balance business goals and user needs when the operation genuinely cannot deliver your design?
Listen forA real example of a constraint (legacy system, staffing model, regulation) and how they staged, descoped, or reworked the design with operations and engineering.
Framing the constraint as stakeholders blocking good design, with no compromise they personally proposed.
09How do you make sure customer feedback actually gets back into the service after launch?
Listen forNamed feedback loops: post-interaction surveys, complaint themes, frontline debriefs, or usability retests, with an example of a change made after go-live.
Feedback treated as a discovery-phase activity only, with no mechanism for iterating on a live service.
Leading and communicating
3 questions10How do you manage and develop a team of junior service designers?
Listen forSpecifics on critique rituals, pairing on research, dividing a blueprint across people, and one example of raising a junior designer's standard of work.
They describe reviewing files at the end rather than any coaching, or have only worked as a solo designer.
11Give an example of how you communicated a design idea to non-designers such as operations or policy staff.
Listen forThey translated the design into the other group's language: cost per case, handling time, compliance risk, and used walkthroughs or role play rather than jargon.
Blaming non-designers for not understanding, or relying solely on sending decks and Figma links.
12How comfortable are you presenting and defending a service blueprint to executives who disagree with it?
Listen forA specific instance of challenge from a senior stakeholder, the evidence they brought, and whether they changed position or held it with a reason.
No experience beyond presenting to their own design team, or defensiveness framed as protecting the user.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Portfolio
35%5Names services they redesigned with measured change for both users and the operation delivering them.
Craft and rationale
25%5Grounds journey work in real research, and can name a finding that overturned what the team assumed.
Feedback and iteration
25%5Redesigns around real operational constraints rather than blaming delivery, and can cite a case where they did.
Working with the brief
15%5Leads designers and carries operations, policy, and technology through a change rather than presenting to them.
Service design leads spend their days explaining a blueprint to operations managers and executives who do not think in swim lanes. Async video lets you hear that explanation before booking a panel, including whether they can make backstage complexity understandable.
Try it on HirevireScreening FAQ
Process basics
What is the difference between a service design lead and a senior UX designer?
A service design lead works across the whole service, including backstage staff processes, policy constraints, contact centre scripts, and systems, not just the screens. Screen for evidence they changed something behind the counter: a rewritten refund policy, a merged intake form, a retrained frontline team. Pure UX candidates often stop at the interface and the design system.
Should I ask for a portfolio before or during pre-screening?
Ask during. Request a link plus a short video where they talk through one service blueprint end to end. Written case studies are often ghost-written or agency polished, so hearing them narrate their own swim lanes, research sample, and what shipped tells you more in three minutes than a PDF does in thirty.
Evaluating answers
How do I tell real user research from workshop assumptions?
Listen for specifics: how many participants, how they were recruited, where sessions happened (call centre, clinic waiting room, branch), and one finding that contradicted the team's assumption. Strong candidates name methods such as contextual enquiry, diary studies, or service safaris. Weak ones describe personas and empathy maps built entirely from internal stakeholder workshops.
What answer shows they can handle operational constraints?
A strong answer describes a design that tested well but hit a real limit: legacy core system, staffing model, regulation, or budget. They then explain what they cut, what they staged, and how they negotiated with operations and engineering. Candidates who blame stakeholders for killing good design will do the same to your delivery team.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
