Pendo adoption challenges: winning over the holdouts

You rolled Pendo out three months ago. The snippet is live, the dashboards are built, and most of your company treats it like the fire extinguisher in the hallway: glad it is there, no plans to touch it. The Pendo adoption challenges I hear about on calls are almost never about the tool. People did not refuse Pendo. They refused what they thought it meant for them, and nobody gave them a reason to think otherwise.

The version of this that costs real money looks like a fintech I started working with this fall. They were heading into a Pendo renewal with no clear owner for the tool and two internal teams, portal and product, who did not communicate with each other. The contract had been running for months and nobody could point to one decision Pendo had changed. That is the stall. The fix below is the one we ran there: shrink the ask, name an owner, ship one thing each team asked for, and say it out loud.

Find out what each team is protecting

Resistance rarely shows up as no. It shows up as “after the release” or a Slack thread that quietly dies. Underneath, each team is guarding something specific.

• Customer success is worried a usage score will second-guess their read on an account.
• Engineering is worried the snippet slows the app, or that product will push guides without a review.
• Product managers are worried that once behavior is visible, the roadmap they defended last quarter looks thin.
• Leadership is worried they paid for a second analytics tool when the first one still has a dashboard nobody opens.

None of those fears are silly. Write them down, one per team, in their words rather than yours. You cannot answer an objection you have paraphrased into something more comfortable.

Give Pendo one owner, then one owner per team

A tool nobody owns is a shared office kitchen. 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 fintech’s two teams had never agreed on who owned Pendo, so the first working session was not about guides. It was about writing two names down: marketing owned the NPS survey, the portal team owned the dashboard questionnaire, and each team got its own 30-minute session instead of one all-hands.

The owner does not 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. One owner, one deputy who can cover a vacation, and everyone else is a reader. If you are the owner and you inherited the mess, the first 90 days as a Pendo admin is the plan I would hand you.

Recruit the loudest complainer

The natural move is to build an advocacy group out of the people who already like Pendo. Skip it. Those people were coming anyway. The person you want is the CSM who said “we already know what our customers do” in the kickoff, or the engineer who asked three questions about page load. They have credibility with the people you are trying to reach, and they will spot the holes in your rollout faster than any fan will.

Give them a real job: they name one question their team keeps asking and cannot answer, and you build the report that answers it. Nothing else until that is done.

The Pendo adoption challenges each team actually has

“Better product decisions” is your reason. It is not the CSM’s reason, and it is not sales’ reason. Each team needs a payoff they would notice by Friday. The table is the one I fill in with clients in the first week; copy it and fill in your own right-hand column.

For customer success the view is usually feature adoption by account. Pendo’s Feature Adoption widget gets you there in an afternoon: add it to a dashboard, pick the segment, and the benchmark line shows which features carry most of the usage. No custom work. If your CS team in particular has gone quiet, I wrote up the specific causes in why customer success teams ignore Pendo, and the fix there is the same fix here, just narrower.

Put Pendo where the work already is

Nobody adds a new tab to their morning. Ask where decisions already get made and put the Pendo number in that room: the feature-usage view is the first slide in product’s weekly prioritization, the usage trend sits next to the renewal date in CS’s account review, and the Monday leadership email carries one Pendo number, the same one every week, with a sentence about what changed. Dashboards do not drive habits. Meetings that expect a number do.

Onboard people in an hour, not a course. Your team does not need to know Pendo. They need to know the three things that answer their question: for a product manager that is usually one feature-usage view, one path, and how to read a retention chart; for CS it is one account view and where the health signal comes from. One hour, live, on their real data, ending with each person finding one thing they did not know about their own users.

Roll it out to one team first

The urge to launch everything at once is strong, because the contract clock is running and the whole company was on the kickoff call. Fight it. Pick the team whose question you can answer fastest with the data you already have, give them two weeks of real use, and only then show anyone else. The other teams will hear about it in the hallway, and being asked “when do we get ours?” is a better position than begging.

With the fintech, the two guides went to their QA environment first, with production two weeks behind, and each team only saw its own session. Narrow first, then earn the right to widen. That is how we run every engagement, and our managed services exist for the teams who want someone to keep running it after the first win.

Show a win before anyone asks

Adoption is not a training problem. It is a proof problem. People start using a tool when they have seen it settle an argument they were part of. Your job in month one is to find one moment where Pendo changed a decision and tell the story in plain terms where everyone can see it: what we asked, what Pendo showed, what we changed. Four sentences. Then make it a habit, one win every two weeks, posted in the same place.

The first time someone from a team you have not onboarded yet replies with “can we see that for our accounts?”, you have crossed over. From there, the table above fills itself in with less effort each time.

Questions people ask

How long should Pendo adoption take?

One team using it weekly inside 30 days is a healthy pace. Company-wide habits take two to three quarters, and trying to compress that is usually what causes the stall. Plan on 60 to 90 days from the first goal to the point where people open it without being asked.

Should we require teams to use Pendo?

No. Mandates get you logins, not decisions. Answer one real question for the team, put the number in a meeting that already happens, and the logins take care of themselves.

What if leadership is the group resisting Pendo?

Retire one manual report they currently receive and replace it with a Pendo dashboard that shows the same number, updated live. Leaders resist new tools and rarely resist getting a report early. Two months of that beats any pitch deck.

If you would rather talk through your own team’s situation than guess at it, a free Pendo strategy call is 30 minutes, there is no pitch, and you leave knowing the one report to build first.