Key design decisions
Working within Salesforce + nCino constraints
Because nCino runs inside Salesforce as a managed package, design work focused on reorganizing existing fields, screens, and components — not building custom UI from scratch. Field placement, visibility rules, grouping, and consolidation using Lightning App Builder and safe extension patterns.
Decision log
Seven decisions, each checked against the dependency map before it shipped
DecisionWhat shippedProblem it fixedDependency check
What shippedOne Lightning page, three sections, one "validated" check each
Problem it fixedSame fields validated in 4 separate activities
Dependency checkDependency-safe to consolidate
What shippedRead-only display with a deep link to edit at the source
Problem it fixedOfficers re-entering Borrower and Product data
Dependency check12 reports, 3 Flows, 2 integrations kept intact
What shippedEmbedded Screen Flow showing each step as it runs
Problem it fixedFee statement generated twice (activities 66 and 86)
Dependency checkButton removed after zero downstream references confirmed
What shippedSingle page, default for Loan Closing Officers
Problem it fixed18 screen jumps, 3.6 min per loan
Dependency checkExisting components rearranged, no fields moved
What shippedValidated sections lock, with a logged manager override
Problem it fixedChecked data could still change later
Dependency checkEvery override recorded in the audit log
What shippedAssignment Flow reads existing officer fields
Problem it fixedManual queue assignment and cherry-picking
Dependency checkZero new data modeling required
What shippedStatus rule back on, milestone-only notifications
Problem it fixed42% status-update miss rate, 2–3 day lag
Dependency checkNotification design fixed, not automation removed