What exact terminology does the dissertation methodology chapter require?
When the rubric asks for a “research design” it isn’t looking for a summary of what others have done. The grading sheet typically circles four key phrases: research paradigm, sampling strategy, data‑collection procedures, and analysis plan. If any of those headings are missing, the committee will flag the whole chapter as “insufficiently methodological.”
Take a look at the rubric excerpt below. Each row shows the criterion, the minimum evidence the grader expects, and a common shortfall that pushes a draft back for revision.
| Criterion | What the grader expects | Typical shortfall |
|---|---|---|
| Research paradigm | Explicit statement (e.g., constructivist, interpretivist) and justification | Vague “qualitative approach” without theory link |
| Sampling strategy | Purposeful or theoretical sampling description, sample size rationale | Listing “interviews” only, no criteria |
| Data‑collection procedures | Step‑by‑step protocol, instrument details, timing | Paragraph that reads like a literature review |
| Analysis plan | Specific coding method, software settings, validation steps | General “thematic analysis” without NVivo workflow |
Notice how each criterion demands a concrete label and a brief justification. When you rewrite, start each subsection with the exact term from the rubric, then add a one‑sentence “why this matters” before diving into the details. That tiny framing move instantly separates methodology from a literature narrative.
Why does my draft read like a literature review and how can I restructure it?
Most students fall into the trap of “review‑heavy” methodology because the same sources that informed the theory also appear in the design description. The technical dead end here is the lack of a clear procedural flow. A reviewer will skim for verbs that signal action—“recruit,” “record,” “code,” “triangulate.” If those verbs are buried in paragraphs, the chapter feels static.
Imagine you’re mapping a road trip. The literature review is the travel guide; the methodology is the itinerary with departure times, stops, and fuel stops. To shift gears, pull the guide out of the itinerary section and place it where you discuss theoretical grounding. Then, in the methodology, list each action as a bullet or numbered step, followed by a brief rationale that ties back to your paradigm.
“When I rewrote my methods as a numbered protocol, my advisor could finally see the ‘how’ instead of a second‑hand summary of other studies.” – graduate student, nursing
Start each paragraph with a process verb, then answer three questions: What am I doing? When will I do it? How will I verify it? This three‑question pattern forces you to stay concrete and prevents the drift back into narrative review.
How do similarity detectors view methodology drafts and what can I do to stay safe?
Similarity software scans for strings of text that match published sources. Because methodology sections often reuse standard phrasing (“semi‑structured interview guide was piloted”), those phrases can trigger false positives. The integrity fear isn’t about plagiarism; it’s about the software flagging you for “over‑reliance on boiler‑plate language.”
Two safeguards work well. First, paraphrase any description that comes directly from a methods textbook. Replace “thematic analysis was conducted following Braun & Clarke (2006)” with “I applied a six‑step thematic analysis, adapting Braun & Clarke’s framework to suit interview data from clinical staff.” Second, keep a “source‑track” table (you can do it in a simple spreadsheet) that records where each procedural phrase originated. When you submit, you can quickly point the committee to the original source if a similarity report pops up.
Critical warning: do not copy‑paste whole paragraphs from method handbooks; even a well‑cited block can raise a red flag. Instead, write the step in your own voice, then cite the original author in parentheses.
What realistic step‑by‑step plan can I follow tonight to start the overhaul without burning out?
Balancing a 20‑hour clinic shift and ADHD means you need micro‑chunks that respect your energy cycles. Below is a checklist you can print and stick on your desk. Each item is designed to fit inside a 90‑minute work sprint followed by a short break.
- Open a fresh document titled “Methodology Blueprint.” Add four headings that match the rubric terms.
- Copy the one‑sentence justification for each heading from your literature review (no more than 30 words each).
- Under “Data‑collection procedures,” write a bullet list of every action you will take (e.g., recruit participants, obtain consent, schedule interviews).
- Switch to NVivo. Create a new project, import a single interview transcript, and label the first node “Pre‑interview logistics.” This tiny win shows the software is set up.
- Write a 150‑word paragraph that explains why you chose purposeful sampling, referencing your research question directly.
- Take a 10‑minute break, stretch, then review the draft for the three‑question pattern (What? When? How?).
When you finish the checklist, you’ll have a skeleton that satisfies the rubric’s terminology demand and already separates methodology from literature. From there, flesh out each bullet into a concise paragraph over the next few days. The key is to stop expanding until the skeleton is complete; otherwise you’ll spiral back into review mode.
Which practical tools and habits help ADHD while juggling a part‑time clinic shift?
ADHD isn’t a barrier; it’s a signal to structure your environment. The most effective habit is the “two‑minute capture.” Whenever a task pops into your head—“email participants,” “order transcription service”—write it on a sticky note or a digital list within two minutes. At the end of each shift, scan the list and move items into your weekly planner.
Use a timer app that supports the Pomodoro technique but customize the intervals. Many students with ADHD find a 25‑minute focus block too short; a 2‑hour focus block with a 15‑minute break works better for deep work like drafting methods. Pair the timer with a “distraction‑free” mode on your computer: close all tabs except the word processor and NVivo.
Another tip is to align your most demanding tasks with your natural energy peaks. If you’re sharper in the morning after a clinic shift, schedule the methodology writing then; reserve evenings for lighter tasks like formatting references.
How can I use NVivo efficiently without getting lost in coding overload?
NVivo feels like a maze when you import dozens of transcripts at once. The technical dead end is trying to code everything in one go. Instead, adopt a “progressive coding” workflow.
Step one: create a single “master node” called “Emergent Themes.” Open one transcript, read it once, and highlight any phrase that seems interesting. Drag those highlights into the master node—no sub‑nodes yet. This gives you a visual sense of theme volume.
Step two: after the first transcript, review the master node and identify three to five recurring ideas. Convert each into a sub‑node (e.g., “Time pressure,” “Patient communication”).
Step three: return to the next transcript and code only to those sub‑nodes. If a new idea appears, add it as a temporary node, but keep the list short. By the time you finish three transcripts, you’ll have a manageable set of nodes that reflect the core of your data.
Finally, run the “coding comparison query” to see how many references each node holds. If a node has only one or two references, consider merging it with a larger theme. This pruning step prevents the dreaded “code bloat” that stalls analysis and eats up precious time.
Start tonight by opening NVivo, creating the master node, and importing the first interview. Even a single coded line counts as progress and keeps the momentum going.