


My Legal Pro Trading
Lawyer App Desktop
Project type: Improvement
Designing intuitive solutions: Simplifying the process of creating new cases
My Legal Pro is an Australian legal tech SaaS platform that provides integration services for the legal process of property transactions between various stakeholders such as lawyers, clients and agents, by increasing the ease of fast, transparent and real-time administration.
Problem Statement
Based on user feedback, we found that the process of filling in new case creation in the application faces several pain points. Among them are a long and time-consuming process, quite a lot of data columns to fill in.
How is the Data Structure?
I conducted an audit to the current flow of create new case. Create new case has 2 separate flow which is individual & non-individual.
Image : Create new case. Old diagram
Old create new case flow only focusing on individual entity. And in this project there will be a flow update for create new case flow which has 2 separate flow which is individual & non-individual.
Image : Create new case diagram
So we can conclude the scope of projects are
Project Goals
Simplifying user flow of create new case. To simplify the flow, I identify the mandatory field & optional, confirm this with project manager
Additional flow for property agent data
Update the UI & design style accordingly
Update the flow as per new requirement : Individual field & non-individual
Old Interface & Flow
In this old interface, the process creating new cases is should be a stepper, that insist to :
Case details
Client details
Review section
This has quite a lot of data to add and it is quite time consuming to complete this task.
Create New Case | Case Details
Create New Case |Client Details
Create New Case |Review Section
I got a solution how might we make this stepper is replaced with tabbing so that the user can skip one optional page and can continue to the end. To ensure which optional fields, I communicated with the product manager and internal lawyer about what is optional and can be skipped
Designing the Interface
Initial Form State
Case Details > Seller
Seller is a person or entity who wants to sell their house or property. The difference between seller and buyer are original purchase price and caveat letter
Case Details > Buyer
And buyer is a person or entity who wants to buy a house or property by their own. Buyer form doesn’t have caveat and original purchase price field,
New Case Has Been Created
After filling up new case form, user can save the case immediately and can move to other tab either to filling up client details agent details, or direct to review tab (skip the client & agent parts). In this new flow, it allow user to skip client & agent section.
Client Details > Seller > Individual
For individual category, it has client’s identity form refers to a personal who own the property
Client Details > Seller > Non-individual
Non-individual category has company & trustee form, it refers to a PIC of property. It uses for e.g office or property of business.
Client Details > Buyer > Individual
Non-individual category has company & trustee form, it refers to a PIC of property. It uses for e.g office or property of business.
Client Details > Buyer > Non-individual
Non-individual category has company & trustee form, it refers to a PIC of property. It uses for e.g office or property of business.
These client details form are optional, so lawyer as a user can skip this step and continue to agent details form or even direct to review section
Agent Details Form Interface
Review Page Interface
On this review page, we have 3 tabs, namely the review session for
Case Details
Client Details
Agent Details
Additional requirement during this project: Share Case Flow
In this project, I got some additional requirement came from higher stakeholders, new cases that has been created can be share to other lawyers.
If there is already a list of other lawyers in the user account, then a list of other lawyers will appear when the user wants to share case access.
User can select multiple person to add to the new case
Case has been shared successfully
Lesson Learned
User Feedback
This project is based on user feedback that feels that the current task flow is too long. So we brainstorm and try to find and formulate what pain points the user experiences, as well as what data can be skipped or what data must be there when registering a new case.
A very important lesson here is openness to feedback and criticism as a UX/UI designer, because in reality the product development lifecycle is a continuous iteration process. There will always be feedback and input to improve the product, user experience and most importantly the UX designer himself.