Cognitive walkthrough and task flow analysis: a powerful duo for optimizing the user experience (UX)

Executive summary

In the dynamic world of digital products, the key to success lies in a flawless user experience (UX). This article explores how combining the cognitive walkthrough, a qualitative technique for identifying friction, with task flow analysis, a quantitative method for measuring user effort, becomes a powerful strategy. Discover how this dual approach lets digital leaders and product teams not only identify hidden pain points, but also quantify the impact of optimizations, making sure every iteration translates into greater user satisfaction and better product performance.

On the Research team, we often find ourselves testing platforms or apps with users who already know them inside out: the famous heavy users. In these cases, more structured tests, with well-defined tasks and rigid steps, don’t always let us fully explore the pain points that come up in everyday use of the product.

That’s why we started incorporating a different method: the cognitive walkthrough. It’s a semi-structured exploration technique in which people can move freely through the interface while they identify friction, opportunities for improvement and critical aspects of the experience.

Although we follow a guide with general goals, what we’re after with this technique is capturing the user’s spontaneous perception, based on their real flow of use. And that becomes especially valuable when we work with products whose advanced users are so familiar with them that traditional tests fail to reveal important problems.

But we didn’t stop there.

We began combining the cognitive walkthrough with another tool that adds a quantitative view: task flow analysis. This technique lets us see how many actions a user performs and how much effort each one involves. That way, the qualitative and the quantitative meet in the same conversation.

Combining the two methods helps us validate the insights from exploratory tests, backing them up with hard data. And that’s very useful when we need to communicate findings to stakeholders, because it gives us a concrete way to show why a task flow needs to be iterated to improve the experience.

It all started with an article

Besides analyzing interfaces, running benchmarks, interviews and workshops, working in Figma and using Miro (among many other things), I also have a habit: I save articles. Lots of them. I have a UX Research folder that’s like my own library, where I collect everything I find, everything colleagues share with me or that I read on social media.

In that folder there’s an article from UX Magazine (yes, it’s still there) that proposes a very interesting method for analyzing task flows. I rediscovered it a while ago and thought it was perfect for making cognitive walkthroughs more solid, combining the qualitative approach with a quantitative layer.

Deep exploration: the cognitive walkthrough in UX

That’s why we’ve incorporated a different and highly effective method: the cognitive walkthrough.

“This semi-structured exploration technique lets users move freely through the interface while they identify friction, opportunities for improvement and critical aspects of the experience.”

Although we follow a guide with general goals, the main purpose of the cognitive walkthrough is to capture the user’s spontaneous perception, based on their real flow of use. This is especially valuable when we work with products whose advanced users are so familiar with them that traditional usability tests fail to reveal important problems or significant UX insights.

Combining qualitative and quantitative: task flow analysis

But we didn’t settle for the qualitative view alone. We’ve started combining the cognitive walkthrough with another tool that brings a quantitative view of UX: task flow analysis.

This technique lets us:

• Quantify how many actions a user performs.
• Measure how much effort each of those actions involves.

That way, qualitative and quantitative research meet in the same conversation. Combining these methods helps us validate the UX insights from exploratory tests, backing them up with concrete data. This is extremely useful when communicating findings to stakeholders, since it provides a tangible way to show why a specific task flow needs to be optimized to improve the user experience and the performance of a digital product.

The inspiration behind the method

Besides analyzing interfaces, running benchmarks, interviews and workshops, and using tools like Figma and Miro, our team has a habit of collecting relevant articles and papers. My UX Research folder is like a personal library where I keep everything I find.

In that collection, I rediscovered a valuable UX Magazine article that proposes a very interesting method for analyzing task flows. I thought it was perfect for making cognitive walkthroughs more solid, combining the qualitative approach with a quantitative layer that’s essential for UX optimization.

How does task flow analysis work?

The logic is simple: you diagram, step by step, the complete path a person takes to complete a task. That includes every screen and action needed.

Once we have the complete flow, we detail each action the user must perform to complete the task. It’s important to note that those actions will depend on the type of flow being analyzed and the device in question. Using a mobile app isn’t the same as using a desktop platform.

You also have to bear in mind that not all flows have the same types of actions. In some we’ll find gestures, biometric validation, welcome screens and scrolling, and in others perhaps only data entry and clicks. That’s why the analysis should be done on a specific flow that can be clearly quantified.

Suppose we’re analyzing a bank transfer flow in a mobile app. We could classify the actions with their corresponding effort level as follows:

• Touch / tap (effort level: 1)
• Scrolling (effort level: 3)
• Entering data (effort level: 10)
• Using biometric sensors (effort level: 5)

Each action is evaluated according to time and accumulated effort. For example, tapping a button is simple, so it has an effort of 1. Entering data, on the other hand, means opening the keyboard, typing, checking what you wrote and so on, so its effort is rated 10.

With the actions defined and their effort levels assigned, we build a table to add things up screen by screen.

The formula is:

Number of actions × Effort level

For example:

User actions	Count	Effort
Tap	12	12
Scroll	3	9
Enter data	1	10
Use biometric sensors	1	5
TOTAL	17	36

This table lets us see, in concrete terms, how many actions the flow requires and how demanding it is to complete.

Reducing effort and improving efficiency with UX

Now, if we redesign that task flow and optimize it based on how users want to use it and on UX/UI best practices, we can clearly show how much the experience improves and, therefore, operational efficiency.

Comparison: initial flow vs. iterated flow (optimization example)

In this case, if the initial flow had a total effort of 36 and the optimized one 26 (for example, if we removed two scrolling steps or simplified the initial taps), we can say the iterated flow is 28% simpler than the original.

“The key to this analysis is the tangible reduction in user effort. Not bad, right?”

Integrating cognitive walkthroughs with task flow analysis gives us a more complete view of the user experience: both what people feel when they use a product (qualitative insights) and what they actually do (quantitative data). It’s a powerful, essential combination, especially useful when we’re working on improving complex flows and want every interaction to count toward user satisfaction, digital product success and technological innovation.

To understand in more depth how similar methods affect efficiency, you can look at studies on the importance of usability in digital platforms.

Need to optimize the experience of your digital products?

Contact our user experience experts.

Discover more solutions for optimizing your digital products.