Research & primary design
Loan
Operations
Two loan-system surfaces: one organises product entry; the other gives application work a clearer structure.
XD preview detail: a queue-led workspace with quick search, section navigation, blank-field states, and an inactive Continue control.
Project overview
The work
behind the work.
This case brings together two artifacts from separate XD source files: a portal that groups entry routes by product and offer code, and a workspace that structures an application into sections.
My areas were UX research and primary product design across the wider loans work. The views make the proposed information architecture, blank-field states, navigation, and task sequencing available to inspect.
Decision in focus
Route into the work. Then structure the work itself.
Read side by side, one original XD preview organises product entry while the other frames an application workspace. Each solves a different part of the wider loan operation.
Portal: organise the routes in
Offer-code entry is separated from browsing. Below it, expandable product groups give automobile, mortgage and other routes a consistent shape without opening every option at once.
Application portal · selected detail from the complete embedded XD preview.
Workspace: keep section and state visible
Queue context and search establish orientation before the form. Section tabs break the application into named areas; blank fields and the inactive Continue control make the initial screen state explicit.
Application workspace · selected detail from the reviewed public XD preview.
Separate direct entry from browsing
An offer code leads with one focused task. Product groups support exploration beneath it, preserving two different ways into the system without merging their hierarchy.
Keep operational context in view
The workspace places queue identity, search and application sections above data entry. That order lets the record retain context as the user moves into a specific section.
Make incompleteness legible
Blank fields and a visually inactive Continue action make the initial state visible in the artifact. The screen does not establish validation behavior or task performance beyond that state.
My areas were UX research and primary product design across the wider loans work. The artifacts establish interface structure, not integration, launch, adoption, usability improvement or a measured business outcome.
Reflection
The constraint.
The response.
The constraint
Loan work begins before an application is opened and continues through a dense operational record. The design challenge was to make different product routes findable, then keep the application workspace readable as sections and required information accumulated.
My response
I treated entry and application work as separate interface problems. The portal groups products and offer-code access into clear routes; the workspace uses queue context, search, section navigation, blank-field states, and a visible inactive action to frame the initial application task.