Overcoming Writer's Block
The best-built scenario in the fourteen weeks, and the only one that diagnoses itself. Read it the way you would read an incident report - not for what failed at the end, but for the control that was never in place at the start.
The case, as the week sets it
The scenario sits on a single slide in the week's deck on writing up, between the material on report structure and the material on abstracts. It is set as an activity: the deck asks what the researcher should do and tells students to post their thoughts to that week's forum. It is attributed to the student researcher's toolkit that accompanies the subject's set text - a text not named on the slide, or anywhere else in the fourteen weeks.
The source gives the person in the case a first name. This library calls her the researcher throughout, and names the software she used no more specifically than the source does.
What is intact, and what is missing
Read the case twice. The first read produces alarm - a deadline, a blank screen, and a supervisor asking for something that does not exist. The second read produces an inventory, and the inventory is what makes this case worth the page.
What the research produced - all of it intact
- Eighteen in-depth interviews, conducted and held
- Six months of overt participant observation in the setting
- The data analysed, in a qualitative analysis package
- A coding tree mapping the relations between the key themes
- Three named themes, articulated well enough to be stated in one line each
- Wide reading, done before entering the field
What the record contains - all of it absent
- No drafts of any written work
- No research diary
- No recollection of how access was negotiated
- No recollection of how the sample of interviewees was devised
- Reading notes that exist but were never organised
- No account of the process that now reads as anything but 'messy'
The left column is a completed research project. The right column is the reason it cannot be written. This is the case's actual lesson, and the source never states it: every one of the researcher's problems is a recording failure, not a research failure.
Four problems, one kind of problem
The case states four distinct difficulties. Set each against what it actually is and what it blocks, and they collapse into one category.
THE FOUR STATED PROBLEMS, CLASSIFIED
| What the case says | What kind of failure it is | What it blocks | Recoverable in six weeks? |
|---|---|---|---|
| No time to prepare drafts of her written work | A recording failure - nothing was written down as it happened | Nothing to start from, revise or show a supervisor | Yes, but only by starting now |
| No time to keep a research diary | A recording failure - the process was never logged | The whole account of how the research was conducted | No - the log cannot be written retrospectively |
| Cannot remember how access was negotiated or the sample devised | A recording failure with an already-visible consequence | The Methods chapter, explicitly | Partly, and only from surviving traces |
| Reading notes not organised for the Literature Review | A recording failure of the mildest kind - the notes exist | The Literature Review, until the sorting is done | Yes - this is a sorting job, not a reading job |
The classification and the recoverability column are this library's reading. The source states the four problems and does not group, rank or classify them.
None of the four rows describes bad interviewing, a thin sample, a weak analysis or a flawed design. The research is sound. What is gone is the record of how it was done - and the record is the raw material of two of the chapters she has to write.
Why the Methods chapter is the one she asks about
Of everything in the case, the Methods chapter is the question the researcher asks out loud: "how is she ever going to write a coherent Methods chapter?" That is not incidental. Every other chapter is written from something that still exists.
- The Findings are written from the analysed data and the coding tree. Both survive.
- The Literature Review is written from the reading and the notes. Both survive, in disorder.
- The Discussion is written from the findings and the literature. Both survive.
- The Methods chapter is written from the record of decisions taken during the project. It does not survive, because it was never made.
The convergence worth noticing is inside the same week. The week's own study notes give a research-design component list - the fullest component list anywhere in the subject - and two of its items name precisely the two facts the case says have been lost.
WHAT THE WEEK'S OWN DESIGN LIST REQUIRES, AGAINST WHAT THE CASE SAYS IS GONE
| Component required by the week's study notes | Status in the case |
|---|---|
| "information about the selection process (means by which information sources will be negotiated and accessed)" | Cannot remember how access was negotiated |
| "selection criteria for research participants/organisations/texts (sample selection, criteria for inclusions and exclusions)" | Cannot remember how the sample of interviewees was devised |
| "study setting - naturalistic or contrived" | Six months' overt participant observation in the setting - recorded in the case, undefined in the subject |
The pairing of the two lists is this library's reading. The week presents the component list and the case study separately and does not connect them.
So the week specifies, in one document, exactly what a design account must contain; and demonstrates, in another, what happens when two of those items were never written down. The design section is treated at The Research Design Section of a Proposal, access negotiation at Covert Research and Negotiating Access, and sample construction at Sampling and Selecting Participants.
The record that was not kept
What can be said without inventing anything is what the case establishes by subtraction. It names the facts that went missing, and those facts are therefore what a record of this project would have had to hold: how access to the setting was obtained and on what terms; how the interviewees were chosen and on what criteria; when each phase happened; and what the researcher decided, and why, at each point where the design could have gone another way.
What the week gives you to answer with
That is not a fatal criticism of the week. The drafting stages are real and are treated at The Challenge of Writing Up, the report structures are given, and the case is well made. The shortfall is specific: the case poses a question the surrounding material cannot fully answer.
Working the last six weeks
The steps below follow from the inventory above rather than from any procedure in the source, and they are marked as this library's synthesis. They are ordered by what the case says still exists.
Triage, in the order the surviving material allows
Write the chapter you already hold
The analysis is done and the coding tree exists. The findings can be drafted from what is already on the screen, without further fieldwork or recollection - and that chapter demonstrates to a supervisor that the project is real.
Reconstruct the methods account from traces, not from memory
Whatever survives of the process - correspondence about access, consent materials, interview schedules, calendar entries, the interview list itself - is evidence of how the project was run. Reconstruct from artefacts you can point at, and stop where the artefacts stop.
Declare what cannot be reconstructed
The subject's own checklist asks you to be realistic and honest about the limitations of your methodology. A chapter that says which design decisions cannot now be evidenced is far stronger than a confident reconstruction that nothing supports.
Treat the notes as a sorting problem
The reading was done. The notes exist. Organising them is a bounded, finishable task with a known input, which is exactly the kind of work a blocked writer can do on a day when drafting is impossible.
Put something in front of the supervisor this week
The supervisor has asked for a draft. A partial draft with a stated gap converts an unbounded panic into a review with an agenda, and the material's own instruction is to start writing drafts early and show them to your supervisor.
Note what the order does. It puts the writing where the evidence is densest and defers the chapter that depends on missing evidence until the surviving traces are assembled - the same logic you would apply to a delivery report written after a handover.
The control that would have prevented it
Three separate places in the supplied material give the same instruction, and the case is the demonstration of what their absence costs. The week's writing-up slides state that many parts of a report can be written early in the research process. The same deck's getting-started slide says to start early. The subject's closing checklist says to start writing drafts of your project report early and show them to your supervisor.
Read against the case, that instruction is not about productivity. It is about capture. Drafting early forces a record into existence while the facts are still recoverable, which is the argument made from a different direction at Note-Taking and Bibliographic Records and reinforced in the subject's closing list at The Do's and Don'ts of Social Research.
Capture while the fieldwork is running
- How access was requested, from whom, on what terms, and what was agreed
- How the sample was constructed, and what was included or excluded and why
- Every design decision that could have gone another way, with the date and the reason
- What changed after the project started, and what prompted the change
- Full bibliographic details of anything read, captured at the moment of reading
- A dated draft of any section that can be written now, however rough
The companion page, Answering the Writer's Block Case, examines a real submission written against this activity - what it saw, and the two problems it never touched.
What to carry forward
- This is a constructed scenario. Its six weeks, eighteen interviews and six months in the field describe the story and set no benchmark for anything.
- The research in the case is complete and sound. The data, the analysis, the coding tree and the themes all survive.
- Every stated problem is a recording failure. Nothing failed in the fieldwork; the account of the fieldwork was never written.
- The Methods chapter is the one she asks about because it is the only chapter written from the record of the process rather than from the data.
- The week's own design component list names the two facts the case says are lost - access negotiation and sample selection - which makes the case a demonstration of the list's necessity.
- The research diary is named as the missing control and defined nowhere in fourteen weeks. Record the gap; do not fill it with a definition the source never gave.
- The transferable control is capture, not discipline: write the record while the facts are still recoverable, and draft early enough that the draft is itself a record.
Frequently asked questions
Is the case based on a real research project?
No. It is a constructed teaching scenario supplied on a slide and attributed to the student researcher's toolkit accompanying the subject's set text. Its figures are properties of the story. Nothing in it should be read as evidence about how long fieldwork takes, how many interviews are enough, or how common writer's block is.
If the block is really a recording failure, why does the researcher feel unable to write at all?
Because the chapters are not independent. The case says she tries one section, then another, and gets confused about how they fit together and where the data should go. When the account of the process is missing, the sections that depend on it cannot be settled, and an unsettled structure makes every section feel like the wrong place to start.
Can a Methods chapter be reconstructed after the fact?
Partly, and only from artefacts. Correspondence, consent materials, interview schedules, calendars and the participant list are evidence of how a project was run and can support an accurate account. What cannot be recovered is the reasoning behind decisions that were never recorded, and an honest chapter says so rather than inventing a rationale.
What exactly is a research diary?
The supplied material does not say. It names the diary in this case as the thing whose absence causes the crisis, lists keeping one as a Do in its closing checklist, and never explains what it contains, how often it is written or how it is used at the write-up stage. This library records that gap rather than filling it with a definition the source never gave.
Does the week supply an answer to its own activity?
No. The prompt asks what the researcher should do and the deck moves on. What the week offers on process is three drafting stages and three words of encouragement. The best-supported answer is the one the case implies through its own inventory: her research is finished, her record is not, and the work of the six weeks is to rebuild the record and write from what survives.
How does this apply to a project report rather than a dissertation?
Identically, and often with a shorter fuse. A post-implementation report, a benefits review or an evaluation is written from the record of what was decided and why, and if that record was never kept the report becomes reconstruction from memory. The controls are the ones you already run: a decision log, an issue register, and drafting sections while the evidence is fresh.
References and source attribution
- The supplied teaching source: weekly study notes, slide decks and assessment activities for a master's-level research methods subject in project management. Author, institution and year are not stated in the supplied files.
- The Week 13 slide deck on the challenge of writing up, slide 17, which carries the case study and its activity prompt. The deck attributes the case to the student researcher's toolkit accompanying the subject's set text; that text is given no author, title or year anywhere in the fourteen weeks.
- The Week 13 study notes, section 2, whose research-design component list specifies the information about the selection process and the participant selection criteria that the case's researcher can no longer recall.
- The closing checklist of the same subject, reproduced by its final week from a methods text's student-researcher toolkit with a copyright line dated 2012, which lists keeping a research diary among its Do items and is paraphrased rather than reproduced here.
Suggested questions for Ask KEVOS
- Classify my own project's write-up problems into research failures and recording failures.
- I cannot evidence how I selected my sample. Draft an honest limitations paragraph that says so.
- What can I still write this week if my analysis is finished but my process notes are missing?
- Turn my project's decision log into the raw material for a methods section.
- Which parts of a research report can be drafted before fieldwork is finished?
- Give me a capture checklist to run alongside interviews so I am not reconstructing later.