Frequently Asked Questions UX
FAQ section on the Icelandic Postal Service website (https://posturinn.is/en/individuals/faq/).

Frequently Asked Questions UX

This article is an upcoming part of?Smart Interface Design Patterns??? and will be a part of the?UX training in September?as well. Free preview.

Barely any website can escape the curse of the?FAQ section. Even seemingly simple products eventually grow roots as the user base expands. Sadly, the?web is not a particularly friendly place, and so users have all kinds of doubts, objections, questions and concerns — and they need to be addressed.

No alt text provided for this image
Walmart FAQ hub used to highlight multiple FAQ guides, depending on the topic of interest, sometimes with one-line answers.

But are FAQs a good solution to do just that? Not necessarily. Let’s explore some of the issues that FAQs have, and how to actually help customers find what they need. You can find more details on that in the?usability chapters in the video library.

Usability Pitfalls With FAQs

We’ve learned to rely upon dedicated FAQ sections over the years, and users seem to understand the concept very well. However, on an FAQ page they typically?scan questions for a specific keyword, or use in-browser search to find what might be relevant for them.

The?questions format, however, doesn’t aid in quick navigation to the answer. And with accordions, the answers usually aren’t accessible without opening each accordion.

No alt text provided for this image
On Airtable Help Center (https://support.airtable.com/), there are no FAQs. Instead all topics are presented as cards, front-loaded with keywords.

This reveals some?significant usability issues:

  • FAQ is unlikely to help?if customers don't know if a particular piece of content or feature exist on the site. People don't call support about tools they don't know exist.
  • FAQs are too slow to use: they are convenient for writers, but take significantly more time for users to scan and understand.
  • FAQs lead to duplication: as multiple pages repeat the same information, they pollute search,
  • FAQs are difficult to navigate: they force content designers to group content by?general type?or?format, rather than?task?(e.g. toolkits, resources, videos),
  • FAQs need to be actively maintained: customer’s questions change frequently, and multiple sections of the site must be updated.
  • FAQs also have governance issues: every piece of content needs an owner, but it’s difficult to assign an owner to an FAQ page spanning multiple topics.

In general, just like PDFs, FAQs are examples of?organization-centric form of navigation?and content. Since many customers don’t know how the organization is structured and how it works, they often experience issues finding an answer in a myriad of?poorly organized questions.

The Best FAQ Isn’t Even There

Typically FAQs emerge because users can't easily find a particular piece of information on the site, and keep sending similar questions to the service desk — after all, these questions are “frequently asked”.

However, this isn't really an indicator that an FAQ section is needed, but rather that?IA, navigation and search aren't working very well. Before setting up an FAQ page, we can try to find a way to show answers where users actually expect to find them.

No alt text provided for this image
With the design above, customers are likely to have plenty of questions about the product: from delivery costs to payment options.

In the eCommerce example above, we leave customers with plenty of unanswered questions. We need to?highlight all the details?about taxes and fees, delivery times, shipping costs, returns policy and payment options — as prominently as possible. But we don’t really need an FAQ for that — we could show them right away (pictured below ↓).

No alt text provided for this image
Addressing concerns about delivery and returns, all at once.

We might need to do a bit more work. We could break down the pieces of content and publish relevant content where people naturally look for it. We also might need to?iterate on IA, navigation design, labels and layout with?top tasks?and?tree testing.

No alt text provided for this image
There are no FAQs on AirBnB (https://www.airbnb.com/help?audience=guest). Instead, topics and guides with short headlines and front-loaded keywords.

And once it all set in motion, we might set up?help hubs, or if absolutely necessary, an FAQ page as a temporary solution.

A Well-Designed FAQ

But what if we do need an FAQ after all? Of course we need to?group questions by topics, and probably design them as accordions. Displaying all answers as is would work with in-browser search, but it might make the page too lengthy to be usable.

No alt text provided for this image
On some Booking.com pages, all questions are organized by topics, with a set of tabs and accordions in each tab.

Here are some of the?useful features of FAQ pages?that you might want to consider:

  • Include the?FAQ link in the footer?of each page,
  • Include a table of contents (perhaps sticky),
  • Alternatively, group accordions in a split-menu (as displayed above),
  • Use autocomplete search (e.g. like?Elementor)?to find specific details in the FAQ might be helpful,
  • Add jump-links with an option to go back to the overview,
  • Allow customers to?open multiple questions at once,
  • Instead of long passages of text, use?bulleted points?and shorter, concise sentences,
  • Front-load questions with?keywords?as far as possible,
  • Validate the quality of FAQ with a “Did this answer your question?” prompt?
  • For longer FAQs, or those with complex answers, screenshots, or videos, you might want to set up?separate answer pages?(or topic pages).

Wrapping Up

FAQs are difficult to navigate and maintain, but they do gather critical information in one single place, and hence can be helpful. But we need to?measure just how helpful they are.

Measure how much traffic your FAQ page has and how often people mark answers as helpful. Establish a regular maintenance review for the content of the page as it might be something that users heavily rely on.

You might not need an FAQ page after all. Perhaps you could break down the answers to each question within the interface. Or perhaps you could create a?help hub, or a?full support guide?with how-to articles, screenshots and videos, dedicated Q&A blog posts and a decent autocomplete. This might be much more efficient than a never-ending list of nested FAQ sections.


Coming Up:?Interface Design Live UX Training?(Sep 8–Oct 6)

Roll up your sleeves and boost your UX skills! We’ll explore usability pitfalls, design process, design KPIs and design patterns in the?upcoming live UX training in September this year. With 8 live sessions, real-life UX challenges,?personal 1:1?feedback?and UX certification for all your hard work! Ah, you can get?just a video library, too. Free preview.

No alt text provided for this image

I'd be absolutely delighted to welcome you there. And it's not quite for you, perhaps you could recommend the course and training to your friends and colleagues? Thank you so much ?? for your kind and ongoing support, everyone —?and I can't wait to see you soon! ????

— Vitaly

Aditya Kushwaha

Visual Designer | Creating Something That Truly Connects

1 年

Agree! Shifting from FAQs to dynamic help hubs enhances user experience by providing context-specific information, reducing redundancy, and ensuring timely updates based on evolving user needs.

回复
Nico Barelmann

E-Commerce Manager @ SPARQ bei Rotk?ppchen-Mumm

1 年
回复
Sebastián Urrutia

Digital Marketing Coordinator en Talana | Publicista | Diplomado Inteligencia Digital de Marketing en USACH | Emprendedor | Saas B2B

1 年

Great insights! Your perspective on rethinking FAQs in UX design is truly thought-provoking. I agree that answering users' questions in context can create a more intuitive and user-friendly experience. Thanks for sharing your expertise and prompting us to question established practices.

回复
Nikol H.

AI Visionary | Building Next-Gen AI Chatbots & Voice Agents to Revolutionize CX & Drive Business Growth | Founder: Elysium AI & AuroraVoice AI ??

1 年

Replace FAQ with human-like chatbots programmed with your business data on your website, built by me???? Streamline your productivity and reduce inquiries!

回复

要查看或添加评论,请登录

Vitaly Friedman的更多文章

  • Designing For Stress and Emergencies

    Designing For Stress and Emergencies

    No design exists in isolation. As designers, we often imagine specific situations in which people will use our product.

    13 条评论
  • ? How To Build Confidence In Your UX Work

    ? How To Build Confidence In Your UX Work

    When I start any UX project, typically there is very little confidence in the successful outcome of my UX initiatives…

    12 条评论
  • ?????? How To Test And Measure Content In UX

    ?????? How To Test And Measure Content In UX

    The goal of the content design is to reduce confusion and improve clarity. Yet often it’s difficult to pin point a…

    21 条评论
  • Useful Customer Journey Maps (+ Figma & Miro Templates)

    Useful Customer Journey Maps (+ Figma & Miro Templates)

    User journey maps are an effective way to visualize user’s experience for the entire team. Instead of pointing to…

    22 条评论
  • ?? Sustainable Design Patterns For UX Designers

    ?? Sustainable Design Patterns For UX Designers

    Digital sustainability is often seen as a technical concern for engineers. We speak about optimization of assets, and…

    23 条评论
  • ?? Designing For Gen Z: Expectations and UX Guidelines

    ?? Designing For Gen Z: Expectations and UX Guidelines

    Every generation is different in very unique ways, with different habits, views, standards and expectations. So when…

    17 条评论
  • ?? How To Improve UX In Legacy Systems

    ?? How To Improve UX In Legacy Systems

    Imagine that you need to improve the UX of a legacy system. A system that has been silently working in the background…

    56 条评论
  • Design Guidelines For Better Notifications UX

    Design Guidelines For Better Notifications UX

    Over the years, I’ve developed a habit to turn off all notifications once a year — both on mobile and on desktop. There…

    32 条评论
  • ?? How To Make A Strong Case For UX Research

    ?? How To Make A Strong Case For UX Research

    Getting a buy-in for UX research can be remarkably difficult. You might find yourself constrained by wrong assumptions…

    14 条评论
  • ?? How To Design Complex Data Tables (+ Figma Kits)

    ?? How To Design Complex Data Tables (+ Figma Kits)

    Complex data tables are difficult to get right. They always come along with filters, sorting, customization options…

    61 条评论

社区洞察

其他会员也浏览了