User Interview, Desktop Research,
Visual Design, Usability Test
Wireframe, High-Fidelity Prototype,
User Testing Report
We conducted one-hour interviews with 3 lawyers and one judge.
In order to identify lawyer's needs, we gathered information from the interview to understand the current BC court order system.
Four lawyers are from different law firms and specific studies to avoid bias.
The current process is all done in print, with ink signatures, and transfers of documentation is done by courier.
It took us 2 weeks to conduct research and understand the current user flow of court order system. Though we foreseen the inefficiencies that exist among the lawyer's cooperation with stakeholders like clerks, judges and clients. Considering the time limitation that we only had 1.5 months to implement the project, our design was focus on drafting a hearing order to the stage of getting approval from opposing lawyers.
Lawyers can use the custom search bar to find cases, clients and court orders that are already stored in the portal efficiently, and use filters to sort by case name, due date.
Lawyers can create new templates of court orders, clients and cases with a click of a button and input data into labelled fields. The system stores all information in an organized way.
Create a custom progress timeline to track where client/case is at. Lawyers can create a status and input notes so they always know where to pick up where they left off.
Once the opposing lawyers update any information of the court order, the timeline is also in sync.
Lawyers can send a drafted court order digitally to the opposing lawyers. Opposing lawyers who are not currently using the system will receive an email notifying them that they have a Court Order waiting to be approved and signed. When they wish to take a look at the document, they click in the email and a text verification code will be sent to their mobile device. Once they enter the code, access will be granted.
After we narrowed down the main ideas for creating the prototype, we conducted user testing with two lawyers to evaluate our ideas. Also, because it was also a learning experience of our school projects, we were tasked to have user testings with cohorts and faculties.
Our objective for tests were to:
1. To determine ease of navigation and functionality for specific tasks.
2. To identify proper usage of legal terms.
3. To gain feedback on recommended improvements.
The test was done on a low fidelity interactive prototype. The users were provided with the specific scenarios tasks to navigate with the website. After completing the tasks, the testers were asked to complete a post-test questionnaire. Then we also had an end-of-session interview.
The inefficiencies that exist within the current legal landscape are not limited to the court order process, Coform is just the beginning of a system for lawyers to manage and file court orders with the opposing lawyers. For the next step, there is still the opportunity to expand the platform into a full-fledged organization and communication tool among lawyers, their clients and the judiciary to modernize the court order system.
It was the first time for me to design a CRM system, except to keep the efficiency of design in mind, to think about the needs of everyone who will use the software is also important, not only because it would ensure the fast communication between different parties, but also it might refer to privacy and security issues.