Keep process state actionable
Status, missing requirements, and the next available action stay close enough that users do not have to reconstruct the process from memory.
Fintech product workflows
piHub
A multi-role fintech product designed around one recurring question: what is happening, what is blocking progress and what can I do next?
- Role
- Product design contribution
- Product
- Fintech product workflows
- Users
- Investors, creditors, applicants, and administrative users
Hiring evidence
What to inspect in the piHub prototypes.
The strongest proof is not visual polish. It is whether each role can understand current state, outstanding requirements, available actions, waiting, failure, and recovery without the product contradicting itself.
Change information density with the job
Dashboards can support scanning and comparison while application and verification steps reduce competing information around consequential decisions.
Waiting is a real product state
Submitted, reviewing, approved, rejected, and resubmission states receive explicit treatment instead of being reduced to a passive badge.
Share rules, not identical screens
Investor, creditor, applicant, and admin journeys can diverge where permissions or tasks differ while retaining one understandable status language.
Creditor flow
Inspect application, account, status, and credit-oriented interaction patterns.
Figma prototype for the creditor-facing flow.
Open creditor prototypeInvestor flow
Inspect role-specific information hierarchy and investment-oriented product states.
Figma prototype for the investor-facing flow.
Open investor prototypeAdmin flow
Inspect the operational side of the same product model and where permissions change available actions.
Figma prototype for the administrative flow.
Open admin prototypeEvidence boundary: these Figma prototypes are public design artifacts. The case does not claim confidential financial metrics, production conversion data, or engineering ownership.
The real friction was uncertainty, not form length.
piHub spans investor, creditor, applicant and administrative journeys. Users can be waiting on themselves, the system or a reviewer, and those states are easy to blur together. The experience needed to make progress legible without forcing every financial workflow into one generic template.
My contribution. I worked across application, credit, verification, account and dashboard experiences. My focus was status language, forms, review moments, information density, permission-aware actions and recovery paths when a process could not move forward normally.
Where the design judgment mattered.
Keep status and next action together
Users should not have to inspect one part of the screen to understand state and another to discover what they can do about it.
Change density with the job
Dashboards support scanning and comparison; application and verification screens reduce competing information when attention matters.
Design recovery as part of the flow
Rejected or incomplete states explain what changed, what remains valid and what needs to happen next.
Screens, shipped material and public references.
The artifacts sit inside the story because proof is more useful next to the decision it supports than in a ceremonial section at the end.
Experience model
Different workflows, one language for progress
The system treats status, requirements and next actions as one product problem. Shared patterns create consistency across roles while allowing the actual workflow to change when the user, permission or financial task changes.
- 01
Dashboards surface what needs attention.
- 02
Applications focus on the information required now.
- 03
Verification explains who or what the process is waiting on.
- 04
Recovery states show how progress can continue.
What this work demonstrates
Less guessing about where a process stands
The system treats status, requirements and next actions as one product problem. Shared patterns create consistency across roles while allowing the actual workflow to change when the user, permission or financial task changes.
Fintech state architectureMulti-role UXForms and recovery design