---
title: "Knowledge Management"
description: "26 posts about Knowledge Management, summarised, each linking to the original."
---

# Knowledge Management
> 26 posts about Knowledge Management, summarised, each linking to the original.

## Articles

### [Why your platform team shouldn't build an AI context layer (even though they probably could)](https://yomu.fyi/post/why-your-platform-team-shouldn-t-build-an-ai-context-layer-even-though.md)
- Company: [Stack Overflow](https://yomu.fyi/company/stack-overflow.md)
- Author: Eira May
- Published: Oct 15, 2026
- Type: Problem & solution

Many engineering teams mistakenly think building an internal AI knowledge context layer is as simple as standing up a vector database and wiring a RAG pipeline to documentation. In reality, a production-grade pipeline requires five continuously maintained stages—capture, deliver, govern, organize, and validate—where each stage’s long-term cost compounds as vendor APIs change and content ages. The critical innovation is the knowledge node, a living record carrying source, ownership, and an automatically computed trust score based on authorship, usage, recency, and conflicts. Trust decays over time, prompting owners for lightweight revalidation when confidence drops, and knowledge is automatically scoped to the correct audience without manual filing. For product companies not in the knowledge-infrastructure business, the compounding maintenance burden makes building this pipeline a distraction compared to leveraging existing platforms like Stack Internal.


### [How We Spread Engineering Knowledge &amp; Culture Across Intercom](https://yomu.fyi/post/how-we-spread-engineering-knowledge-amp-culture-across-intercom.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Problem & solution

Large engineering organizations often face siloed knowledge and culture as teams focus on their own domains. Intercom addresses this with engineering tours, where engineers temporarily transfer to another team to work on a specific project, such as building a scalable solution for database performance issues. New engineers go on tour within their first few months, and all engineers are encouraged to tour at least once a year. Tours are designed with a mentor and can be feature-oriented, shipping a new product or tool with a demo at the weekly Show and Tell, or tech-debt oriented, fixing bugs or performance issues. Beyond code, tours build relationships and spread culture across offices in Dublin, London, and San Francisco, and the concept has expanded to other departments like Customer Support and Marketing; engineers bring back learnings to their home teams.


### [The Ticket: Fueling The AI machine with the knowledge it needs](https://yomu.fyi/post/the-ticket-fueling-the-ai-machine-with-the-knowledge-it-needs.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 5, 2026
- Type: Problem & solution

The performance of an AI-driven customer support engine depends directly on the quality of the knowledge that feeds it, as accurate, up-to-date content is critical for giving customers instant and trustworthy answers. Investing time and care into help content can significantly boost automated resolution rates, as Intercom has experienced firsthand. Many busy support teams struggle to prioritize maintaining their help centers due to limited resources, but filling content gaps and updating content after launching new products is essential for AI success. Knowledge content compounds in value over time; Intercom’s transition from its Resolution Bot to the Fin AI chatbot resulted in resolution rates skyrocketing from the start. Knowledge management should be cultivated as a company-wide responsibility, with input from product, engineering, sales, and marketing teams, and in the near future, internal knowledge will also be fed to AI to help agents answer complex queries.


### [Anyone can start building verified knowledge with Stack Internal](https://yomu.fyi/post/anyone-can-start-building-verified-knowledge-with-stack-internal.md)
- Company: [Stack Overflow](https://yomu.fyi/company/stack-overflow.md)
- Author: Caroline Thomas
- Published: Sep 30, 2026
- Type: Announcement

Stack Internal, now generally available, enables anyone to create a free Starter workspace, connect their top three data sources, and collaborate with a couple of teammates to capture and store verified knowledge. The platform evaluates knowledge using five signals—provenance, recency, expertise, corroboration, and human validation—and automatically flags conflicting information at response time to convert team know-how into validated institutional memory. It automatically detects subject matter experts based on topics, and when a critical knowledge gap arises, it notifies the right expert directly in Slack for validation, allowing confirmation or updates within that conversation. An MCP server pushes trusted, verified knowledge into AI tools like Claude, Codex, and Cursor, grounding responses in the organization’s own know-how rather than model guesses. Governance features include custom roles and permissions, full activity tracking with self-serve exportable audit trails, and a knowledge health dashboard displaying metrics like Helpful Answer Rate and Daily Active Users.


### [Unity Catalog Pages: a governed home for your business knowledge in Genie Ontology](https://yomu.fyi/post/unity-catalog-pages-a-governed-home-for-your-business-knowledge-in-gen.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Tim Feng, Ashish Singh
- Published: Sep 23, 2026
- Type: Announcement

Business concepts like active customer or completed trip are often defined differently across teams, scattered in Slack threads and spreadsheets, causing AI agents to guess confidently when answering questions. Databricks introduces Unity Catalog Pages as a governed home within Genie Ontology where data stewards with Genie Code define the authoritative meaning of those terms and entities. Pages complement existing semantics — metric views how to calculate, domains where to look, and certification what to trust — by capturing what each concept means. Genie Code can bootstrap Pages by extracting definitions from Confluence, Slack, Google Docs, or GitHub via MCP-connected tools, turning weeks of work into minutes. When Genie One uses a Page to ground an answer, the Page is cited as a clickable source so users can inspect the definition and verify the reasoning.


### [From better privacy to our new ChatGPT plugin, here's what's new on Stack Overflow for Agents](https://yomu.fyi/post/from-better-privacy-to-our-new-chatgpt-plugin-here-s-what-s-new-on-sta.md)
- Company: [Stack Overflow](https://yomu.fyi/company/stack-overflow.md)
- Author: Phoebe Sajor, David Gibson
- Published: Sep 15, 2026
- Type: Announcement

Stack Overflow for Agents is an API-first knowledge exchange designed to address the “ephemeral intelligence gap,” in which agents lose solutions when a session’s context window disappears. The platform preserves agent-generated knowledge and adds trust scores, validation gateways, reputation-linked posts, and steering context to encourage verification and corrections. After three months, Stack Overflow has introduced a ChatGPT plugin that packages its existing skills into one installable OpenAI capability, plus Playbooks for structured procedural workflows distinct from Blueprints and TILs. New controls let users choose whether agents post locally, save drafts, request review before publishing, or post autonomously; read-only access supports proprietary work. The team says agents are already using and improving shared knowledge, but it is still seeking conclusive, quantifiable evidence of the platform’s value.


### [The new product introduction process: How to make sure your Agent is ready every time you ship](https://yomu.fyi/post/the-new-product-introduction-process-how-to-make-sure-your-agent-is-re.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Author: Sean Reid
- Published: Jun 26, 2026
- Type: Tutorial

Frequent product releases can leave an AI Agent’s knowledge base outdated, causing it to hand off launch-related questions to humans when support volume peaks. The NPI process described here makes Agent readiness part of shipping, with support involved early in product, engineering, and go-to-market planning. Before launch, teams prepare clear customer-language content with full context, review and retire affected or duplicate material, then test likely questions, edge cases, and answer quality in the customer environment. At Fin, release details, walkthrough notes, demos, and GTM briefs form an input package for Operator, which proposes content updates, drafts, FAQ tests, and fixes. Post-launch Monitors and Scorecards track resolution rate and CX Score for two or four weeks, depending on launch complexity, to guide improvements.


### [The ultimate guide to knowledge management for your Service Agent](https://yomu.fyi/post/the-ultimate-guide-to-knowledge-management-for-your-service-agent.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Author: Beth-Ann Sher
- Published: May 27, 2026
- Type: Tutorial

AI-driven customer service depends on knowledge management because a Service Agent needs accurate product, feature, policy, and troubleshooting information to resolve queries end to end. The guide divides the work into two phases: building a knowledge base, and maintaining, optimizing, and scaling existing content. It recommends using support conversations and tools such as Fin Recommendations to identify gaps, prioritize FAQs, onboarding guides, troubleshooting material, and other resources, then centralize content and control what the Agent can use. Ongoing practices include scheduled reviews, a request log, launch-planning updates, consistent terminology, audience targeting, and contact details for escalation. The stated conclusion is that knowledge management should be a continuous core service function, with improvements producing more resolutions, better data, and further opportunities to refine support.


### [Meet Operator: An Agent for your customer operations](https://yomu.fyi/post/meet-operator-an-agent-for-your-customer-operations.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Author: Patrick Andrews
- Published: May 15, 2026
- Type: Announcement

Operator is an agent for customer operations that works across Fin and the Intercom helpdesk, addressing the ongoing effort required to manage AI and human support work. It can analyze operational data and conversation samples, explain metric changes and root causes, maintain help-center content from briefs, and identify content gaps with localized drafts. Operator can also debug Fin conversations, propose configuration fixes, build Procedures and other automations, run simulation tests, and support incident response and rep management. Its purpose-built tools and proposal system present structured diffs for review, editing, and approval before changes go live; the announcement says more than 200 early users are trying it and that it is available in early access.


### [The ultimate guide to knowledge management for your Sales Agent](https://yomu.fyi/post/the-ultimate-guide-to-knowledge-management-for-your-sales-agent.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Author: Beth-Ann Sher,Fred Walton
- Published: May 13, 2026
- Type: Tutorial

AI-powered inbound sales depends on knowledge management: accurate, current information about products, pricing, plans, qualification, and routing gives a Sales Agent the context to answer questions and guide buyers. The guide describes knowledge management as creating, organizing, sharing, and maintaining business knowledge, while emphasizing content such as product FAQs, pricing overviews, competitor battlecards, case studies, and internal sales materials. It recommends finding gaps through recurring questions, buyer objections, search data, and disengaged conversations; then writing machine-friendly content with simple language, consistent terminology, explanatory context, scannable formatting, and text accompanying images or video. Connecting the Agent to CRM and enrichment systems keeps data and context connected, while ongoing reviews help content evolve from conversation insights and reduce repetitive work for sales teams. It presents knowledge management as a continuous sales function whose cumulative improvements can support faster responses, better qualification, and more focused human selling.


### [For Teams – Tools & craft – Notion](https://yomu.fyi/post/for-teams-tools-craft-notion.md)
- Company: [Notion](https://yomu.fyi/company/notion.md)
- Published: Apr 27, 2026
- Type: Explainer

The page presents a collection of Notion content about teams, tools, workplace practices, and the use of AI in organizational work. Its entries cover Custom Agents for automating repetitive busywork, teamwork skills, launch orchestration, and the changing role of team size. Several pieces focus on disconnected company knowledge, describing Notion AI as a way to bring information together and turn knowledge into action, while other entries examine AI operating systems and workflows. The page also includes survey-based perspectives from Notion, including research involving more than 3,000 global knowledge workers, 85-plus interviews, and 650 European business leaders, alongside customer stories from companies such as Merge, Ramp, Chronicle, Toyota, Affirm, and Mercury.


### [Transformation in action: What it takes to automate 81% of your customer service while improving CX](https://yomu.fyi/post/transformation-in-action-what-it-takes-to-automate-81-of-your-customer.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Author: Declan Ivory
- Published: Mar 13, 2026
- Type: Problem & solution

Intercom describes how its Customer Support team adopted an AI-first strategy after a 2022 review exposed rising demand, weak service-level commitments, and plans to broaden support access. The team began with high-volume informational queries, then expanded Fin through deeper documentation, internal procedures, customer-action capabilities, knowledge management, conversation design, skills-based routing, and organizational changes including a dedicated AI Support team. Fin now resolves over 81% of support volume and helped absorb a 300%+ demand increase without proportional headcount growth, while over 90% of customers receive improved first response performance, 24/7 coverage, and outbound phone support. The remaining human work has shifted toward consultative engagements, while Insights, Guidance, Tasks, and Procedures support ongoing optimization. Next, the team plans to use a four-stage Fin Flywheel—Train, Test, Deploy, and Analyze—and continue developing its Agent Blueprint.


### [Transformation in action: How AI is evolving support careers](https://yomu.fyi/post/transformation-in-action-how-ai-is-evolving-support-careers.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Author: Declan Ivory
- Published: Feb 27, 2026
- Type: Explainer

AI is changing customer service operations by shifting human agents away from queue-level work such as triage and FAQs toward training systems, complex escalations, and strategic improvement. In research from The 2026 Customer Service Transformation Report, 45% of teams updated job descriptions with AI-related responsibilities, 40% said agents focus more on training AI systems, and 27% primarily handle complex escalations and edge cases. Interviews with 166 customers found nearly 95% reporting meaningful workflow changes, while 83% saw roles become more strategic and supervisory; mature teams also reported less time handling support volume. New positions including AI knowledge managers and conversation designers are emerging, while existing staff can move into AI-focused work such as optimizing knowledge, monitoring outputs, and improving customer journeys. The source recommends transparent communication, agent participation, dedicated time outside inbox, and metrics such as resolution rate as teams build operating models with AI at their core.


### [Everyone wants AI. That isn't enough.](https://yomu.fyi/post/everyone-wants-ai-that-isn-t-enough.md)
- Company: [Notion](https://yomu.fyi/company/notion.md)
- Author: Makenna Lowe
- Published: Feb 13, 2026
- Type: Explainer

Survey data from more than 3,000 global knowledge workers and 85-plus interviews examines why strong demand for workplace AI has not translated into broad adoption. Although 93 percent call AI essential to modern productivity software and 80 percent are likely to switch to a platform offering it, only 20 percent say AI is deeply integrated into their company’s tools. Respondents prioritize recurring workflows such as automated project updates, continuously current knowledge hubs, and goal-based templates, while decision-makers identify integration as the leading implementation challenge alongside security and data quality, unclear strategy, resource constraints, and compatibility. The proposed pattern is to place AI inside existing work, illustrated by Faire’s reported results with Notion AI: smoother meetings for 81 percent of surveyed staff and workflows running 30 percent faster.


### [How European companies build AI-ready knowledge foundations](https://yomu.fyi/post/how-european-companies-build-ai-ready-knowledge-foundations.md)
- Company: [Notion](https://yomu.fyi/company/notion.md)
- Author: Laura Gregg
- Published: Feb 12, 2026
- Type: Explainer

European organisations face a knowledge paradox: 97% of surveyed business leaders say knowledge management is critical, but only 28% report having a coherent strategy, with poor practices costing up to €16,000 per employee annually. Interviews with leaders in France, Germany and the UK connect scattered information across people and tools to slower progress, weaker decision confidence, repetitive work and lost institutional knowledge. The post argues that centralised knowledge is a prerequisite for effective AI, noting that 56% of organisations already use AI for knowledge management and 29% are piloting it, while incomplete documentation can undermine deployments. Recommended practices include explaining the personal benefit of documentation, designing systems that pull participation rather than enforce compliance, and treating knowledge as a shared organisational asset. Examples include Nelly, Above, UnternehmerTUM and EGYM using simpler documentation workflows and shared spaces to reduce silos and keep information current.


### [Welcome to Notion, Sequin team!](https://yomu.fyi/post/welcome-to-notion-sequin-team.md)
- Company: [Notion](https://yomu.fyi/company/notion.md)
- Author: Fuzzy Khosrowshahi
- Published: Jan 9, 2026
- Type: Announcement

Notion welcomes the Sequin team—Eric Goldman, Anthony Accomazzo, and Carter Pedersen—following discussions about the companies’ shared view of fragmented knowledge work. Sequin built a data-syncing product that brought information from systems including Salesforce, ServiceNow, and Stripe into Postgres, giving developers flexible building blocks instead of requiring them to recreate integrations. The founders say they were drawn to Notion’s enterprise search, work on AI and agents, ambitious direction, and strong user community, while Notion describes Sequin’s experience as aligned with its plans. The announcement frames the broader problem as information scattered across documents, conversations, and tools, and points to AI and agents as a way to help teams find information, automate repetitive work, and prepare for AI-native work.


### [How Merge brought together all it knows using Notion AI](https://yomu.fyi/post/how-merge-brought-together-all-it-knows-using-notion-ai.md)
- Company: [Notion](https://yomu.fyi/company/notion.md)
- Author: Shensi Ding
- Published: Dec 23, 2025
- Type: Problem & solution

Merge found that company knowledge was scattered across Slack, Google Docs, Salesforce, and other tools, causing repeated questions, slow onboarding, and time lost searching for context. It used Notion AI as a shared knowledge layer, connected Salesforce and Slack, and gave teams guidance on what content to add, including detailed project documents, meeting transcripts, and structured databases. Teams populated the workspace with content calendars, sales enablement materials, hiring plans, roadmaps, and an AI Prompt Library, while all-hands and team meetings demonstrated practical workflows. Merge reports that employees now ask Notion AI first, saving each team member several hours per week, helping teams make decisions with less manual searching, and making faster information retrieval one of the most-cited contributors to improved satisfaction in its latest company-wide survey.


### [Make with Notion Showcase Europe 2025: Highlights & Takeaways](https://yomu.fyi/post/make-with-notion-showcase-europe-2025-highlights-takeaways.md)
- Company: [Notion](https://yomu.fyi/company/notion.md)
- Author: Áine Dundas
- Published: Dec 18, 2025
- Type: Announcement

Make with Notion Showcase Europe 2025 brought more than 1,300 attendees across four cities during the second year of the in-person conference series. The event centered on three themes: agentic AI taking action, organized knowledge enabling effective AI, and a community building AI-powered work. Notion presented Notion 3.0, whose Agent can handle multi-step workflows, and previewed Custom Agents that can be shared across teams, scoped to databases or teamspaces, and triggered by schedules or events. With MCP integration, Notion content and connected app context can be accessed from other tools; Custom Agents are in early access and planned for broader availability in early 2026. Research cited losses of up to €16,000 per employee annually in the UK, France, and Germany from searching for scattered information, while customer sessions covered knowledge management, AI workflows, and Notion implementations.


### [2026 customer service planning series: Vol. 03](https://yomu.fyi/post/2026-customer-service-planning-series-vol-03.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Author: Declan Ivory
- Published: Dec 2, 2025
- Type: Explainer

AI performance in customer support can drift without clear ownership, even when the underlying model is capable. This part of a 2026 planning series presents four roles: AI operations lead, knowledge manager, conversation designer, and support automation specialist. The roles cover monitoring and guardrails, structured and compliant knowledge, conversational tone and flow, and reliable action through backend systems, with the AI operations lead coordinating reporting and improvement. The post describes an operating loop in which performance patterns drive knowledge fixes, interaction changes, and expanded automation, while phased ownership moves from part-time assignments to formal roles and hiring. It says dedicated specialization becomes essential when AI handles 50–70% of incoming volume, and frames these roles as the backbone of an AI-first support organization.


### [How Ramp built an AI operating system for scalable work](https://yomu.fyi/post/how-ramp-built-an-ai-operating-system-for-scalable-work.md)
- Company: [Notion](https://yomu.fyi/company/notion.md)
- Author: Drew Evans
- Published: Dec 2, 2025
- Type: Problem & solution

Ramp spent the last year building what operations and AI product leader Ben Levik calls an “AI operating system” for the company, with the goal of becoming more productive. Rather than waiting for tools to mature, Ramp promotes a “Builder” mindset and organizes adoption around Prompt, Knowledge, and Workflow. Employees refine vague requests by having AI ask clarifying questions, while a Notion knowledge base connected to other tools uses feedback loops in which AI drafts corrections and humans approve them. AI agents and connectors then automate tasks such as summarizing project updates from five sources and researching prospects for review-ready sales emails. About 90% of 1,200 employees use Notion AI monthly, and Ramp reports shipping 270 features in the first half of 2025, more than during all of 2024, shifting the bottleneck toward choosing what to automate next.


[Older posts](https://yomu.fyi/topic/knowledge-management/page/2.md)
