Posted on

The accidental techie (5): Shadowing

 [ part 1, part 2, part 3, part 4, part 5 ]

The other night, our youngest had a friend over for a sleepover. It so reminded me of shadowing, known in AI as knowledge elicitation and in software design as requirements engineering. Whatever you call it, it remains my favourite time in any project because it satisfies all my nosy urges. I love to go in and see who people are, what they do, and how they use technology in their environment: A stalker by any other name.

Our young friend was obviously seeing us in our natural habitat, but in conversation I got to hear all about her life too, which is quite different yet similar to ours. I was fascinated. Even so, with my new knowledge, I still feel very disconnected these days, and like most people fundamentally, want to know: What do other people do in their own homes? Especially raising children. Am I doing it right? My children’s lives are so different from my life as a child. It all seems a bit rigid to me and a bit too nuclear-family based, these days, but a friend said to me just recently that her life was exactly like that, no people just dropping in whenever, and that was normal to her, so you know, perhaps it’s not time, it’s geography.

That said, I struggle with the idea that there’s a rigid schedule and no random event or visitors. At my mum’s funeral, some of my cousins were reminiscing about how they’d often come down to breakfast to find one of our uncles sitting in the kitchen, even though he lived four doors down. And, when I was young, I would get the bus (9p for 2 miles) to my auntie’s house and stay for days, no one had to be somewhere you couldn’t go with them, unless it was the pub, and if the house was full, then you’d wake up in the morning with more people in bed with you than before you went to sleep.

It is different in the workplace, I am not having a sleepover (my niece: Auntie Ruth, you look so cute in your sleeping mask when you are asleep) or brushing my teeth with the people I shadow, but, I am their silent witness as they go about their business, and we all spend a lot of time at work. So, it is not surprising the stories people want me to know about them often include their personal lives. People are so much more than the jobs they are doing.

I had forgotten how excited I used to get about shadowing until last Saturday night. I was at a party and had such a laugh talking about computing and tarot. And then, I rode my bicycle home, under a very cool, late-midnight sky, past people in the park drinking beer, sitting in the remnants of a very hot summer’s day. Freewheeling it took me way back, to Lausanne, to those dark cycle paths and a midnight skinny dip in lac leman during my PhD days at EPFL.

For two years I was working on a project with exhibition planners at the Palais de Beaulieu, Lausanne. It was a really nice project though slightly tangential to my PhD so I would need to stay late on Thursday nights to prepare for the next day. I would normally peddle home around 2am feeling a lovely breeze after hours of programming, long after everyone had left.

But I didn’t mind, I used to like programming alone late at night. I would sit in my bra – the offices were hot – and lean out of the window for a slinky cigarette. Not that I really smoked, but a gauloise in a lacy bra out the window of the engineering department after a boiling hot day was sometimes just what that girl felt like she needed, on occasion, when things were compiling.

