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.
Many organizations are afraid of designing and running experiments for product development. Validation of the assumption approach has not been widely spread in the industry as a standard. Hypotheses are taken as facts and they are turned into requirements and features without verification. In contrast, other companies seem to be more customer value-oriented and validate […]
Are you bored by hearing about Spotify’s Model, Basecamp’s Shape Up, or Netflix’s “No Rules Rules”? All of them do have something in common. They tailored something unique to match both their ambition and their strengths, while honestly acknowledging their weaknesses.