Here is a striking fact worth sitting with: the button placement on your product comparison page might now be considered regulatory evidence.
That is not hyperbole. Under the FCA’s Consumer Duty framework, the design decisions your team makes about digital journeys are no longer just UX choices. They are documented proof of whether your firm genuinely supports customer understanding, or quietly undermines it.
Following the FCA’s August 2025 findings on digital journey design, financial services firms are facing a sharper reality. Regulators are paying attention to how interfaces guide decisions, where customers drop off, and whether the overall experience nudges people toward outcomes that actually serve them. Analytics data tells that story clearly, whether firms intend it to or not.
This post breaks down what the FCA actually found, what good and poor design looks like in practice, when your own data becomes evidence against you, and what a Consumer Duty-aligned design brief should include. If your organisation commissions digital product design without someone who understands both design craft and FS compliance fluently, this is worth reading carefully.
Your Interface Is a Regulatory Document Now
In August 2025, the FCA published its findings on digital design in customers’ online journeys, and the message was unambiguous: how you design your interface is now a compliance matter, not just a UX one.
The FCA’s position is direct. Digital journey design “can encourage customers in a specific direction and can influence their understanding of products and features.” That is not a warning about future risk. That is a description of current enforcement territory.
What makes this significant is the granularity. The FCA is not talking about broad product strategy. It is talking about button placement, information hierarchy, form field ordering, the sequencing of disclosures. The same level of scrutiny applied to a product disclosure document now applies to where you put your primary call-to-action. If your design considerations around a journey step nudge a customer toward a fast decision that is not in their interest, that is a Consumer Duty problem, full stop.
For firms commissioning digital financial services work, this creates a specific risk that is easy to miss. Every sprint that produces interface changes without a regulatory lens is generating compliance exposure, not just shipping features. The risk accumulates quietly across your product estate.
The broader shift is structural. Digital financial services can no longer be treated as a marketing or conversion function with compliance bolted on afterwards. The overview of what good digital journeys require has changed permanently. Design is now a compliance-critical discipline, and firms that have not caught up to that yet are already behind.
What the FCA Actually Found in August 2025
That August 2025 publication covered good and poor practice across apps, websites, and financial promotions. Read it as a compliance document if you like, but it functions just as well as a design brief.
That speed-vs-informed-consent tension sits at the heart of the FCA’s concern.
Online choice architecture (OCA) and dark patterns are called out explicitly, not as vague concerns but as named regulatory issues. That puts them in the same enforcement conversation as the UK’s Digital Markets, Competition and Consumers Act 2024 and the EU Digital Services Act, both of which target unfair OCA practices. Firms operating across jurisdictions are facing this pressure from multiple directions simultaneously.
The target market requirement, embed customer knowledge from the start, not bolt it on post-launch, applies equally here.
Perhaps the most significant shift for digital teams is the analytics point. The FCA identifies customer interaction data, including dropout rates at critical decision stages, as a tool firms should already be using to monitor and evidence compliance. Your journey metrics are now part of the regulatory record. That is a different brief entirely than funnel optimisation.
Good Design vs. Poor Design: What It Looks Like in Practice
So what does all of this look like when you’re actually staring at a Figma file or a live journey? Here’s the practical split.
Calibrate information density to decision weight. A direct debit setup can be lean and fast. A mortgage application cannot. The more consequential the decision, the more breathing room the interface needs to give the customer. Compressing a complex product journey into five frictionless screens is not good UX; under Consumer Duty, it is a red flag.
Disclosure placement is not a layout preference, it’s a sequencing obligation. Burying critical risk information below the fold, or dropping it after the primary CTA, effectively inverts the logic of informed decision-making. The customer has already committed psychologically before they’ve seen what they needed to know. That ordering is now a compliance problem, not just a usability one.
Put decision points where context exists, not where conversion peaks. It is genuinely tempting to place a “proceed” prompt at the moment a customer is most engaged. But if they haven’t absorbed the relevant information yet, that prompt is pushing them toward a fast decision rather than an informed one, which is precisely what the FCA flagged.
OCA patterns are under the microscope. Opt-out defaults on add-on products, countdown timers on selection screens, pre-ticked consent boxes; these are no longer just ethically questionable. They are patterns that sit uncomfortably with the FCA’s Consumer Duty framework’s requirement to act in good faith and support genuine customer understanding.
High drop-off at a disclosure stage might mean it’s working. If customers are pausing or abandoning after reading a risk disclosure, that is worth investigating before you optimise it away. It may signal the disclosure is doing exactly what it should.
Finally, document the rationale behind every material design decision. Why this pattern? What outcome was it designed to support? This kind of record-keeping, much like designing for accessibility where intent must be demonstrable, is increasingly what firms need to show regulators, not just show users.
When Your Analytics Become Evidence
Documenting your design decisions is only half the job. The other half is proving, through live data, that those decisions are actually working.
Every digital journey your firm runs is generating behavioural data constantly: click paths, dwell times, drop-off rates, the frustrated rage-clicks that tell you something has gone badly wrong. The FCA has made clear it expects this data to actively demonstrate compliance, which changes what your analytics stack needs to do. Proper Google Analytics configuration is no longer just good practice for a digital financial services product; it is the infrastructure your regulatory evidence sits on.
Here is where it gets pointed. A high abandonment rate at a critical decision node, say, the risk disclosure screen before an investment product purchase, is not automatically a UX problem to engineer away. The FCA flags it as a potential signal that the design is undermining genuine customer understanding. The user is leaving because something is wrong, and that something might be your interface.
The inverse is also true. Analytics showing customers moving through informed decision stages at a measured pace can actively demonstrate Consumer Duty compliance. Good data tells a good story, if you have set it up to capture the right things.
That is the catch. Most analytics frameworks are built to report on funnels, not outcomes. Retrofitting regulatory reporting onto an existing setup after an FCA review is significantly harder than designing the measurement framework from the start.
Design teams and compliance teams are currently measuring different things entirely. Closing that gap means defining shared metrics, and that requires someone who speaks both languages fluently.
The Gap Most FS Firms Have Right Now
So who’s actually equipped to solve this? That’s where things get uncomfortable.
Most design agencies brought into financial services work are optimising for the wrong scoreboard. Conversion rates, task completion, drop-off reduction, these are legitimate UX metrics, but they sit in direct tension with Consumer Duty expectations when they come at the cost of informed decision-making. A frictionless journey isn’t automatically a compliant one.
Compliance teams have the opposite problem. They understand the Consumer Duty’s outcome requirements well enough, but translating “ensure customer understanding” into a specific component decision, an information hierarchy call, or a design system standard is a different skill set entirely. Knowing the rule and designing for it are not the same thing.
The result is firms that are simultaneously over-engineered for engagement and under-designed for compliance. That’s not a theoretical risk; it’s the kind of misalignment that invites active regulatory scrutiny.
The analytics gap is the evidence gap.
With over 15 years spanning UX design, financial services, brand, and compliance-adjacent work, the ability to hold both the design craft and the regulatory lens at the same time is precisely what most FS firms are missing right now. Not a designer who reads compliance documents occasionally. Someone for whom both are native languages.
What a Consumer Duty-Aligned Design Brief Looks Like
So what does closing that gap actually look like in practice? It starts with the brief itself.
A compliant design brief opens with target market definition in the FCA’s terms: the characteristics, needs, and objectives of the specific customer group the product serves, including who it explicitly does not serve. This is not a marketing persona. It is a regulatory control, and briefs that skip it create downstream compliance exposure with every interface decision that follows.
From there, the brief specifies two classes of metrics. Traditional UX measures like task completion and time-on-task still matter. But alongside them, the brief must define outcome metrics: how customers are engaging with key product risk disclosures before completing the journey, for instance. If you cannot measure it, you cannot evidence it.
Documentation is a deliverable, not a formality. Every material step in the journey, fee disclosures, risk warnings, eligibility checks, requires a recorded rationale explaining which interface choice was made and which Consumer Duty outcome it was designed to support. This is what auditors review. Building it in from the brief stage is considerably easier than retrofitting it after the fact.
Analytics integration gets scoped at the brief stage, not after launch. Which events are tracked, what a compliant outcome looks like in the data, who owns remediation if metrics flag a problem: these are brief-level decisions, not sprint retrospective ones.
Finally, the brief is reviewed by someone who can read it through a design craft lens and a regulatory compliance lens at the same time. That dual-literacy is, frankly, the whole point.
This Applies Beyond Consumer Credit
One important caveat before you file that brief away: the August 2025 findings are not a consumer credit story. The Consumer Duty covers the full retail landscape, including mortgages, investments, insurance, and savings products. If it has a digital journey, it is in scope.
That matters because each product category carries its own complexity profile. The design patterns that work fine for a current account opening flow are genuinely inadequate for an investment product, where demonstrating customer understanding of risk is a regulatory prerequisite, not a nice-to-have. An insurance renewal journey sits somewhere in between. Treating these as interchangeable is where firms quietly accumulate compliance exposure.
For firms with multi-product digital estates, the risk compounds. Fixing journeys product-by-product, in isolation, tends to produce inconsistency across the estate. One product line meets the FCA’s expectations around decision point sequencing; another still has pre-ticked add-on boxes and buried risk disclosures. That patchwork approach does not hold up well under a holistic supervisory review.
Firms operating across jurisdictions face the same pressure under the UK’s Digital Markets, Competition and Consumers Act 2024 and the EU Digital Services Act, regulatory convergence means the scrutiny playbook is shared.
The Design Brief Just Got More Serious
So regardless of which products your firm offers or which jurisdictions you operate in, the underlying obligation is the same. That obligation runs from the first wireframe through to post-launch monitoring.
Here is where to start.
Audit your current journeys against the FCA’s August 2025 findings. Look specifically at information placement, decision point sequencing, and any OCA patterns that prioritise speed over informed consent. If you would not be comfortable showing a particular screen to an FCA reviewer, that is your answer.
Audit what your analytics are actually measuring, if the framework can’t evidence customer understanding at key disclosure points, flag it now.
Document your existing design decisions now, retrofitting Consumer Duty rationale is harder than building it in, and the gaps are visible.
Bring design and compliance teams onto a shared brief, that alignment is the foundational fix. Good content design for financial services is where those two disciplines meet in practice.
That shared brief is exactly what Simon Alcock builds. If your firm needs someone who reads a design system and a regulatory framework with equal fluency, that is the conversation worth having.
Conclusion
The FCA’s August 2025 findings made one thing undeniable: interface design is now a compliance function, not just a commercial one. Firms that treat these as separate disciplines are carrying real regulatory risk inside their own products.
The core takeaways are straightforward. Your digital journey is evidence. Your analytics need to measure understanding, not just conversion. Every design decision should have a documented rationale tied to customer outcomes. And design and compliance teams must work from the same brief, not parallel ones.
The good news is that this is solvable. Consumer Duty-aligned design does not mean sacrificing performance. It means building journeys where clarity and commercial outcomes point in the same direction.
If your firm is ready to close the gap between what your interfaces do and what the regulator expects, start that conversation now. The firms moving first are already building the advantage.
