[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-2PhuEqqWx6ISyO_lpuaPoKNbQ9WlP4ChKVB0rRPyVH4":3,"sanity-IvSCtHLWIGh-4gGhKSSvZqRNbQ4eDa1cgabwm76C3L8":375},{"data":4,"sourceMap":-1},{"latestPodcast":5,"latestReleases":14,"post":39,"recent":350},[6],{"_id":7,"publishedAt":8,"slug":9,"sponsored":12,"title":13},"f83eb5f0-1237-487f-84d8-f7abf2318c39","2026-06-25T07:40:00.000Z",{"_type":10,"current":11},"slug","code-isnt-causing-your-production-failures",null,"Code isn’t the only thing causing your production failures",[15,21,27,33],{"_id":16,"publishedAt":17,"slug":18,"title":20},"eb5b66eb-9410-4329-83bb-22bbff39402a","2026-04-28T13:00:00.000Z",{"_type":10,"current":19},"turn-scattered-knowledge-into-trusted-intelligence","Turning scattered knowledge into trusted intelligence: Stack Internal 2026.3",{"_id":22,"publishedAt":23,"slug":24,"title":26},"369c2401-b62e-4a37-8ff8-bf603023ecad","2026-03-02T15:03:00.988Z",{"_type":10,"current":25},"what-s-new-at-stack-overflow-march-2026","What’s new at Stack Overflow: March 2026",{"_id":28,"publishedAt":29,"slug":30,"title":32},"5e9053a4-07ea-447c-91ea-29e0b6228537","2026-02-02T15:00:00.000Z",{"_type":10,"current":31},"what-s-new-at-stack-overflow-february-2026","What’s new at Stack Overflow: February 2026",{"_id":34,"publishedAt":35,"slug":36,"title":38},"a1b538eb-a8a6-46d0-80a1-ac70ec9bb935","2026-01-05T10:00:00.000-05:00",{"_type":10,"current":37},"what-s-new-at-stack-overflow-january-2026","What’s new at Stack Overflow: January 2026",{"_createdAt":40,"_id":41,"_rev":42,"_type":43,"_updatedAt":44,"author":45,"body":57,"comments":320,"dateUrl":321,"excerpt":75,"legacyBody":322,"product":12,"publishedAt":325,"slug":326,"sponsored":12,"tags":328,"title":349,"visible":320},"2023-05-25T09:39:12Z","wp-post-13119","myT5Pq7GfgxKvTeIcgvU4s","blogPost","2023-11-08T17:23:47Z",[46],{"_createdAt":47,"_id":48,"_rev":49,"_type":50,"_updatedAt":47,"avatar":51,"employee":53,"name":54,"slug":55},"2023-05-23T16:27:18Z","wp-author-244","9HpbCsT2tq0xwozQfkcuVr","blogAuthor",{"_type":52},"image","none","Christopher Tozzi",{"current":56},"ctozzi",[58,69,77,93,101,109,118,126,134,144,152,160,168,176,184,192,209,217,225,238,250,262,274,286,305],{"_key":59,"_type":60,"children":61,"markDefs":67,"style":68},"5f356c0b6439","block",[62],{"_key":63,"_type":64,"marks":65,"text":66},"5f356c0b64390","span",[],"Knowledge sharing would be easy if it were a set-it-and-forget-it affair. But the reality is that knowledge is shared on an ongoing basis.",[],"normal",{"_key":70,"_type":60,"children":71,"markDefs":76,"style":68},"6b329a93a58f",[72],{"_key":73,"_type":64,"marks":74,"text":75},"6b329a93a58f0",[],"",[],{"_key":78,"_type":60,"children":79,"markDefs":89,"style":68},"40102bfa85ba",[80,84],{"_key":81,"_type":64,"marks":82,"text":83},"40102bfa85ba0",[],"Why companies are shifting to Q&A as the new format for knowledge management.\n",{"_key":85,"_type":64,"marks":86,"text":88},"40102bfa85ba1",[87],"844f581687f2","Download now (pdf)",[90],{"_key":87,"_type":91,"href":92,"reference":12},"link","https://info.stackoverflowsolutions.com/Enterprise_ABM-C-Suite-new-approach.html?utm_source=dmbs&utm_medium=blog&utm_campaign=20-Q1-Enterprise-ABM-C-Suite-new-approach&utm_content=Ad3Upp-LP-PDF",{"_key":94,"_type":60,"children":95,"markDefs":100,"style":68},"6e0c5f2a4d5a",[96],{"_key":97,"_type":64,"marks":98,"text":99},"6e0c5f2a4d5a0",[],"That should be intuitive, but it is a point that many organizations miss. They implement knowledge management strategies that are poorly suited for sustaining constant, ongoing sharing of organizational knowledge.",[],{"_key":102,"_type":60,"children":103,"markDefs":108,"style":68},"a101d53c2d24",[104],{"_key":105,"_type":64,"marks":106,"text":107},"a101d53c2d240",[],"Here’s how to avoid that pitfall and build a knowledge-management strategy that supports ongoing knowledge sharing:",[],{"_key":110,"_type":60,"children":111,"markDefs":116,"style":117},"373c1f0948fd",[112],{"_key":113,"_type":64,"marks":114,"text":115},"373c1f0948fd0",[],"The what and why of ongoing knowledge sharing",[],"h2",{"_key":119,"_type":60,"children":120,"markDefs":125,"style":68},"234efef4d3be",[121],{"_key":122,"_type":64,"marks":123,"text":124},"234efef4d3be0",[],"Ongoing knowledge sharing means what it sounds like: the ability to share information constantly, on a continuous basis.",[],{"_key":127,"_type":60,"children":128,"markDefs":133,"style":68},"f3278a8bf223",[129],{"_key":130,"_type":64,"marks":131,"text":132},"f3278a8bf2230",[],"Being able to share knowledge in an ongoing fashion is important for several reasons:",[],{"_key":135,"_type":60,"children":136,"level":141,"listItem":142,"markDefs":143,"style":68},"14be866e4448",[137],{"_key":138,"_type":64,"marks":139,"text":140},"14be866e44480",[],"Information is constantly changing. Whenever it changes, updated information must be reshared with people who rely on that information.",1,"bullet",[],{"_key":145,"_type":60,"children":146,"level":141,"listItem":142,"markDefs":151,"style":68},"d1567f6b037d",[147],{"_key":148,"_type":64,"marks":149,"text":150},"d1567f6b037d0",[],"It’s hard to know ahead of time with complete accuracy which information an employee or team might need to perform a certain task. Thus, the ability for that employee or group to ask for knowledge in order to gain clarifications or address needs that were not foreseen is critical.",[],{"_key":153,"_type":60,"children":154,"level":141,"listItem":142,"markDefs":159,"style":68},"fdf78c92e36f",[155],{"_key":156,"_type":64,"marks":157,"text":158},"fdf78c92e36f0",[],"The back-and-forth sharing of knowledge between different members of your organization is how organic organizational knowledge is cultivated. It is only by being able to share new discoveries and feedback on a constant basis that you can keep organizational knowledge up-to-date and accurate.",[],{"_key":161,"_type":60,"children":162,"markDefs":167,"style":117},"0a38f3d14ab9",[163],{"_key":164,"_type":64,"marks":165,"text":166},"0a38f3d14ab90",[],"The challenge of ongoing knowledge sharing",[],{"_key":169,"_type":60,"children":170,"markDefs":175,"style":68},"5470b9715aa0",[171],{"_key":172,"_type":64,"marks":173,"text":174},"5470b9715aa00",[],"Again, it may seem intuitive that effective knowledge sharing should have these qualities. If you look at the ways in which many organizations manage internal knowledge, however, you’ll notice that their strategies do little to promote ongoing sharing of information.",[],{"_key":177,"_type":60,"children":178,"markDefs":183,"style":68},"07130c1f5133",[179],{"_key":180,"_type":64,"marks":181,"text":182},"07130c1f51330",[],"For example, consider documentation databases. They may be a good way to document very specific technical information that does not change frequently, but if you rely on a centralized documentation database to store all internal knowledge, you will struggle with the inability to update that information quickly or improve it based on feedback from different members of your team. Instead, your knowledge base will be centralized and delivered from the top-down. You end up imposing knowledge on your employees rather than allowing them to cultivate it organically.",[],{"_key":185,"_type":60,"children":186,"markDefs":191,"style":68},"93530616a2a4",[187],{"_key":188,"_type":64,"marks":189,"text":190},"93530616a2a40",[],"In other cases, organizations may think that they have achieved ongoing knowledge sharing because they rely on real-time (or near real-time) communication tools, like instant messages or face-to-face meetings, as the foundation of their strategy for sharing organizational knowledge. But real-time communication is not the same thing as ongoing knowledge sharing.",[],{"_key":193,"_type":60,"children":194,"markDefs":208,"style":68},"6cd9d711f834",[195,199,204],{"_key":196,"_type":64,"marks":197,"text":198},"6cd9d711f8340",[],"Ephemeral communication tools like instant messages and meetings are not a good way of recording and sharing information that needs to be retained for a long period of time; nor are they very effective for sharing knowledge across the organization, because the number of people you can effectively include in a meeting or instant message channel is limited. (Well, you ",{"_key":200,"_type":64,"marks":201,"text":203},"6cd9d711f8341",[202],"em","could",{"_key":205,"_type":64,"marks":206,"text":207},"6cd9d711f8342",[]," invite as many people as you want, but if you have company-wide meetings every week, you will probably waste a lot of time that your employees could spend working, and they may not pay much attention in a large group setting anyway. As for instant messages, it’s unlikely that everyone on your team will pay attention to mass communication channels.)",[],{"_key":210,"_type":60,"children":211,"markDefs":216,"style":117},"29139b2c869c",[212],{"_key":213,"_type":64,"marks":214,"text":215},"29139b2c869c0",[],"Effective strategies for ongoing knowledge sharing",[],{"_key":218,"_type":60,"children":219,"markDefs":224,"style":68},"9622d169ebe7",[220],{"_key":221,"_type":64,"marks":222,"text":223},"9622d169ebe70",[],"In contrast to the solutions described above, an effective knowledge-sharing strategy is founded on knowledge management tools that are:",[],{"_key":226,"_type":60,"children":227,"level":141,"listItem":142,"markDefs":237,"style":68},"e5ed327db96f",[228,233],{"_key":229,"_type":64,"marks":230,"text":232},"e5ed327db96f0",[231],"strong","Discoverable",{"_key":234,"_type":64,"marks":235,"text":236},"e5ed327db96f1",[],", so that anyone who needs information can easily find it.",[],{"_key":239,"_type":60,"children":240,"level":141,"listItem":142,"markDefs":249,"style":68},"b4e42ee00683",[241,245],{"_key":242,"_type":64,"marks":243,"text":244},"b4e42ee006830",[231],"Collaborative",{"_key":246,"_type":64,"marks":247,"text":248},"b4e42ee006831",[],", meaning that all employees or stakeholders can participate in building and improving organizational knowledge.",[],{"_key":251,"_type":60,"children":252,"level":141,"listItem":142,"markDefs":261,"style":68},"3cbf64a296da",[253,257],{"_key":254,"_type":64,"marks":255,"text":256},"3cbf64a296da0",[231],"Easily accessible",{"_key":258,"_type":64,"marks":259,"text":260},"3cbf64a296da1",[]," to everyone who needs to be able to work with them.",[],{"_key":263,"_type":60,"children":264,"level":141,"listItem":142,"markDefs":273,"style":68},"9cf4d45ff333",[265,269],{"_key":266,"_type":64,"marks":267,"text":268},"9cf4d45ff3330",[231],"Able to store information persistently",{"_key":270,"_type":64,"marks":271,"text":272},"9cf4d45ff3331",[],", but still flexible enough that information can be updated easily.",[],{"_key":275,"_type":60,"children":276,"level":141,"listItem":142,"markDefs":285,"style":68},"6f221b635c65",[277,281],{"_key":278,"_type":64,"marks":279,"text":280},"6f221b635c650",[231],"Easily tailored",{"_key":282,"_type":64,"marks":283,"text":284},"6f221b635c651",[]," to the individual needs of different teams or individuals when necessary.",[],{"_key":287,"_type":60,"children":288,"markDefs":302,"style":68},"1dd504a517b3",[289,293,298],{"_key":290,"_type":64,"marks":291,"text":292},"1dd504a517b30",[],"Tools like documentation databases, instant messages, emails, or face-to-face meetings don’t have these qualities. Solutions like ",{"_key":294,"_type":64,"marks":295,"text":297},"1dd504a517b31",[296],"8215be3188ba","Stack Overflow for Teams",{"_key":299,"_type":64,"marks":300,"text":301},"1dd504a517b32",[]," do. By making it simple to record and share knowledge in a user-friendly, intuitive interface, and to update knowledge on a continuous basis, Teams enables a level of flexibility and dynamism that facilitates truly ongoing knowledge sharing.\n",[303],{"_key":296,"_type":91,"href":304,"reference":12},"https://stackoverflow.com/teams",{"_key":306,"_type":60,"children":307,"markDefs":317,"style":68},"fb46bf707489",[308,312],{"_key":309,"_type":64,"marks":310,"text":311},"fb46bf7074890",[],"See how Stack Overflow for Teams can transform collaboration within your organization.\n",{"_key":313,"_type":64,"marks":314,"text":316},"fb46bf7074891",[315],"a716590ef950","Learn more",[318],{"_key":315,"_type":91,"href":319,"reference":12},"https://info.stackoverflowsolutions.com/Enterprise_ABM-Overview.html?utm_source=dmbs&utm_medium=blog&utm_campaign=20-Q1-Enterprise-ABM-C-Suite-new-approach&utm_content=Ad3Upp-Prod-Overview",true,"2019/09/27",{"code":323,"language":324},"\u003C!-- wp:columns {\"className\":\"has-2-columns\"} -->\n\u003Cdiv class=\"wp-block-columns has-2-columns\">\u003C!-- wp:column -->\n\u003Cdiv class=\"wp-block-column\">\u003C!-- wp:paragraph -->\n\u003Cp>Knowledge sharing would be easy if it were a set-it-and-forget-it affair. But the reality is that knowledge is shared on an ongoing basis.\u003C/p>\n\u003C!-- /wp:paragraph -->\u003C/div>\n\u003C!-- /wp:column -->\n\n\u003C!-- wp:column -->\n\u003Cdiv class=\"wp-block-column\">\u003C!-- wp:paragraph {\"backgroundColor\":\"very-light-gray\"} -->\n\u003Cp class=\"has-background has-very-light-gray-background-color\"> Why companies are shifting to Q&A as the new format for knowledge management.\u003Cbr>\u003Ca href=\"https://info.stackoverflowsolutions.com/Enterprise_ABM-C-Suite-new-approach.html?utm_source=dmbs&utm_medium=blog&utm_campaign=20-Q1-Enterprise-ABM-C-Suite-new-approach&utm_content=Ad3Upp-LP-PDF\">Download now (pdf)\u003C/a>\u003C/p>\n\u003C!-- /wp:paragraph -->\u003C/div>\n\u003C!-- /wp:column -->\u003C/div>\n\u003C!-- /wp:columns -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>That should be intuitive, but it is a point that many organizations miss. They implement knowledge management strategies that are poorly suited for sustaining constant, ongoing sharing of organizational knowledge.\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>Here’s how to avoid that pitfall and build a knowledge-management strategy that supports ongoing knowledge sharing:\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:heading -->\n\u003Ch2>The what and why of ongoing knowledge sharing\u003C/h2>\n\u003C!-- /wp:heading -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>Ongoing knowledge sharing means what it sounds like: the ability to share information constantly, on a continuous basis.\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>Being able to share knowledge in an ongoing fashion is important for several reasons:\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:list -->\n\u003Cul>\u003Cli>Information is constantly changing. Whenever it changes, updated information must be reshared with people who rely on that information.\u003C/li>\u003Cli>It’s hard to know ahead of time with complete accuracy which information an employee or team might need to perform a certain task. Thus, the ability for that employee or group to ask for knowledge in order to gain clarifications or address needs that were not foreseen is critical.\u003C/li>\u003Cli>The back-and-forth sharing of knowledge between different members of your organization is how organic organizational knowledge is cultivated. It is only by being able to share new discoveries and feedback on a constant basis that you can keep organizational knowledge up-to-date and accurate.\u003C/li>\u003C/ul>\n\u003C!-- /wp:list -->\n\n\u003C!-- wp:heading -->\n\u003Ch2>The challenge of ongoing knowledge sharing\u003C/h2>\n\u003C!-- /wp:heading -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>Again, it may seem intuitive that effective knowledge sharing should have these qualities. If you look at the ways in which many organizations manage internal knowledge, however, you’ll notice that their strategies do little to promote ongoing sharing of information.\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>For example, consider documentation databases. They may be a good way to document very specific technical information that does not change frequently, but if you rely on a centralized documentation database to store all internal knowledge, you will struggle with the inability to update that information quickly or improve it based on feedback from different members of your team. Instead, your knowledge base will be centralized and delivered from the top-down. You end up imposing knowledge on your employees rather than allowing them to cultivate it organically.\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>In other cases, organizations may think that they have achieved ongoing knowledge sharing because they rely on real-time (or near real-time) communication tools, like instant messages or face-to-face meetings, as the foundation of their strategy for sharing organizational knowledge. But real-time communication is not the same thing as ongoing knowledge sharing.\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>Ephemeral communication tools like instant messages and meetings are not a good way of recording and sharing information that needs to be retained for a long period of time; nor are they very effective for sharing knowledge across the organization, because the number of people you can effectively include in a meeting or instant message channel is limited. (Well, you \u003Cem>could\u003C/em> invite as many people as you want, but if you have company-wide meetings every week, you will probably waste a lot of time that your employees could spend working, and they may not pay much attention in a large group setting anyway. As for instant messages, it’s unlikely that everyone on your team will pay attention to mass communication channels.)\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:heading -->\n\u003Ch2>Effective strategies for ongoing knowledge sharing\u003C/h2>\n\u003C!-- /wp:heading -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>In contrast to the solutions described above, an effective knowledge-sharing strategy is founded on knowledge management tools that are:\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:list -->\n\u003Cul>\u003Cli>\u003Cstrong>Discoverable\u003C/strong>, so that anyone who needs information can easily find it.\u003C/li>\u003Cli>\u003Cstrong>Collaborative\u003C/strong>, meaning that all employees or stakeholders can participate in building and improving organizational knowledge.\u003C/li>\u003Cli>\u003Cstrong>Easily accessible\u003C/strong> to everyone who needs to be able to work with them.\u003C/li>\u003Cli>\u003Cstrong>Able to store information persistently\u003C/strong>, but still flexible enough that information can be updated easily.\u003C/li>\u003Cli>\u003Cstrong>Easily tailored\u003C/strong> to the individual needs of different teams or individuals when necessary.\u003C/li>\u003C/ul>\n\u003C!-- /wp:list -->\n\n\u003C!-- wp:paragraph -->\n\u003Cp>Tools like documentation databases, instant messages, emails, or face-to-face meetings don’t have these qualities. Solutions like \u003Ca href=\"https://stackoverflow.com/teams\">Stack Overflow for Teams\u003C/a> do. By making it simple to record and share knowledge in a user-friendly, intuitive interface, and to update knowledge on a continuous basis, Teams enables a level of flexibility and dynamism that facilitates truly ongoing knowledge sharing.\u003Cbr>\u003C/p>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:html -->\n\u003Cp class=\"has-background has-very-light-gray-background-color\">See how Stack Overflow for Teams can transform collaboration within your organization.\u003Cbr>\u003Ca href=\"https://info.stackoverflowsolutions.com/Enterprise_ABM-Overview.html?utm_source=dmbs&utm_medium=blog&utm_campaign=20-Q1-Enterprise-ABM-C-Suite-new-approach&utm_content=Ad3Upp-Prod-Overview\">Learn more\u003C/a>\u003C/p>\n\u003C!-- /wp:html -->\n\n\u003C!-- wp:block {\"ref\":13951} /-->","html","2019-09-27T18:42:56.000Z",{"current":327},"best-practices-for-ongoing-knowledge-sharing",[329,337,342],{"_createdAt":330,"_id":331,"_rev":332,"_type":333,"_updatedAt":330,"slug":334,"title":336},"2023-05-23T16:43:21Z","wp-tagcat-abm","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":335},"abm","ABM",{"_createdAt":330,"_id":338,"_rev":332,"_type":333,"_updatedAt":330,"slug":339,"title":341},"wp-tagcat-knowledge-management",{"current":340},"knowledge-management","knowledge management",{"_createdAt":330,"_id":343,"_rev":344,"_type":333,"_updatedAt":345,"slug":346,"title":348},"wp-tagcat-productivity","ZP7627ZkmfDRGke9Ig9IwB","2024-01-23T15:01:58Z",{"current":347},"productivity","Productivity","Best Practices for Ongoing Knowledge Sharing",[351,357,363,369],{"_id":352,"publishedAt":353,"slug":354,"sponsored":12,"title":356},"28e560af-f0aa-4d46-bd90-f435ad604aa7","2026-06-26T14:00:27.102Z",{"_type":10,"current":355},"paging-charity-how-can-engineering-leaders-avoid-becoming-bond-villains","Paging Charity! How can engineering leaders avoid becoming Bond villains?",{"_id":358,"publishedAt":359,"slug":360,"sponsored":12,"title":362},"4b22c2a3-3779-4966-93eb-5230391dbdce","2026-06-23T14:08:58.595Z",{"_type":10,"current":361},"your-ai-shipped-a-backend-that-boots-that-is-the-whole-problem","Your AI shipped a backend that boots. That is the whole problem.",{"_id":364,"publishedAt":365,"slug":366,"sponsored":12,"title":368},"5cf362e1-fe7b-45af-b69c-914731c6a052","2026-06-23T14:00:00.000Z",{"_type":10,"current":367},"the-2026-developer-survey-is-now-open-for-human-developers-only","The 2026 Developer Survey is now open (for human developers only)!",{"_id":370,"publishedAt":371,"slug":372,"sponsored":12,"title":374},"30b995f7-7cb9-4dd8-bf71-d0685940a32b","2026-06-19T14:00:00.000Z",{"_type":10,"current":373},"dispatches-from-o-reilly-from-capabilities-to-responsibilities","Dispatches from O'Reilly: From capabilities to responsibilities",{"data":376,"sourceMap":-1},{"count":377,"lastTimestamp":12},0]