Pasts + Futures

Case Study & Paper

May 9, 2012 @ 09:30, Room: 12AB

Chair: Siân Lindley, Microsoft Research Cambridge, UK
Envisioning Ubiquitous Computing - Paper
Community: design
Contribution & Benefit: Examines technological visions of the future and the role of 'envisioning' within ubicomp and HCI communities. Critiques these envisionings and recommends changes in ways we read, interpret and use them.
Abstract » Visions of the future are a common feature of discourse within ubiquitous computing and, more broadly, HCI. 'Envisioning', a characteristic future-oriented technique for design thinking, often features as significant part of our research processes in the field. This paper compares, contrasts and critiques the varied ways in which envisionings have been used within ubiquitous computing and traces their relationships to other, different envisionings, such as those of virtual reality. In unpacking envisioning, it argues primarily that envisioning should be foregrounded as a significant concern and interest within HCI. Foregrounding envisioning's frequent mix of fiction, forecasting and extrapolation, the paper recommends changes in the way we read, interpret and use envisionings through taking into account issues such as context and intended audience.
ACM
Steampunk as Design Fiction - Paper
Community: design
Contribution & Benefit: A critical look at Steampunk through the lenses of design fiction, DIY, and appropriation. Provides a new perspective on design strategies for HCI rooted in questions of ethics, values, and identity.
Abstract » In this paper we look at the Steampunk movement and consider its relevance as a design strategy for HCI and interaction design. Based on a study of online practices of Steampunk, we consider how, as a design fiction, Steampunk provides an explicit model for how to physically realize an ideological and imagined world through design practice. We contend that the practices of DIY and appropriation that are evident in Steampunk design provide a useful set of design strategies and implications for HCI.
ACM
Revisiting the Jacquard Loom: Threads of History and Current Patterns in HCI - Paper
Community: design
Contribution & Benefit: We describe and reflect on the workings of the Jacquard loom from the perspective of contemporary HCI: materiality, graspability, full body interaction, sustainability and age.
Abstract » In the recent developments of human computer interaction, one central challenge has been to find and to explore alternatives to the legacy of the desktop computer paradigm for interaction design. To investigate this issue further we have conducted an analysis on a fascinating piece of machinery often referred to as one of the predecessors of the modern day computer, the Jacquard loom. In analysing the Jacquard loom we look at qualities in design and interaction from some different perspectives: how historical tools, crafts, and practices can inform interaction design, the role of physicality, materiality, and full-body interaction in order to rethink some current conceptions of interaction and design of computational devices.
ACM
Lost and Found: Lessons Learned from a Design Retrospective - Long Case Study
Community: design
Contribution & Benefit: Case study reflecting on the long-term design of an information management system for students. Can help designers understand the impact of multiple influences on the overall transformation of a system.
Abstract » Reflection is critical for understanding how designs evolve and the factors that impact that evolution. This is especially meaningful for projects that have taken place over a long period of time and with consistent overall direction. In this case study, we reflect back over the design of an information gathering and management system built for students in higher education. We demonstrate how users can be involved in various ways over a development period that spans many years; we show that designs of different fidelities can effectively garner user feedback; and we illustrate the impact of multiple influences, including users, research team members, and resource limitations on the overall transformation of the system. We conclude with a series of lessons learned that we hope will help future researchers plan and execute their own design-implement-evaluate lifecycles.