User Flow Documentation
Modern software applications can get complex rather quickly. To help make sense of the underlying architecture I usually begin every design project with a userflow document. Instead of focusing on a single user path, a document like this allows many different scenarios and edge cases to be captured in a single view. It helps stake holders see the system as a whole. This document proposes two new possible solutions for a requested product feature and compares those two options with the current solution displayed horizontally along the top. The document became a tool for discussion between product, design and development teams.