SOMA
Seacert Order Management Application
Project & Problem
The process for obtaining the certificates/keys are disastrous. You have to go through 100+ pages of instructions and make sure you follow every step. This process was stressful for both the customers and the Seacert operation team.
Here is the list of problems:
-
The process is too long
-
Making changes is too hard after the pdf form is submitted
-
Seacert operation team have to manually enter the data
-
Too many support requests
My Role
I was assigned to work on the SOMA (Seacert Order Management Application) to provide the solution to the problems stated above. I worked closely with the Product Manager, Engineering team, and Seacert Operation team to work on this project. For me, the challenge at this stage was to understand the current system and learn the technical terminologies.
Here are some of the things I learned about the current system, and the vision we have for SOMA.
-
Seacert has about 3 big companies as a client and their order takes up about 80% of the whole orders.
-
We need to approach carefully and take feedbacks from those 3 companies should be taken seriously.
-
At this point, we don't have a large number of users. Only about 8 user accounts are needed per company. Primary users are the engineers and technicians.
-
There should be a way for billing to accommodate the current billing process with the company in China.
-
Since each user deals with thousands and millions of keys, the admin user of the company needs to monitor the orders and needs a way to activate/inactivate users.
Process
I began creating wireframes by translating the current order process to what SOMA should be. I began with simple ways to make the orders and then expanded from there. The iteration process was endlessly going back and forth, and along the way, we checked with our users for feedback on the development.
Release 1
Release 2+
Mockup