Those long nights were worth it, though. I loved going round the exhibition centre on Fridays to shadow the head draughtsman and see how he went about putting together an exhibition. On exhibition days we would walk about and he tell me exactly about the things you can’t model in a computer, but we’d try anyway. We’d try to model who didn’t want to be next to whom, following the classic AI problems of the travelling salesman and the eight queens, which don’t really work in the real world. He was an amazing teacher, always truthful with a charming diplomacy. I’d follow along making notes, sampling cheese and drinking vin blanc during the quatre heures. (I still do the quatre heures #friyays) there is nothing better than sitting down at 4pm for a little glass of vino and an amuse-bouche.

The one time I had an ethnographer do shadowing for me which I wrote about over on A List Apart, I so felt like I was missing out, even though I repeated him, saying that it was tedious, even though it never was to me. I thought I had to say it, to be one of the lads. Yeah, I know, I am not one of the lads and to top it all, with him doing the shadowing, I just felt like I was getting all the information second hand. But, I did get to spend a day watching the steel roll out in massive slabs in the mills at Corus, Teesside. Wow! That was a sight.

There were some sights at ICI too, not just when I was with me auld fellas, but in places like the Caustic Soda plant – it had a big pile of salt outside – and someone once said to me: Don’t even touch the door handles when you are in there. Hilarious. I went round various places mainly to fix computers with my screwdrivers and earth bracelet but most of the shadowing I did to figure out what software someone needed to support them in their job, was drumroll, in the accounts department.

The plus side of this was that I found that in an office, it is easier to look professional, out onsite with so many unknown variables sometimes it would be hard to look sensible. If I hadn’t dressed right and got my skirt stuck on some piping, or the time I couldn’t park the site car properly then I didn’t look like I knew what I was doing at all and that could be detrimental to me being taken seriously.

I got the job onsite because I had a driving licence. But, my driving wasn’t very good. I’d never had a car, my parents never had a car, in fact the only experience of driving I had had up until that point was the 25 lessons to pass my test and one go in my big brother’s car which had left-hand drive so it made everything even more confusing. However, tenacious as ever, I didn’t let my lack of experience hold me back.

One time, I was trying to park the car back into it’s spot. It was a smallish parking space and it was on a hill, and there was a skip and a lorry, and another car not properly parked and if I had had more experience, I might have thought it was too small a space. As it was I just squeezed the car into the space by parking it up on the rim of another big car, and as the car was tilted really high, on top of, what I think was, a Bentley, I realised I couldn’t leave it like that. But no matter what I did, grinding the gears and what have you, I couldn’t get it back off the rim, it was just scraping along the side. I was there for ages, but then the blokes on the building site opposite came over and lifted my car off the Bentley and said that that it was the site boss’s car and he might not have been impressed with my parking. Luckily, there was no harm done and we laughed and laughed as they said that I was the luckiest person ever as neither of the cars had a scratch on them.

I don’t think I have really learnt my lesson, as I still squeeze my car into tiny spaces. Recently, I was parking in my street when an auld gadgie came over and told me that I had balls for parking in such a small space. And, I would know, he said and went on to explain that he had been a long distance lorry driver and in the army, and had driven many types of vehicles but he had in all his years never seen driving like mine. I may not be one of the lads but I have balls people, balls.

He might have changed his mind if he’d seen me the day I was driving round ICI whilst lying down. Such a bad idea, but the speed limit was low so it was ok. Eventually I picked up another student, who was shadowing me this time as I was soon to return back to my degree and he was taking over my job, and it was only after a while, he asked me why I was driving looking like a woman of ill repute. I explained that I couldn’t shift the seat up and it was the only way to reach the pedals. Between us we managed to move the an inch or two until I gave up and let him drive as he had longer legs and I was the one who got sit in the passenger seat and say ridiculous things.

Though the one time I did let a colleague drive the van it was a terrible idea. We had been monitoring the Pont sur la Versoix outside of Geneva airport. She was collecting data. I was shadowing so that I could write nice software to support my colleagues and demonstrate the thesis of my thesis. And, then on our way back, I said: Turn right here (actually I said: Tourne a droit ici) and dippy chick that she was, she drove straight into the wall (Me: Frein, frein, frein) and then turned into a nervous wreck so I had to deal with the police and then drive the bloody wrecked car back to the lab. Honestly. She was so bad at driving.

Another time, against my better judgement, we let her drive again and she ploughed into a Swiss-German couple when we were on our way to Lugano to see how the fibre optic cabling we used to monitor bridges was made. To be fair it was a bit of a windy Alpine road going up the hill. The Swiss-German couple didn’t think so, they’d driven on those roads for 30 years without having dippy chicks drive into them. Luckily, I was in the back and one of the two guys we were travelling with was Swiss-German so he sorted out the mess. That night we went to a nightclub called Desperados and went a bit bonkers, glad to still be all in one piece and with jobs after damaging yet another car.

I think that is why I liked the Zurich architects project I worked on. I got the train there and back nice and had breakfast on the way there in the lovely restaurant car and then a quatre heures apero on the way back. Sometimes I’d leap off the train at Berne and meet a friend for dinner before catching the last train back to Lausanne.

The project was again a constraints solver but this time using case-based reasoning to design apartment layout. And, every week I used to go to Zurich and talk to the architects there, and shadow them sometimes when they went round offices or on building sites. They designed very carefully following the building regulations hence the idea to use a constraint solver, and endless fascinating conversations about what is easy and hard to model in a computer. I spent many a happy hour up there listening to my main contact, a lovely woman with a passion for design, who said at the end of our time together, that she thought of me more as a friend than a shadow. It was completely mutual. I loved her. She was inspirational.

Not everyone felt the love though, the day I told everyone at ICI in the main office that I had been diagnosed with low blood pressure, my boss had a very unlikely outburst and said: Low blood pressure. That’s because you go around raising everyone elses’s. I thought up until that point that I blended in. But apparently not, I was told by another colleague when they were checking if a job had been done that the answer on the phone came, Oh yes that woman in the checked trousers sorted it. Imagine a woman in (checked – what can I say? It was the ’90s) trousers coming round fixing things. Though, I’d learnt my lesson, I wore trousers now, I was sick of showing my knickers after getting stuck on a pipe somewhere on site.

My ICI boss said to me on my leaving review that when they had been choosing where to put that year’s students, everyone else slotted into a role somewhere apart from me. I didn’t fit anywhere. But honestly, why would anyone slot anywhere? It’s a peculiar idea, which is why shadowing is so important. Everyone is different, and unique, and people carry out their jobs in their own ways, so why wouldn’t we all take time out to get to know people instead of forcing them to work in a certain way.

Not everyone agrees though, as my PhD supervisor said one time: I hate her, she comes in here with her own ideas and thoughts. I was a bit baffled as I thought that was the point of research, but you know, we are all different, and it seems I baffled him as much as he did me. Once, he asked me, as I was shaking a printer cartridge over my head and I may have gotten a teensy bit of ink on his face as he came back from the bin over which he’d been carefully shaking the other cartridges: How have you gotten through life like this? I honestly wonder how you are still alive.

Freewheeling, baby, that’s how, I didn’t say that to him, as he was already far too red in the face for any more of my unique insights that day.

See, I listen very carefully. I hear you, I see you. I know everything about you, and let me tell you, you are important and unique and contribute to this world, and it’s not just part of my job to tell you that. It’s who I am. Now go on, keep making lovely things and if I can help with some software, or to shake things up a bit, invite me round, but let me just grab my sleeping mask as I may be staying a while.

Posted on

User or Used? Human-Computer Interaction: Dialogue, Conversation, Symbiosis (3)

If you torture the data enough, it will confess to anything.
– Darrell Huff, How to Lie With Statistics (1954).

[ 1) Introduction, 2) Dialogue or Conversation, 3) User or Used, 4) Codependency or Collaboration, 5) Productive or Experiential, 6) Conclusions]

