<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Drawing A Line in Community Central forum</title>
    <link>https://www.servicenow.com/community/community-central-forum/drawing-a-line/m-p/3591562#M7779</link>
    <description>&lt;P&gt;Knowledge Managers and Creators, where do you draw a line?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm stuck between reducing the number of user-facing technical support "How to" articles, which crams a lot of content into each, or having a lot of much shorter articles that address fewer resolution options.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What criteria do you use to determine the overall amount of content in a single article?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm writing these articles without AI because while Copilot, Gemini, etc. provide basic information (e.g., update your device drivers), they don't cover the nitty-gritty of&amp;nbsp;&lt;EM&gt;how&lt;/EM&gt; to perform these actions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example, some articles have more than a dozen topics, which may be overwhelming for readers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My overall goal is using knowledge to reduce ticket count but I don't want to drown them in a sea of information. When do you hit a limit?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your comments.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 26 Aug 2026 13:52:00 GMT</pubDate>
    <dc:creator>DavidReynolds</dc:creator>
    <dc:date>2026-08-26T13:52:00Z</dc:date>
    <item>
      <title>Drawing A Line</title>
      <link>https://www.servicenow.com/community/community-central-forum/drawing-a-line/m-p/3591562#M7779</link>
      <description>&lt;P&gt;Knowledge Managers and Creators, where do you draw a line?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm stuck between reducing the number of user-facing technical support "How to" articles, which crams a lot of content into each, or having a lot of much shorter articles that address fewer resolution options.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What criteria do you use to determine the overall amount of content in a single article?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm writing these articles without AI because while Copilot, Gemini, etc. provide basic information (e.g., update your device drivers), they don't cover the nitty-gritty of&amp;nbsp;&lt;EM&gt;how&lt;/EM&gt; to perform these actions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example, some articles have more than a dozen topics, which may be overwhelming for readers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My overall goal is using knowledge to reduce ticket count but I don't want to drown them in a sea of information. When do you hit a limit?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your comments.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2026 13:52:00 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/drawing-a-line/m-p/3591562#M7779</guid>
      <dc:creator>DavidReynolds</dc:creator>
      <dc:date>2026-08-26T13:52:00Z</dc:date>
    </item>
  </channel>
</rss>

