Who is this user? Where are they from? What are they doing when they run into this problem?
Lean user testing to start empathizing with the user, and their needs. Interviews with existing customers? Surveys? Card sorting? Competitive analysis? Discover and explore
Validate or invalidate assumptions, the hypothesis and even initial requirements.
Include engineering, PM and all stakeholders early on for input, but keep UI and visuals out of the conversation.
Balancing basic needs & behaviors of users, coupled with functionality & in turn, informing MVP.
Cross functional conversations regarding feasibility of functionality & data
Aligning user centered design and experience with business goals.
Sketch out basic UI and navigation, either from a design system or component library or from scratch.
Sketching, prototyping & continually evolving the approach.
Get feedback from my fellow designers, scrum team & early rounds of user input.
Document key interactions, feature behaviors, solidify workflows and UI elements.
Delivery to engineering will most likely be incremental depending on the sprint schedule and level of effort/resources, but an overall complete set of workflows and interactions is key.
Documented and delivered all UI and interaction artifacts using a combination of tools including Figma, Sketch, Adobe XD, Whimsical & HTML/CSS/JS.
What worked? What didn’t? What do the numbers show vs. what are users saying?
Are we solving the problem initially defined? If V1 isn’t performing as well as assumed, what are the next improvements to address?
Analytics can provide initial insight into how a new feature or product is performing, and sometimes in-product surveys or post-release customer interviews can provide additional qualitative data, and give insight into future improvements.