Technical Area: I learned a lot about the overarching topic of UX design, including what constitutes good design vs bad design, how usability and aesthetics factor into the design process, and building task flows. Delving further into the field, I learned about competitive analysis as a tool that can be used to understand users by identifying competitors and dimensions. We also discussed how design thinking is an essential mindset while working in UX. It was interesting to learn that it is non-linear in nature, and that it essentially weaves together the steps of empathizing with a user, defining the issue, ideating solutions, creating prototypes, and undergoing testing. Understanding the different types of user research as well as conducting that research is also essential to UX design, and we particularly focused on the importance of user interviews and card sorting as tools for gathering feedback. Another technical topic I learned about was affinity mapping, which allows one to organize and cluster several ideas in a collaborative manner. It works by gathering individual data, clustering similar topics, and then identifying themes under a broad goal. We also looked at the process of ideation, which involves developing and brainstorming new ideas. In particular, we looked at “how might we” statements, dot voting, and impact-feasibility matrices as tools to help the process of ideation along. In terms of more technical topics, we looked at user flows and information architecture. User flows were especially helpful because it became easier to see the user’s movement while interacting with Stemaway. Learning about information architecture also helped me understand the importance of building a structure that facilitates our understanding of ourselves as users and our position with regards to the information we are working with.
Tools: We used tools like Miro, which is essentially an online collaborative whiteboard platform. Miro allowed us to work efficiently in teams and virtually use sticky notes to organize our thoughts and ideas in terms of constructing affinity maps, user flows, and information architecture. We also started using an organization tool called asana, which helps us keep track of the tasks we’ve completed, need to complete, and are in the process of completing.
Soft Skills: I learned several soft skills over the course of these few weeks, including collaboration and communication. My collaboration skills have been put into practice extensively as I meet with my team, discuss ideas almost every day, and work through different design solutions. Working with different people and interviewing users to gather information has honed my communication skills, especially since I have had to learn how to communicate UX ideas in layman terms.
- I was able to conduct two rounds of user interviews which helped me truly grasp an outsider’s perspective on Stemaway and harness information that allowed an insight into what aspect of the Stemaway interface needed improvement.
- I also conducted another form of user interview called card sorting, which allowed me to observe the user’s thought patterns and intuition with regards to my specialization of the platform (the taskbar).
- I helped construct a good portion of the affinity map that later became the basis for our core problem.
List of Meetings:
- Introductory Meeting - June 1
- Meeting 2 - June 2
- Meeting 3 - June 3
- Meeting 4 - June 5
- Meeting 5 - June 8
- Meeting 6 - June 9
- Meeting 7 - June 10
- Meeting 8 - June 11
- Meeting 9 - June 15
- Meeting 10 - June 16
*These meetings included larger meetings with my UX team, and smaller, collaborative meetings with my subgroup to work on our project.
Goals for the upcoming week:
- Learn to use the figma platform and incorporate it into my work.
- Take more initiative in introducing my ideas to the group and make an attempt to collaborate further.
- Get more involved with asana so as to keep myself on track and paced.
- The first task was affinity mapping, and we received some help from our team leads in the form of asking questions and referring to training webinars. Some hurdles included some conflict over how to cluster different ideas and what subgroups/hierarchies to create, and we solved this by discussing the similarities and differences between each group.
- The second task was conducting user interviews about the general experience of interacting with Stemaway with one user from the other subgroup and one user who was not familiar with Stemaway. We used training webinars and instruction from the leaders to get a broad idea of which direction the interview was supposed to go. Some hurdles included figuring out what type of questions to ask, directing the user who wasn’t familiar with Stemaway so that they didn’t encounter issues, and communicating the different questions clearly. We resolved these issues by studying videos that directed what an ideal user interview would look like.
- The third task we undertook involved brainstorming different solutions to a variety of “how might we” statements that we came up with and then using dot voting and impact-feasibility matrix to further evaluate those solutions. The hurdles in this task included actually coming up with enough solutions to cluster and weighing the pros and cons of solutions against each other. We solved this hurdle by allowing ourselves ample time to brainstorm the solution and then reconvening to discuss those solutions. Again, we used training webinars and some help from the leads in order to accomplish this task.
- The fourth task we participated in was constructing a user flow diagram for the Stemaway taskbar. Hurdles included identifying the exact number of steps/clicks that a user would need to take to their destination and understanding which steps were conscious user decisions. We solved this hurdle by repeatedly testing out the taskbar ourselves and drawing observations from there. We referred to training webinars to assist with this task.
- The fifth task involved conducting a card sorting interview with a user who wasn’t familiar with Stemaway. One hurdle included identifying which terms were relevant enough to include in the sorting itself, and we resolved this hurdle by looking at which taskbar features we personally felt were the most significant. We used training webinars to assist with this task.