Use case
A project is the unit of work
The problem
What gets in the way
People copy the same work into a board, a doc, and a calendar. The copies drift. Status meetings become archaeology.
What changes
After you start using it
- 01
One set of tasks, several views
- 02
Statuses you define for the project
- 03
Milestones and cycles when a project needs them
Workflow
From empty project to a board you trust
- 01
Create a project in the workspace. Name the statuses the way you already speak.
- 02
Add tasks as they appear. Drag them when status changes.
- 03
Switch to list, timeline, or calendar when that view answers the question faster.
Write the proposal
Prep kickoff notes
Review comments on the draft
HighSend the invoice
Publish the homepage
What you use
Capabilities in this job
- 01
Workspaces, projects, and boards
A workspace is the boundary for members and projects. A project holds statuses and tasks. The board is the live kanban view: columns are statuses, cards are tasks. Opening a task uses the inspector so you stay on the board.
- 02
Board, list, timeline, and calendar
Switch the project view without copying the work into another tool. List, timeline, and calendar show the same tasks as the board.
Questions