Preparation before capture
Lighting and positioning affect a face scan, but instructions compete with the camera task if shown at the same time. I placed preparation in a separate step, then kept the capture screen focused on positioning the face.
A Know Your Customer (KYC) platform connecting mobile identity verification with tools for configuring checks and reviewing evidence.
I designed the customer journey, configuration tools and review workspace, working with product management and engineering from user flows and prototypes through detailed UI and developer handoff.
The challenge
Customers needed guidance through unfamiliar tasks: scanning a face, capturing an identity document or providing proof of address. Teams needed to configure those requirements and later examine the results.
My task was to connect these experiences: translate the selected checks into customer steps, then organise the resulting evidence for review.
Choose the required checks, their order and the journey they create.
Explain what to prepare, how to capture it and what to review before submitting.
Connect the verification status with individual checks and source documents.
The customer experience
The mobile journey had to support different checks without presenting every requirement at once. I designed preparation, capture and review as distinct steps, with guidance matched to the task.
Lighting and positioning affect a face scan, but instructions compete with the camera task if shown at the same time. I placed preparation in a separate step, then kept the capture screen focused on positioning the face.
Submitting a photo does not mean it is readable. I added guidance before passport scanning and a review step with specific quality criteria, so customers could check the capture before continuing.
A customer may have a paper proof of address or an existing digital file. I provided camera and upload routes, so the journey could accommodate either starting point.
Configuration and case review
The desktop tools supported two different tasks: defining what a customer would be asked to do, and examining the evidence they submitted. I designed the configuration and review views around the information each task required.
Policy configuration
Each configuration choice changes what a customer must do. Teams needed to see how individual checks fitted together, including their requirements and cost.
I brought those details into the builder and added a final summary of the complete sequence. This gave teams a way to review the journey they had configured before publishing it.
Case review
A status alone cannot explain a verification result, while showing every detail at once makes a case harder to scan. Reviewers needed both an overview and a way to investigate individual checks.
I organised the workspace into a case overview, a history of checks and source-document views. This let reviewers begin with the current status and open the supporting details within the same case.
Let’s work together
Tell me about the product and the part that needs fixing. A few sentences is enough.
Tell me about it