AI-First UX Will Break Our Loan Journeys
The framing around AI-first UX tends to focus on enterprise productivity tools and knowledge workers. That's the wrong place to look if you're building consumer credit products in the UK. The more interesting question is what happens to a regulated loan application journey when the interface stops being a form and starts being a conversation. Right now, our origination flows are essentially digitised paper. A sequence of fields, disclosures, affordability questions, consent checkboxes. Compliance teams have spent years getting comfortable with exactly what the customer sees and when they see it. Agentic UX breaks that contract. If an AI can carry context across a workflow, answer questions mid-journey, and adapt what it surfaces based on the conversation, then the "journey" as a fixed, auditable sequence starts to dissolve. That's not a UX problem. That's a Consumer Duty problem. The FCA's focus on good outcomes and fair treatment assumes you can point to the experience a customer had. You can screenshot a form. Auditing a conversational agent that behaved differently for different customers because it was personalising in real time is a genuinely harder compliance challenge. - The obligation to present information clearly doesn't disappear because the interface is conversational - Pre-contractual disclosure requirements don't care whether the customer is reading a screen or talking to an agent - Vulnerable customer identification becomes more complex when there's no standardised journey to assess against None of this means AI-first UX is the wrong direction for consumer credit. A well-designed conversational experience could do a much better job of explaining loan terms than a wall of text most customers scroll past. The potential for genuinely improved comprehension is real. But the teams building these journeys need compliance and technology working together from the start, not compliance reviewing a finished prototype. The question worth sitting with is whether your organisation is structured to do that, or whether you're still treating UX as something that gets signed off at the end.
