RevelicaRevelica

Menu


Playbook

Data mining

Run Data mining

Run a data mining experiment to test an assumption. Systematically searches web and workspace evidence, sets success criteria upfront, and produces a structured experiment report.

Use when

  • You need to validate whether a specific assumption is true before investing in a solution
  • You have pre-mortem output and want to test the mandatory assumptions first
  • You want to gather market evidence for a hypothesis before a roadmap review
  • You are about to run customer interviews and want to know what to look for

What You Get

  • Evidence Source

    Saved references to every source consulted — URLs, publications, data sets — so future research can build on this work rather than repeating it.

  • Evidence Finding

    Specific findings from each source, each classified as supporting or contradicting the assumption being tested, with reasoning.

  • Experiment Report

    A structured record of the experiment: question, success criteria, methodology, findings summary, result, and recommended next steps.

How It Works

  • 1
    Define the experiment upfront

    Write the question, set explicit success criteria, and document the methodology before searching for anything. Setting success criteria first is what prevents confirmation bias.

  • 2
    Check the workspace first

    Search existing evidence sources so you do not redo research that has already been done — prior work is often more relevant than a fresh web search.

  • 3
    Search the web systematically

    Use specific, falsifiable queries — not queries designed to confirm your hypothesis. Look for data that could prove the assumption wrong as much as data that supports it.

  • 4
    Record findings and produce the report

    Save each source and finding with a clear stance on whether it supports or contradicts the assumption. Summarize the experiment result and recommended next steps.

Why structured data mining beats ad-hoc research

Unstructured research has a well-documented bias problem: you find evidence that confirms what you already believe. Data mining experiments are different because they require you to set success criteria before you start searching — what would supported look like? What would refuted look like? Then you search systematically for evidence that could go either way. The result is an experiment report that captures not just what you found, but what you were looking for and why the evidence supports or contradicts the assumption.

Who it's for

Most valuable after a pre-mortem or hypothesis refinement session has identified specific assumptions to test. Works best when the assumption is specific and falsifiable — vague assumptions produce inconclusive results.

Product Manager
User Researcher
Product Strategist

Frequently asked questions

What is data mining in product management?
In product management, data mining means systematically searching for evidence — in web sources, market research, customer data, or workspace knowledge — to test whether a specific assumption is true or false. It is structured and pre-registered (success criteria set before searching) to avoid confirmation bias.
How do you test a product assumption before building?
Frame the assumption as a falsifiable claim, set explicit success criteria for supported and refuted, then search for evidence that could go either way. Document each finding with a stance and reasoning. Avoid the temptation to search only for confirming evidence.
What is the difference between data mining and customer interviews?
Data mining searches for existing evidence — published reports, web data, market signals — to test a specific assumption. Customer interviews generate new primary evidence directly from customers. Data mining is faster and cheaper; interviews are more specific to your actual customers. Both are valid and often complementary.

Community Examples

Works better with

GitHubGitHubNotionNotionPostHogPostHogSlackSlack