Sunday 12 June 2011

Reflecting on Reflection

I'd like to reflect on a few papers I've been reading to ground a study I'm conducting into ways of recording the design process within a school of architecture. "Narrative, Memory and Practice: Tensions and Choices in the Use of a Digital Artefact" (2009) and "Slow Technology - Designing for Reflection" (2001).

The first of these papers focuses on the use of a series of “SenseCams”, wearable cameras equipped with a wide angle lens, and programmed to take pictures at regular preset intervals, but that can also be used as a conventional camera to deliberately capture certain images. The unit is also equipped with several other sensors that record information such as the number of steps the wearer has taken over the course of a day.

Essentially the paper sets out the case for “reconstruction narratives”, a story told from a captured individuals point of view, to be selectively recounted at a later date.

For me the central issue here is how captured photo series are reviewed. It is interesting to note that the study group happily shared their recordings, particularly those made at group events, but for the purposes of any project I would propose, expecting a user to sit at a computer and sifting through days of recordings does not seem viable. This has essentially been the concern I have raised regarding sketch books, that notes are taken, doodles made, but never looked at again.

This moment is the fundamental interaction between the device and the user, and ultimately you’re getting handed a photo album. Its an album that contains images of events that you may not normally think about, and pushes the users to reflect on their daily lives. But, it does not prompt or suggest this reflection. I believe it would be very easy, especially in a “professional” context, to declare yourself to busy for something so frivolous.

This observation is in no way a criticism of the study. The other paper (“Slow Technology – Designing for Reflection”) states that it is this willingness to sit, take time, and think back over past events that is so important if people are to reflect on their lives or learning. An absence of productivity may be required in order to precipitate reflection.

“However, slow technology differs in that it is not supposed to reduce cognitive load or make digital information and computational resources more readily available. Slow technology is not about making technology invisible, but about exposing technology in a way that encourages people to reflect and think about it.”

What I see a need for is a sort of conversation stater, in a friendly non pressured environment to promote reflection and informal learning. The idea would be to essentially put up a flag next to an individual, and draw others to them initiating a sharing of opinions and knowledge that would otherwise go untapped.

References;

Lindey, S. E. et al, "Narrative, Memory and Practice: Tensions and Choices in the Use of a Digital Artefact" (2009), British Computer Society

Hallnas, L. & Redstrom J., "Slow Technology - Designing for Reflection" (2001), Personal & Ubiquitous Computing

No comments:

Post a Comment