FAQ Document

    Interview Type

    Build comprehensive knowledge bases from expert insights

    What Is It?

    1

    A discovery interview that identifies and answers the most common and important questions about a topic.

    2

    Goes beyond obvious questions to uncover what people should be asking but aren't.

    3

    The AI helps identify patterns, misconceptions, and gaps in existing documentation.

    Why Use AI for This?

    1

    AI discovers questions through conversation rather than pre-defining them

    2

    Ensures answers are complete and self-contained

    3

    Identifies misconceptions to address proactively

    4

    Organizes Q&As into logical categories

    When to Use

    Building comprehensive FAQ pages

    Creating help center content

    Documenting common customer questions

    Onboarding documentation

    Support knowledge base articles

    Content Structure

    1

    Core Questions

    The most frequently asked questions that every user needs answered

    2

    Edge Cases

    Less common but important scenarios users encounter

    3

    Troubleshooting

    What to do when things don't work as expected

    4

    Misconceptions

    Common misunderstandings that need to be addressed

    5

    Advanced Topics

    Deeper questions for experienced users

    Interview Approach

    Strategy

    Ask "What do people commonly ask about [specific aspect]?"

    Strategy

    Probe for the most frequent questions first

    Strategy

    Get complete, standalone answers

    Strategy

    Identify misconceptions to address

    Strategy

    Cover edge cases and troubleshooting

    Example Questions

    Q

    What do people most often ask you about this topic?

    Q

    What questions should people be asking but aren't?

    Q

    What are the most common misconceptions?

    Q

    How would you explain that to someone non-technical?

    Q

    What if they're dealing with [specific scenario]?

    Q

    What troubleshooting tips can you share?

    Q

    Can you give me a real example of when someone encountered this?

    Real-World Examples

    Support Team Creates Product FAQ

    45 minutes of interviews with 3 support engineers became comprehensive 30-question FAQ covering product, pricing, and technical issues

    Onboarding Manager Builds New Hire FAQ

    20-minute interview transformed tacit knowledge into comprehensive resource answering all common new hire questions

    Best Practices

    Pro Tip

    Don't pre-define the FAQ questions

    Pro Tip

    Discover questions through the conversation

    Pro Tip

    Get complete, standalone answers

    Pro Tip

    Ensure answers are actionable and specific

    Pro Tip

    Cover the most important questions thoroughly

    Common Mistakes to Avoid

    Pre-writing FAQ questions instead of discovering them through conversation

    Providing incomplete answers that generate follow-up questions

    Using jargon or technical language that confuses the target audience

    Missing the questions people should ask but don't know to ask

    Not organizing FAQs into logical categories for easy navigation

    Related Resources