One slug, every browser, every device
b/onboarding fires from the address bar, Raycast, Spotlight. Day one — no install required for new hires.
Use case · Onboarding
New hires productive on day one.
Not week three.
Day-one onboarding becomes one BookSlash board with the ten links every new engineer, designer, or PM actually opens — plus a checklist, a Loom intro, and the on-call shortcut. Replace a 30-page Notion doc nobody finishes with a board they keep coming back to.
The shape of the work
Three steps from Slack invite to shipping.
Most "onboarding" is a folder of links and a hope. The pattern that actually works is short, specific, and on a single canvas.
- 1
Hand them a slug
Send b/onboarding-eng on day one. They land on the same board every other engineer landed on. No Notion folder hunt, no Slack thread to pin.
- 2
Ten shortcuts they will memorise
b/wiki, b/repo, b/oncall, b/runbook, b/dash, b/figma, b/loom-intro, b/buddy, b/calendar, b/standup. Five days in, they fire from muscle memory.
- 3
A checklist that closes
Tasks live on the board, owned by the new hire. Their buddy can see what is open. The board doubles as a 30/60/90 review canvas — same URL, longer life.
Onboarding board template
b/onboarding-eng — what it actually contains.
Steal this template. Eight nodes, every one purposeful. Stamp out per-team variants for design, marketing, customer success, and finance.
b/onboarding-eng
8 nodes- Loom welcome
Two-minute loom from the eng manager: the team, the stack, the rhythm. Embedded live, not a link.
- Slug glossary
b/wiki, b/repo, b/oncall, b/runbook, b/dash. The ten shortcuts every engineer needs from week one.
- Buddy + manager
Names, headshots, calendar slugs. b/calendar-buddy, b/calendar-manager — book directly.
- First-week checklist
Tasks node owned by the new hire: laptop, accounts, first PR, first standup, first paired pairing session.
- Architecture mind map
Five-node mind map of services and ownership. Click any node to land on its runbook.
- On-call shortcut
b/oncall. Pinned. The single most-used slug after week one.
- 30 / 60 / 90 review
Same board, scrolled down. Manager and new hire fill it together at week 4, 8, 12.
- Office hours timer
A countdown to the first weekly office hours block. Removes the "should I interrupt?" question.
Why this works
Six things a Notion folder cannot do.
Real tasks, real ownership
Checkboxes live on the board, owned by the new hire. Manager sees what closes; nobody chases.
Live Looms, not screenshots
Embed the welcome video and the architecture walkthrough. Updates on the original Loom flow through automatically.
Directly bookable buddies
b/calendar-buddy and b/calendar-manager are on the board. No Slack DM dance for that first 1:1.
Doubles as 30/60/90 review
Same board, longer life. The retro lives where the onboarding started — closing the loop on what worked.
A countdown to first office hours
Removes the "should I interrupt?" question. A timer node is worth more than a calendar invite for week one.
Every CSM in our team has b/<account-slug> committed to muscle memory. Onboarding a new hire used to take two weeks; now it's an afternoon.
IO
Imani Okonkwo
VP Customer Success · Praxis Cloud
Frequently asked
Questions, answered.
About 30 minutes for the first one, ten minutes for every variant after. Most teams build one board per role (engineering, design, marketing, customer success) and stamp it for each new hire by duplicating and updating the assignee.
Yes. New hires get the Member role and can check off tasks, add comments, and pin extra context as they learn it. The original template stays untouched in /boards/templates so the next hire gets a clean copy.
Most teams keep the long-form Notion doc and put a slug to it on the board (b/onboarding-doc). The board becomes the daily-use surface; the Notion doc becomes the deep reference. Updates to the Notion URL only need to happen once on the BookSlash side.
Yes. Tasks have assignees and timestamps; the audit log records who checked which task and when. Owners and Admins can export progress for HR or compliance reporting.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial