Financial Services

Concept Case Study — MCD Lab

FinFlow

A digital financing application rethought from scratch: less perceived effort, clearer decisions and confidence at every step.

Services

UX Research
Product Strategy
UX Design
UI Design
Design System
Accessibility
UX Analytics

Disciplines

Research
Product Strategy
Product Design
Design System
Accessibility

FinFlow is an independent concept study by MCD Lab. It does not represent a real client and contains no real outcomes, metrics, testimonials or user data.

Overview

FinFlow explores what a digital financial product looks like when it is designed around understanding rather than around a form.

Context
Online financing applications pile up steps, documents and rules that are rarely explained to the person going through them.
Objective
Design a journey where every step is short, predictable and justified — from the first screen to confirmation.
Approach
Structure the journey, reduce the load per screen and build a consistent, accessible interface system.

The challenge

The problem in this kind of product is rarely visual. It is comprehension: a lot is asked, little is explained, and errors only surface at the end.

Long journeys with no sense of progress
Technical language at decision moments
Documents requested without context
Errors caught late, after the effort is spent

The design question

How can a complex financial process be made understandable without oversimplifying it or hiding what matters?

This question guided every decision that followed.

Discovery

This is a concept study: no research with real users was conducted. Discovery relied on desk analysis and established interaction design patterns.

Pattern analysis
Review of digital application flows and conventions already documented in UX literature.
Task mapping
Breaking the application into minimal tasks, dependencies and waiting points.
Heuristics
Reviewing the flow against usability and error-prevention heuristics.
Accessibility standards
Reading WCAG 2.2 AA as a design constraint from the start, not as a final review.

No interviews, no samples, no conclusions presented as empirical evidence.

Assumed needs

Conceptual needs, framed as working hypotheses to be validated in a real context.

Know where I am
Understand what is left, before and during the journey.
Understand why
Know the reason behind every field and document.
Be able to pause
Stop and resume without losing what is already done.
Trust the process
See what happens to the data and what comes next.

Experience principles

01
One step, one decision
Each screen asks the minimum needed to move on.
02
Explain before asking
Context sits next to the field, not in a footnote.
03
Prevent rather than correct
Validate on entry, not at the end.
04
Consistency over novelty
Repeated patterns lower cognitive load.

Information architecture

The application was reorganised around user intent — not around an internal system structure.

01
Simulation
Amount, term and estimate before any personal data.
02
Personal details
Identification in short blocks with visible progress.
03
Financial information
Income and commitments, with the purpose explained.
04
Documents
Requested at the right moment, with per-file status.
05
Review
An editable summary before anything is submitted.

Progressive disclosure

Instead of one monolithic form, the journey reveals information as it becomes relevant, always keeping progress in sight.

FinFlow interface on tablet and smartphone showing a step 4 of 8 indicator and financial information fields. — Step by step, with persistent progress on desktop and mobile.

A step indicator that never disappears
Short blocks with a single purpose each
Extra detail available on request

Application dashboard

The application stops being a tunnel and gets a place of its own: a panel showing status, next steps and history.

FinFlow dashboard “Your application, always with you” on a laptop, with the mobile version beside it. — The same application state, coherent across laptop and phone.

Current status in plain language
The next action always identified
Continuity across devices

Smart forms

Fields were designed to reduce effort: logical grouping, assisted formats and contextual help.

FinFlow “Your details” screen with personal data fields and the application progress indicator. — Personal details collected in short, readable blocks.

Visible labels, never placeholder-only
Assisted formatting for dates and amounts
Inline help next to the field that needs it

Error prevention

The goal is not to show errors better: it is to stop them happening.

Validation at the moment of entry
Messages that explain how to fix
No data loss when going back
Explicit confirmation before irreversible actions

Document upload

The most fragile moment of the process gained its own state, clear requirements and simple recovery.

01
Before
What is requested, why, and in which formats.
02
During
Upload progress and immediate file checks.
03
After
Per-document status and a clear action when something fails.

Review and confirmation

Before submitting, everything entered is shown in an editable summary — no surprises on the last screen.

Summary per section, editable in place
Conditions visible before submission
Confirmation with explicit next steps

Accessibility

WCAG 2.2 AA was treated as a design constraint, not as a final audit.

Contrast checked across all states
Full journey operable by keyboard
Generous touch targets on mobile
Errors programmatically tied to their fields
Reduced-motion preferences respected

Mobile first

The journey was designed for the smallest screen first, where load is felt most — and only then expanded.

One decision per screen
Primary actions within thumb reach
Progress and next action always visible

Design system

FinFlow sits on its own system of tokens and components, built to scale without losing coherence.

Colour, type, spacing and radius tokens
Form components with every state defined
Progress, status and feedback patterns
Content and tone-of-voice rules

Trust

In a financial context, trust is built through clarity — not badges or promises.

Explain each data point where it is requested
Always show what happens next
Avoid commercial language at decision moments

From initial concept to refined experience

Internal concept — not a real client

A comparison between the first internal exploration of the flow and the refined concept. Both sides are MCD Lab work — neither represents a real product.