Interaction Flows

What if there was a better way to do designer/dev handoffs?

Problem

Working with an overseas development and UX team, I needed to figure out a better way to hand off my designs. In 2017, I developed a whole new way to document interaction design: Interaction Flows.

 

I had just read this article on Nielsen and Norman on Wireflows, which argued for the fusion of user/task flows and wireframes. While they show processes and relationships in a simple way, user flows don’t show how the visual elements provide entry points into each page or how they facilitate the user’s goals. 

Wireframes are great for laying out those visual elements, but by themselves, they are not very descriptive of the relationship or flow between pages.

I looked back on the microinteractions framework from Dan Saffer’s book and thought: why not combine these two awesome approaches? Why not define the triggers/rules/feedback/loops/modes in the wireflow?

Thus birthed the Interaction (IX) Flow.

Example of an Interaction Flow

Example of an Interaction Flow

Why an Interaction Flow?

The thoroughness of the IX Flow can be intimidating, but communicating these interactions has many benefits:

  1. Centralizes the flow, visual design, and interactions in one document

  2. Can be exported as a PDF, JPEG, etc. so this document can be viewed on any desktop

  3. Reduces guesswork and ambiguity on the developer’s part

  4. Reduces mistakes during development

Read More

After positive reception by leadership, multiple development teams, and fellow UX peers, I decided to write about the process on Medium, got picked up by UX Planet, and ended up in Medium's Top 20 Posts with over 40K views! 

You can read the Medium article here:

Previous
Previous

Reusable Data Tables

Next
Next

PTO Management App