It’s a few weeks into a project. Everyone has taken their seats and logged into the web conference. The key bullet on the agenda reads: Review first iteration of product visual designs. You’ve even built a prototype to show participants the proposed end-to-end experience. But a few clicks into the walk-through, the meeting grinds to a halt. A key stakeholder has questions. Others chime in. Instead of showcasing your work, you find yourself bouncing between mock-ups, requirements documents, and pitch decks. Your hopes of forging consensus around the customer experience have faded.
We’ve all been in meetings like this. Frequent working sessions, well-documented business requirements, and extensive design iterations prove insufficient to establish consensus. The reality is that stakeholders and team members are often on different pages, and there are plenty of opportunities for misunderstandings and confusion when dealing with complex products, time-constrained activities, and geographically distributed teams. Executives may not be able to attend key meetings. Stakeholders can get lost in a sea of PDFs, Sketch files, and Google Docs. Not everyone pays attention to the latest Slack post. And some team members struggle with technically complex documents and detailed process flows. What if you could synthesize all of the complexities into one simple visual that conveyed the story clearly to stakeholders?
If you work in a creative firm or are part of an in-house design team, you understand the importance of getting clarity and consensus from stakeholders early in the project. However, it can be challenging to find the right way to communicate the story to a diverse team with different needs and backgrounds. Over the past few years, our product design team has found a surprising level of success addressing this problem by using a hybrid kind of design deliverable we call a thumbflow. It’s an artifact uniquely suited for communicating complex product experiences and getting everyone on the same page. Our UX design work for clients like Adobe, Citrix, and Oracle has given us an opportunity to explore, iterate, and test several variations—each tuned for a slightly different set of needs.
A thumbflow tells a story of how customers interact with products and each other. It draws from a number of design artifacts and document types you’re already familiar with and is presented in an approachable and easy-to-consume format. Much like a flow diagram, it showcases a sequence of events and interactions, but it avoids the temptation to illustrate all possible scenarios and keeps the amount of technical detail appropriate for consumption by less technical team members. Like a wireframe, it includes a high-level, abstracted view of the product interfaces, but instead of representing all content and interface elements, only a thumbnail version of the screens are shown. This forces the designer to consider only the aspects of each screen that are essential to high-level storytelling and ensures that the document remains glanceable. Similar to journey maps and personas, it touches on who the user is, what they are doing, and why. It does this in a way that focuses exclusively on user actions and the relevant product screens, features, and workflows that exist to support their needs and activities.
Other powerful attributes of thumbflows include:
As for business benefits, thumbflows:
Today is a perfect time to experiment with thumbflows. If a project is underway, you’ll have plenty of design artifacts to draw from. If it’s just starting up, think about incorporating thumbflows from the outset. You might want to begin with a simple one, or just jump right in with a more complex version if the situation warrants it. As the product evolves, so will your thumbflows. And the next project? The thumbflows will probably look very different. No matter what you come up with, we’d love to hear from you about your experience. Contact us at firstname.lastname@example.org.