In the last blog I wrote about human dialogue with a computer versus the conversation between humans via a computer. The dialogue with a computer is heavily designed whereas human conversation especially via social media has come about serendipitously. For example, Twitter came from texting which was invented by engineers as tool to test mobile phones.

This is an example of what I call serendipitous design which works by users employing systems to do what they want it to do, which is the no-function-in-structure principle and then a designer find ways to support them. In contrast, the way to create systems which support users to do their job better uses the cardinal rule: know your user with all the various tools and techniques UX designers have borrowed from anthropology. You design with your user in mind, you manage their expectations, and you have them at the front of your mind as a major factor of the design so that the system has specific goals.

But, however hard you try, with each new system or software or form of communication, you often end up changing how people work and the dialogue is less about a field of possibilities with insight, intuition, and creativity, and more about getting people to do extra stuff on top of what they already do. And, because people are keen to get in on whatever new thing is happening they buy into what I call the myth of progress and adopt new ways of working.

[pullquote]This begs the question are we creating systems for users or the used?[/pullquote] This begs the question are we creating systems for users or the used? Today, I was chatting to a roadsweeper, he told me that last year he was driving a lorry but the council’s initiative to reduce carbon emissions means that 80 lorries were taken off the road and the drivers are now out sweeping the streets on foot. He showed me his council-issue mobile phone which tracks his every move and presumably reports back to the office his whereabouts at all times. Not that he needs it, if he sits on a wall too long, local residents will phone the council to complain that he is sitting down and not working hard enough.

Tracking is not new, smart badges, invented at Xerox PARC, were trialled in the 1990s in the early days of ubiquitious computing (ubicomp). The idea was to move computers off the desktop and embed them into our infrastructure so that we interact with them without our knowledge, freeing the user from the need to learn complex systems. In the badges’ case, everyone could be located by everyone else in the building, rather like the Harry Potter Marauder’s map. However, it smacks rather too much of surveillance, especially if your boss decides you are spending too long in the toilet or by the water cooler and, that your behaviour needs to change. The road sweeper instead of a badge has a mobile phone and people who spy on him and grass him up in part because they lack context and don’t know that he is entitled to a 20 minute break.

[pullquote]Must I really run all my important ideas past my fridge?[/pullquote] But it’s not just as part of a job, we have Google Maps recording every journey we make. And yet, ubicomp was less about having a mobile device or about surveillance, it was the forerunner to the Internet of Things, the ambient life, which is there to make things easier so the fridge talks to your online shopping to say that you need more milk. But what if I go vegan? Do I need to inform my fridge first? Must I really run all my important ideas past my fridge? This is not the semiotic relationship psychologist and mathematician J.C.R. Licklider had when he had his vision of man-computer symbiosis.

I was speaking to someone the other day who monitors their partner’s whereabouts. They think it’s useful to see where the partner is at any given time and to check that the partner is where they said they would be. No biggie, just useful. I mentioned it to another person who said that they had heard several people do the same. I wonder why am I so horrified and other people just think it’s practical.

Insidious or practical? I feel we are manipulated into patterns of behaviour which maintain the status quo.

