How to get a new hire actually using your CRM in their first week

Here's how CRM onboarding goes at most companies. Day one or two, someone senior shares their screen for two hours and tours the whole system — pipelines, views, fields, reports, the works. The new hire nods, takes notes they'll never open again. Then for the next three weeks they ask the person next to them (or the team Slack channel) every time they need to do anything, because a two-hour tour of someone else's screen transferred approximately nothing.

The tour isn't lazy. It's usually thorough. It fails anyway, for one reason: nobody learns a tool by watching it. You learn a tool by doing ten real tasks in it, badly at first, with help nearby.

So here's the plan I'd run instead. It's built for a CRM because that's the highest-stakes case — bad CRM habits contaminate your data forever — but it works for any core tool. It assumes nothing fancier than a list, a doc, and a bit of discipline; where a tool like ours helps, I'll say so and you can ignore it.

Before they start: pick the ten tasks

Not the hundred features. The ten tasks this specific role performs in a normal week. For an SDR that might be:

1. Log a call
2. Create a contact and attach it to an account
3. Advance a deal to the next stage
4. Book a meeting that syncs to the calendar
5. Add a contact to a sequence
6. Check which of their accounts have open tasks today
7. Merge duplicate contacts
8. Log an objection in the right field (not in free-text notes)
9. Find the accounts they own that have gone quiet
10. Update a close date without being yelled at by a validation rule

Writing this list is the highest-leverage hour in the whole process, and it's the step everyone skips. If you can't name the ten tasks, your onboarding problem isn't the new hire — it's that the role's actual workflow lives in the heads of whoever's been there longest.

Day 1: one task, done for real

Skip the grand tour entirely. Give them a fifteen-minute orientation — here's what the CRM is for at this company, here's the one dashboard that matters — and then have them do exactly one real task from the list, end to end, on real data. Log a real call. Create a real contact.

One task sounds absurdly small. That's the point. The goal of day one isn't coverage, it's calibration: they learn that they're expected to drive, not watch, and you learn how they handle the tool cold.

Days 2–3: the ten tasks, hands on their own keyboard

Work through the list. For each task, the pattern is: they attempt it themselves first, with a guide open — written steps, or an interactive walkthrough if you have one — and a human they can ask when the guide isn't enough. Then they do it a second time without the guide.

The person "nearby" should resist the urge to grab the mouse. Every time the mentor does the click, the mentor gets the practice. This is the quiet failure of shadow training: three weeks of sitting next to Sarah produces a new hire who is excellent at watching Sarah.

This is also where the format of your documentation starts to matter. A doc in another tab means constant alt-tabbing and lost context. Guidance that lives on the CRM itself — highlighting the actual field, waiting for the actual click — removes the translation step. That's the product we build, so discount my enthusiasm appropriately, but the principle stands with any format: the closer the instructions are to the buttons, the less gets lost in between. (I compared the formats honestly here.)

Day 4: the conventions, now that they can ask good questions

Every CRM has a shadow rulebook: what "Stage 3" really means here, which fields sales leadership actually reads, why you never delete an account, the difference between how the system was designed and how the team uses it. On day one this is noise. On day four — after they've touched real records — it snaps into place, and the new hire asks sharp questions instead of nodding.

Do this as a conversation, not a lecture, and write down whatever surprises them. Every question they ask is a gap in your documentation that the next hire will hit too.

Day 5: solo flight, measured by doing

End the week with a simple check: they run all ten tasks, alone, no guide. Not a quiz — quizzes measure recall, and recall isn't the job. Watch for where they hesitate. Hesitation on Friday tells you exactly what to reinforce on Monday, while it's still cheap.

Then — and this matters more than anything above — make sure they know where help lives from week two on, because they will forget things. That's not a training failure; forgetting the merge flow you used once, eleven days ago, is just how memory works. The question is whether re-learning it costs thirty seconds or a Slack interruption. This is where self-serve, in-context help earns its keep: the fix for "people keep asking the same questions" is almost never more training, it's a shorter path from question to answer at the moment of the question.

What this replaces

Notice what's not in the plan: no two-hour tour, no video playlist as homework, no "shadow me for a few weeks." A week of doing beats a month of watching, and it front-loads the mistakes into the window where mistakes are free.

The one-line version, if you keep nothing else: stop measuring onboarding by what you showed them. Measure it by what they can do alone. Everything else in this post is just that sentence with logistics attached.