A project is a bet on one driver — a measure you are trying to move — with milestones that say whether it is working. Tasks attach their dated milestones to it, updates set its health, and the directory timeline shows every project's milestones as diamonds on one axis.
There is no separate goal layer. The driver is the goal.
When to use a project
A project is worth creating when a number matters for longer than one task and keeps generating work:
- A measure for the quarter. Trial-to-paid conversion to 8% by March. Pricing tasks, onboarding tasks and channel tasks all attach milestones to it, and one page shows whether the number is moving.
- A launch. First 500 orders on the new line. The launch plan's dated milestones land on the project, and the timeline shows what depends on what.
- A turnaround. Churn under 3% by year end. Updates from the people doing the work set the health; a quiet project cannot claim to be on track.
When something else fits better
- One question with one answer. Run a task. If it turns out to matter for a quarter, make the project then.
- A backlog. Projects are not your issue tracker. Connect Jira or Linear and the work reads what is actually in flight.
- Things the work needs from you. Those are Issues — assumptions to confirm, numbers to supply, decisions to make.
How a project is organised
A project has four tabs: Overview (driver, progress, milestones, updates), Activity (what has happened), Resources and Issues.
Create a project
- Open Projects in the sidebar and choose New project.
- Name it after the driver, not the work: Trial-to-paid conversion, not Onboarding revamp.
- Set the status — Backlog, Planned or In progress — the lead, and the target date if there is one.
- Add the first milestone: the number and the date.
Members with a read-only role do not see New project; see Roles and permissions.
Milestones
A planned milestone is the link between tasks and the project: when a task builds a timeline with dated milestones, those milestones appear on the project, and the tasks under each are the rows the diamond depends on. Expand a planned milestone to see them and the progress each last reported.
Every milestone title opens its own page, showing the kind, status, target date, a link to the directory timeline and, for planned milestones, the tasks on the way to it. Status can be changed there as well as on the project.
Health
Health is not set directly. It comes from updates:
This is deliberate. A project that has gone quiet cannot claim to be on track, and the person who knows is the person who posts.
Views
Header pills filter by status — All, Backlog, Planned, In progress, Completed, Canceled, Archived — and you can switch between a list and a board. Every filtered view is a URL you can share; the parameters are documented under the hood.
Timeline takes you to the directory timeline, where each project's milestones are diamonds and the tasks that lead to them are the rows beneath.
Star a project to keep it in your sidebar. Favourites are yours, not the directory's.
Dependencies
A project can be blocked by another; the reverse relation is derived, so you set it once. Filter by relation to see what is blocking, what is blocked, and where a dependency is violated by the dates.
Notifications
Subscribe to a project to be told when an update is posted, a milestone moves, or an issue scoped to it changes. See Notifications.
Projects and tasks
Projects and tasks meet in two places. A task's timeline puts planned milestones on the project it belongs to. And a task about the same driver reads the project — its hypothesis, its milestones, its latest update — from memory like any other doc, so a pricing task knows the conversion target it is supposed to serve.
Limitations
- Projects are manual. A task does not create one for you.
- A project belongs to one directory. A driver shared across two organisations needs a project in each.
- Deleting is available for manual projects only; archive anything you may want back.