Last week, I woke up and checked my Fitbit to see how I had slept which is slightly worrying now – I never needed anything to tell me how I slept before – and there was a new box in there: Female Health. I clicked on it. It asked me about birth control, when my next period is due, how long it lasts and so on. Intrigued, I entered the requested data. The resulting box said: Your period is due in eight days. Really? I mean, really? It was wrong even though I had tinkered with the settings. So, then it had a countdown: Your period will last four more days, three more days…etc. Wrong again. And, now it is saying: Four days to most fertile days. This is so irritating. It feels like Argos, you know, how the system and the reality of you getting something you’ve ordered never quite match up. I know together me and my Fitbit can build up data patterns. Will they be insightful? Time will tell. The bits which really concern me is that it said it wouldn’t share this information to anyone, okay… but then it added that I couldn’t share this information either. What? I am guessing that it wants me to feel safe and secure. But what if I wanted to share it? What does this mean? Menstrual cycles are still taboo? I can share my steps but not my periods? My husband and I laughed about the idea of a Fitbit flashing up a Super Fertile proceed with caution message when out on date night.

[pullquote]I regularly lie in bed pretending to be asleep to see if I can fool my fitbit[/pullquote]But, it’s not just me and my Fitbit in a symbiotic relationship is it? Someone is collecting and collating all that data. What are they going to do with that information prying into me and my Fitbit’s symbiotic space? It rather feels like someone is going to start advertising in there offering birth control alternatives and sanitary protection improvements. It feels invasive, and yet I signed up to it, me the person who thinks a lot about technology and privacy and data and oversharing. And, even now as I sit here and think about my mixed feelings about my Fitbit, the idea of wearing something on my arm which only tells me the time, and not my heart rate, nor the amount of steps I am doing, feels a bit old-fashioned – I am myself am a victim of the myth of progress. I am user and used. Confession, I regularly lie in bed pretending to be asleep to see if I can fool my Fitbit. It’s changing my behaviour all the time. I never used to lie in bed pretending to be asleep.

Back in 2006, I watched Housewife 49, it was so compelling, I bought the books. Nella Last was a housewife in Barrow-in-Furness who kept a diary along with 450 other people during and after the war. It was part of the Mass Observation project set up by an anthropologist, a poet, and a filmmaker, which sounds rather like the maker culture of HCI today. They didn’t believe the newpapers reporting of the abdication and marriage of King Edward VII, so went about collecting conversation and diary entries and observations on line. Rather like today, we have social media with endless conversation and diary entries and observations. The newspapers are scrambling to keep up and curate other peoples’ tweets because they have traditionally been the only ones who shape our society through propaganda and mass media. Now, we have citizens all over the world speaking out their version. We don’t need to wait for the newspapers.

We are living through a mass observation project of our own, a great enormous social experiment and it is a question worth asking: User or used? Who is leading this? And what is their goal? And, then we have the big companies collecting all our data like Google. And, we all know the deal, we give them our data, they give us free platforms and backups and archives. However, it doesn’t necessarily mean that they are right about the results of their research on our data, or have the right to every last piece of information to use, even if you give it freely, because there is a blurring of public and private information about me and my steps and periods and birth control.

Anthropologist Agustín Fuentes has written a thoughtful article about the misuse of terms such as biology in Google’s manifesto and consequently, the sweeping generalisations to which it comes. Fuentes says we have no way of knowing what happened before we collected data and even now as we collect data, we have to maintain our integrity and interpret it correctly by using terms and definitions accurately. Otherwise, we think that data tells the truth and stereotypes and bias and prejudices are maintained. I love the quote:

If you torture the data enough, it will confess to anything.

Information is power. Hopefully, though, there are enough anthropologists and system designers around who can stop the people who own the technology telling us what to think by saying they are having insights into our lives whilst peddling old ideas. We need to pay attention to truth and transparency before we trust so that we can have more open dialogue in the true sense of the word – an exploration of a field of possibilities – to lead to real and effective change for everyone.

Let us all be users not the used.

[Part 4]

Posted on

Human-computer interaction, cyberpsychology and core disciplines

A heat map of the multidisciplinary field of HCI @ Alan Dix

I first taught human-computer interaction (HCI) in 2001. I taught it from a viewpoint of software engineering. Then, when I taught it again, I taught it from a design point of view, which was a bit trickier, as I didn’t want to trawl through a load of general design principles which didn’t absolutely boil down to a practical set of guidelines for graphical-user interface or web design. That said, I wrote a whole generic set of design principles here: Designing Design, borrowing Herb Simon’s great title: The Science of the Artificial. Then, I revised my HCI course again and taught it from a practical set of tasks so that my students went away with a specific skill set. I blogged about it in a revised applied-just-to-web-design version blog series here: Web Design: The Science of Communication.

Last year, I attended a HCI open day Bootstrap UX. The day in itself was great and I enjoyed hearing some new research ideas until we got to one of the speakers who gave a presentation on web design, I think he did, it’s hard to say really, as all his examples came from architecture.

I have blogged about this unsatisfactory approach before. By all means use any metaphor you like, but if you cannot relate it back to practicalities then ultimately all you are giving us is a pretty talk or a bad interview question.

