Hello! Welcome to the second module of your course on analyzing user flows.
In the first module, we established a foundational framework for looking at user flows, focusing on deconstructing them into their core components and learning to differentiate between high-friction and low-friction experiences.
Today, we begin our deep dive into diagnosing specific "flow pathologies." Our learning outcome is to identify friction points in user flows related to data entry and form design. Forms are one of the most common and critical interaction points in any digital product, making them a frequent source of user frustration and drop-off.
In this lesson, we will:
- Explore the underlying reasons why forms can be so challenging for users.
- Categorize common friction points into issues of cognitive load and interaction cost.
- Examine specific design principles and best practices that help you spot and prevent these friction points.
Let's get started.
1. The Core Challenge: Why Users Dislike Forms
At its heart, a form is a conversation. But unlike a human conversation, it's often one-sided, rigid, and demanding. Every field you add is another question you're asking the user, and each question contributes to the overall effort required to complete the flow. The primary goal in form design is to make this "conversation" as smooth and effortless as possible.
The most effective way to reduce form friction is simple, yet often overlooked: ask for less information.
Form Design Principles: 13 Best Practices
To understand this foundational principle, let's turn to an article by CXL, a well-regarded resource in conversion optimization. This first section explains why simply removing fields is your most powerful tool.
Please read the section titled '1. Less is more: remove form fields.' As you read, consider the concept of 'greedy marketer syndrome' and how it conflicts with user experience goals.
As the article points out, the average checkout form often has twice as many fields as necessary. Your role as a designer involves constantly questioning the necessity of each piece of data you request. Is it essential for this specific step in the user flow, or can it be collected later, or not at all? This mindset is the first step in diagnosing form-related friction.
2. Identifying Friction: Cognitive Load
Cognitive load refers to the mental effort required to process information. When a form is poorly organized, visually cluttered, or ambiguous, it forces the user to think too much, increasing the likelihood of errors and abandonment.
Layout and Visual Organization
A clean, logical layout is crucial. The user should be able to scan the form and instantly understand the path to completion.
Better Forms Through Visual Organization
The Nielsen Norman Group are pioneers in UX research. This short video provides an excellent visual summary of how to organize a form to reduce cognitive load.
Please watch the entire video. Pay close attention to the three core principles: the importance of label placement (0:22), the rationale for single-column layouts (0:57), and using spacing to group related information (1:41).
The video highlights three key friction points related to layout:
- Ambiguous Labels: Labels that are equidistant between two fields create uncertainty. The principle of proximity is key here—a label should be visually grouped with its corresponding input.
- Multi-Column Layouts: These can disrupt a user's vertical scanning momentum, making it easy to miss fields. While there are exceptions for very short, related inputs (like Month/Day/Year), a single column provides a clear, predictable path.
- Poor Information Scent: Failing to use whitespace to "chunk" related information (e.g., separating "Shipping Address" from "Payment Details") forces the user to parse one long, undifferentiated list of questions.
To reinforce the point on single-column layouts, let's look at some data.
Form Design Principles: 13 Best Practices
The CXL article we viewed earlier provides quantitative evidence supporting the single-column principle.
Read the brief section '2. Single-column beats multi-column forms.' Note the significant difference in completion time found in their eye-tracking study.
Ambiguous Fields and Instructions
Friction also arises when users are unsure what's expected of them for a specific field.
-
Required vs. Optional: Is this field necessary? Ambiguity here leads to hesitation. The best practice is to only ask for what's required. If you must include optional fields, mark them clearly (e.g., with "(optional)") rather than marking only the required fields with an asterisk, which adds visual noise.
-
Input Format: Does this field have a specific format? A classic example is a date or phone number. Instead of just showing an error, provide an example format or, even better, use input masks or auto-formatting.
-
Input Length: How much information is needed? The physical size of an input field can provide a powerful visual cue.
This next video from the Malewicz channel has a quick, clever tip on how field size can reduce ambiguity.
Watch the segment from 3:53 to 4:23. Notice how the length of the input field itself acts as a piece of micro-copy, guiding the user's input for things like CVV or zip codes.
3. Identifying Friction: Interaction Cost
Interaction cost is the sum of physical efforts (like typing and clicking) and mental efforts (like making decisions) required to complete the form. Even if a form is understood perfectly, high interaction cost can make it feel like a chore.
Inefficient Data Entry
The less a user has to type, the better. Modern forms should leverage technology to minimize manual entry.
Form Design Principles: 13 Best Practices
Let's return to the CXL article to explore several ways to reduce the physical effort of data entry.
Please read the following three sections: '6. Use saved data and automated suggestions.' Focus on the difference between autofill and autosuggest. '8. Consolidate name and address fields.' This relates back to reducing the number of interaction points. '9. Offer radio buttons instead of drop-down boxes.' Note the data on completion time.
Key takeaways for reducing interaction cost include:
- Use Autofill/Autosuggest: Leverage browser-saved data and APIs (like Google Places for addresses) to complete information for the user.
- Consolidate Fields: A single "Full Name" field is lower effort than separate "First Name" and "Last Name" fields.
- Choose the Right Component: For a small, finite set of options (e.g., 2-5 choices), radio buttons are often better than a dropdown because they make all options visible at once, reducing clicks.
Poor Error Handling
Users will make mistakes. How the system responds is a critical factor in the user experience. The worst-case scenario is a user submits a long form, only to have the page reload with a list of errors at the top, forcing them to hunt for their mistakes.
This creates immense friction. The solution is to provide feedback right where and when the error occurs.
Form Design Principles: 13 Best Practices
Effective error handling is about clear, immediate communication. The CXL article has an excellent section on this, referencing a foundational study in the field.
Read sections '3. Communicate errors clearly' and '4. Use inline form-field validation.' The statistics from Luke Wroblewski's study in section 4 are particularly powerful in making the case for real-time feedback.
Inline validation provides a tight feedback loop that helps users correct mistakes instantly, reducing frustration and increasing success rates.
4. Practical Application: Spot the Friction
Let's apply these concepts. Imagine you are auditing a registration flow for a new webinar. You encounter the following form:
This is a hypothetical example illustrating several common form design issues.
Based on what we've covered, take a moment to identify at least four distinct friction points in this form design. What are they, and why do they create a poor user experience?
Think about cognitive load (layout, clarity) and interaction cost (input method, error handling).
Click here to see a breakdown of the issues.
Here are some of the primary friction points in this example:
- Multi-Column Layout: The form uses two columns, which disrupts the natural top-to-bottom flow and increases the chance that a user might miss a field.
- Poor Grouping: "Email" and "Phone Number" are separated from "Full Name," while "Country" is grouped with job-related information. This logical disconnect increases cognitive load.
- Inefficient Input for "Country": A dropdown with over 100 options is a high-interaction-cost component. A text field with autosuggest/autocomplete would be far more efficient.
- Ambiguous Required Fields: The instruction "All fields with * are required" forces the user to scan for the asterisk. It's better to mark the few optional fields with "(optional)". The "Job Title" field's optionality is unclear.
- Strict Formatting without Guidance: The password requirements are only shown after an error. This information should be visible upfront to prevent the error in the first place (inline validation).
- "Clear Form" Button: This button offers high risk (accidental data deletion) for very little value. Users can simply navigate away if they wish to abandon the form.
Conclusion
In this lesson, we moved from a general understanding of user flow friction to the specific, common pathologies found in form design. You are now equipped to systematically identify these issues in the products you work on.
Key Takeaways:
- The First Principle: The best way to improve a form is to shorten it. Question every field.
- Reduce Cognitive Load: Use a single-column layout, group related information logically with whitespace, and ensure labels and instructions are unambiguous.
- Lower Interaction Cost: Minimize typing with autofill and smart defaults, choose efficient input controls (like radio buttons over dropdowns for few options), and consolidate fields where possible.
- Provide Real-Time Feedback: Use inline validation to alert users to errors as they happen, not after submission.
In our next lesson, we will broaden our focus from a single screen to the journey between screens. We will learn how to detect navigational dead-ends and confusing information architecture (IA) within a flow, another critical source of user friction.
Can't find a good explanation? Sign up and we'll make it for you
Sign up