Organising work in projects

8 min Free preview

Many assistant products let you group chats, files and instructions into a project or workspace. Used well, this keeps context consistent across many related tasks.

What to put in a project

  • Reference files that rarely change, such as a style guide or product specification
  • Standing instructions about tone, audience and format
  • A short glossary of the terms your team uses

What to keep out

Leave out stale drafts, superseded versions and confidential material that the whole group should not see. A project is only as good as its contents.

Naming and structure

Use names that describe the purpose, such as "Client onboarding emails 2026" rather than "Project 3". Start a new project when the purpose changes, not every time the scope grows a little.

Sharing

If a project can be shared, check who gets access and what they are allowed to change. Shared instructions shape everyone's output, so treat them like team documentation.