Article · Start here
Build your first project
Updated 18 May 2026
Getting started · 3 of 5≈ 10 minutes total
A task is a thing you do. A project is a thing the team does — together, visible to everyone, with the chat about it sitting next to the tasks themselves.
Steps
- Open the sidebar. Click + New project at the top of the project list.
- Give it a name. Something a human would search for — "Spring relaunch" beats "Q2 marketing initiative". You can rename it later.
- Add the first three tasks. Don't add fifty. Three. Real ones. The project doesn't feel real until something is in it.
That's the whole creation flow — title and tasks. View choice, workflow attachment, custom fields, and the rest of the setup come later, only as the work asks for them.
What you just unlocked
- One place for related work. Everything for the spring relaunch sits together. Open the project, see the lot. You stop hunting through threads.
- The same data, every screen. Your board and your designer's board are literally the same board — in real time. Move a task and they see it move within a second. No "which version is yours?"
- Chat next to the work. Each project has its own thread. The conversation about a task lives with the task, not in a DM that disappears down a Slack scroll.
Activity is visible too
Every change on every task lands in the project's activity log: assignments, status moves, comments, attachments. Anyone with project access can look back and see what happened. No "who told who" archaeology when something needs revisiting next quarter.
Next up
The thing that makes a project worth having is the second person.