PAYLOCK
A company that focuses on community parking in areas such as residential neighborhoods, universities, apartment complexes, parking garages, etc. where parking permits are necessary. Paylock serves as a platform where a user can purchase a parking permit and, on a larger business/authoritative scale, manage parking permits for multiple people.
MY ROLE
Redesign a user portal that can accommodate a variety of necessary documentation that simply clarifies the permit status to a wide range of user personas - especially those who are not as tech savvy.
TIME FRAME
1 Week
BEFORE
Before, the user portal presented a chart that showed room for improvement in navigation, information concerning each permit and how to reach that information. Prior to redesign, many users would face the problem of not knowing what they were looking at. The page has the option to sort the chart by the given categories but people didn't know how to do that if they even knew that was an option. Also, If you wanted to see why some of the permits were pending, and clicked on the info icon, instead of a tool tip popping out to the side it would take you to a totally new page for document information. Some user's account may show one car, and another account may show hundreds of cars in their permit section. Users would need clarification on which specific permit they were looking for and simplifying the process of finding a specific permit and finding out which documents are necessary in order to activate that specific parking permit.
MY GOAL
Create a seamless dashboard that would organize each permit by it's type. The interface needed to be able to show the genaral majority of the permit information without being overbearing while clearly showing which permit was being shown and it's status.
It is also my focus to create a cohesive experience throughout the process from registering for a new permit to updating an existing permit.
AFTER
Left drawer navigation that host actions such as searching specific permits, filtering a view and adding a new permit. There is also a key showing how many permits are pending or expired to efficiently manage permits and clarify the overall status at scale.
Sectioned categories to view all general permit information in one interface. One of the most commonly viewed information is the visitor code which has it's own emphasized section with clear call to action such as to share, refresh, and copy.
One thing I think that I would change with this UI is the Visitor Code section. I would scale it down a bit and trim the information- making it an overall smaller section that could expand when the user tries to change the information with the visitor code.
Adding a new permit.
Documents
This page is accessed when you click the view documents button, when adding a new permit or account, and if the permit is not yet active and is pending due to missing documents, that information will be shown on the permit details page (above) in the top section, which from there the user will reach this page and be able to see and provide necessary documentation in order to activate the permit.
Sections of the documentation process have been bucketed into categories such as permit documentation, vehicle documentation, and residence documentation. Because depending on which docuements the user is able to provide, there is a variety of options and variations in which documents must be provided. This was how I solved the problem on informing the user of the different scenarios of how to provide their documentation AND notifying the user about the status of the information that has been uploaded (approved missing info, declined, pending review).
Uploading files / documents.
Selected Works
JobNimbus Mobile AppProject type
DOMO Goals AppProject type
PayLockProject type
Alliance CounselingProject type
AssembleProject type
GOJIProject type