Starting a new tool is never just “sign up and go.” If you’ve got to bring people into Quantified—whether you’re an admin, ops lead, or just the unlucky team member who drew the short straw—this guide’s for you. We’ll skip the shiny marketing promises and get into the weeds of what really works (and what’s just noise) when onboarding new users.
Step 1: Get Your House in Order
Before you invite anyone, take a breath. Nothing slows onboarding like chaos behind the curtain. Here’s what you need to sort out first:
- Know your use case. Why are you using Quantified in the first place? Is it tracking sales performance, monitoring call quality, or something else? If you can’t answer this, neither can your team.
- Set up roles and permissions. Decide who needs admin access, who’s a regular user, and who just needs to view stuff. Don’t leave everyone as an admin "just in case." It’s a headache later.
- Clean up your data. If you’re importing contacts, teams, or history, make sure it’s not a mess. Bad data is like glitter—it gets everywhere and never really goes away.
Pro tip: If you’re migrating from another tool, take the time to map old fields to Quantified’s setup before you start importing. You’ll thank yourself later.
Step 2: Add Users (But Don’t Spam Everyone at Once)
Now that you’re set up, it’s time to invite people. Resist the urge to bulk-invite your entire org on day one.
- Start with a pilot group. Pick a handful of people—ideally, folks who don’t mind giving honest feedback and won’t panic if things are weird for a day or two.
- Go to the Users section. In Quantified, this usually lives under Admin or Settings.
- Choose your invite method:
- Manual add: Type in names and emails, set roles, hit send.
- Bulk import: Upload a CSV if you’re adding a bunch. Double-check column headers (seriously, this is where most imports break).
- SSO/integration: If you’ve set up SSO (like Google Workspace or Okta), you can sync users in one go. This is slick, but test with a couple of accounts first.
Watch out: Don’t assume everyone needs access right away. More users = more support tickets and confusion if things aren’t ready.
Step 3: Customize the First Experience
First impressions matter. If new users log in and see a blank dashboard or confusing data, you’ll lose them.
- Set up sample data or demo content. If Quantified supports dummy data, turn it on for new accounts. If not, create a sample workflow or report.
- Write a welcome message. Even a short note (“Hey team, here’s where to start…”) goes a long way. Use Quantified’s built-in welcome tools if available, or just ping folks in Slack/email.
- Pin key resources. Link to guides, FAQs, or even a 2-minute “how to” video. Don’t expect users to find help on their own.
Pro tip: Ask your pilot group what confused them. Fix it before rolling out to everyone else.
Step 4: Train, But Don’t Overwhelm
Nobody reads a 50-page onboarding deck. Here’s what actually helps:
- Short live walkthroughs: 15-20 minutes on Zoom or in person. Show the basics: logging in, finding reports, doing the main thing they need to do.
- Office hours or Q&A: Set aside a slot for “ask me anything” time. People will show up with questions you didn’t think of.
- Asynchronous help: Record a quick screen share, write a no-nonsense FAQ, or point to Quantified’s help docs. Keep it simple.
What to skip: Long training sessions, forced quizzes, or anything that feels like homework. Most people just want to know how this fits into their day.
Step 5: Set Expectations (And Keep Them Real)
Don’t oversell what Quantified will do out of the box. If there’s manual setup, say so. If reports are empty until they start using it, explain that.
- Tell people what’s changing. Is Quantified replacing another tool? Are there new metrics they’ll be measured on? Spell it out.
- Explain what’s not changing. If core workflows stay the same, reassure folks.
- Share the “why.” People buy into a tool if they know why it matters to their work—not just because “leadership said so.”
Honest take: Most resistance comes from confusion or fear of extra work, not hatred of new tools. A little clarity goes a long way.
Step 6: Collect Feedback Early (and Actually Use It)
You won’t get onboarding perfect the first time. But you can get closer, fast, if you ask for feedback early and act on it.
- Send a super-short survey after a week: “What was confusing? What was helpful? What do you still need?”
- Watch usage patterns. Are people logging in? Completing key actions? If not, follow up and ask why (individually, not with a guilt-trip blast email).
- Adjust materials. If you keep getting the same question, fix your guides or tweak the process.
What to ignore: Overly generic advice like “delight your users” or “gamify onboarding.” Just get the basics working and improve from there.
Step 7: Roll Out to the Rest (Iterate, Don’t Dump)
Once your pilot group is up and running—and you’ve smoothed out the bumps—invite the rest of your users. But do it in waves, not all at once.
- Stagger invites. Roll out by team, location, or department. This keeps support requests manageable.
- Use your champions. Ask people from your pilot group to help answer questions or show others the ropes. Peer support beats another memo from IT.
- Monitor adoption. Track who’s using Quantified and who’s stuck. Nudge stragglers with a direct message, not a mass reminder.
Pro tip: Keep your onboarding docs updated as you go. Don’t let them rot—outdated info kills trust fast.
Step 8: Keep Support and Communication Open
Even after onboarding, people will have questions or hit snags.
- Set up a clear support channel: Slack channel, email alias, or even a dedicated person.
- Schedule check-ins: A quick sync after a month can catch lingering problems.
- Share wins: If a team finds a clever use for Quantified, broadcast it. Real examples are better than case studies.
What not to do: Don’t disappear after launch. Radio silence = “you’re on your own now,” which nobody likes.
Onboarding doesn’t have to be a drawn-out ordeal or a mad dash. Get the basics working, keep your process lightweight, and be ready to adjust. Skip the over-complicated rollouts and listen to your users—they’ll tell you what matters. Start small, fix what’s broken, and keep moving. That’s how you actually get people using Quantified (or any tool, really).