- name
- research-proposal-writing
- description
- Use when writing research proposals or grant applications for qualitative or grounded theory studies.
# Research Proposal Writing (Qualitative & Grounded Theory)
A strong proposal convinces reviewers that the study is **important, feasible, ethical, and methodologically coherent**—even when outcomes are emergent rather than hypothesized.
## Proposal structure (typical)
- Summary/abstract.
- Specific aims or objectives.
- Significance/innovation.
- Background (tailored—see GT paradox below).
- Methods: design, setting, participants/sampling, data collection, analysis, rigor, ethics, timeline, team roles.
- Dissemination; broader impacts (funder-dependent).
- Budget and justification; facilities/resources.
## The grounded theory proposal paradox
GT proposals must demonstrate preparedness without **predetermining findings**. Frame the topic as an **area of interest** and justify why emergent theory is needed. Describe **analytic procedures** (constant comparison, memoing, theoretical sampling) rather than a finalized conceptual framework.
## Writing for non-qualitative reviewers
Translate:
- “Saturation” → explain as **stopping criterion based on category development**, not magic N.
- “Emergence” → clarify disciplined procedures that prevent cherry-picking.
- “Rigor” → name concrete techniques (audit trail, triangulation, debriefing) appropriate to your paradigm.
Avoid jargon walls; include a concise **why qualitative** paragraph.
## Significance section
Connect to gaps: what is unknown, costly, unjust, or theoretically weak. Specify **who benefits** and how knowledge will be used—without overpromising causal claims qualitative designs cannot support.
## Methodology justification
Defend **why GT** (or other approach) fits the phenomenon. Describe **initial sampling** and how **theoretical sampling** will evolve. Name software if used, but emphasize **analytic discipline**, not button clicks.
## Timeline
Use phased milestones: IRB, pilot, initial interviews, iterative coding cycles, selective/theoretical coding, write-up. Build time for **transcription** and **team reconciliation**.
## Budget
Include transcription, participant incentives, travel/site costs, software licenses, translation/back-translation if needed, and conference dissemination if allowed.
## Broader impacts (NSF-style framing)
Education/training products, public engagement, tools/templates (de-identified), community partnerships—aligned with funder values.
## NIH-specific considerations (qualitative)
Qualitative work may appear in mixed-methods aims; justify **integration**. Human subjects sections must be meticulous. Check relevant FOAs for qualitative-friendly language and review panels.
## NSF-specific considerations
Broader impacts and data management plans must be realistic for qualitative constraints; describe **metadata and sharing limits** ethically.
## Red flags reviewers notice
- “We will prove hypothesis X” in classic GT proposals.
- Vague analysis (“themes will be identified”) with no procedural depth.
- Sampling that cannot possibly support claims.
- Ethics underspecified for sensitive topics.
## Checklist
- [ ] Paradox of emergence handled with procedural specificity.
- [ ] Rigor strategies named and matched to paradigm.
- [ ] Timeline includes iterative analysis realities.
- [ ] Budget covers hidden qualitative costs.
- [ ] Data management/sharing ethically truthful.
## References (starting points)
- Stern, P. N. (Ed.). *Grounded theory in applied practice* — proposal and project realities.
- O’Cathain, A., Murphy, E., & Nicholl, J. (2008). Multidisciplinary, interdisciplinary, or dysfunctional? *Journal of Mixed Methods Research*.
- Funder solicitation texts and sample funded proposals (when accessible).
GitHub에서 보기