Project Basics
Creating a project
Setting a project up: the fields, sensible dates, and what to do in the first ten minutes.
Last updated September 2, 2026
Create a project from the board or the project list. There is very little to fill in, which is deliberate — the detail belongs in the scope, not in a long form nobody completes.
| Field | What to put in it |
|---|---|
| Project name | What the work is, in the words the team says out loud. |
| Description | A sentence for anyone who has not been in the meetings. |
| Status | Where it has got to. |
| Priority | How it ranks against everything else in flight. |
| Start date | When work begins. |
| Target completion date | When it is meant to be finished. |
| Team member | Who is responsible for it. |
The first ten minutes
- Write the scope — what this covers and, more importantly, what it does not.
- Add the people and what each is responsible for.
- Break out the first handful of tasks. Not all of them — just enough to start.
- Record any constraints you already know about.
A TARGET DATE NOBODY BELIEVES IS WORSE THAN NONE
Put in the date the work will realistically finish, not the one that was asked for. A board full of dates that passed weeks ago stops being read, and then the genuinely late project looks like all the others.
Deleting
Deleting a project cannot be undone and takes its tasks, notes and files with it. A finished project belongs at a completed status, not deleted — the record of how it went is the useful part.