Week 3. Reframing the Work
What I did this week
Supervisor Meeting (June 9th):
I had a meeting with Trevor and Sarah. The following were discussed.
[Meeting Summary]
1. Community alignment
Understand what the DRS and service design conferences are. Review the papers that have been accepted so far to identify what kind of papers this community selects, and define what contribution I can make to this community. The key is to demonstrate in the paper that I sufficiently understand this conference community. Think from the perspective of the conference reviewers.
2. Framework example papers
Look for cases among previously accepted papers that presented a framework. Examine how they presented their framework and identify what I can apply to my own paper.
3. Framework refinement
Refine the framework based on workshop feedback.
3-1. Elevate the "Why" column into synthesized, higher-level statements.
3-2. Rename the "Check" column to "Validation" or "Indicators".
3-3. Add subtitles to the guide to convey the meaning more clearly.e.g., Indicator - ways to verify if it's working
3-4. The framework is currently explained in text only. Showing the actual UI alongside it and connecting it to the relevant part of the framework would likely make it easier to understand.
3-5. Explaining it with reference to real-world cases would likely make it easier to understand. Develop a concrete application scenario.
4. Service design framing
Service design should be holistic. Right now it looks too much like UX/UI, so I need to show that this work can be applied from a broader, bigger-picture perspective. Rather than limiting the language and framing to UX/UI, describe it from a service design point of view.
e.g., When writing the Abstract, state something like "this paper is service design but connects to UX/UI" so that reviewers can grasp the context right from the start of the paper.
Expand the design implications to address services beyond the screen (e.g., in-person viewings, surrounding systems). No additional data collection is needed; this is purely a matter of framing.
5. Prepare the skeleton and share the Google Doc
Prepare a bare-bones paper skeleton, aligned with Track 7, consisting of section headings and one-to-two sentence descriptions per section. Share the Google Doc with Trevor's and Sarah's personal Gmail addresses, and once the skeleton is ready for feedback, notify them by message before the next meeting (June 30, 10am).
Community Alignment:
I started with the first item from the meeting summary: understanding the community. DRS (Design Research Society) is the oldest and most multidisciplinary society for design research, founded in the UK in 1966. It serves as the parent society that covers design research as a whole. ServDes (Service Design and Innovation Conference) is a specialised conference within that umbrella, focused on service design. It began as a Nordic annual conference and has grown into a biennial international event, publishing proceedings through a double-blind peer review process.
The community I am entering is ServDes. However, this community sits within a broader design research tradition that values theoretical contribution, methodological rigour, and design-as-research framing. So I need to retain the practice-oriented character of ServDes while being clear about what my knowledge contribution is, at the level DRS expects.
[The Character of the ServDes Community]
The community is highly international (with many authors from Brazil, Korea, Finland, Italy, and China, and Korean papers appearing every year), and it actively values geographic specificity rather than treating it as a limitation.
It has a clear sense of what design is for. The work mainly addresses themes such as public services, social innovation, and community. → When applying this to my thesis, I need to translate my work into the language of public good, such as housing access, exclusion, and precarity, rather than commercial profit.
The unit of analysis is the system. The work deals with ecosystems, structural coupling, and the like. In other words, the community looks for systemic thinking rather than UX/UI design. → In my thesis, I should position the work as an intervention into the landlord-tenant-platform multi-actor system.
Many of the papers make use of frameworks. They employ conceptual tools such as models and frameworks.
Rather than resolving contradictions neatly, the community frequently frames them productively (as tensions and paradoxes), focusing on how to view them and on what direction design might best move toward.
What I am planning for next week
by June 14th
Framework example papers
by June 16th
Framework refinement
by June 24th
Paper skeleton
Reflections
This week shifted my perspective more than I expected. Going into the community alignment research, I thought it was just background work. But the more I looked into ServDes, the more I realised how much the framing of my paper needs to change. The feedback from my supervisors, especially around service design framing and expanding beyond the screen, is pushing me to reframe the contribution. That feels manageable, but it requires careful thinking about language and positioning before I start writing.



Comments