Menü
Use when writing research proposals or grant applications for qualitative or grounded theory studies.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when writing academic prose for qualitative research — findings, methods, discussion sections with appropriate voice and conventions.
Use when conducting participatory action research (PAR) involving collaborative inquiry, cycles of action and reflection.
Use when formatting academic work in APA 7th edition style — citations, references, headings, tables, and manuscript structure.
Use when designing or conducting case study research following Yin's multiple case study methodology or Stake's approach.
Use when developing and densifying categories with properties, dimensions, conditions, and consequences.
Use when formatting academic work in Chicago/Turabian style — notes-bibliography or author-date systems.
| name | research-proposal-writing |
| description | Use when writing research proposals or grant applications for qualitative or grounded theory studies. |
A strong proposal convinces reviewers that the study is important, feasible, ethical, and methodologically coherent—even when outcomes are emergent rather than hypothesized.
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.
Translate:
Avoid jargon walls; include a concise why qualitative paragraph.
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.
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.
Use phased milestones: IRB, pilot, initial interviews, iterative coding cycles, selective/theoretical coding, write-up. Build time for transcription and team reconciliation.
Include transcription, participant incentives, travel/site costs, software licenses, translation/back-translation if needed, and conference dissemination if allowed.
Education/training products, public engagement, tools/templates (de-identified), community partnerships—aligned with funder values.
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.
Broader impacts and data management plans must be realistic for qualitative constraints; describe metadata and sharing limits ethically.
