“It happened mid-workflow — the PM launches a new dashboard feature.. pendo handled something they'd been doing manually, and it just worked. That was the moment it stopped being a tool they were evaluating and became one they relied on.”
When I'm the pm launches a new dashboard feature, I want to track feature adoption and identify which features users discover vs. which they ignore, so I can build in-app guides and tooltips that help users find value without overwhelming them.
A product manager at a B2B SaaS company who uses Pendo as both their analytics platform and their in-app communication tool. They track feature adoption, build onboarding guides, run NPS surveys, and analyze user paths — all without filing engineering tickets. They appreciate that Pendo lets them own the user communication layer. They've become the person who says "let's add a guide for that" whenever a feature has low adoption, and they're starting to wonder if they've created guide fatigue.
To reach the point where track feature adoption and identify which features users discover vs. which they ignore happens through pendo as a matter of routine — not heroic effort. Their deeper aim: build in-app guides and tooltips that help users find value without overwhelming them.
pendo becomes invisible infrastructure. Track feature adoption and identify which features users discover vs. which they ignore works without intervention. The old problem — too many guides and tooltips create a cluttered experience that users learn to dismiss — is a memory, not a daily fight. Guide frequency management that prevents tooltip fatigue by limiting how many guides a user sees per session.
The PM launches a new dashboard feature. After two weeks, Pendo shows that only 15% of users have visited the page and only 8% have used the key interaction (custom date range). The PM creates a targeted in-app guide: a tooltip pointing to the new dashboard in the navigation, followed by a walkthrough of the date range feature. They target it at power users who haven't visited the new page. After a week, the visit rate jumps to 40% and the interaction rate to 22%. The PM marks it as a win but notices that the guide dismissal rate is 60% — meaning more than half of users who see the tooltip close it without engaging. They refine the copy and targeting for the next iteration.
Manages Pendo for a B2B SaaS product with 1K–50K users. Tracks adoption of 20–50 key features. Has built 15–40 in-app guides (tooltips, modals, walkthroughs). Runs quarterly NPS surveys and ad-hoc CSAT surveys. Creates custom segments based on behavior, plan type, and user role. Reviews Pendo dashboards weekly for adoption trends. Spends 20–30% of their time in Pendo. Has a guide strategy that defines when to use tooltips vs. modals vs. banners.
The proof is behavioral: track feature adoption and identify which features users discover vs. which they ignore happens without reminders. They've customized pendo beyond the defaults — templates, views, integrations — and their usage is deepening, not plateauing. When new team members join, they hand them their setup as the starting point.
Too many guides and tooltips create a cluttered experience that users learn to dismiss keeps recurring despite updates and workarounds. They start tracking how much time they spend fighting pendo versus using it. The switching cost was the only thing keeping them — and it's starting to look like an investment in the alternative.
Pairs with pendo-primary-user for the standard product analytics perspective. Contrast with posthog-growth-engineer for the developer-centric analytics approach. Use with amplitude-primary-user for the analytics-focused comparison without in-app guidance.