A | B | C | D | |
---|---|---|---|---|
1 | Discovery Type | Tactic | Description | Use case |
2 | Zero-contact discovery | Check support tickets | Filter yesterday’s Zendesk/intercom tickets for the word “X,” copy the top ten, highlight the common problems. AI is becoming super helpful in analyzing support tickets. | Need data within minutes and no meetings |
3 | Zero-contact discovery | Crunch your numbers | Graph feature usage for the last 30 days, circle sharp drops and unexplained spikes. | Post-launch health check of a feature |
4 | Zero-contact discovery | Competitor tear-downs | Sign up for the closest competitor, click every button, map each screen, note where their choices differ from yours. Gaps appear in minutes, not weeks. | Planning roadmap gaps against rivals |
5 | Zero-contact discovery | Review mining | Scrape App/Play Stores, and G2 reviews. Sort by the extreme stars. Zero- and one-star ranks point to problems you might share. | Validating pain points in the wider market |
6 | ||||
7 | Low-contact discovery | Micro “Lazy” polls | Insert a single-question Typeform inside the empty state of your feature. Ten clicks later you have some signals. | Quick directional feedback inside the product |
8 | Low-contact discovery | Fake-door test | Ship a disabled button labeled with the future feature, measure click-through for a week. This is like a demand forecast for an unshipped feature. | Test demand before investing engineering effort |
9 | Low-contact discovery | Pre-recorded Zoom call snippets | Search “pricing objection” in Zoom/Gong recordings, watch five minutes. Listening to raw objections is much better than reading second-hand summaries every time. | Get qualitative insight with zero scheduling |
10 | Low-contact discovery | Dog-food sprint | Force the whole squad to use the feature all week. Bugs that once felt theoretical will find you by midweek. | Harden a feature before public beta |
11 | Low-contact discovery | Session replay watch-party | Play ten Hotjar/FullStory recordings, pause at every rage-click. Watching frustration with your team brings empathy to your whole team. | Build shared empathy for real user friction |
12 | ||||
13 | High-contact discovery | 45min Customer interview | Recruit three target users for 45m-1hr calls. Ask five open questions, show no slides, stay silent after each question. You will surface the important motives in under an hour. | Surface deep motives and jobs-to-be-done |
14 | High-contact discovery | Customer advisory Slack | Share a Figma mockup in a private Slack channel and ask “Would you pay for this?” Instant thumbs-up or down with zero friction. | Iterate quickly on design direction |
15 | ||||
16 | Embedded discovery | Shadow your customers | Spend a day in the customer’s office, do their job shoulder to shoulder. Pain points becomes clear to everyone; you will never debate priority again. | Entering a vertical/domain you don’t yet understand |
17 | ||||
18 | ||||
19 | ||||
20 | ||||
21 | ||||
22 | ||||
23 | ||||
24 | ||||
25 | ||||
26 | ||||
27 | ||||
28 | ||||
29 | ||||
30 | ||||
31 | ||||
32 | ||||
33 | ||||
34 | ||||
35 | ||||
36 | ||||
37 | ||||
38 | ||||
39 | ||||
40 | ||||
41 | ||||
42 | ||||
43 | ||||
44 | ||||
45 | ||||
46 | ||||
47 | ||||
48 | ||||
49 | ||||
50 | ||||
51 | ||||
52 | ||||
53 | ||||
54 | ||||
55 | ||||
56 | ||||
57 | ||||
58 | ||||
59 | ||||
60 | ||||
61 | ||||
62 | ||||
63 | ||||
64 | ||||
65 | ||||
66 | ||||
67 | ||||
68 | ||||
69 | ||||
70 | ||||
71 | ||||
72 | ||||
73 | ||||
74 | ||||
75 | ||||
76 | ||||
77 | ||||
78 | ||||
79 | ||||
80 | ||||
81 | ||||
82 | ||||
83 | ||||
84 | ||||
85 | ||||
86 | ||||
87 | ||||
88 | ||||
89 | ||||
90 | ||||
91 | ||||
92 | ||||
93 | ||||
94 | ||||
95 | ||||
96 | ||||
97 | ||||
98 | ||||
99 | ||||
100 |