Skip to main content
Use one Pod for an initiative whose working group and information scope stay substantially the same. For example, a product launch team can keep its brief, decisions, open questions, and deliverables together through the launch period.

​
Set it up

  • Name the Pod after the initiative and state its outcome and success criteria in the description.
  • Add the owner, contributors, and reviewers; use Restricted visibility if the material is not for the whole workspace.
  • Save the approved brief, roadmap, and design references in Files.
  • Create tasks for deliverables, each with an owner, expected result, and due date where known.

​
Run the work

Use conversations to discuss decisions and record why they were made. Convert follow-ups into tasks and update status as the work changes. At a regular review, ask an Agent to group work into completed, in progress, blocked, and not started, citing the relevant task or conversation. Project-system imports, meeting transcript processing, or scheduled summaries require supported tools and configuration. Check imported tasks for duplicate IDs and ownership. A status summary is a working view: confirm important dates and completion in the authoritative project system.