WEBVTT 00:00:03.200 --> 00:00:07.088 One of the things that can be quite hard to remember during design 00:00:07.088 --> 00:00:10.527 is to keep in mind that you're in a bigger context. 00:00:15.520 --> 00:00:20.800 It's easy to get focused on the device you're  designing for or a particular screen. 00:00:20.800 --> 00:00:24.435 This isn't helped by the tools you use. 00:00:24.845 --> 00:00:30.520 Typically, when somebody presents a design, what you see nowadays for a digital design, 00:00:30.520 --> 00:00:35.988 whether it's for a phone-based application or web-based application, is a wireframe. 00:00:35.988 --> 00:00:39.793 And there are so many tools that help you generate these. 00:00:39.793 --> 00:00:44.778 But of course, what that does is it focuses you on the screen, on the page, 00:00:44.778 --> 00:00:49.260 not on the wider context in which it's based. 00:00:49.260 --> 00:00:55.579 So, how can you try and focus on this? There's a lot more things in this context than the screen. 00:00:55.579 --> 00:00:58.578 There's the things that happened before. 00:00:58.578 --> 00:01:03.092 So, if you recall the scenario of Betty in the warehouse, 00:01:03.092 --> 00:01:08.811 the consignment arrived late; she'd had a bad night. 00:01:08.811 --> 00:01:14.287 These all contribute to the context the person's in; so, all the things that have happened in the past. 00:01:14.287 --> 00:01:19.653 And there's other people around. There's Betty's children, particularly the child who woke in the night. 00:01:19.653 --> 00:01:23.763 There's Tony, who works in the warehouse as well, who noticed there was a problem. 00:01:23.763 --> 00:01:26.949 Emma, who's on the night shift, who prepared the 00:01:26.949 --> 00:01:30.000 crib sheets. So, a lot of other people around 00:01:30.000 --> 00:01:32.772 – some of those are about interactions that are  happening at the moment; 00:01:32.772 --> 00:01:36.335 some of those connected past events. Some of those might influence it. 00:01:36.335 --> 00:01:38.960 For instance, the boss or the client, 00:01:38.960 --> 00:01:43.280 perhaps Betty has to engage with other people; if there's a problem with a consignment, 00:01:43.280 --> 00:01:47.899 perhaps the delivery folks who provided it. 00:01:47.899 --> 00:01:51.122 So, there's lots and lots of people involved as well. 00:01:52.400 --> 00:01:59.002 The body – we are physically-embodied people;  we're not sort of eyes and fingers 00:01:59.002 --> 00:02:02.236 to use a computer system; we're a whole person. 00:02:02.236 --> 00:02:07.714 So, again, recall that Betty is supporting this gear thing 00:02:07.714 --> 00:02:12.362 on a balance between her hip and a slightly weak hand. 00:02:12.680 --> 00:02:17.103 That does suggest, even without going... you can probably picture this, 00:02:17.103 --> 00:02:20.983 somehow or other there's a computer screen, but without anywhere to put things out. 00:02:20.983 --> 00:02:24.372 So, perhaps there are other... understanding a body 00:02:24.372 --> 00:02:27.799 might suggest ways you redesign the space. 00:02:27.799 --> 00:02:33.331 But clearly, there's issues about the body of the person involved, which influences things. 00:02:33.331 --> 00:02:38.221 Does somebody have to stretch a long way? That can make you think about things. 00:02:38.221 --> 00:02:42.775 There's the physical environment as well. So, it was interesting. Betty had to 00:02:42.775 --> 00:02:45.510 take the gear thing and bring it to the computer. 00:02:45.510 --> 00:02:48.740 There were distances involved, and a warehouse is a big place. 00:02:48.740 --> 00:02:53.119 If you're designing an office system, then you might not have to think about great distances. 00:02:53.119 --> 00:02:57.177 But in a warehouse or an outside task there might be big distances involved. 00:02:57.177 --> 00:02:59.739 Does somebody have to carry things like the way that Betty did? 00:02:59.739 --> 00:03:03.216 Would it be better then, once you start  thinking about that, 00:03:03.216 --> 00:03:07.667 to have some sort of system where she might have something handheld to take to the part? 00:03:07.667 --> 00:03:13.001 Not necessarily all of the system, but they might be doing just  something enabling them to scan what the part was 00:03:13.001 --> 00:03:16.798 and then go back and have a look  at things, rather than have to carry it over. 00:03:16.798 --> 00:03:19.469 Is it noisy or quiet? Is it hot or cold? 00:03:19.469 --> 00:03:23.440 I mean, I'm guessing a warehouse might be on the chilly side, 00:03:23.440 --> 00:03:26.109 but then there's lots of people and lots of activities, so maybe not. 00:03:26.109 --> 00:03:29.421 Maybe – thinking of the body, maybe it gets hot. 00:03:29.421 --> 00:03:33.621 And certainly it could be quite a noisy environment with forklift trucks around. 00:03:33.621 --> 00:03:38.833 So, again, you might think "Oh, we'll have a hands-free system and make it voice-operated." 00:03:38.833 --> 00:03:44.364 But that's not going to work if there's a forklift truck driving behind the back of you in the middle of trying to do the interaction. 00:03:44.412 --> 00:03:47.953 So, you have to keep this in mind, the whole  context. 00:03:47.953 --> 00:03:52.125 Otherwise, the system you design that might look great in a wireframe 00:03:52.125 --> 00:03:55.376 doesn't actually contribute and fit into the bigger picture.