Week 10. Nearing the Finish
What I did this week
Revised the Validation section
The second round of interviews with users actually produced fairly surface-level feedback. Rather than offering new insights, participants mostly confirmed that the prototype met the needs they had described. At first I worried whether this was enough for a validation section, but following Trevor's advice, I shifted the framing. I made it clear that this stage was never meant to be exhaustive validation but was an intentionally scoped, initial test, and I described the interview procedure in more detail to establish academic rigour.
Wrote the Introduction
I wrote it following a five-part structure: (1) a motivational statement about why I undertook this research, (2) a brief snapshot of what is currently known in the literature, (3) the research goals and objectives, (4) why this research matters now, and (5) a paragraph signposting the structure of the paper. I kept my own personal rental experience in the opening, but pushed it beyond anecdote by framing distrust as a structural problem that runs in both directions.
Wrote the Background
I brought over the literature review I had written for my proposal and cleaned up the formatting and references. I went back and checked each cited paper against the original source, making sure every claim lined up with its evidence. In the process I swapped in one paper that fit my argument better, tightened the wording of my citations to stay faithful to what the sources actually say, and organised the references to match the conference template.
Wrote the Conclusion
I wrote it in three parts: (1) a summary of what the paper presents and its key contributions (the framework, the prototype, and the validation), (2) future work and next steps, and (3) a short, optimistic closing paragraph hoping the wider research community will adopt and build on the framework.
What I am planning for next week
Revise the paper
Once Trevor's feedback on the paper comes in, revise accordingly.
Write the Acknowledgements, References, and Abstract sections.
The Abstract is best written last, once the paper is complete, so I will get to the other sections first.
A few refinement tasks
Double-check that the transitions between the phases connect well, so a reader can follow the logical flow.
Move the Framework in Application part inside the Design section. If the template has no Heading 3, I will create a custom style, something like italics, to distinguish a third-level heading without breaking the template format.
Check that participant quotations are italicised consistently throughout the document.
Double-check that all references are in place and correctly formatted.

Reflections
What struck me was how, after writing three big sections in one week, the pieces started to connect. The question I raise in the introduction returns in the conclusion, and the Background carries through into the Discussion. For the first time, it felt less like a pile of paragraphs and more like a real paper.



Comments