“A major new feature shipped three weeks ago.. Something that used to take 30 minutes took 30 seconds. They looked at the old way and couldn't believe they'd tolerated it. That was the aha.”
When I'm a major new feature shipped three weeks ago, I want to publish in-app onboarding and feature announcements without an engineering sprint, so I can understand which features are being used by which user segments without SQL.
A product manager at a B2B SaaS company who owns feature adoption and in-app user education. They have engineering bandwidth for product, not for tooltips. Pendo lets them publish in-app guides without a ticket. They've also realized that Pendo's analytics tell them something different from their product analytics tool — not better, different. Pendo tells them where users are, not just what they do.
To publish in-app onboarding and feature announcements without an engineering sprint — reliably, without workarounds, and without becoming the team's single point of failure for pendo.
A product manager who trusts their setup. Publish in-app onboarding and feature announcements without an engineering sprint is reliable enough that they've stopped checking. Guide targeting that accounts for in-session user behavior (not just page URL. They've moved from configuring pendo to using it.
A major new feature shipped three weeks ago. Adoption is 12% of eligible users. The PM is in Pendo trying to understand if this is a discoverability problem or a value problem. They're looking at the funnel from "feature page viewed" to "feature used once" to "feature used three times." There's a drop between view and first use that suggests discoverability. They're about to build a guide that appears on the feature page for users who have viewed it but not used it. They will not file a ticket to do this.
Uses Pendo at a SaaS company with 200–5,000 business customers. Manages 10–30 active guides across different features and user segments. Reviews Pendo's feature adoption dashboard weekly alongside their engineering release cadence. Uses Pendo NPS for quarterly sentiment measurement. Collaborates with customer success on Pendo data — sometimes productively, sometimes not. Has a Pendo admin who configured the initial installation; the PM manages everything above the data layer. Has connected Pendo to Salesforce for account-level adoption reporting.
Two things you'd notice: they reference pendo in conversation without being asked, and they've built workflows on top of it that weren't in the original plan. Publish in-app onboarding and feature announcements without an engineering sprint is consistent and expanding. They're now focused on understand which features are being used by which user segments without SQL — a sign the basics are solved.
Guides that trigger at the wrong moment because the targeting rules are approximate 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 `intercom-primary-user` for the in-app guidance vs. proactive messaging workflow. Contrast with `posthog-primary-user` for the PM-layer tool vs. engineering-embedded product analytics philosophy. Use with `ux-researcher` interviewer persona for qualitative follow-up on low-adoption segments identified in Pendo.