frankglendon Design an end-to-end research study
The host authors a reviewable proposal. This skill supplies planning guidance, not fieldwork, statistical execution or an independent agent runtime.
- Read the brief and authorized references. Separate client requirements, historical proposals, hypotheses and findings. Record the decision, markets, population, period, budget and intended use. Follow existing user authorization; progress with explicit reversible assumptions where appropriate. Do not invent supplier access, prices, experience or credentials.
- Map each business decision to research questions, method, sample/analysis base, analysis, deliverable and action condition. Remove modules without a decision use. Preserve regional scope and verify existing operations before calling a study first entry.
- Choose the necessary stages. For mixed-method work, explain how qualitative findings challenge hypotheses and become quantitative constructs/stimuli, and how quantitative results could change recommendations. Use design and review guidance; two unrelated method lists are insufficient.
- Specify qualitative method, recruitment states, sample/city rationale, interview length, module probes, stimuli, coding and negative cases. Do not multiply every balancing attribute into tiny cells. Shop-alongs/diaries drawn from interviewees are subsets, not additional unique participants. Themes are not population percentages and assumed personas are not validated segments.
- Specify the quantitative population, frame/source, screening, quotas, base/boost samples, questionnaire order, measures, pretest, QC, weighting and analysis bases. Size critical comparisons rather than just the total. An opt-in sample does not support a probability-sampling margin of error or guaranteed representativeness. NPS uncertainty is not a binary proportion formula. Randomized stimulus responses do not establish real-world revenue lift.
- Name the data, method, assumptions and fallback for each analysis. Check segment stability/assignability, distinguish perceived prices from elasticity, and narrow claims or add data when bases are insufficient. A described method does not mean its estimator is implemented.
- Use the proposal outline to cover deliverables, dependencies, schedule, staffing roles, costing quantities, risks and unresolved decisions. Adapt depth to the brief rather than copying historical sample sizes or fixing a page count.
- Review coverage, sample arithmetic, time budgets, local versions and method integration. Distinguish a draft ready for review from authorization/readiness to conduct fieldwork. Hand the frozen survey design to
research-questionnaire, its coded specification toresearch-codebook, and stage status toresearch-workflow.
Label the artifact as a proposal until research has been conducted. Do not prefill segment sizes, preferences or growth outcomes. If exporting Office, use the host's document/presentation tools and complete Microsoft Open XML SDK and visual checks. Keep client originals local; public examples must be generic or synthetic.