You have to put concise constraints around a given design problem and relate it back to the job that people do and which they have come to learn about. Waffling on about Bucky Fuller (his words – not mine) with some random quotes on nice pictures are not teaching us anything. We have a billion memes online to choose from. All you are doing is giving HCI a bad name and making it sound like marketing. Indeed, cyberpsychologist Mary Aiken, in her book The Cyber Effect, seems to think that HCI is just insidious marketing. Anyone might have been forgiven for making the same mistake listening to the web designer’s empty talk on ersatz architecture.

Cyberpsychology is a growing and interesting field but if it is populated by people like Aiken who don’t understand what HCI is, nor how artificial intelligence (AI) works then it is no surprise that The Cyber Effect reads like the Daily Mail (I will blog about the book in more detail at a later date, as there’s some useful stuff in there but too many errors). Aiken quotes Sherry Turkle’s book Alone Together, which I have blogged about here, and it makes me a little bit dubious about cyberpsychology, I am waiting for the book written by the neuroscientist with lots of brainscan pictures to tell me exactly how our brains are being changed by the Internet.

Cyberpsychology is the study of the psychological ramifications of cyborgs, AI, and virtual reality, and I was like wow, this is great, and rushed straight down to the library to get the books on it to see what was new and what I might not know. However, I was disappointed because if the people who are leading the research anthropomorphise computers and theorise about metaphors about the Internet instead of the Internet itself, then it seems that the end result will be skewed.

We are all cyberpsychologists and social psychologists, now baby. It’s what we do. We make up stories to explain how the world works. It doesn’t mean to say that the stories are accurate. We need hard facts not Daily Mail hysteria (Aiken was very proud to say she made it onto the front page of the Daily Mail with some of her comments). However, the research I have read about our behaviour online says it’s too early to say. It’s just too early to say how we are being affected and as someone who has been online since 1995 I only feel enhanced by the connections the WWW has to offer me. Don’t get me wrong, it hasn’t been all marvellous, it’s been like the rest of life, some fabulous connections, some not so.

I used to lecture psychology students alongside the software engineering students when I taught HCI in 2004 at Westminster University, and they were excited when I covered cognitive science as it was familiar to them, and actually all the cognitive science tricks make it easy to involve everyone in the lectures, and make the lectures fun, but when I made them sit in front of a computer, design and code up software as part of their assessment, they didn’t want to do it. They didn’t see the point.

This is the point: If you do not know how something works how can you possibly talk about it without resorting to confabulation and metaphor? How do you know what is and what is not possible? I may be able to drive a car but I am not a mechanic, nor would I give advice to anyone about their car nor write a book on how a car works, and if I did, I would not just think about a car as a black box, I would have to put my head under the bonnet, otherwise I would sound like I didn’t know what I was talking about. At least, I drive a car, and use a car, that is something.

If you don’t use social media, and you just study people using it, what is that then? Theory and practice are two different things, I am not saying that theory is not important, it is, but you need to support your theory, you need some experience to evaluate the theory. Practice is where it’s at. No one has ever said: Theory makes perfect. Yep, I’ve never seen that on a meme. You get a different perspective, like Jack Nicholson to his doctor Keanu Reeves says in Something’s Gotta Give: Hey! We’re not all doctors, baby. Reeves has seen things Nicholson hasn’t and Nicholson is savvy enough to know it.

So, if you don’t know the theory and you don’t engage in the practice, and you haven’t any empirical data yourself, you are giving us conjecture, fiction, a story. Reading the Wikipedia page on cyberpsychology, I see that it is full of suggested theories like the one about how Facebook causes depression. There are no constraints around the research. Were these people depressed before going on Facebook? I need more rigour. Aiken’s book is the same, which is weird since she has a lot of references, they just don’t add up to a whole theory. I have blogged before about how I was fascinated that some sociologists perceived software as masculine.

In the same series I blogged about women as objects online with the main point being, that social media reflects our society and we have a chance with technology to impact society in good ways. Aiken takes the opposite tack and says that technology encourages and propagates deviant sexual practices (her words) – some I hadn’t heard of, but for me, begs the question: If I don’t know about a specific sexual practice, deviant or otherwise, until I learn about on the Internet (Aiken’s theory), then how do I know which words to google? It is all a bit chicken and egg and doesn’t make sense. Nor does Aiken’s advice to parents which is: Do not let your girls become objects online. Women and girls have been objectified for centuries, technology does not do anything by itself, it supports people doing stuff they already do. And, like the HCI person I am, I have designed and developed technology to support people doing stuff they already do. I may sometimes inadvertently change the way people do a task when supported by technology for good or for bad, but to claim that technology is causing people to do things they do not want to do is myth making and fear mongering at its best.

The definition of HCI that I used to use in lectures at the very beginning of any course was:

HCI is a discipline concerned with the design, evaluation and implementation of interactive computing systems for human use and with the study of major phenomena surrounding them (ACM, 1992).

