DOTA 2 is a multiplayer online video game that has around 0.8 million players in the world. In this project, I designed a mobile app with an aim to help players can effectively understand their performance, and ultimately improve their skills.
Discovery phase consisted of me asking many questions to clarify the project. Based on the information I discovered, I defined problem, goal, and success metrics. This helped me clearly see the direction I am heading. After that, I sketched out ideas until I find a promising one, then moved to my laptop, where I created lofi and hifi wireframes.
First thing I did was to fully understand the project by talking to my PM and collecting as much information as possible. This helped me discover the context of the project, problem, target users, requirements, and deadline. Through the discussion, I learned that our competitors provide useful data, but often times it’s overwhelming, and users prefer to see a cleaner platform that provides only relevant data. However, we were missing research data so, I decided to conduct quick quantitative research to validate the problem. Through the research, I found out that the hypothesis was wrong. Users actually love seeing an overwhelming amount of data because it ensures that the website has in-depth data that users can find any types of information they seek.
I curated my findings into 2 UX artifact; persona and journey map, which were extremely useful to present my findings to the team.
How might we help users navigate through a tremendous amount of data so they can quickly find the information they are looking for?
Defining success metrics is important as it helps everyone in the team to have a mutual understanding of what success looks like. In the project, we defined our success metrics to be the improvement of the speed users complete their tasks.
I believe, during the ideation, more people you have, the better ideas will be. Since I was the only designer in the team, I looked for people who are free in the office to brainstorm ideas with me. I presented the journey map I created based on the user research, which helped us identify and strategize for key moments in the product.
I organized ideas we came up with in the ideation session into a sitemap. I then had a meeting with my PM to make sure whether they are all feasible or not. Based on the discussion, we decided what will be in 1st iteration and what will be in our future iteration. This was one of my crucial steps in the process because by communicating with dev at this time of the process, I was able to understand the technical constraints. For example, dev pointed out that some of the info is impossible to get considering the timeline we had, so I revised those features before actually sketching out how it will look like.
Based on the discussion we had, I then sketched out how the feature might look like. Then, I turned the sketches to lo-fi, and to hi-fi.
So, how is this solving the problem we defined? Let me explain:
As a future step, I will be collecting data from Firebase because data is crucial as it informs how real people in the real world are using the product. Based on the data I get, I will be refining design goals, and improve upon.