Academic English revision

Your Methodology Reads Like a Recipe. Your Supervisor Wants a Decision Log.

Plain English in a methodology section means visible decision logic, not simpler vocabulary. You already made the choices. You just never wrote the 'why this, not that' next to them.

Your methodology section is four hundred words long and contains zero reasons. You listed what you did, in passive voice, in the chronological order you did it, with every term precisely defined per the textbook. And your supervisor wrote 'too technical' in the margin. You stared at those two words and thought: every single term is correct. I used the exact phrasing from Creswell. How is this 'too technical'? Here is the thing they are not saying, the thing you will not hear in the feedback office: they do not need simpler words. They need to see you think. Your methodology reads like a recipe card taped inside a lab cupboard. They want a decision log. And the difference is not vocabulary. It is structure.

When a reader says 'I cannot follow your method,' they almost never mean 'your vocabulary is too advanced.' They mean 'I cannot see the chain of choices you made.' You jumped from one step to the next without explaining why step A led to step B. You presented the method as a fixed pipeline, the only way to do it, when in reality you made at least five judgment calls along the way. The reader cannot see those calls. So they assume you did not make them. A method with no visible decisions looks like a template you filled in. That is what 'too technical' actually means in a margin note: 'I cannot tell where you exercised judgment and where you just followed the manual.' The fix is not to delete jargon. It is to attach a reason to every step that could have been done differently.

Look at this sentence, the one that appears in probably half the qualitative methodology sections you have ever read: 'Data was collected using semi-structured interviews with a purposive sample of 12 participants. Thematic analysis was conducted following Braun and Clarke (2006).' It is not wrong. It is just invisible. Now watch the same content with the reasoning surfaced: 'I interviewed 12 participants, all of whom had experienced X. I chose purposive sampling over random because I needed depth on a narrow population, not statistical breadth. Then I coded the transcripts using Braun and Clarke's (2006) framework, not because it is the default for qualitative work, but because my data was text-heavy and I wanted an inductive path.' Same facts. Same citation. But now the reader sees you choosing. And a reader who sees you choosing trusts you. The 'not because X, but because Y' construction is the single most underused tool in methodology writing. One sentence. That is the whole trick.

The structural fix is almost embarrassingly simple once you see it: for every methodological decision, write one sentence of 'why this, not that.' You do not need a paragraph. You need the contrast. 'I used thematic analysis rather than content analysis because I was generating themes from the data rather than testing a pre-set coding frame.' That is it. The contrast does the explaining. I run my methodology draft through EasyDue before I finalize it, not to change my wording, but to check whether each step actually has a 'why' attached or whether it is just a verb plus a noun floating there with no justification. If a step can be deleted and the logic does not change, it is not a decision. It is decoration. Cut it, or give it a reason.

Mixed-methods sections suffer the same disease, but worse, because the stakes feel higher and the temptation to list is stronger. Here is the flat version: 'A mixed-methods design was employed, incorporating both quantitative survey data and qualitative focus group discussions. The survey consisted of 25 Likert-scale items administered via an online platform.' You told the reader you did two things. You did not tell them what each piece is for, or what would break if one were missing. Now the same content structured as complementary logic: 'I paired a 25-item survey with three focus groups. The survey gave me the what, which demographic groups reported the highest stress. The focus groups gave me the why, what that stress actually looked like in their daily routines. One without the other would have left a hole I could not explain.' The reader now sees the architecture. The two methods are load-bearing, not just 'I did both.'

The same logic applies to reliability and validity statements, where students hide behind decimal points like it is a shield. Flat version: 'The reliability of the instrument was established through a Cronbach's alpha coefficient of 0.87. Content validity was confirmed by two subject-matter experts.' You reported two numbers and walked away. Here is the version where you actually sound like a researcher: 'Before I sent the survey out, two experts in the field reviewed each item. One flagged question 14 as ambiguous between two readings. I rewrote it. The final instrument scored 0.87 on internal consistency, high enough to trust the pattern, low enough that the items are not all just paraphrasing each other.' You just narrated a process of fixing a problem. That is what validity actually is. It is not a score you achieved. It is a process you can tell as a story. The number is the receipt. The story is the method.

Here is the sentence to pin above your desk: 'Your reader does not need to replicate your study. They need to trust that you made deliberate choices and can defend them.' Plain English in a methodology section does not mean replacing 'purposive sampling' with 'I picked people on purpose.' It means making the logical chain visible so the reader never has to wonder what is behind a step. You already made the decisions. You just never wrote them down. Next time you are staring at a methodology draft that sounds like a lab manual, ask one question: can I delete this line and nothing changes? If yes, it is not a methodology. It is a to-do list. And a to-do list does not get you through viva. I use EasyDue to stress-test whether my 'whys' are actually in the text or just in my head before I hit submit. It does not write the reasoning for you. It shows you where the reasoning is missing. That is the whole job.