For me, human-computer interaction was and still remains Gestaltian: The whole is greater than the sum of the parts, by this I mean, that the collaboration of a human and a computer is more than a human typing numbers into a computer and then waiting for the solution, or indeed typing in sexually deviant search terms into a web crawler to find a tutorial. And, with the advent of social media, HCI is more than one person connecting to another, or broadcasting online, which is why the field of cyberpsychology is so intriguing.

But the very reason why I left the field of AI and went into HCI is: AI reasons in a closed world and the limits of the computational power you have available. There are limits. With HCI, that world opens up and the human gets to direct the computer to do something useful. Human to human communication supported by technology does something else altogether which is why you might want the opinion of a sociologist or a psychologist. But, you don’t want the opinion of the sociologist on AI when they don’t understand how it works and has watched a lot of sci-fi and thinks that robots are taking over the world. Robots can do many things but it takes a lot of lines of code. And, you don’t want the opinion of a cyberpsychologist who thinks that technology teaches people deviant sexual practices and encourages us all to literally pleasure ourselves to death (Aiken’s words – see what I mean about the Daily Mail?) ‘cos she read one dodgy story and linked it to a study of rats in the 1950s.

Nowadays, everyone might consider themselves to be a bit of a HCI expert and can judge the original focus of HCI which is the concept of usability: easy to learn, easy to use. Apps are a great example of this, because they are easy to learn and easy to use, mainly though because they have limited functionality, that is they focus on one small task, like getting a date, ordering a taxi, sharing a photo, or a few words.

However, as HCI professor Alan Dix says in his reflective Thirty years of HCI and also here about the future: HCI is a vast and multifaceted community, bound by the evolving concept of usability, and the integrating commitment to value human activity and experience as the primary driver in technology.

He adds that sometimes the community can get lost and says that Apple’s good usability has been sacrificed for aesthetics and users are not supported as well as they should be. Online we can look at platforms like Facebook and Twitter and see that they do not look after their users as well as they could (I have blogged about that here). But again it is not technology, it is people who have let the users down. Somewhere along the line someone made a trade-off: economics over innovation, speed over safety, or aesthetics over usability.

HCI experts are agents of change. We are hopefully designing technology to enhance human activity and experience, which is why the field of HCI keeps getting bigger and bigger and has no apparent core discipline.

It has a culture of designer-maker which is why at any given HCI conference you might see designers, hackers, techies and artists gathering together to make things. HCI has to exist between academic rigour and exciting new tech, no wonder it seems to not be easy to define. But as we create new things, we change society and have to keep debating areas such as intimacy, privacy, ownership, visibility as well as what seems pretty basic like how to keep things usable. Dix even talks about having human–data interaction, as we put more and more things online, we need to make sense of the data being generated and interact with it. There is new research being funded into trust (which I blogged about here). And Dix suggest that we could look into designing for solitude and supporting users to not respond immediately to every text, tweet, digital flag. As an aside, I have switched off all notifications, my husband just ignores his, and it just boggles my mind a bit that people can’t bring themselves to be in charge of the technology they own. Back to the car analogy, they wouldn’t have the car telling them where they should be going.

Psychology is well represented in HCI, AI is well represented in HCI too. Hopefully we can subsume cyberpsychology too, so that the next time I pick up a book on the topic, it actually makes sense, and the writer knows what goes on under the bonnet.

Technology should be serving us, not scaring us, so if writers could stop behaving like 1950s preachers who think society is going to the dogs because they view how people embrace technology in the same way they once did rocknroll and the television, we could be more objective about how we want our technological progress to unfold.

Posted on

Web design (5): Structure

A collaborative medium, a place where we all meet and read and write.
– Tim Berners-Lee

[Part 5 of 7 : 0) intro, 1) story, 2) pictures,  3) users, 4) content, 5) structure, 6) social media, 7) evaluation]

Many designers have adopted a grid structure to design web pages because a) it lends itself well to responsive design and b) it allows a design which is easy for users to understand. Designers literally have about five seconds before a user will click away to find a different service/page/content provider if the page is laid out in a way which is difficult to understand.

In a great talk for An Event Apart, Designer and Developer Advocate at Mozilla, Jen Simmons looks offline at magazines for inspiration and remembers how there was much experimentation and creativity online until everyone adopted grids and fell into a rut of grids.

But, it is easy to understand why everyone adopted grids, because users create their own understanding of a webpage from its structure. Text is complete within itself and meaning comes from its structure and language rather than the ideas it contains. This is a fundamental principle of semiotics, the study of meaning.

Managing expectations

When a webpage is judged to be useless, it is often because it does not behave in the way the user is expecting, particularly if it is not very attractive.

