SmartStop

User Research

AS-IS MAPPING

In order to understand the users exact pain point during the entire journey, I created two as-is maps of the users thoughts, feelings, and actions. Since the problem was two-pronged, there were two possible ways a user might chose to come into the problem space.

Doing this allowed me to identify where in the users' life the solution would fit into. I found that the solution created would have to be quick and easily navigable, with little onboarding. Since the user is approaching the application from a place of frustration, it is imperative to reduce that with as little user input as possible.

Waiting in line flow

Finding parking flow

PERFECTING PERSONAS

In order to identify how the application will fit in with the lifestyle and practices of the user, I created user personas of the target users. The two user personas helped formulate the paths a standard user would take and determine where the two types of actions would cause the path to diverge.

Since Esther’s problems are geared towards calculating line wait times, determining the optimal time and route to take to arrive at a location by a specific time, this user persona was used to determine the potential constraints that she may face when navigating the application.

Jacob's persona focused on using the application to plan ahead and find parking spots- his persona helped determine the finer points that the application would address and how to incorporate it with the rest of the platform.

HOW MIGHT WE MAP

After identifying the place in the journey the user would be most affected, I began ideating potential problem areas that could be addressed through a How Might We Map (click here to view). This was done to create a frame around which I would solidify my ideas- by having the outer boundaries of what the solution would encompass, I knew how far in the problem space to ideate for.

Doing this helped me put out all of the possible ideas that could be implemented into the solution area, and then break it down into what would work as an MVP feature compared to what would be less important. Instead of immediately considering feasibility, I was able to put down any idea that could solve the problem.

MOSCOW PRIORITIZATION

In order to lay out the functional requirements of the application and gain a full understanding of what the project entails, I made a MoSCoW Prioritization chart (click here to view) in order to relate all the various aspects of the application together.

After coming to an understanding of initial features, I used this to make a value by feasibility chart to come up with the worthiness of implementing each feature into the application. Doing this filtered the ideas that were most relevant to the problem at hand and allowed consideration for what should be included in the minimum viable product. During this process I found that some features such as recommending an optimal entry- way into a location diverged from the original purpose, and removed it during the mockups.

Ideation

WIREFRAMES

Upon ideating what features to include, I drew out these initial wireframes to go through the flow of how they will be laid out, using usability heuristics to guide the layout. This was done to get a better understanding of the whole user flow, and how each part would fit together.

This created the base for the UI of the application. It informed me where to keep room for icons, what content should be present, what images and taskbar to use, and how I wanted notification screens to appear based on certain commands.

Wireframe of the first part of the app experience

Wireframe of the second part of the app experience

Wireframe of the third part of the app experience

Wireframe of the fourth part of the app experience

MOCKUPS AND TYPOGRAPHY

In order to begin the visual design process and set out a sitemap for how the application would be structured, I created medium fidelity mockups to illustrate where example content would be, the hierarchy of the headings compared to the text, and what images would need to be sourced. I also set out the the typography and colours for the design

This set the base for what would become the final version of the application. I was thoroughly able to create an understanding of the core flows to employ, and how to best display the information required for each of these flows. I set out the primary and secondary buttons to use, as well as designed the main selection screens.

Hierarchy of text and the colour scheme used

Onboarding

The onboarding process is a way to introduce new users to what SmartStop offers, provides them with a change to setup their initial information, and gives them a run through of important functions in the application. Here, I have chosen to focus on the searching and viewing of a location during the onboarding so that any potential user has a chance to utilize the application for its core purpose right off the bat.

Add Conditions

Due to the community-based nature of the application, users will have to contribute information regarding the current conditions of locations they are at. They will be able to search through both locations, and parking lots to find the one they are looking for and add both numerical and general information about the current conditions. If a location does not currently exist on the map, the user will be able to manually add it in.

Search

When looking to depart to a destination, users can use the Search function to find the current wait times/space at the location. This also presents them with directions to the locations, and then prompts them to add information about the locations current information to help future users.

Create Alert

Instead of simply looking at current conditions, it is also possible to plan trips in advance, whether alone or with friends. Users will select a location, date, indicate the possibility of repetition, and will be allowed to invite friends to the trip as well. Each confirmed trip will have its own screen where each invitee’s status can be seen, as well as allow for changes to the trip’s information. The prototype also allows for a view of the notification the user will get prior to the time of departure.

What did I learn?

BRAINSTORMING TECHNIQUES

Since this was my first design project, I focused on understanding how to go from the brainstorming stage to a cohesive application prototype. I learnt how to use various brainstorming techniques, and compiling my ideas while bringing it back to the original user needs before narrowing down on one final idea. I explored various brainstorming techniques to understand the benefit each of them brings to the ideation process.

FUTURE SCALABILITY

In the future, it will be possible to improve the current model by incorporating user testing, and evaluating what processes currently work, what could be improved on, and deciding if any should be removed.
Future versions can look at implementing an incentive based system for members to add information regarding locations, either within the application using a tier based membership system or in conjunction with a third party application offering rewards.
It can also offer data for certain dates and times based on historical data to offer better preparedness for users, but this would require the application to be in circulation for enough data to be gathered to predict trends.

Managing traffic in local roads, parking lots, and popular areas

Personal project case study

Problem

Solution