Objective: Build a financial product users rely on by transforming data into Agency, Trust, and Velocity.
Agent Use
Use this file as a light UX policy layer when the task involves copy, tone, trust, financial anxiety, drop-off reduction, declined states, success states, or layout refinement without a fully specified design.
This file does not replace a completed Figma design. It helps choose the intent behind a variation.
When To Use
- The user asks to refine a layout for trust, urgency, clarity, or conversion.
- The user asks for vibe-coded UX or a new target-user variant.
- The task touches declined, success, verification, reactivation, or stalled-user moments.
- A design file exists but copy or behavioral emphasis is unresolved.
When Not To Use
- The task is a direct design-to-code implementation of an approved design.
- The task is only route wiring, component export cleanup, or token sync.
- The requested change is purely visual and already specified by Figma.
1. Strategic Pillars
Pillar I: Reducing Post-Approval Dissonance
- Target: Window Shoppers & Hesitant Applicants.
- UX Intent: Validation. Shift the UI from "Selling" to "Confirming."
- Logic: Use a Commitment-Consistency UI. Remind them of the why, such as consolidating high-interest debt.
- KPI: Reduce Prime Funding Lag from 3.4 days to less than 2 days.
Pillar II: Velocity for the Vulnerable
- Target: Second-Chance Seekers.
- UX Intent: Relief. Minimize cognitive load and interaction cost.
- Logic: Prefer instant verification patterns and reduce manual fields wherever the approved flow allows.
- KPI: Maintain less than 24-hour funding capability.
Pillar III: The "Bridge to Yes" (Rejection Logic)
- Target: Aspiring Borrowers.
- UX Intent: Advisory. Pivot from a hard no to a not yet.
- Logic: Show a next best action, improvement path, or eligibility delta when available.
- KPI: Engagement with financial education or credit-building tools.
2. Segment-Aware UX Logic Matrix
| Segment | Primary UX State | Design Principle | Feature Priority |
|---|---|---|---|
| Prime/Good | The Professional | Efficiency & Clarity | ROI Calculators, Rate Comparison |
| Near-Prime/Fair | The Partner | Growth & Encouragement | Milestone Trackers, Credit Health |
| Subprime/Poor | The Provider | Speed & Simplicity | Instant Verification, SMS Status Updates |
| Pipeline/Stalled | The Re-activator | Progressive Reveal | Chunked Forms, "Pick up where you left off" |
3. Agent Decision Rules
| Situation | Use intent | Design rule | Copy rule |
|---|---|---|---|
| User is approved, qualified, or comparing | Validation | Show clarity, value proof, control, and next-step confidence | transparent, benefit-led, low pressure |
| User is urgent or vulnerable | Relief | Reduce field count, reduce reading load, make the next action obvious | calm urgency, plain language |
| User is declined or near-miss | Advisory | Show next best action and progress path | "not yet", supportive, specific |
| User is stalled or returning | Re-activation | Use progressive reveal and resume cues | familiar, encouraging, action-oriented |
4. Global Design Standards
- Information Architecture: Lead with benefit metrics, such as debt reduced, rather than anxiety-heavy debt framing.
- Visual Language: Use stable blues and greens. Use amber for declines to signal work in progress rather than stop.
- Copywriting: Use Active Agency voice: "Check my rate" instead of "Submit Application."
- Validation: If a UX strategy changes the supplied design, state the reason and ask for user approval when the change is structural.
5. Business Goal Alignment
Our UX strategy aims to move the product from a Lender to a Financial Partner. By designing for the "Long Shot" and the "Window Shopper" with equal intentionality, we build a reliable ecosystem that users return to as their financial situation improves.