Pendo is installed, the data is flowing, and the thing you’re worried about is the thing every admin worries about: it will just sit there. Your product managers will open it twice, your CS team will ask you to pull the report instead of logging in, and in six months someone in finance will ask what the license is for. That fear is reasonable. It’s also fixable, and the fix is not another training session.
Search “getting team to use Pendo” and most of what comes back is feature tours. Features aren’t the problem. Pendo pays off when the system around it works: a goal people agree on, one person who owns it, and a plan that fits the week your team already has. Here’s how I set that up, in five steps, each with a question to ask about your own setup.
Before the steps, a few ground rules:
“We bought Pendo to understand our users” is not a goal. It’s a mood. A goal is a question someone on your team is already trying to answer and can’t. Which features do trial accounts never touch? Where do new admins get stuck in week one? Which customers went quiet before they churned?
Pick one question per team, and pick the team that’s loudest about not having the answer today. If product keeps arguing about which feature to sunset, that’s your first goal. If CS keeps getting surprised by renewals, start there. Write the question at the top of your Pendo project doc in plain words, so anyone can read it and nod.
Self-check: if I asked three people on the team what Pendo is for, would they give the same one-sentence answer?
A tool nobody owns is a shared kitchen at the office. Everyone uses it, nobody cleans it, and the fridge gets scary by Friday. Pendo without an owner goes the same way: half-finished tags, three dashboards that disagree, and a feature list nobody trusts.
The owner doesn’t have to be senior. They have to be the person who checks the data weekly, answers “is this number right?”, and says no to the fourth dashboard. Give them a title inside the team (Pendo admin is fine) and a standing slot on the calendar. One owner, one deputy who can cover a vacation, and everyone else is a reader.
I’ve lost this one myself. Early on I ran a two-hour Pendo training for a team of eight, felt great about it, and checked logins a month later: two. The training was fine. Nobody owned what happened the next morning, so nothing did.
Self-check: if the data looked wrong tomorrow, does everyone know exactly who they’d message?
Your team does not need to know Pendo. They need to know the three things that answer their question from step one. For a product manager that’s usually one feature-usage view, one path, and how to read a retention chart. For CS it’s one account view and where the health signal comes from.
Build the onboarding around that. One hour, live, on their real data, ending with each person finding one thing they didn’t know about their own users. Then a one-page cheat sheet with screenshots and the owner’s name at the bottom. Save the deep dives for the two people who ask for them.
If you’ve already done a broader rollout and it stalled, I wrote about how to win over the team that won’t use it. The short version: shrink the ask until saying yes is easier than saying no.
Self-check: could a new hire on this team use Pendo for their one question after 60 minutes with the cheat sheet, without asking me?
Nobody adds a new tab to their morning. So don’t ask them to. Ask where decisions already get made and put the Pendo number in that room.
The first time that number changes a decision, adoption stops being your project and becomes their habit. (Yes, I have watched a dashboard get built in a workshop and never opened again. More than once.) Dashboards don’t drive habits. Meetings that expect a number do.
Self-check: name one recurring meeting on this team where a Pendo number is on the agenda every time. If I can’t, the tool isn’t in the workflow yet.
Momentum comes from a visible early win, not a big one. Pick something you can show in 30 days: a guide that cut support tickets on one feature, a segment that found the accounts going quiet, a chart that settled a two-month argument in five minutes.
Set the target before you start so the win is real. Pendo lets you put a measurable goal on a guide and track against it (Set guide goals), which is the easiest place to get a clean before-and-after. Then tell the story in the team channel: what we asked, what Pendo showed, what we changed. Keep it to four sentences (nobody reads the long version, including me).
If you’re still in the first month, the first 30 days plan covers what to set up so this win is possible.
Self-check: what is the one result I could show the team by this time next month, and did I write the target down today?
People don’t adopt Pendo. They adopt the answer it gave them last week.
The limit of this advice: it assumes the install is healthy. If your tagging is a mess or the data doesn’t match what people see, no amount of ownership fixes that, and you should start with the plumbing. But if the numbers are right and nobody looks, the five steps above are the whole job.
Try one thing this week: pick the single meeting from step four and get one Pendo number onto its agenda. Not a dashboard. One number, and a sentence about it.
Once the team is in, what Pendo adoption success looks like at each checkpoint shows the numbers to expect at thirty, sixty and ninety days.
Plan on 60 to 90 days from the first goal to the point where people open it without being asked. The first 30 days are setup and one win, the rest is repetition inside meetings that already happen.
No. Start with the team that has the sharpest unanswered question and the loudest complaints, get them a visible win, and let the next team ask for it. Rolling out to everyone at once produces a lot of logins in week one and none in week six.
Leadership cares about the decision, not the tool. Put one Pendo number into whatever they already read every week and tie it to a decision they made. Two months of that beats any pitch deck.
Getting team to use Pendo is a plan, not a training, and it’s a lot easier with someone who’s run the plan before. Book a strategy call and we map your first 90 days with you: https://deliberatesignals.com/pendo-strategy-call/.