A parking lot captures unrelated questions or out-of-scope conversations during UX meetings or workshops to keep the discussion focused and maintain momentum.
Cognitive maps, concept maps, and mind maps are diagramming techniques that can be utilized throughout the UX process to visualize knowledge and surface relationships among concepts.
By placing colored dots, participants in UX workshops, activities, or collaborative sessions individually vote on the importance of design ideas, features, usability findings, and anything else that requires prioritization.
Stories build empathy and make the user needs and pain points memorable to your team. Effective stories speak the language of the audience, are rooted in data, and take advantage of compelling artifacts.
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.
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.