Skip to content
Global sound
5 Minute UX

5 Minute UX

Using Task Flows to Map User Paths

· 11 min · Season 1 Episode 433

Show notes

Learners will construct task flow diagrams that map user decision nodes and branching paths. This capability allows practitioners to align application logic with user mental models and clarify complex processes before development handoff.

Learning Objective: By the end of this lesson, learners will be able to construct task flow diagrams that distinguish user decision nodes, branching paths, and terminal states to clarify complex application processes.

Transcript

Task Flow Structure and Components

Task flows are diagrams that identify the specific path users take through a website or application, utilizing visual elements similar to site maps.

At the heart of any basic task flow are decision nodes, which ask a definitive question like, "Is the user logged in?" From this point, branching paths represent distinct routes based on the answer, where "Yes" leads directly to a Logged-In Page, while "No" directs the user to a Not Logged-In Page.

These routes eventually converge on terminal states, which are the final pages or states reached, such as the Home Page, the Logged-In Page, or the Not Logged-In Page.

By clearly identifying these three structural components, you can construct diagrams that distinguish user decision nodes, branching paths, and terminal states to clarify complex application processes.

Key Points:

• Task flows are diagrams identifying the path users take through a website or application, utilizing visual elements similar to site maps.

• A basic task flow includes decision nodes, such as the question 'Is the user logged in?'.

• Branching paths represent distinct routes based on the decision, where 'Yes' leads to a Logged-In Page and 'No' leads to a Not Logged-In Page.

• Terminal states are the final pages or states reached, such as Home Page, Logged-In Page, or Not Logged-In Page.

Distinguishing Task Flows from Site Maps

You've already seen how a task flow maps the user's journey through decision nodes and branching paths. Now, let's clarify where that fits versus a site map. A site map communicates the visual hierarchy of a site’s or application’s layout, showing how pages nest and relate to one another. A task flow, however, provides details of users’ options and the specific paths they will be able to take. While they may appear similar at first glance, they serve distinct purposes in information architecture, which means you can't just swap one for the other without losing critical context.

Think about the login example we just covered. The site map shows you that a Logged-In Page and a Not Logged-In Page exist within the structure. The task flow explains the decision node, "Is the user logged in?", and how that answer dictates which of those pages the user actually reaches. One is a static blueprint of the space, while the other is a dynamic map of movement through that space. You need both to fully understand the user experience, but they answer fundamentally different questions about how the product works and…

Website: castopod.gogomito.com

Live, last hour: 15,023 songs on 7,730 stations in 144 countries

Discover the world through radio

More ways to discover (9)

Heard something good? Save it, or open it straight away in Spotify.

Radio 538 luisteren - Live!Popular right now