Week 4. Before the Writing Begins
Updated: Jun 30
What I did this week
Framework Example Papers:
To understand how frameworks are typically presented in ServDes papers, I looked through accepted papers from ServDes 2023 and 2025 that proposed frameworks. Here is what I found.
1. Introduction structure
Most papers follow the same pattern: here is the problem, here is what existing tools are missing, and here is the framework I am proposing to fill that gap.
2. Visualisation
There is no single correct format. Some use tables, others use diagrams. What they have in common is that the visual form reflects the logic of the framework itself. The structure of the idea determines the shape of the image. (examples below) -> For my framework, I felt that creating a sense of connection between the tenant and the landlord was important, which is why the current visual of bridging them together makes sense.
3. Explaining components
The typical flow is: written explanation first, then the visual, then supporting text below. Not just a visual with a caption.
4. Application
Some papers apply the framework to a real case study, others test it against a specific domain as an example, and some propose it as a theoretical framework without full application. A range of approaches are accepted. -> I'm going with the second type, using my own Application Scenario, a hypothetical tenant-landlord scenario, to show how the 4-pillar framework works.
5. Positioning the contribution
The "this framework contributes X to field Y" statement appears in multiple places, including the Abstract, Introduction, and Conclusion, so reviewers can find it easily.
Framework Refinement:
Based on supervisor feedback from last week, I refined the Framework Application Guide.
[Framework Application Guide]
Based on supervisor feedback from last week, I refined the Framework Application Guide.
1. Elevated the "Why" column from raw participant quotes into synthesised, higher-level principle statements.
2. Renamed "Check" to "Indicators."
3. Added subtitles to each column to make the meaning clearer at a glance.

[Application Scenario]
I also developed a concrete application scenario to show how the framework works in practice from both sides of the rental relationship. In the paper, each of these moments will be paired with the corresponding UI design.
Tenant: A in her mid-twenties, who has just moved to a new city for a new job. She is looking for a one-year rental with no local connections and no one to ask for help.
Landlord: The owner of one of the listings A is interested in. She has rented to three tenants before.
Tenant | Landlord | |
Verification | She sees a profile with verified badges for government ID and property ownership. She does not know this landlord at all, but the badges give her a baseline of confidence before she even reads the listing. | She checks A's profile and sees a government ID badge and a Digital Credit Verification badge, the latter coming from an integrated credit bureau API. She does not need to guess about financial reliability. |
Predictability | The landlord's average response time is listed as 1 hour. Forty minutes have passed since A sent her first message, and she is not anxious. She knows roughly when to expect a reply. | A's average response time is 15 minutes. The landlord expects the back-and-forth to move quickly. |
Transparency | The landlord's bio includes her name, age, and occupation. The listing covers price, layout, and amenities, but also includes a micro-story: why she loves this place, and what kind of tenant she imagines living there. By the end, A feels like she knows something real about both the person and the home. | A's bio mentions that she has just moved to this city for a new job. She has never met A, but something about that reads as honest and grounded. She feels like she has a sense of who this person is. |
Accountability | The landlord has three reviews from previous tenants, averaging 4.5 stars. Reading through the written reviews, A gets a sense that she is consistent and easy to deal with. | A only has one review. But given her age, a limited rental history makes sense. That one review is 4.9 stars, and the written comment is positive. It is enough. |
What I am planning for next week
This week ran longer than expected. Benchmarking the example papers and working through the refinements took more time than I had planned. I will begin tomorrow and aim to have the skeleton ready by June 24th or 25th, which still keeps me on track for the June 30th supervisor meeting.
Reflections
I thought finding the framework example papers would be a quick task to tick off. But going through them made me realise that knowing how to position and present a framework is just as strategic as the research behind it. There is still enough runway before the deadline, so taking the preparation seriously now seems like the smarter move over rushing in.
The scenario exercise was something I had always carried around in my head, but this was the first time I actually wrote it out properly. Putting it into words made it feel more concrete than I expected. And I think pairing each moment in the scenario with the corresponding UI in the paper will make the whole thing much more intuitive for readers. It stops the framework from feeling abstract and makes it feel like something that actually operates in real situations.
The skeleton is the next big step, and I will admit it is the part I have been quietly putting off. Time to start.



Comments