Designers either need to manage a user’s expectations by giving them what they are expecting in terms of the service they are looking for, or they need to make it super attractive.  Attractive things don’t necessarily work better but we humans perceive them as doing so  because they light up the brain’s reward centre and make us feel better when we are around them. We are attracted to attractive things which is given by certain Gestalt principles such as unity, symmetry, and the golden ratio.

Gestalt: similarity, promixity

Good design is one thing, but we also have specific expectations about  any given webpage. We scan for headings and white space and interpret a page in those terms.  This is because according to Gestalt theory we will interpret items according to their proximity: items which are close together, we will group together; or similarity, items which are similar we interpret as together.

And also, because we have been to others sites and we transfer our experiences from one site to another and anticipate where certain functions should be.

Where am I? Where have I been? Where am I going?

Main menus are usually at the top of the page, grouped together and are used for navigation through the site.  Secondary navigation may take place in drop down menus, or in  left or right hand columns. Specific house keeping information can be found in the footer, or the common links bar if there is one.

If users are completely lost they will use the breadcrumbs, which Google now uses instead of the URL of sites as part of the results their search engine serves up. Therefore, it is in a designer’s interest to put breadcrumbs on the top of page.

Users will stay longer and feel better if they can answer the three questions of navigation as articulated by usability consultant Steve Krug:

  1. Where am I?
  2. Where have I been?
  3. Where am I going?

Often this answered by changing links to visited, not visited and enforcing the consistency of the design by adopting a sensible approach to colour. There is a theory of colour in terms of adding and subtracting colour to create colour either digitally, or on a palette, but there is alas, no theory about how to use colour to influence branding and marketing, as personal preferences are impossible to standardise.

HTML 5 & CSS 3

As discussed earlier in part 1 of this series, we separate out our content from our presentation which is styled using CSS 3. Then, once we know what we want to say we use HTML 5 to structure our text to give it meaning to the reader. This may be a screen reader or it may be a human being.

HTML 5 breaks a page into its header and body, and then the body is broken down further into specific instructions. Headings from <h1> to <h6>, paragraphs, lists, sections and paragraphs, etc., so that we can structure a nice layout.  There are thousands of tutorials online which teach HTML 5.

The nice thing about sections is that we can use them to source linked data from elsewhere and fill our pages that way, but still keep a consistent appearance.

Theoretically one page is great, or a couple of pages fine, but once we get into hundreds of pages, we need to think about how we present everything consistently and evenly across a site and still provide users the information for which they came.

Information architecture

Information architecture (IA) is the way to organise the structure of a whole website. It asks: How you categorise and structure information? How do you label it so that users can navigate or search through it in order to find what they need?

The first step is to perform some knowledge elicitation of the  business or context and what everyone (owners, customers) known as stakeholders expect from the proposed system. This may include reading all the official documentation a business has (yawn!).

If there is a lot of existing information the best way to organise it is to perform a card sort. A card sort is when a consultant calls in some users, gives them a stack of index cards with content subjects written on them, along with a list of headings from the client’s site—“Business and News,” “Lifestyle,” “Society and Culture”— then users decide where to put “How to floss your teeth”.

This can take a few days each time and a few goes, until a pattern is found, us humans love to impose order on chaos, we love to find a pattern to shape and understand our world.

Once we have a structure from the card sort, it becomes easier to start designing the structure across the site and we begin with the site map.

The site map reflects the hierarchy of a system (even though Tim Berners-Lee was quite emphatic that the web should not have a hierarchical structure).

Then, once a site map is in place, each page layout can be addressed and the way users will navigate. Thus, we get main menus (global navigation), local navigation, content types to put in sections and paragraphs, etc., along with the functional elements needs to interact with users.

Other tools created at this time to facilitate the structure are wireframes, or annotated page layouts, because if is is a big site lots of people may be working on it and clear tools for communication are needed so that the site structure remains consistent.

Mock up screen shots and paper prototypes may be created and sometimes in the case of talented visual designers, storyboards are created. Storyboards are sketches showing how a user could interact with a system, sometimes they take a task-base approach, so that users could complete a common task.

Depending on the size of a project, information architects will work with content strategists who will have asked all the questions in the last section (part 4) on content and/or usability consultants who will have spoken to lots of users (part 3) to get an understanding of their experiences, above and beyond their understanding of the labelling of information in order to answer questions such as:

  • Does the website have great usability which is measured by being: effective and efficient; easy to learn and remember; useful and safe?
  • How do we guide users to our key themes, messages, and recommended topics?
  • Is the content working hard enough for our users?

Sometimes, it may just be one person who does all of these roles and is responsible for answering all of these questions.

It takes time to create great structure, often it takes several iterations of these these steps, until it is time to go on to the next stage (part 6) to start sharing this beautiful content on social media.

[Part 6]

Posted on

Web design (7): Evaluation

desktopetc

A collaborative medium, a place where we all meet and read and write.
– Tim Berners-Lee

