A project is one line of work inside a workspace — a product, a campaign, a side bet, a launch. Tasks, assets, and the conversation about that work all live under their project so they don't bleed into the rest of the company.
Why projects exist
- Keep context tight: the team only sees what's relevant to the project they're working in
- Separate the main business from experiments — a SaaS launch and a podcast can run in parallel without crossing wires
- Make finished work easy to find later — every asset is filed under the project that produced it
What a project contains
- The tasks the team has worked on for this line of work
- Goals tied to it (revenue, ship dates, milestones)
- Assets produced (copy, code, video, reports)
- Any project-specific knowledge the chairman pinned
One project or many?
Start with one. Add a second project only when the work has a different audience, a different goal, or a different brand voice. Splitting too early just creates empty containers; merging later is annoying.
For how to spin one up, see the create-a-project guide.