Retrospectives are a dedicated time to come together, reflect, and collaboratively improve your design team’s process. In this video, we'll walk through the four components of a retrospective and how to use this meeting effectively.
Journey maps are useful for building common ground in an organization, but practitioners often have questions and misunderstandings about their scope and how to create them.
User need statements, also called problem statements or point-of-view statements, are a tool for defining and aligning on the problem you are going to solve.
Retrospectives help teams reflect on their process, identify strengths and areas to improve, and turn insights into actionable plans for better future work.
When conducting research for customer-journey maps, use qualitative methods that allow direct interaction with or observation of users, such as interviews, field studies, and diary studies.
How storyboards fit within the UX design process, and the steps needed to make a successful storyboard to visualize a workflow, customer journey, or user story.
As a facilitator, it’s your responsibility to make sure the time spent in workshops is as productive as possible for attendees, while at the same time ensuring that you get the insights you need in order to move your project forward.
The majority of UX and design professionals define design thinking roughly the same, regardless of industry and experience, but there’s no agreement on the specifics.
Like tech debt, UX debt piles up over time and, if left unaddressed, leads to compounding user problems and costly cleanup efforts. Agile teams can modify their processes to track and resolve UX debt.
Formative usability testing is best done with a small number of study participants, so that you have time and budget to test more design iterations of the user interface.
