In User Interviews, ask non-leading questions.I’ve gathered important learning from each stage of the process: The work on Eager Beaver has been divided into two parts: Discover & Define stages which took relatively little time and Develop & Deliver, where I spent more time working on high-fidelity prototype. Despite the limited timeframe, I was able to make design decisions and move quickly thorugh the design process. Individualized learning goals and progress notifications What I’ve learned from Eager Beaverīeing the solo UX/UI designer for the project has had its challenges.This feature can offer a unique value propositions for Eager Beaver. A feature where users can learn only the cards they have marked as “repeat”.In order to ensure a clear structure of the app, I’ve created a sitemap, based on the user flows.Īs a design is never finished, there are some features and interactions I would like to develop futher: This step helped me keep the design user-centered, by showing me what pages or screens of the app will be needed from the perspective of Nina. I set out to map my proto-persona’s User flow. Dictionary: with option to add different languages User Flows: How would Nina add & study flashcards in Eager Beaver?.Deck overview: with study sessions, recently added cards, & cards marked repeat.Flashcards overview: with list of flashcards organized into subjects & access to other users’ publicly shared flashcards.Dashboard: with run streak and goals, recently viewed (continue learning).Primary Features: What would help Nina the most?įrom the stories, there were 4 main features of Eager Beaver that emerged: In order to move forward with the design and define the core functionality of Eager Beaver, I’ve created User & Job Stories from the perspective of my proto-persona Nina. That ensured the further design decisions stayed user-centric. With the information from the interviews, I started narrowing down the scope of the project, creating a proto-persona.