Design for Emotion and Flow

I was reading ReadWriteWeb this morning and I came across an interesting article about user experience design. It focused on Trevor Van Gorp’s theory of Emotion and Flow. It is based around the concept that we have no much information available at our fingertips that the resource that a website needs to compete for most of all is the users attention. He shows that there is a fineline between boredom and anxiety, and it is here that the user is most productive.

I think this is very important when designing for social applications as there is so much competition and users time and attenion is finite, you have to give them an interface that does maximise their “flow” and thus their productivity on your site to ensure they come back.

Conducted 1st Technical Test – Very Limited!

We conducted our first test using the ardunio, breadboard and led. This was quite a limited test because we only used one sensor, as we currently only have one sensor (the others are being delivered from a shop in the states) and one corresponding LED. We were only really interested in testing the way that pulses are sent out and the results showed that opinion on this is pretty mixed, rather unsurprisingly really. Ideally we would allow the users to send out differerent length pulses of light or a different brightness, dependent on how hard or how long they press the sensors for. Unfortunately the basic sensors we have for the prototype wont allow us to do this so we will use light pulses that quicly go to full brightness and then have a long fade out. This was not only the most popular in our test but we all feel it is the most effective display both aesthetically and emotively.

1st Technical Test (Planning)

It is imperative that we conduct an initial technical test as soon as possible as it really is the only way to test our concept. Paper prototypes, participatory designs and user interviews are great but it is still so conceptual, you are not testing something real. I think this makes people more inclined just to say yes and less likely to critique the product as they are only going on what you say.

We have decided that the best way to display our product at the show is using two interactive boxes We do not have enough time to actually create the bracelets in an earlier posts so we came to the conclusion that showing the concept of communicating with colour using abstract devices.

Therefore our first technical test should be using a wired up breadboard and arduino and totally foregoing the bluetooth aspect. There will be two aspects to this text, firstly we need to test the led display with a semi-transparent perspex screen and guage peoples reactions to what the differents colours and movements of light mean. The other part is investigating how intuitive the controls are – we are using two variable resistors to create the display and there needs to be obvious correlations between what is done to the switch to what appears on the display.

To get to this stage we need to agree on a set number of controls that correspond to a set number of functions. If we don’t this then it will be impossible to programme and then impossible to test.

Scenario Testing & Participation Design

Yesterday we conducted our first user scenario tests (essentially our version of a paper prototype) and did some participatory design sessions. It was actually really useful and the people we interviewed were mostly very interested in the product.

We tested people who all had experience of LDR’s, but only half were currently in an ldr. There were no real noticeable trends between those who were currently in LDR’s and those who aren’t. Though it might have been interesting to ask how long they have been in their current relationship or were in their last one as that might really influence their opinion on the product.

To see the feedback <a href=”http://pre-sense.wetpaint.com/page/Usability+Feedback” target=”_blank”>click here.

We must now meet up- myself, Imran and Frederik to discuss how these results should be fed back into the design process.

Two Development Streams

A few days ago Frederik and myself spoke to Nicolas who teaches in the school of Graphic Design. He is an expert in sensors and prototyping and was really useful in explaining sensors and hardware we can use for the prototyping process. He explained the three stages of prototype we must go through, the first one – a large wired system incorporating a big breadboard and a large arduino.

The next stage could be in the form of a bracelet but still very much a prototype – use small ardunio and smaller led’s. This will probably be the last prototype stage that we can realistically achieve in this project.

After this we could give our design to an engineer who could stamp it into a circuit board and we could integrate this into the product. We do not have time to do this.

Therefore this has given us two development streams – the technical prototype which will have two stages and we will test the operation of the device with these prototypes.

At the same time we can develop a non-working physical mock-up to give an idea of how the finished product will look. We can test the physical and aesthetic qualities of the device with this prototype.

Participatory Design

At this stage it will be beneficial to engage these users in some participatory design to get some insight how they would envision this device looking, feeling and operating. This though introduces a very important question – are we designing for general use – of people in ldr’s? or are we designing for a specific couple in a ldr? In my opinion the mere idea of this kind of personal and initimate communication is grounded in the concept of individual customisation. Unfortunately we do not have the time or resources to to do this, so we have to accept that our device is one for generic use. Our method of overcoming this is to incorporate an element of flexibility and simplicity in the design so that each set of users can essentially come up with their own use for the device. This gives two design criteria, firstly the actual communication / display mechanism has to be sufficiently braod and changeable to allow for many different kinds of interpretation. Secondly the actual physical design of the device has to be as simple and unobtrusive as possible – it should seamlessly integrate into the users lives.

Show links for useful papers that use participatory design here…

Week Commencing June 16th

Continue User Interviews –
Focus on current ways of digital communication
Dependent on outcome of our concept – what are their thoughts on this?
Will create a paper prototype (based on a set of scenarios) and test with 5 students in ldr at the LCC.

Will ask Imran & Frederik to log his communication with their gf’s this week – just listing every day when they have contact and what

Participatory Design –
I think participatory design would be great but I just wonder if it would actually add value to this particular project – I mean would do we really have time and would we just be doing it for the sake of it? – will check with group.

Target Audience –
Need to define this in a written statement.
Need to actually identify and contact specific test participants will put up a notice at lcc – doubt if it will get any response but you never know – gumtree also. Basically will do my best to recruit people I don’t know, if I can’t will have to resort to friends

1st Usability Tutorial

Had first usability tutorial with Mazy, all went quite well, I was happy that she conceded that it would be impossible to user test on real couples in ldr’s as we would surely be able to only get access to one of the pair. Once we have a prototype suitable enough an option would be to test on couples who don’t live together and possibly have busy schedules so don’t see each other that much, alternatively a long distance relationship of say 2 hours? – could be an option.

In the mean time I need to ask a couple I know who live apart to record they’re communication for a week. I’m interested in the frequency, the method of comms, if they have developed any special routines, practices etc.

For the next tutorial (two weeks) I need to have:

Conducted initial user surveys on current digital communication methods within relationships and expected use of proposed device.

Defined specific user group and recruited suitable participants for ongoing tests / focus group research.

Conducted an analysis of relevant existing research, and identified where your product can improve on any other similar products developed in this area.

Develop a suitable mock-up / prototype / simulation to conduct testing on to demo in next tutorial, devise 1st draft test script.

Should be ok… just need to finalise this damn concept first, where the hell is my group!!

Initial Usability plan

Below is my initial usability plan, though at this stage, without having a finalised concept, I am finding it very hard to envision how the physical prototype testing may pan out:

Though right now I do realise that despite it being important to have an overall plan of the usability tests it is more important to realise that it is going to change, especially as we have not totally decided on our concept yet and we don not know what is possible. So I think the key is to be prepared, plan things out but build in flexibility to that plan.

Interviews

Interviews with potential users can be done in the pre-development stage.

Need to determine:
current ways they communicate
Ways they misuse or modify current forms of communication
their opinions on haptic communication
their thought given certain scenarios