Use Collections to organize work

Overview

Collections are a flexible way to organize and surface your TheyDo content for different audiences and purposes. This guide covers common patterns for using collections to keep work focused and easy to navigate.

Curating for leadership

Executives and senior stakeholders often need a clear, focused view — not the full workspace. A collection gives them a single entry point with the context they need, and the TheyDo Agent scoped to answer their questions.

Some useful patterns:

  • QBR or exec readout. One collection per review: the relevant journey, top opportunities, a saved view of key metrics, and the Agent ready for live questions.
  • Theme-based hub. A collection around a strategic theme — like churn, NPS, or onboarding — that stays up to date as you link new content. Leadership has one place to check what's happening on a topic.

Curating for cross-functional teams

Collections work well for handing the right context to teams who don't live in journey management.

  • Product squad onboarding. Link the squad's domain journeys, relevant personas, and top insights. They land on a focused view with the Agent scoped to their work, not the whole workspace.
  • Business unit views. Each BU gets its own collection with the journeys, opportunities, and metrics relevant to them. Clean separation without duplicating content.
  • Service or pain hub. Everything related to a specific service or customer pain (for example, baggage claim or the checkout flow) lives in one container: journeys, insights, opportunities, solutions.

Curating for onboarding

A collection is a great way to show a new team member exactly where to start in the workspace.

  • Link the most relevant journeys and building blocks for their context
  • Use the description to frame what they should focus on first
  • The Agent can answer their questions scoped to only what you've curated

Keeping collections manageable

A few things to keep in mind as you build and maintain collections:

  • One audience or theme per collection. Collections are most useful when they're focused. If a collection starts covering too many topics, consider splitting it.
  • The Agent scopes to roughly 1,000 insights. For large business units or broad themes, create multiple collections — for example, one per region or sub-topic — to keep the Agent's answers grounded and relevant.
  • Unlinking is safe. If a piece of content no longer belongs, unlink it. The original stays in your library; only the connection to this collection is removed.
  • Description text is for context, not AI input. Use the description to frame the collection for viewers. It's not included in what the Agent reasons over — only linked items are.

What's not available yet

A few things are on the roadmap but not in this version:

  • Sortable and filterable columns in the Collections overview
  • Owner-only edit controls on shared collections (right now, anyone with workspace access can add or remove items)
  • Sharing a collection directly from the navigation panel