Updated
My First Task for Product Teams
A product launch touches design, engineering, and marketing — each with its own idea of what 'done' means. One shared workflow keeps everyone pointed at the same stage.
Illustrative workflow
Step 1
Set up the project's workflow
Apply the Website or Mobile App template, or define your own stages if your launch process looks different.
Step 2
Assign work with clear ownership
Every task has one owner and a due date; subtasks handle anything that needs to be broken down further.
Step 3
Keep handoffs visible on the task
Comments and @mentions carry design feedback, engineering questions, and sign-offs on the task itself, not in a side channel.
Step 4
Report progress without a status meeting
Pull a report filtered to the project to see completion rate and overdue tasks — the update leadership was going to ask for, already available.
Where This Usually Gets Messy
How Product Teams Use It
Set up the project's workflow
Apply the Website or Mobile App template, or define your own stages if your launch process looks different.
Assign work with clear ownership
Every task has one owner and a due date; subtasks handle anything that needs to be broken down further.
Keep handoffs visible on the task
Comments and @mentions carry design feedback, engineering questions, and sign-offs on the task itself, not in a side channel.
Report progress without a status meeting
Pull a report filtered to the project to see completion rate and overdue tasks — the update leadership was going to ask for, already available.
Start From a Built-In Template
The Website template ships with the app — apply it and the stages below are ready before you add a single task.
Features You'll Use Most
Frequently Asked Questions
Can different workstreams see only what's relevant to them?
Roles control access at the workspace level; within a project, everyone with access sees the same board — there's no per-task visibility filtering today.
Can I track a launch across multiple projects?
Reports can be filtered to a single project or pulled across the whole workspace, giving a combined view when a launch spans more than one project.
Does this replace a design tool like Figma?
No — it's not a design tool. It tracks the tasks and handoffs around the design work, not the design files themselves.
Put this workflow into practice
Connect priorities to clear acceptance conditions and the decisions needed for delivery.
Acceptance Criteria Examples: A Practical Writing Guide
Acceptance criteria are observable conditions a particular work item must satisfy before it is accepted. Write them around behavior and evidence, including important failure cases. A definition of done sets broader quality expectations across work items.
ExploreProject Status Report Template: Progress, Risks and Decisions
A project status report summarizes progress toward an outcome for a stated reporting period. Include completed deliverables, upcoming commitments, risks, changed dates and decisions needed, with an owner for each follow-up.
ExploreHow to Assign Tasks: Ownership, Deadlines and Follow-Up
Assign a task by agreeing the outcome, accountable owner, required inputs, finish condition and realistic timing. Check the person's capacity and authority before treating the assignment as an accepted commitment.
ExploreSet Up Your Workspace
Free plan available — no credit card required.