--- title: "Towards a Question and Answer world" id: "18000" type: "post" slug: "towards-a-question-and-answer-world" published_at: "2025-06-02T10:31:30+00:00" modified_at: "2025-06-02T11:35:35+00:00" url: "https://www.cherryleaf.com/2025/06/towards-a-question-and-answer-world/" markdown_url: "https://www.cherryleaf.com/2025/06/towards-a-question-and-answer-world.md" excerpt: "Technical communication has traditionally been rooted in instructional guides: comprehensive resources users could turn to when they needed information. But that information was only useful if users could actually find it. The expectation was that users would search for what..." taxonomy_category: - "AI" - "Technical Communication" - "trends" taxonomy_post_tag: - "AI" - "questions" - "trends" --- Technical communication has traditionally been rooted in instructional guides: comprehensive resources users could turn to when they needed information. But that information was only useful if users could actually find it. The expectation was that users would search for what they needed and then read it. On the provider’s side, the goal was to make content easy to find, understand, and act upon. While those in-depth resources still have their place, the way users want to access information may be undergoing a seismic shift. [Michael Andrews](https://www.linkedin.com/feed/update/urn:li:activity:7332045234794594304/) and [Ardis Ramey](https://www.linkedin.com/posts/ardisramey_chatbots-are-shifting-the-emphasis-from-reading-activity-7333526225388216320-avmM/) have suggested technical communication is rapidly moving towards a question-and-answer (Q&A) paradigm. ## From reading to asking According to Ardis Ramey, chatbots are shifting the emphasis from *reading* to *asking*. Reading requires time, focus, and often some prior knowledge. Asking, by contrast, is fast, intuitive, and accessible. In this new model, users don’t need to know *where* the answer lives – they just need to know *what* they want to ask. ## Why the change? For years, we’ve been conditioned by search engines like Google. [Questions dominate search queries.](https://www.seocopilot.com/search-query/percentage-of-search-queries-are-questions) Voice searches tend to be more conversational and are more likely to be phrased as questions. Estimates suggest that about [65% of voice searches are in question format](https://magecomp.com/blog/google-search-statistics-and-facts/) . And now we have chatbots. The promise is: - Users get quick, direct answers. - Chatbots can understand context better than static documents, offering more tailored responses. - Reduced cognitive load – sifting through documentation is work; getting an answer directly feels effortless. ## But not a static FAQ For years, the FAQ page been a staple of many websites. But as the UK’s Government Digital Service (GDS) pointed out in their post [FAQs: why we don’t have them](https://gds.blog.gov.uk/2013/07/25/faqs-why-we-dont-have-them/) , traditional FAQ pages often become: - A dumping ground for content that doesn’t fit neatly elsewhere. - A reflection of organisational assumptions about what users ask, rather than actual user needs. - A source of content duplication and maintenance headaches. - A poor user experience, forcing users to scan a long list of questions that may or may not be relevant to their specific, nuanced problem. GDS argued that if information is important enough to be in an FAQ, it should be findable and well-integrated into the main content where users naturally look. A Q&A world shouldn’t be a world of static FAQs. Instead of directing users to a fixed list, every part of the knowledge base becomes a source of answers. The FAQ is everywhere and nowhere specific. Users won’t navigate to a particular list. They’ll instead ask their question via a chatbot or an intelligent search bar. ## What does this mean for technical communicators? This shift isn’t a death knell for Technical Authors. It’s a refocusing of our core skills. Long-form guides and Help systems don’t disappear; they become the foundational content for these Q&A experiences. Here’s how our role may need to adapt: 1. A Q&A approach focuses on the direct path from question to isolated answer. This doesn’t mean abandoning structure, but rather ensuring each part can be effectively decontextualised and re-contextualised by an AI. 2. Content must be granular, capable of standing alone as a coherent answer to a specific question. 3. Clear headings, structured sections, and rich metadata (schemas, taxonomies, and consistent terminology) help AI understand, index, and retrieve information accurately. 4. Ambiguity is the enemy of AI comprehension. Our writing must be precise and unambiguous. 5. We must become adept at predicting and understanding what users will ask, not just what tasks they perform. This means analysing search queries, support tickets, and chatbot logs to continually refine content. In short, the future isn’t about crafting a list of 20 common questions. It’s about building a robust, intelligent knowledge system that can handle any question, and deliver a meaningful answer. ## The evolving skill set of the Technical Author The core competencies remain, but they’re evolving. We’ll likely need to: - Learn tools for publishing content to AI-ready formats, or adapt to new features in existing platforms. - Design content specifically for AI consumption and for question-based discovery. - Continuously maintain and refine content, ensuring AI learns from the right sources and improves over time. ## Challenges and opportunities Naturally, this shift brings challenges: - AI can hallucinate, provide incorrect answers, or miss important nuance. - A poorly designed chatbot interface can feel like a modern-day Clippy. - Users may receive shallow answers when deeper context is needed. This is where technical communicators shine, by structuring content impeccably and overseeing the quality of AI-driven experiences. The opportunities, though, are significant: - Faster problem resolution, and happier users. - Improved content findability. - Reduced strain on support teams through call deflection. - A more strategic role for techcomm professionals as the architects and curators of knowledge systems. ## What do you think? How is your organisation navigating this shift? Are you already designing for question-based access? Share your thoughts in the comments below. ### Share this: - [Share on Facebook (Opens in new window) Facebook](https://www.cherryleaf.com/2025/06/towards-a-question-and-answer-world/?share=facebook) - [Share on LinkedIn (Opens in new window) LinkedIn](https://www.cherryleaf.com/2025/06/towards-a-question-and-answer-world/?share=linkedin) - [Share on WhatsApp (Opens in new window) WhatsApp](https://www.cherryleaf.com/2025/06/towards-a-question-and-answer-world/?share=jetpack-whatsapp) - [Share on Bluesky (Opens in new window) Bluesky](https://www.cherryleaf.com/2025/06/towards-a-question-and-answer-world/?share=bluesky) - ### *Related* ### One Comment One of my clients recently transitioned from structured online help (which I previously authored) to a knowledge base environment for user assistance. I’ve been closely involved in this shift, and it’s been a valuable learning experience as I navigate a range of tools and technologies. I now use AI to help extract and repurpose existing content into knowledge base articles and videos, ensuring each piece includes structured sections, meta-tags, and other search-friendly elements to improve discoverability. This is an ongoing project—next steps include optimising content for the platform’s built-in chatbot and developing a process for turning support tickets into helpful knowledge base articles. Interesting times! ### Leave a Reply[Cancel reply](/2025/06/towards-a-question-and-answer-world/#respond) This site uses Akismet to reduce spam. [Learn how your comment data is processed.](https://akismet.com/privacy/) #### Previous post [Results from our “Using AI in techcomm” 2025 survey](https://www.cherryleaf.com/2025/05/results-from-our-using-ai-in-techcomm-2025-survey/) #### Next post [Why developer portals fail (Hint: It’s probably your docs)](https://www.cherryleaf.com/2025/06/why-developer-portals-fail-hint-its-probably-your-docs/) #### Browse posts by month Browse posts by month Select Month October 2026 (3) September 2026 (12) August 2026 (8) July 2026 (7) June 2026 (14) May 2026 (8) April 2026 (6) March 2026 (14) February 2026 (9) January 2026 (9) December 2025 (7) November 2025 (9) October 2025 (10) September 2025 (7) August 2025 (6) July 2025 (1) June 2025 (3) May 2025 (2) April 2025 (5) March 2025 (3) February 2025 (3) January 2025 (2) November 2024 (8) October 2024 (3) September 2024 (2) August 2024 (3) July 2024 (4) June 2024 (1) May 2024 (2) April 2024 (4) March 2024 (1) February 2024 (2) January 2024 (1) December 2023 (2) November 2023 (9) October 2023 (8) September 2023 (5) August 2023 (3) July 2023 (1) June 2023 (1) May 2023 (2) April 2023 (3) March 2023 (2) January 2023 (2) December 2022 (4) November 2022 (1) October 2022 (1) September 2022 (1) August 2022 (1) July 2022 (1) June 2022 (1) May 2022 (2) April 2022 (1) March 2022 (1) February 2022 (1) January 2022 (2) December 2021 (1) November 2021 (2) October 2021 (1) August 2021 (1) July 2021 (2) June 2021 (3) May 2021 (5) April 2021 (3) March 2021 (3) February 2021 (1) January 2021 (2) December 2020 (4) November 2020 (4) August 2020 (3) February 2020 (3) January 2020 (1) November 2019 (3) October 2019 (1) September 2019 (1) August 2019 (3) July 2019 (2) June 2019 (3) May 2019 (4) April 2019 (1) November 2018 (2) October 2018 (1) July 2018 (2) June 2018 (4) May 2018 (2) April 2018 (3) March 2018 (4) February 2018 (2) January 2018 (3) December 2017 (2) October 2017 (3) September 2017 (1) August 2017 (3) July 2017 (2) June 2017 (7) May 2017 (4) April 2017 (5) March 2017 (1) February 2017 (7) January 2017 (1) December 2016 (3) November 2016 (4) October 2016 (1) September 2016 (5) July 2016 (1) June 2016 (3) May 2016 (1) April 2016 (2) February 2016 (2) January 2016 (5) December 2015 (1) November 2015 (4) October 2015 (2) August 2015 (1) July 2015 (1) June 2015 (2) May 2015 (3) February 2015 (2) January 2015 (6) December 2014 (1) October 2014 (1) September 2014 (4) June 2014 (4) May 2014 (1) April 2014 (2) March 2014 (3) February 2014 (4) January 2014 (4) November 2013 (2) October 2013 (5) September 2013 (3) July 2013 (3) June 2013 (11) May 2013 (4) April 2013 (6) March 2013 (7) February 2013 (4) January 2013 (4) December 2012 (9) November 2012 (23) October 2012 (14) September 2012 (8) August 2012 (4) July 2012 (12) June 2012 (12) May 2012 (10) April 2012 (8) March 2012 (12) February 2012 (3) January 2012 (6) December 2011 (2) October 2011 (3) August 2011 (1) June 2011 (5) May 2011 (2) April 2011 (1) January 2011 (1) December 2010 (1) November 2010 (3) October 2010 (4) September 2010 (8) August 2010 (5) May 2010 (2) April 2010 (3) March 2010 (3) February 2010 (2) January 2010 (3) December 2009 (2) November 2009 (6) September 2009 (1) July 2009 (6) June 2009 (7) April 2009 (8) March 2009 (3) February 2009 (3) January 2009 (3) December 2008 (1) November 2008 (3) October 2008 (3) September 2008 (4) August 2008 (1) July 2008 (3) June 2008 (5) May 2008 (2) April 2008 (2) March 2008 (3) February 2008 (2) January 2008 (1) November 2007 (3) October 2007 (2) September 2007 (1) July 2007 (3) November 2006 (1) October 2006 (2) September 2006 (3) August 2006 (1) April 2006 (1) March 2006 (3) #### Browse posts by category