Get started
Onboarding checklist
A pragmatic first-week checklist for rolling Planoda out to a team — from import to your first cycle.
Last updated
Rolling a new tool out to a team is mostly about momentum. This checklist is the order we recommend for a smooth first week. Each step links to a deeper guide.
Day one
Create the workspace and your first team, set the team key, and invite the people who will actually use it this week (not the whole company yet). Import existing work from your old tool so people see their real tasks on the first login — a half-empty workspace gets abandoned. The Importing guide covers CSV and per-tool paths.
Day two to three
Agree on your workflow states (Backlog → Todo → In Progress → In Review → Done is a sane default) and your priority scale. Start your first cycle and pull a realistic amount of work into it. Keep estimates lightweight at first — points or t-shirt sizes — and tighten them once you have a cycle of history.
End of week one
Wire one or two automations that remove obvious busywork (for example, move an issue to In Review when a PR is opened). Connect Slack so updates land where the team already talks. Resist the urge to automate everything on day one — add rules as real friction shows up.
Related
- QuickstartCreate a workspace, invite teammates, and create your first issue — the five-minute path from sign-up to a working board.
- Importing & migratingMove work in from Linear, Jira, Trello, Asana, and others — with identifiers, state, and history preserved where possible.
- Cycles & estimatesRun time-boxed cycles, estimate work, and read velocity — without ceremony.