You inherited Pendo, or you just bought it, and the first thing you noticed is how much of it there is. Guides, tagging, segments, dashboards, NPS, feedback, and a Slack thread of people asking when they can “get in there.” The objection I hear most from new admins is “I don’t know where to start.” You don’t start with features. Every Pendo admin setup I’ve seen work started with a plan, and the plan has five parts.
Before we go into the five, a few ground rules:
Pendo touches product, customer success, marketing, and usually somebody in data. The first mistake a new admin makes is trying to be all of them. Your job in the first two weeks is to write five names down: who owns the install (the snippet on your app), who owns tagging (naming the pages and features Pendo tracks so reports mean something), who owns guides (the in-app messages), who owns feedback, and who owns the reporting people actually look at. Some of those names will be yours. Not all of them should be.
A composite from our client calls: the admin who quits at month four is almost always the one who owned everything, because every request from every team landed on one desk. The admin who is still there at year two had a name next to each area, even if that name was “the CS lead, one hour a week.”
Self-check: could you say out loud, today, who owns guides and who owns tagging? If either answer is “me, I guess”, that’s your first meeting.
It’s tempting to open Pendo and start clicking tag on everything. Don’t. Sit with your product lead and draw, on paper, the five to eight moments that matter for a customer: they sign up, they finish setup, they invite a teammate, they hit the feature that makes them stay, they renew. That map decides what you tag first, because tagging everything gives you a report nobody can read.
Pendo’s journey map metrics are built to answer “how many people got from A to B, and how long did it take”, but only if A and B are moments you chose on purpose. Otherwise it’s like being handed car keys and a road atlas with every road highlighted. Very thorough. Completely useless.
Self-check: if I asked you to name the one moment in your product where a customer decides to stay, could you point to it in Pendo?
Now you tag. The rule is simple: every page or feature you tag should answer a question someone asked. “Are people finding the new export?” is a question. “Track the settings page” is a chore. Tag your journey moments first, then the three or four features product is arguing about this quarter, and stop there for 30 days. That list of 40 guides from the intro? It waits until the tags underneath it exist, because a guide you can’t measure is a poster.
Then a small, boring step that saves the whole thing: agree on names. Pick a naming convention (something like Area: Page: Action) and write it in a shared doc before the third person gets tagging access. I’m pretty far from perfect here. The first account I ran had “Dashboard”, “dashboard”, and “Dash – new” as three separate features for a year, and I made two of them. Every report I built had an asterisk on it. (Yes, my data was bad, so I should feel bad.)
Self-check: could a new hire read your feature names and know what they mean without asking you?
Pendo can collect feedback, run NPS (the “how likely are you to recommend us” score), and show you what users are asking for. Collecting is the easy half. The hard half is the loop: where does a piece of feedback go, who reads it, and when does the person who gave it hear back? If you can’t answer those three, you have a suggestion box, not a feedback system.
Set the loop up small. One survey, one owner who reviews it every other week, one place (a doc, a board, a channel) where product sees themes rather than 300 raw comments. Pendo’s feedback insights help you group the raw stuff into themes, and we wrote about the queue most teams forget in our post on the product feedback workflow.
Self-check: pick one piece of feedback from last month. Can you trace who saw it and what happened next?
Here’s the part most 90-day plans skip. Around day 60, write down what working means for your company in three numbers. Maybe it’s: 80% of the journey moments tagged and named correctly, one guide live that changed a behavior you can measure, and one product decision this quarter that cited Pendo data. Your three will be different. The point is that “working” is written down before someone asks you to prove it.
Then set a rhythm. A 30-minute monthly review of tags, guides, and who has access keeps the account from turning into the closet where everything gets shoved. If you want to know what that closet looks like, read 5 signs your product experience platform needs governance. Every sign on that list started as a skipped monthly review.
Self-check: if your VP asked “is Pendo working?” tomorrow, what three numbers would you show?
Every struggling Pendo setup we’ve been asked to rescue had the same shape. Someone learned the tool very well and nobody owned the plan. The guides were fine. The tagging was fine-ish. But no one had agreed on who owned what, which moments mattered, or what working looked like, so the account drifted until it became a line item finance asked about.
Nobody ever fixed a Pendo problem by learning one more feature. The fix is a person with a name next to each area, a map, and a definition of done. That’s the whole system, and it fits on one page.
Try one thing this week: write the five ownership names from step one on a single sheet and share it with your product lead. If one line is blank, book that meeting. That’s your day one.
If your team is stretched thin, our Pendo consultants can help build ownership that does not fall on one desk.
When you want to know what the numbers should look like at each checkpoint, read what Pendo adoption success looks like in ninety days.
Find out who owns each area (install, tagging, guides, feedback, reporting) and write the names down. Everything else in the setup depends on those answers, and most problems trace back to a blank on that list.
Plan on 90 days to reach “working” as you defined it in step five, with the first useful report inside 30. Smaller teams get there faster, and larger ones spend more of the first month on ownership.
No. Tag the five to eight journey moments and the features product is actively debating, then stop for a month. Tagging everything produces reports nobody reads and names nobody agrees on.
You’re the one who has to make this work, and you can. Book a strategy call and we map your first 90 days with you.