There are no items in your cart
Add More
Add More
| Item Details | Price | ||
|---|---|---|---|
Once a researcher has finally narrowed a topic into a clear, well-defined research question, there is a strong pull toward momentum. The hard intellectual work of narrowing feels finished, and the instinct is to move quickly into the field: schedule interviews, open a data folder, and start "doing" the research. Design can feel like the administrative step standing between a good question and actual data collection.
Many qualitative approaches use similar data collection techniques. Interviews, observation, and document analysis all appear across nearly every methodology, so it is easy to assume that any reasonable-sounding design will work. As a result, researchers sometimes make design decisions informally, by default, or by copying a study encountered in the literature, without examining whether that study's underlying assumptions actually fit their own question.
This is also where the relief of finally having a clear question can work against a researcher. After the difficulty of narrowing a broad topic into a researchable question, design can feel like it should be the easy part, a matter of logistics rather than another round of genuine methodological decision-making. That expectation is exactly what leads to so many design choices being made by default rather than by design.
A researcher has a clear, well-defined question about how first-time academic department chairs navigate their role transition. She decides simply to "do interviews." But she has not settled whether this is phenomenology, case study, or narrative inquiry, three different methodologies that would each shape who she recruits, what she asks in her interviews, and how she analyzes the data she collects. When she is later asked what her methodology is and why, her only answer is that she is conducting qualitative interviews, which describes a data collection method, not a methodology.
Her question was strong. Her design, left unexamined, was not equipped to answer it.
• Treating design as simply choosing a data collection method, rather than an integrated set of decisions — the overall methodology, who you will recruit and why, and how you will analyze what you collect — that must cohere with one another and with the question.
• Choosing a methodology because it is familiar or was used by an advisor, rather than because its underlying assumptions genuinely fit the question.
• Assuming design decisions can be revisited freely later without cost, when some — who is recruited, what is asked, how data is documented — cannot be undone once collection begins.
• Describing method mechanically ("I conducted twelve semi-structured interviews") without explaining why that choice fits the specific question being asked.
Experienced researchers do not treat design as paperwork that precedes the "real" research. They treat it as the mechanism that determines whether a study can answer its question at all. A genuinely strong question paired with a mismatched design produces data that simply cannot speak to what the researcher wants to know. No amount of careful execution afterward can repair that. Rigor in qualitative research is largely determined at the design stage, before a single participant is recruited.
Experienced researchers also treat design as an argument, not just a set of choices. Every design decision should be defensible on its own terms, not "this is what is commonly done," but "this is what this specific question requires." That distinction is usually what separates a design that holds up to scrutiny from one that invites it.
None of these steps takes long on their own, but skipping them is exactly what makes design problems expensive to fix later.
• Before choosing a methodology, articulate explicitly what kind of understanding your question requires: lived experience, a process unfolding over time, a single case with clear boundaries, such as one organization, program, or event, or shared meaning-making within a group. Different qualitative approaches are built to answer different kinds of questions.
• Write a one-paragraph rationale connecting your question, your methodology, who you will recruit and why, and your analysis plan. If any one of these does not logically follow from the others, that is a design problem to solve now.
• Read two or three published studies using your intended methodology and note specifically how their design choices connect to the assumptions behind that methodology. Examine not just what they did, but why it fit their question.
• Ask your advisor or a methodologist to critically review whether your design decisions fit together before you finalize your ethics application, not after.
• Treat any design decision you are genuinely unsure about as a flag for further reading or consultation, not a detail to smooth over with confident-sounding language in your proposal.
It is tempting to measure progress by how quickly a study moves from question to data. But the studies that hold up under scrutiny are usually the ones where the researcher slowed down at exactly this stage, where design was not a box to check, but a set of decisions made with the same seriousness as the research question itself.
Time spent here is rarely wasted, even when it feels slow. It is almost always faster, in the end, than discovering a design flaw once data collection is already underway.
Design decisions carry real weight, and it is worth getting a second set of eyes on them before you commit. That is part of what RTM's mentoring relationships and broader community exist to offer.
Launch your Graphy