Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Continuous Discovery & Feedback Playbook

Purpose

To make continuous discovery a habit, every Product Manager (PM) needs a clear, lightweight system to capture, interpret, and act on user feedback at every stage of the product lifecycle. This playbook spells out the cadences, channels, and responsibilities that keep the flywheel spinning.

Feedback Cycle at a Glance

  1. Capture – Automatic telemetry & always‑on inboxes collect raw signals.

  2. Triage (Daily) – PM/Product Ops tag, dedupe, and link notes in Productboard.

  3. Sense‑Make (Weekly) – Combine qualitative notes and Pendo dashboards into a short discovery summary.

  4. Outcome Reviews (14/30/60/90 days) – Inspect KPIs, decide iterate / scale / sunset, broadcast learnings. fileciteturn1file2turn1file9

  5. Broadcast Wins (Monthly) – Release notes, roadmap updates, and Slack call‑outs close the loop and prime the next cycle. fileciteturn1file12

14 / 30 / 60 / 90‑Day Outcome Review

Timeline

Meeting Length 

Attendees

Inputs

Outputs

T+14

20 min

PM, UX, Eng Lead

Early adoption funnel, key errors

List of fast‑follow bugs / UX tweaks

T+30

30 min

PM, UX, Eng Lead, CS

KPI deltas vs. targets, qualitative quotes

Iterate / Scale decision logged

T+60

25 min

PM, Data, CS

NPS trend, churn signals

Confirm value messaging / enablement gaps

T+90

30 min

Same as T+30 + Exec Sponsor

Full business impact review

Final Iterate / Scale / Sunset call; Productboard card → Launched
 Prep Checklist

  • Confluence Outcome Review template duplicated.

  • Pendo dashboard link pasted.

  • NPS responses exported.

  • Tech‑ops health (errors, latency) snapshot attached.

Pro‑Tip: Schedule all four meetings the day the feature goes to Beta so calendars are locked in advance.

Customer Outreach Cadence

Week

Touchpoint

Channel

Purpose

Owner

1

"First‑Look" invite & quick poll

Email → Productboard form

Confirm first impressions / bugs

PM

2–3

1‑on‑1 interview (30 min)

Zoom

Deep‑dive on value & workflow fit

PM + UX

4

Usage recap & tip sheet

Email (Pendo Guide link)

Drive activation of lesser‑known paths

CS

8

Thank‑you + NPS survey

In‑app banner & follow‑up email

Capture loyalty metric at end of journey

CS
 

PMs aim for 1–2 discovery conversations per week to keep insights fresh.

In‑Product Motions (Pendo)

Motion

Trigger

Segment

Goal

Notes

Release Walkthrough

First login after update

All tenants w/ feature enabled

Awareness & basic task success

3‑step guide, dismissible

Micro‑Survey

Feature used ≥ 3×

Primary persona

Collect JTBD fit feedback

1 open text + 1‑click scale

NPS (Loyalty)

45 days post first use

Paying accounts

Track sentiment over time

2‑question (score + why)
 

All guides tag events back to Productboard automatically via Zapier for streamlined evidence gathering.

Awareness & Closing the Loop

  1. Google Chat #Operations – Ship threads with GIF or Loom demo; tag the dev who crushed the top bug.

  2. Monthly Roadmap Brief – Confluence one‑pager per product line summarising shipped, next, and learning. fileciteturn1file12

  3. Public Portal Refresh – Move card status, add outcome highlights so customers see progress. fileciteturn1file14

  4. Rapid‑Win Wednesdays – Reserve ½‑day engineering slot; PM selects top‑voted tweak; ship same day.

NPS at End of Journey

  • Timing: Send at T+60 (email) and T+90 (in‑app) to capture both immediate and sustained sentiment.

  • Tool: Pendo NPS module; auto‑tag response with feature ID.

  • Analysis: Include NPS trend in 60‑ & 90‑day Outcome Reviews.

Feedback Channels – Process Summary

 

Channel 

Cadence

Owner 

Tool 

How it Feeds Productboard

In‑Product (Guides, Surveys, Telemetry)

Continuous

PM

Pendo

Zapier → Insights, auto‑tagged

Email Outreach

Release W1, W4, W8

PM / CS

HubSpot → PB Form

Manual review & link

Customer Advisory Board (CAB)

Quarterly

Head of Product

Zoom + Miro

PM logs takeaways as Insights

CXT User Group

Semi‑annual live + quarterly webinars

Marketing

On‑site + Webinar

Moderated Slido poll; export notes
 

RACI Snapshot

Activity

PM

UX

Eng Lead

Data

CS

Product Ops

Define KPIs & Telemetry

A

C

C

C

I

I

Daily Triage

A

I

I

I

C

C

Weekly Discovery Summary

A

C

C

C

C

I

14/30/60/90 Review

A

C

C

C

C

I

Roadmap & Comms

A

I

I

I

C

I
 

(A = Accountable, C = Consulted, I = Informed)

Templates & Automation

  • Outcome Review 1‑Pager (Confluence → Templates > Outcomes). fileciteturn1file2

  • Discovery Summary template for weekly sense‑making.

  • Pendo → PB Auto‑Tag Rules (Zapier folder).

  • Calendar Automation – Jira automation schedules Outcome Review meetings on release.

Success Metrics

  • Post‑Launch Outcome Achievement Rate ≥ 75 % per PM. fileciteturn1file9

  • Feedback SLA: 100 % of new notes triaged within 7 days. fileciteturn1file3

  • NPS > 40 on new features within 90 days.

Remember

Feedback loops don’t maintain themselves, PMs keep the flywheel going.

Tools collect; humans decide and act.