commercial lending • greenfield product • evolving scope
Credit360
Navigating changing requirements without losing a coherent product model.
Credit360 is a greenfield platform digitizing the commercial lending workflow from transaction initiation through credit approval. I led the design of One Memo, the experience used to assemble and review lending information across that workflow.
Role
Lead Product Designer
Timeline
Jun 2025 - Present
Status
UAT • In Progress
01 • So what was the problem?
I designed for one segment, then the scope changed.
I initially designed One Memo for a single lending segment (Corporates). After sharing the design, the scope expanded to three segments with different loan types, data requirements and user needs.
Why initial design didn't work anymore
Built specifically for Corporates workflow
Using one information structure
Did not account for other segments and different loan types
The design question
How can One Memo support three segments
without showing everyone everything?
02 • Redesigning One Memo for variation
Same core structure designed for different needs.
I restructured One Memo with a shared structure and segment specific modules, so it can adapt to different needs without duplicating the entire experience.
Before: Corporate -based structure
After: Modular multi-segment structure
03 • key decisions
01
A shared core for all segments.
constraints:
The three segments shared some information, but required different input and analysis.
options considered:
Separate memo for each segment
One universal memo with every field
C. Shared core + controlled variation
outcome:
The final structure keep shared information stable while allowing segment-specific modules to change.
02
Let the loan request type guide the memo.
constraints:
Not all loan request types use the same One Memo template.
options considered:
A single template for all loan requests
B. Conditionally enable necessary steps from shared workflow
outcome:
Depending on the loan request types selected in the beginning, the system allows users to bypass irrelevant steps, creating seamless experience.
03
Allow users rebuild the memo.
constraints:
Even with the standardized template, some deals need ad hoc analysis we can't account for in advance.
options considered:
Hardcode all possible inputs
Make users attach ad hoc analysis as an attachment
C. Create modular structure where user could modify the One Memo layout and inputs
outcome:
By default, One Memo will show the standardized One Memo template (based on the user segment), and allow users to modify the detailed sections and pages as needed based on the deal requirements.
04 • Outcomes
What did the new design enable?
3x scope.
Successfully expanded scope from the initial 1 segment to the 3 segments.
1 structure.
Standardized 6+ different types of templates across all the loan type and segments.
42% efficiency.
Selected user groups have reported memo process has been significantly quicker with the new One Memo.
05 • reflection
What I'd carry forward.
Late business context and scope changes cannot always be prevented. This project reinforced the value of defining what must remain stable and where the product should be able to flexible, so new requirements can be absorbed without fragmenting the experience.