CASE STUDY
CASE STUDY
Stipulation Manager
Project Background
In the process of applying for an advance, Customer submits a set of required documents needed to start processing the application
Documents are reviewed/handled by different teams (Prequalification, Processing, Sales, Closing, Underwriting)
All groups have access to Salesforce as the source of truth for any Customer information
Business decision was made to remove Salesforce access for user groups that primarily work in other applications (Prequalification, Processing, Underwriting, Closing)
My Role
My role was to redesign the current Stipulation Manager into an independent component that can be used in any other application.
Design Process
Design Considerations
Five distinct groups with distinct sets of functions will use the component
Prequalification team: upload documents, preview, delete
Processing team: upload documents, assign tag(s), preview, delete
Underwriting team: upload documents, review, download, assign themselves as reviewers, accept/reject a document, request a new document, add notes to a document, sign off on all documents
Closing team: upload documents, review, download, assign themselves to a document, assign a status to a document, accept documents
Sales team: upload documents, preview documents, view stipulation status
The current system cannot serve custom UI
The information needs to be arranged in such a way to serve each of the five groups in an effective way without much customization
Features that existed in Salesforce need to be transferred to the new component
Application processing is mostly linear
The features of the component will build up as the stages of the application advance through the flow
Enhanced Stipulation Manager will be embedded in an iFrame
Any modals can only take up the size of an iFrame (iFrame cannot control it’s parent window)