Are FAQs helping or hurting your content?

FAQs are one of the most common content deliverables in change communications. They feel familiar, safe and efficient. But from a content design perspective, FAQs often make information harder to find, harder to scan and harder to maintain.

Content design is about helping users complete tasks quickly and confidently. It starts with user needs, uses evidence rather than assumptions and focuses on findability, clarity and accessibility.

From this perspective, the question is not whether FAQs are good or bad in theory. The question is whether they genuinely help users achieve what they came to do.

The case for FAQs

There are a few reasons FAQs continue to appeal.

They appear to address common questions in one place, making content easier to find. This is true when there's only a few questions and answers are short.

FAQs can also be useful in a transactional context. For example, say you're pushing users to an application form for an internal course. You've included eligibility criteria in the workflow to reduce unnecessary submissions. Research and testing shows the criteria will create noise. When the form determines a user is not eligible, it sends them to an FAQ screen. The screen displays three well-researched and tested answers in an FAQ format. This increases understanding and reduces resistance.

Research is key. Without data showing what questions users have, FAQs only reflect assumptions.

The case against FAQs

In practice, FAQs often undermine good content design.

They are usually based on assumptions

Most FAQs are not written from the user's perspective. Project team's add questions based on assumptions. They're not validated through search data, analytics or user research. This results in content that feels plausible but does not match how users think or search.

They encourage poor information architecture

FAQs often become a dumping ground for content that does not fit elsewhere. Over time, they grow into long, unstructured lists that users must scan line by line. This increases cognitive load and makes information harder to find.

They duplicate content and increase maintenance effort

FAQs often repeat information published in other places on a site. The result is too many sources of truth. This increases the risk of outdated or inconsistent information.

They are not task focused

Users usually arrive with a goal, not a question. They want to understand something specific, solve a problem or complete a task.

They reduce scanability

Long lists of questions are difficult to scan. Even more so when phrasing is inconsistent or too formal. People don't read online, they scan. The desire for someone to read all FAQs requires an unlikely high level of engagement in the content.

When FAQs may be appropriate

FAQs can be useful in limited circumstances.

• They work best when the questions are derived from real data such as search logs or support requests.

• They should be short, focused and limited in number.

• They are most effective when users genuinely frame their needs as questions and when answers cannot easily live elsewhere.

Even then, FAQs should not replace well-designed core content.

Better alternatives to FAQs

In most cases, there are stronger options.

• Surface answers where users need them, on the relevant page and at the right point in the task. Use clear headings that reflect user language.

• Topic-based landing pages, service pages and task-focused guides are usually easier to scan, easier to maintain and more effective for users.

• Search data is particularly powerful. Analysing what people actually type into search tells you far more about user needs than brainstorming questions in a workshop.
  

A simple decision guide

Before adding an FAQ, ask:

• Do we have evidence that users ask these questions?

• Do the questions match real search terms?

• Could this information live more clearly on an existing page?

• Would a task-based content structure reduce the need for questions at all?

If the answer to most of these points is no, an FAQ page is unlikely to help.

Final thought

FAQs often feel helpful because they are easy for organisations to create. For users, they frequently hide information rather than reveal it.

Good content design prioritises tasks over questions, evidence over assumptions and clarity over convenience. In most intranet and internal content contexts, this leads to clearer structures, better findability and fewer FAQs overall.