Skip to main content

BETANow in public beta.Public betaBeta

日本語Español

FAQ-005 Published

Step-guide FAQ

An FAQ that asks for two or three choices and shows only the questions that apply.

FigmaThis part is included in our free, editable Figma file: 235 website UI patterns across 32 parts, 2 designs each Open in Figma Community ↗ (opens in a new tab)

Wireframe (desktop) | Step-guide FAQ

Step-guide FAQ UI design (desktop wireframe)

Wireframe (mobile) | Step-guide FAQ

Step-guide FAQ UI design (mobile wireframe)

What changes on mobile

  1. Choices stacked at full width: Side by side, the labels would wrap and be hard to read, so each is a full-width button that is easy to tap.
  2. Choices summarized in one line above the results: Even on a narrow screen, it is clear what the results are based on, and the choices can be changed from there.
  3. Scroll to where the next step is visible: After choosing, the page moves so the next heading is in view and nobody has to hunt for it.
  4. Full-width contact button: When the matching questions do not solve it, people can go straight to the contact form.

Before you choose this pattern | Step-guide FAQ

Good fit

  • Which questions matter depends clearly on the reader's situation
  • Readers in different positions land on the same page: prospects and customers, individuals and companies
  • Readers struggle to think of search words, and choices get them there faster
  • Support pages for a service, help for members, FAQs at desks that handle many kinds of procedure

Poor fit

  • Few questions that can be scanned in a list (the <a href="/patterns/en/faq-full-list/">full-list</a> or <a href="/patterns/en/faq-accordion/">accordion</a> FAQ works better)
  • Questions cannot be split by the reader's situation (if every choice leads to the same questions, the steps only add effort)
  • Readers already have a clear word to search for (the <a href="/patterns/en/faq-search/">searchable FAQ</a> gets them there faster, just by typing)

Why this wireframe works | Step-guide FAQ

No search word needed; choosing gets you there

A search box goes unused if readers cannot think what to type. Offering the situation and the topic as choices means people reach the questions that concern them without finding words.

Readers in different positions see only what applies to them

Showing cancellation steps to a prospect, or the sign-up flow to a customer, helps nobody. Asking for the situation first means readers in different positions who land on the same page each see only the questions that apply.

The choices stay visible and can be changed at any time

Without knowing what the results are filtered by, readers cannot trust them. Showing the path, such as “Current customer › Payment”, means people can go back a step and choose again from right there.

When nothing solves it, contact with the choices carried over

Some people read the matching questions and are still stuck. A contact panel under the results that carries the choices into the form lets them ask without typing the same explanation again.

On mobile, full-width choices work one-handed

On mobile the choices stack as full-width buttons. After a choice the page moves to where the next question is visible, so the thumb barely has to travel.

Common mistakes | Step-guide FAQ

No question is visible until the steps are done

If the first screen is only choices, people who want the whole list, or who fit none of the options, leave. Make “See all questions” available from any step.

Too many steps before the results

Four or five questions and more people give up midway. Aim for two or three; if that cannot split the questions, combine with search or categories. There is no need to drop an important distinction just to shorten the steps.

No path for people who fit no option

If their situation is not among the choices, readers cannot proceed. Provide “Not sure” and “Other”, show a broader set in that case, and point to all questions or contact if nothing fits.

Old results remain after going back

If step 1 is changed but step 2 and the results stay as they were, the page shows contradictory results. On a change, update everything that follows.

Zero-result combinations with nowhere to go

Some combinations of choices may have no questions to show. Before launch, walk every combination to find zeros, and add questions or point to similar questions, all questions or contact.

FAQ | Step-guide FAQ

How should I divide the choices?

Look through the enquiries and questions for the points where the answer changes depending on the reader. Divisions where the visible questions clearly change, such as prospect or customer, individual or company, work well. Avoid divisions where every choice shows the same questions, which only add effort.

Can the same question appear in several results?

Yes. A question such as “I want to change my payment method” concerns both current customers and people thinking of canceling, so show it in both. Forcing each question into one place leaves questions that never reach the people who need them.

Can I add a search box too?

Yes. People with a clear word use search; people without one use the steps. In that case, make sure both routes reach the same questions and answers so nothing drifts.

How does this differ from the categorized FAQ and the plan finder?

The categorized FAQ has readers pick one topic to filter by. The step guide has them choose a situation and then a topic, filtering by the combination. The plan finder in the pricing table narrows to one plan as a rule; the step guide shows several matching questions and lets readers choose.

Related pages

Share this pattern

Send this page to your team or your design partner.

Was this pattern useful?

Written by

Yuta Okano

ENVY DESIGN Inc.

CEO / Director / Designer

14 years in the web industry. Has worked on more than 500 web projects, from corporate and recruiting sites to e-commerce. Focuses on information architecture, direction and design, from planning websites to improving them. In recent years he has focused on AIO (AI optimization) and GEO, helping sites get cited by generative AI search such as ChatGPT, Perplexity and Google AI Overviews.

Review and revision history

  1. Published AvatarYuta Okano Pattern published