Use Cases & Best Practices

Example: Good vs. Bad Snippets

❌ Bad Snippet (too long, not reusable):

• Title: Company history

• Content:

  “Our company was founded in 2015 by a small group of engineers in San Francisco who wanted to solve the problem of fragmented productivity tools. Since then, we’ve grown into a global team serving thousands of customers across multiple industries.”

Why it’s bad: This tries to hold too much in one snippet. It’s hard for AI to reuse consistently, and pieces of the content may go out of date.

✅ Good Snippets (short, reusable facts):

• Title: Company founding year Content: 2015

• Title: Headquarters Content: San Francisco

• Title: Customers served Content: Thousands worldwide

Why it’s good: Each snippet is clear and atomic — a single fact per entry. AI can combine them flexibly in answers, and they’re easy to update individually as details change.

Core Components of AI Knowledge

AI Knowledge is built from simple, structured parts that make facts easy to store, share, and reuse across Motion.

Component	What It Is	Why It Matters
Title & Content	Each snippet has a Title (what the fact is about) and Content (the fact itself).	Keeps snippets concise and searchable. Example: Title: Company founding year → Content: 2015.
Personal vs. Team Knowledge	Snippets can live in your personal library (private) or in team knowledge (shared).	Gives you control over what context stays private vs. what supports the whole team.

Scope

AI Knowledge in its current form is designed to focus on concise, reusable facts that keep AI grounded and accurate.

• Short, key-value snippets → Store information as atomic entries (e.g., Title: Support hours → Content: 9am–5pm EST).

• Personal and team visibility → Snippets can be private to you or shared across your team for collective accuracy.

• Permissions-aware → AI will only reference snippets you have access to, ensuring relevance and security.

How This Relates to Other Features

AI Knowledge doesn’t replace Motion’s other tools — it complements them by serving as the source of concise, reusable facts. Here’s how it fits alongside other features:

• vs. Docs → Docs hold longform content (plans, briefs, narratives). Knowledge holds short, atomic facts. Think of Docs as the story, and Knowledge as the flashcards.

• vs. AI Employees → AI Employees can reference Knowledge snippets to make their outputs more accurate and consistent. Example: A Customer Success Employee can pull the latest Support hours from Knowledge when drafting a client update.

• vs. AI Chat → AI Chat is the interface where Knowledge gets applied. Snippets feed into answers so responses stay aligned with your facts, style, and workflows.

Together, Knowledge, Docs, AI Employees, and AI Chat form a connected system: Docs tell the story, Knowledge keeps the facts straight, Employees act on them, and Chat ties it all together.