View the original post
Summary: 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 of work processes and design decisions is a form of organizational memory : it prevents teams from running around in circles — repeating mistakes or simply arguing over the same topics again and again. A challenge faced by UX practitioners working in Agile is the notion of minimal documentation — in an attempt to work fast, teams stop writing down important information. Alternatively, too lengthy documentation runs the risk of being ignored. In either case, the result is time wasted to recall information or retrace design decisions instead of experimenting and iterating to improve the product for end users.
This article discusses how to document and communicate the right types of UX details throughout the Agile product-development process. Teams adopting these practices won’t be overwhelmed by excessive documentation and will easily remember what’s important.
Documentation Throughout Agile Product Development
Regardless of the product development phase, keep these factors in mind with UX documentation: