Why launch-day training fails
A single session teaches the tool in the abstract, days before anyone has a reason to use a given feature. By the time a rep needs to build a sequence, three weeks have passed and the demo is gone.
The teams with strong adoption do something less impressive and more effective: short, role-specific, repeated, and tied to work people already have to do that week.
Role-based sessions, 45–60 minutes each
| Role | Cover | Deliberately skip |
|---|---|---|
| Sales reps | Logging activity, pipeline hygiene, sequences, meeting links, mobile app | Reporting internals, workflow building |
| Sales managers | Pipeline and ageing reports, forecast view, coaching from activity data | Marketing email tooling |
| Marketing | Lists vs workflows, forms, email, campaign reporting, contact governance | Deal stage administration |
| Service | Ticket pipelines, SLAs, knowledge base, canned responses | Attribution reporting |
| Admins / ops | Properties, permissions, workflow standards, data quality dashboard | Nothing — this group needs depth |
Practice on live records
- 01Ask each attendee to bring three of their own real deals or contacts.
- 02Work through the actual task — log the call, move the stage, send the sequence — during the session.
- 03Have them do it, not watch it. Screen-share round-robin if the group is small enough.
- 04End with one committed change per person, written down.
- 05Follow up on those commitments in the first clinic a week later.
The 30-day reinforcement loop
The named internal owner matters more than any session. Adoption collapses when the only person who knows the portal is external.
- Week 1: 20-minute clinic — questions only, no agenda, recorded.
- Week 2: clinic plus one new capability relevant to that role.
- Week 3: manager review of adoption metrics with individuals, framed as support rather than audit.
- Week 4: clinic, then publish the top ten questions as short written answers.
- Ongoing: monthly 20-minute session and a named internal owner for questions.
Measure adoption, not attendance
Attendance tells you nothing. Track logged activities per rep per week, the share of deals with required fields complete, open deals with a scheduled next activity, and weekly active users. Put these on the data-quality dashboard so they are visible without anyone asking.
Set the expectation before go-live that these are the numbers leadership will look at. Training without a measured expectation is a suggestion.
Document as you go
Record every session and store them in a knowledge base with plain, searchable titles — 'How to log a call and set the next step', not 'Sales Session 2'. New joiners then onboard themselves in a day.
Add short written SOPs for the five processes people get wrong most. Video is good for demonstration and terrible for a quick check at 4pm.
Common mistakes
- One giant all-hands session before anyone has a reason to use the tool.
- Training on demo data instead of the attendee's own records.
- No internal owner, so every question goes to an external consultant.
- Measuring attendance rather than logged activity and field completeness.
- Recording sessions with titles nobody can search.