How to write a task flow

When creating a Compatibility Test on Fable, the feedback you get can often depend on the type of instructions you give in your task flow. If the task flow you are testing is long or complex, you’ll need to break it into multiple requests. This allows for testers to focus on providing high quality feedback, rather than focusing on complex instructions.

What is a task flow?

A series of steps (“flow”) that users complete for a specific task. Task flows are similar to user flows, except they’re generally linear without multiple branches or paths. E.g., all users would follow the same steps to complete that specific action, such as creating an account or going through a checkout process. Source: UX Beginner

Below is an example of what an approved task flow looks like, as well as some tips to help you as you write your own.

Illustration of brunette woman wearing a yellow t-shirt.

Amber Knabl, Customer Success @ Fable

“Instructions should be specific enough that you know every tester will be completing the same task in the same way, but not so specific that testers have to follow overly complex instructions.”

Example task flow

Title: Explore Fable’s Learning Centre

Description: In this task you will explore Fable’s Learning Centre as a customer, providing feedback on how accessible the process to find and consume tutorial articles is.

User Journey:

  1. Review the topics under the “How to use Fable” section.
  2. Under “Go beyond accessibility compliance”, review the categories.
  3. Select the article titled “The top 5 things you should know when working with people with a disability”.
  4. Explore the main points of the article.
  5. Return to the Learning Centre homepage using the main menu.
  6. Watch the featured video embedded in the “Hear from our community” section.
  7. Interact with the video player controls, including captions and skipping to different timestamps.
  8. Return to the top of the page using the jump to top feature.

Things to note:

  • Testers will complete the task in the same way: This allows you to pinpoint exactly where issues occurred, when they are reported.
  • Each step includes only one task: All steps are clear, minimizing the chances of testers to make assumptions or attempt t