[Part 7 of 7 : 0) intro, 1) story, 2) pictures,  3) users, 4) content, 5) structure, 6) social media, 7) evaluation]

Even though evaluation is the final part of this series, it should not be left to the end of any software project. Ideally, evaluation should be used throughout the life cycle of a project in order to assess the design and user experience, and to test system functionality and whether it meets user requirements without creating unexpected results or confusion.

Expert analysis

Expert (or Theoretical) analysis uses a detailed description of the design, which doesn’t have to be implemented. This creates a model of the user’s activity and then analysis is performed on that model.

It is one way of assessing whether a design has good usability principles. It cannot guarantee anything but can hopefully flag up any design flaws before time and money gets spent on implementation.

Expert analysis is best used during the design phase and experts can assess systems using:

Heuristics which are rules of thumb and not true usability guidelines. Usability expert Jakob Nielson developed 10 usability heuristics in 1995 and they are still widely used and quoted today.  Design consultant, Ari Weissman says that heuristics are better than no testing at all, but to say that they can replace getting to know your users and understanding them just silly. Researchers at the University of Nebraska found that heuristic evaluation and user testing complement each other and are both needed.

Review-based evaluation uses principles from experimental psychology and human-computer interaction (HCI) literature to provide evaluation criteria such as menu design, command names, icons and memory attributes to support/refute design decisions. Reviews may even use style guidelines provided by big companies such as Microsoft and Apple.

Model-based evaluation uses a model to evaluate software. This model might be taken from HCI literature such as Stuart Card’s GOMS and Ben Shneiderman’s Eight golden rules of dialog design.

Cognitive walkthroughs are step-by-step inspections which concentrate on what the user is thinking whilst learning to use the system. Alas, it is the analysts who act as the user and try to imitate what the user is thinking. Walkthroughs can be used to help develop user personas.

However, the main criticism is that novice users are often forgotten about because analysts have lots of experience and their pretending to be users can introduce all sorts of bias into your system. The advantages of this approach is that areas which are unclear in the system design can be easily flagged up and fixed cheaply and earlier on in the life cycle.

Using your user: user testing

The most informative types of evaluation always take place with the user. This can happen in the laboratory or in the field. In the laboratory, usability consultants have a script, such as this one by usability expert Steve Krug. The usability consultant asks the user to either do whatever they are drawn to do, or to perform a specific task,such as buying a product on the site, whilst talking aloud. This thinking aloud protocol not only identifies what the problem is, but also why. The best thing about usability testing is that clients can hear a user saying something which may be obvious to the consultant but not to the client and which the client might not believe if the consultant just told them. Co-operative evaluation is a very similar technique to usability testing.

Outside the laboratory, you can follow the user about and shadow them in the workplace, to see how the user interacts with your software, or the current software that your new software will hopefully improve upon. This is ethnography and a way of learning about the context in which your users work. It can be very expensive and time consuming to hire ethnographers to go into users’ workplaces.

A cheap and cheerful way of reproducing this shadowing is to get the users to keep a diary or blog, known as a cultural probe.  They are quick and easy to put together using open-ended questions which encourage users to say all the things they might not say during a testing session.

Empirical evaluation

Another relatively cheap and cheerful method is to get your user group to fill out a questionnaire or a survey in order to get their feedback.

The questionnaire needs to be designed very carefully, following these instructions, otherwise you can end up with a lot of information, but nothing tangible. The main advantage is that you get your users opinions and you can measure user satisfaction quite easily.

The disadvantage is it that is hard to capture certain types of information in a questionnaire such as the frequency of a system error, or the time taken to complete a task.

Logging

Computers can collect statistics of use, to tackle the sorts of questions like time taken and frequency of system errors.  Web stats are a great way of seeing this sort of information as well as which pages are the most attractive and most useful to users.  Eye-tracking software and click captures are also useful ways of collecting data. However, care needs to be taken not to introduce any bias in the interpretation of this data.

Informal evaluation

Informal evaluation methods can be useful, in the design stage for example, but are better suited in the context of performing research as they do not always yield usable results which can be used to guide design.

Focus groups: This is when you get a group of users together and they discuss subjects led by a moderator. Focus groups can be useful. However, they can lead to users telling you what they think they want, rather than what they need. As this 2002 paper asks: Are focus groups a wealth of information or a waste of resources?

Controlled experiments test a hypothesis like this great example: College students (population) type (task) faster (measurement) using iPad’s keyboard (feature) than using Kindle’s keyboard, by identifying independent and dependent variables that you can collect data on after testing in a simulation of real world situations such as in a college where iPads and Kindles are used.

No matter how great your website or software system is, it can always be improved by some method of evaluation. There are many methods involving users and experts to make your system as good as it can be throughout the whole lifecycle of your website or your software. Evaluation is the only way to identify and correct those design flaws.