Documenting UX processes and design decisions are organizational memory, so even Agile and Scrum projects that emphasize minimal documentation benefit from two cases of lightweight UX documentation.
Succinctly documenting the right details in key places helps Agile teams avoid information overload. When UX documentation is skipped or disorganized, teams waste time trying to find or remember information instead of improving the product. Documentation is too often deprioritized in the name of agility or speed. Writing things down is a critical part of thinking through your UX work and prevents your team from making the same mistakes twice. Start documenting the right types of details now to move faster later.
This presentation explains how Wardley Maps were used to inform the always evolving strategy for the modernization of Ticketmaster’s core ticketing platform not only in terms of technical capabilities and architecture but also process maturity, organizational design, and more.
Analytics and Quantitative Usability Testing UX research techniques help you gain quantitative insight into user behavior. However, each method provides different types of information and can answer different kinds of research questions.