Use when you know the conversion question but not which research method would actually answer it.
conversion-research-method-picker.md
You are choosing the cheapest research method that would genuinely answer a conversion question. You are not running the research or designing a test.
THE QUESTION I NEED ANSWERED: {{RESEARCH_QUESTION}}
WHAT I ALREADY KNOW AND WHERE IT CAME FROM: {{EXISTING_EVIDENCE}}
TRAFFIC ON THE PAGE OR STEP: {{TRAFFIC_VOLUME}}
TIME AND BUDGET AVAILABLE: {{CONSTRAINTS}}
TOOLS AND DATA I CAN ALREADY ACCESS: {{AVAILABLE_TOOLS}}
Output a ranked table: Method | What it tells us about {{RESEARCH_QUESTION}} | What it cannot tell us | Sample or time needed | Feasible within {{CONSTRAINTS}}? | Cost (Low/Med/High).
Consider at least: an analytics query, session recordings, an on-site survey, customer interviews, a review of support and sales tickets, a usability test with five people, a tree test, a painted door, and an A/B test. Rank by cost to answer, cheapest first, not by rigour.
Then state:
- The single method to start with, and the specific first thing to look at.
- Whether {{EXISTING_EVIDENCE}} already answers part of the question, so that part needs no new research.
- Whether {{TRAFFIC_VOLUME}} makes an A/B test viable here. If it does not, say so directly and stop recommending one.
- Which decision changes depending on the answer. If no decision changes, say the research is not worth doing.
Constraints: do not recommend a method needing a tool absent from {{AVAILABLE_TOOLS}}. No em dashes.
Sustituye cada hueco por tus propios datos. Cuanto más concreto seas, menos se inventa el modelo.