Map a customer onboarding process with actionable tasks

Explain handoffs visually and give each agreed step an owner.

Use this approach for a small team coordinating a repeatable process: customer onboarding, campaign preparation, employee setup, or a service handoff. This example maps one customer's onboarding. It is a manual plan, not an automated workflow.

Build the route

  1. Open the customer's project and its Design canvas. Add a heading such as Northstar onboarding.
  2. Add Start / End shapes for Kickoff agreed and Customer live.
  3. Add horizontal swimlanes or clearly labeled areas for Customer Success, Delivery, and Launch review. These are visual labels; they do not create departments or assign tasks.
  4. Add Task nodes named Confirm customer requirements, Configure the agreed setup, Run acceptance review, and Confirm launch. Place each in the relevant area.
  5. With Work off, connect the steps in their intended order. Add a Decision diamond labeled Accepted? after acceptance review. Label the outgoing paths Yes: confirm launch and No: agree corrections.
  6. Add a Task for Agree and complete corrections on the No branch, with an ordinary connector back to the review. A return arrow explains the process; it does not create recurring work automatically.

Make the process usable

Open All Tasks and assign each actionable step to a responsible person, with realistic dates and clear completion criteria. Add the agreed brief or setup instructions near the relevant steps. Include a note explaining who makes the acceptance decision.

Try the handoff: update Confirm customer requirements, then ask the next owner to find Configure the agreed setup in their accessible task views. The ordinary arrow explains why their work comes next; the task record gives them the action and context.

Use Work only for a different question

If Configure the agreed setup needs smaller tasks, connect those smaller Tasks to it with Work enabled. That records a breakdown. Keep the main route's connectors ordinary so the sequence is not accidentally modeled as a chain of parent and child tasks.

The diagram can show several possible paths. It does not evaluate a decision diamond or automatically close tasks on an unused branch. Agree with the team which work remains active and update the actual task records.

Review and reuse carefully

At each handoff, update the task and add a progress note when the next owner needs context. During a process review, improve unclear labels or missing steps. If you copy a plan for another customer, check every copied task, owner, date, and reference; do not assume a copied diagram remains linked to the original tasks or resets all work details.

Result: colleagues can understand the process on Canvas and manage its actions through the same project's task views.