hermes
58 entries · 53 prompts, 2 personas, 3 workflows

Product discovery

Problem framing, customer interviews, opportunity trees and hypothesis testing.

Start here 2

The general, start-from-zero entry for a need in this category: it works from a blank start, asks for what it needs and hands off to the specific entries. Example: Plan a trip.

Search and filter in Product discovery
  • Product coach

    Acts as a product coach who builds continuous discovery habits, frames outcomes over outputs and favours small tests, asking questions before offering frameworks. For PMs and product teams.

  • Coach me through my first discovery project

    Coaches a new or accidental product owner through their first discovery project one question at a time, from framing the problem to who to talk to, what to ask and how to make sense of it.

Specific 55

One situation, audience, tool or format inside the category. Example: Plan a road trip with children.

  • Analyse competitor reviews

    Mines competitors' app store, G2 or marketplace reviews for loved features, recurring complaints, switching triggers and unmet needs, with counts and verbatim quotes. Use to find openings.

  • Discovery sprint track

    Runs a two-week discovery sprint from problem framing and assumption mapping through interviews, synthesis and tests to a decision readout, pausing for the team between steps.

  • Synthesize customer interviews

    Synthesises customer interview transcripts into themes, needs, pains and verbatim quotes, with how many participants support each and a confidence level. Use after a round of interviews.

  • Design a validation experiment

    Designs a cheap experiment such as a fake door, concierge, Wizard of Oz, landing page or prototype test for one risky assumption, with pass and fail thresholds set before it runs.

  • Run a willingness-to-pay study

    Designs or analyses a willingness-to-pay study (Van Westendorp, Gabor-Granger or interviews) with questions, sample, analysis steps and how to read the result. Use before setting a price.

  • Write an opportunity assessment

    Writes a product opportunity assessment covering the problem, for whom, size, alternatives, why us, why now, success measures, critical risks and a go, explore or stop call.

  • Write a problem statement

    Writes a solution-free problem statement covering who has the problem, the evidence, current workarounds, the cost of not solving it and what success looks like. Use when starting discovery.

  • Write a research screener

    Writes a participant screener for interviews or usability tests with behavioural qualifying questions, disqualifiers that hide the target, quotas and an invite message.

  • Drill follow-up probes

    Runs a ten-round practice game where the user writes one follow-up question to a short customer quote and gets a score for openness, focus on past behaviour and depth, plus a model probe.

  • Define jobs to be done

    Writes jobs-to-be-done statements and maps the forces of progress (push, pull, anxiety, habit) and the switching timeline from customer interviews, with evidence for each.

  • Map assumptions behind an idea

    Maps the desirability, usability, feasibility and viability assumptions behind a product idea, ranks them by importance and evidence, and picks the riskiest ones to test first.

  • Map an opportunity solution tree

    Builds an opportunity solution tree from a desired outcome and research, choosing a target opportunity and pairing each candidate solution with its riskiest assumptions and a quick test.

  • Write a customer interview guide

    Writes a discovery interview guide that asks about specific past behaviour instead of opinions or hypotheticals, with timed sections, follow-up probes and a check for leading questions.

  • Map a value proposition canvas

    Maps a value proposition canvas with ranked customer jobs, pains and gains against the product's pain relievers and gain creators, marks evidence versus assumption, and shows fit gaps and tests.

  • Run a desk research scan

    Plans and structures secondary research before talking to anyone, with search terms, source types, a reliability grade, a claims table and the gaps that become interview questions.

  • Run opportunity scoring

    Runs outcome-driven opportunity scoring from importance and satisfaction ratings, showing the calculation per outcome, to find underserved and overserved needs and what to do next.

  • Write a customer interview snapshot

    Turns notes from one customer interview into a one-page snapshot with a memorable quote, the story told, opportunities, insights and follow-ups, ready the same day.

  • Interpret validation test results

    Interprets the results of a fake door, landing page, concierge or prototype test against preset thresholds, checking traffic quality and bias, and decides proceed, iterate or stop.

  • Plan a design sprint

    Plans a five-day design sprint with a fit check, sprint brief and questions, team roles, pre-sprint recruiting, a timed daily agenda, materials and a customer test plan.

  • Plan jobs-to-be-done switch interviews

    Plans switch interviews with recent buyers, with a timeline from first thought to purchase and probes for the push, pull, anxiety and habit forces.

  • Plan point-of-service intercept interviews

    Plans short intercept interviews where a service happens, such as a shop counter, station or clinic waiting room, with permissions, a three-minute script, time-slot sampling and a note grid.

  • Public service product owner

    Acts as a product owner for a government, council, health or charity service who starts from user needs and policy intent, designs for people who cannot go online, and measures completion and equity.

  • Write a discovery readout

    Turns discovery findings into a short readout for decision-makers with the decision on page one, findings graded by strength of evidence, open questions, options and the decision asked for.

  • Audit the evidence behind an idea

    Grades the validation evidence for a product idea from compliments and hypothetical promises up to past behaviour and real commitments, then says what is known and the next test.

  • Do discovery without customer access

    Plans discovery when access to customers is blocked or gated, using proxies such as support logs, sales calls, reviews and analytics, and a case for getting direct access.

  • Estimate what a problem costs

    Estimates the yearly cost of a customer or operational problem from rough inputs, with every assumption visible, a low-base-high range and cash kept apart from capacity. Use to size a fix.

  • Interview frontline staff about their work

    Writes a discovery guide and session plan for interviewing frontline staff at their workstation before changing their tools or processes, with anonymity, shift timing and last-real-case questions.

  • Interview internal stakeholders before discovery

    Plans short interviews with sales, support, success and leaders before customer research, with questions per role, how to separate opinion from evidence and a hypothesis list to test.

  • Interview people who did not buy

    Plans discovery with non-customers who chose a competitor, a DIY workaround or nothing, with where to find them, a choice-story interview guide and a barrier frame for synthesis.

  • Map a B2B buying committee

    Maps everyone in a business customer's buying decision, from users and champion to economic buyer, IT, procurement and blockers, with each one's goal, objection and discovery questions.

  • Map current alternatives to a problem

    Maps how target users solve the problem today - competitors, spreadsheets, agencies, workarounds or nothing - with cost, switching barriers and the gap each leaves.

  • Map a business customer's workflow

    Documents a business customer's current end-to-end workflow from interviews or observation - steps, roles, tools, handoffs, data and time sinks - and marks where a product fits.

  • Map workarounds around an internal tool

    Turns staff interview or observation notes into a ranked register of workarounds around an internal tool, each with who does it, how often, the risk it carries and the need behind it.

  • Validate a physical product idea
    WorkflowProduct discoveryLegal · safety checks

    Takes a physical product idea through gated steps - buyer interviews, a concept and price check, a prototype test, a preorder test and a go, revise or stop call - before money goes into tooling.

  • Plan a customer co-design workshop

    Plans a co-design workshop with customers, with participant mix, a timed agenda, sketching and ranking exercises, facilitation rules and how outputs feed the backlog.

  • Plan a design partner programme

    Plans a design partner programme for a new B2B product with partner criteria, recruiting pitch, give-and-get terms, cadence, feedback capture and exit criteria.

  • Plan a service prototype test

    Plans how to test a new service before building it, using desktop walkthroughs, staff role-play and Wizard-of-Oz runs that prototype the backstage too, with pass criteria for both.

  • Run a public service discovery

    Runs a public or charity service discovery in gated steps - policy intent, research with offline and assisted users, evidenced needs, the journey, and an alpha, reframe or stop call.

  • Review a customer interview guide

    Critiques a draft interview guide question by question for leading, hypothetical, compound and pitching questions and rewrites each into a past-behaviour question.

  • Review a customer interview transcript

    Reviews a real discovery interview transcript for interviewer mistakes such as leading questions, pitching and missed follow-ups, with line references, rewrites and what the interview actually proved.

  • Simulate a customer discovery interview

    Plays a realistic customer for discovery interview practice, rewarding open questions about past behaviour and misleading leading ones, then reviews what the interviewer learned versus assumed.

  • Test unboxing and setup instructions

    Plans an out-of-box test of a physical product's packaging, assembly or setup instructions with first-time users, covering tasks, think-aloud prompts, timing, error logging and a severity scale.

  • Write a discovery research plan

    Writes a one-page discovery plan linking each learning goal to the decision it informs and the cheapest method that can answer it, with sample, timeline, budget and attendees.

  • Write discovery interview outreach messages

    Writes the email, LinkedIn, in-app and community messages that ask customers or prospects for a discovery call, with incentive wording and two follow-ups that get calls booked.

  • Write a problem validation survey

    Writes a survey that sizes how widespread and painful a problem is among target users, with behavioural screening, frequency and workaround questions and no hypothetical buying questions.

  • Write a smoke test landing page

    Writes the landing page copy and measurement plan for a smoke test of a product idea, with one call to action, a pass threshold and honest follow-up for sign-ups.

  • Find who your research sample is missing

    Compares the people a team has researched with the people its product or service serves, shows who is missing or over-represented and sets quotas and routes for the next round.

  • Interview people who stopped using your tool

    Plans churn interviews for a free or open-source tool without telemetry, with how to find lapsed users,, a switch-interview guide and a synthesis template. Use when you need to know why people stop.

  • Set up a weekly customer interview habit

    Sets up a sustainable weekly customer interview habit for a product trio or solo PM, with automated recruiting, a rota, a 30-minute format, a one-page snapshot and a route from insight to decisions.

  • Plan a pilot of a new service

    Plans a time-boxed pilot of a new service at one or a few sites, with fair site choice, a comparison site, success and harm criteria set in advance, staff load, data to collect and a decision meeting.

Showing 50 of 55. See them all in search

Advanced 1

Expert or deep work that assumes the user can judge expert output. Example: Plan croissant lamination.

  • Build a job map

    Builds a job map of the steps a customer goes through to get a job done, with desired outcome statements per step and where today's solutions fail.