Launch deliverables
Create separate tasks for copy, design, and publishing preparation. Give each an owner and date, then follow progress on the board.
Lists and tasksWhat’s next?
What’s next?
Who’s taking it on?
Write down the task, choose an owner, and set a due date. Follow its status in the channel’s list or board.
First-week preparation#welcome
Open a task, then change its owner or status.
Changes in this example are not saved to your workspace.
Product tour with sample contentOpen a task and change its owner or status. Switch to Board to see the same task move with your change.
Give the next step an owner.
Write the details needed to complete the work in a task. Set an owner, priority, status, and due date, then let the team follow it in a list or board.
Task, bug, and story work types
Describe the work as a task, bug, or story. The team can tell whether it is tracking a deliverable, a problem, or a piece of development scope.
Status, priority, owner, and due date
Who will do it, when is it due, and where does it stand? Keep those answers in the task’s fields and update its status as work changes.
List, table, board, backlog, and sprint views
Review details in a table and progress on a board. Use backlog and sprint views to plan work for a delivery period.
Subtasks, files, comments, and work log
Follow subtasks, comments, and files inside the open task. Keep logged time with the work it belongs to.
Explain the task’s purpose in the shared plan.
The task shows who will update the guide. The Canvas plan explains which part needs to change and why. Put the files and decisions in a shared note so the person taking on the task can read its scope.
welcome
Open an example
The first-week plan
Our plan for welcoming new teammates.
Decision
We’ll start the first day with introductions and a short workspace tour.
Try editing the decision in this sample note.
Let’s keep the first-week guide in this channel’s Canvas tab.
What comes next
| Task | Owner | Status |
|---|---|---|
| First-week guide | Maya | In progress |
| Channel descriptions | Alex | In progress |
| First-day schedule | Jamie | To do |
Welcome tasksRelated link
Welcome planning notes
Monday · People and culture team
Agenda
- First-week guide
- Team channels and the people who can help
- The first-day schedule
Decision
We’ll add the team channels and people who can help to the guide. New teammates will tour the workspace together on their first day.
Try editing the decision in this sample note.
Guide: Maya. Channel descriptions: Alex. Schedule: Jamie.
Project planRelated link
Review the scope in Project plan and the supporting information in Team handbook.
Give “let’s do this” a next step.
Maya owns the guide update. Return to #welcome to see the conversation that led to the task.
Define the work
Set work type, priority, owner, and due date.
Plan it
Move backlog work into a sprint or order it on the team board.
See progress
Track status, subtasks, comments, and work logs in the task drawer.
At the next check-in, see who owns the task, where it stands, and when it is due alongside the discussion.
Make the follow-up visible.
Product development
Organize bugs, tasks, and stories in the task center. Plan work from the backlog into a sprint and clarify the scope with descriptions and subtasks.
Keep the task record current.
Update the status, owner, and due date as the work progresses. Add the relevant conversation or document link to the description so the next owner can pick up from the same source.
Frequently asked questions.
A few details about using this feature and what it covers.
Give the first task an owner and a date.
Open Lists in your channel, write down the work, and follow it with the team in List or Board.