Flows
User flows
(Sometimes they get pretty big.)
The above user flow above is from a Hybris project for a medical device company. It depicts the affiliate onboarding process and its various ramifications.
This is really too big a project artifact to be adequately displayed in a portfolio. I show it here only to illustrate that I create user flows like this in order to capture the “happy paths” and the alternate paths that users may take through a website or app. This is the ten-thousand-foot view.
User flows accomplish a few things:
Enable designers, developers, and product owners to align on the big picture.
Suggest the pages/screens of the product.
Imply the types functional components which will be needed.
It’s not the most visually stimulating aspect of my work, to be sure, but I love diving into the extreme details and thinking through all of the potential “what-if” scenarios.
User flows are broken down into a more bite-sized artifact: task flows.
“Look. This stuff ain’t rocket science. But you can’t skip it,
and you sure as heck can’t fake it.”
Task flows
Click to enlarge.
These are Task Flow diagrams. They represent individual linear tasks a user needs to achieve. They are the one-thousand-foot view.
Task Flows capture critical interaction points and also bring to light which specific screens and components need to be designed.
Depending on the scope, there may be dozens of these for a given project.