A task flow is a diagram showing the linear steps a user takes to complete one specific goal. No decision points. No branching paths. Just the straight line from trigger to completion for a single user doing a single thing.
People confuse these constantly. The distinction is simple.
A task flow for "Reset password" looks like this:
Click "Forgot password" → Enter email → Open email → Click reset link → Enter new password → See confirmation
Six steps. One path. Done.
A user flow for the same task would include: What if the email isn't in the system? What if the reset link expired? What if they're locked out after too many attempts? What if they remember their password halfway through? Each of those becomes a branch with its own path.
Task flows are intentionally reductive. That's the point. They force you to identify the ideal path before you worry about edge cases. User flows are more comprehensive but harder to read and share. Use task flows for alignment and communication. Use user flows for implementation specs.
Task flows do something specific that directly improves your card sort: they tell you which content items users need to access during common tasks.
Map out 8-10 of your most common task flows. Then look at which content items (pages, features, tools) appear across them. A content item that shows up in 6 out of 10 task flows — like "Account Settings" or "Help Center" — probably deserves prominent placement in your information architecture. It's a high-traffic node that users need to reach from multiple starting points.
This analysis also tells you what cards to include in your sort. If a task flow for "Upgrade my plan" touches the pricing page, comparison table, FAQ, and checkout flow, all four of those should be cards in your sort. You're testing whether users can find the things they actually need during real tasks, not just whether they can organize a random list.
Task flows also expose sequential relationships. If users consistently go from "Product page" to "Size guide" to "Add to cart," that sequence should influence your navigation — the size guide should be accessible from the product page, not buried three levels deep in a "Resources" section.
Pick one task. Pick one user type. Then:
If you find yourself adding diamond-shaped decision nodes, stop. You're building a user flow. Strip it back to the single happy path.
Most task flows have 4-8 steps. If yours has 15, either the task is genuinely too complex (and should be simplified in the product) or you're documenting multiple tasks as one.
A practical limitation: task flows assume a single path, which means they can oversimplify. Real users take detours, make mistakes, and use features in unexpected sequences. Task flows are useful for identifying content relationships and informing IA decisions, but they shouldn't be your only lens on user behavior.
What is the difference between a task flow and a user flow? A task flow shows the linear steps for completing one specific goal — no decision points, no branching. A user flow includes decision points, multiple paths, and error states. Task flow for password reset is a straight line of 6 steps. User flow for password reset includes branches for expired links, wrong email, account lockout, etc. Use task flows for simplicity and alignment; use user flows for comprehensive design specifications.
How do task flows inform card sorting? Task flows reveal which content items users need to access during common tasks, which directly informs what cards to include in your sort. A card that appears in multiple task flows — like account settings or help documentation — probably deserves prominent placement in your information architecture. Task flows also expose sequential relationships between content that should be reflected in your navigation structure.
How do you create a task flow diagram? Pick one specific task and one user type. Start with the trigger (what prompts the user to begin), then document each step as a single action — one screen or one interaction per step. End with the completion state. Keep it linear with no branching. If you find yourself adding decision diamonds, you're building a user flow, not a task flow. Most task flows have 4-8 steps.
Explore related concepts, comparisons, and guides