Case Study
TI Credit Report
Role
Lead UI/UX Designer
Duration
36 Months
Domain
FinTech · Credit Intelligence
Team
Solo Designer
Context
The Platform
TI Credit Report is an enterprise credit intelligence platform serving banks, financial institutions, and lending teams. Its primary users are bank managers and financial analysts who process hundreds of credit applications per week.
Every workflow, every data point, and every UI state has a direct impact on whether a loan is approved or declined. Clarity isn't a preference here — it's a professional requirement. Errors carry financial and reputational consequences.
The redesign had to earn trust through precision, not novelty. Every decision was made against the backdrop of regulatory obligations and the expertise of domain professionals who would notice any misstep.
Platform
Enterprise Credit Intelligence
Users
Bank Managers, Financial Analysts
Scope
150+ Screens, 4 User Journeys
Stakes
High — Lending Decisions
Problem
What Was Broken
The legacy platform wasn't just outdated visually — it was actively slowing down banking professionals. Three compounding failures caused friction at every step of the credit lifecycle.
01
Static Long Forms
Monolithic forms with 40+ simultaneous fields caused high abandonment and input errors. Analysts had to hold too much context in their heads to complete a single workflow.
02
Unstructured Data Reports
Credit reports were raw numerical tables with no grouping, no hierarchy, and no insight surfacing. Extracting a single meaningful data point required significant manual effort.
03
Cognitive Overload at Scale
Users processing hundreds of applications weekly faced decision paralysis. The interface demanded maximum mental effort for minimum output — unsustainable at operational scale.
The Real Challenge
Why This Was Hard
The problem wasn't bad UI — it was that simplification was genuinely constrained. Four factors made every design decision load-bearing. Getting any one of them wrong would have broken the product.
Challenge 01
Regulatory Compliance Was Non-Negotiable
Every workflow had to satisfy enterprise compliance frameworks, financial regulatory requirements, and legal audit-trail standards. UI patterns that reduced steps could not, under any circumstance, compromise data integrity or break compliance trails.
Challenge 02
Legacy Infrastructure Locked the Design Space
Fixed API contracts and aging backend systems meant I had to design within existing data structures. No new endpoints. No redesigned payloads. Every visual simplification had to map to a data model I couldn't change.
Challenge 03
Users Were Domain Experts, Not Novices
Analysts and bank managers have years of domain experience and deeply entrenched mental models. Over-simplifying for general usability would have slowed them down. The design had to match their expertise — not flatten it.
Challenge 04
Zero Tolerance for Ambiguity
Credit decisions carry financial and legal consequences. Ambiguous UI states, unclear validation, or misleading data visualizations were not acceptable failure modes. Every interaction had to be unambiguous under pressure.
My Approach
How I Solved It
Each decision below was a deliberate trade-off — not a preference. I had to choose what to simplify, what to preserve, and what to restructure entirely.
Decision 01
Progressive Stepper Forms
I replaced monolithic form layouts with a contextual stepper. The decision was to chunk the workflow by task intent — not by data category — so each step only exposed fields relevant to that stage.
This reduced perceived complexity and maintained compliance because every field was still captured — just sequenced around how analysts actually think, not how the legacy system stored data.
Decision 02
Dashboard-Based Reports
I restructured raw tabular credit data into structured, scannable dashboards. The key decision was to elevate insight over completeness — score indicators, trend charts, and segmented panels surfaced what analysts needed to act, not everything the database returned.
This worked within the fixed API contracts: I reorganised existing data fields visually rather than requesting new data structures.
Decision 03
Data Hierarchy Optimization
I established a strict visual hierarchy across all data-heavy screens: primary metrics at the top, secondary context in the middle, granular detail accessible on demand. This wasn't a style choice — it was an information architecture decision.
The challenge was that expert users still needed access to all the underlying data. Progressive disclosure preserved completeness while reducing the default cognitive load.
Decision 04
Building for Scale, Not Just the MVP
From the start, I chose to invest in a design system rather than screen-by-screen execution. This was a strategic bet: the platform was scoped at 25 screens but I could see it would grow. A unified component architecture was the only way to scale without design drift.
Role-Based User Journeys
Four distinct journeys — analysts, compliance managers, bank partners, consumers — each designed with tailored hierarchy matching their domain responsibilities.
Scalable Component Architecture
A unified design system that scaled from 25 to 150+ screens across all user journeys without visual or functional inconsistency.
Guided Multi-Step Workflows
Credit workflows restructured as stepper flows with contextual validation — matching how banking professionals actually process applications.
Wireframe-First Information Architecture
Every screen was mapped as a low-fidelity structure before any visual work. This uncovered hidden workflow complexity before it became expensive to fix.
Before vs After
Legacy vs Modern
The same task — submitting a credit application — went from an overwhelming wall of simultaneous inputs to a structured, guided multi-step flow.
Before — 40+ simultaneous fields, no hierarchy
After — Progressive stepper with structured hierarchy
Impact
Measurable Outcomes
Outcomes validated through post-launch usability studies and stakeholder feedback across the banking teams using the platform daily.
40%
Faster Task Completion
Credit workflows that previously took analysts an average of 18 minutes were reduced to under 11 minutes through progressive disclosure and smarter task sequencing.
150+
Screens Shipped
A single, unified design system scaled from an initial 25-screen scope to cover all four user journeys — analysts, managers, bank partners, and end consumers.
60%
Reduced Cognitive Load
Post-launch usability studies measured a 60% reduction in decision errors and user-reported mental effort — attributed to improved information hierarchy and progressive disclosure.
Trusted by Banking Analysts Nationwide
The redesigned platform is used by bank managers and financial analysts to evaluate creditworthiness and make high-stakes lending decisions at scale — daily.
Complex Workflows Made Navigable
Dense reports and monolithic forms became structured dashboards and stepper flows that match how analysts actually think — not how legacy systems stored data.
Design System That Survived the Team Growing
The component architecture and token system I built absorbed 6× scope growth — from 25 to 150+ screens — without visual drift or inconsistency.
Compliance Maintained Throughout
Every simplification was validated against regulatory requirements. No workflow was streamlined at the cost of audit-trail integrity or data accuracy standards.
Shipped — Desktop Screens
Shipped — Mobile Screens
My Role as Lead
What I Actually Did
As the sole designer on this engagement for 36 months, I wasn't executing a spec — I was making the decisions. Every choice about structure, hierarchy, workflow, and scope came from me. That required navigating regulatory constraints, legacy infrastructure, and expert stakeholders simultaneously.
Set the UX strategy for the entire platform — defined which problems to solve first and why
Decided to invest in a design system from day one, before scope justified it — a call that absorbed 6× growth without regression
Mapped four distinct user journeys from scratch: analysts, compliance officers, bank partners, and consumers
Resolved the tension between compliance requirements and usability — finding the minimum friction path that still passed regulatory review
Managed design reviews directly with product managers and engineering teams without a design manager above me
Designed 150+ screens across desktop, tablet, and mobile — all within a single coherent system I built and maintained solo
Next Case Study
RMT Holotrack
Industrial IoT · Spatial Data Visualization