WEBVTT

00:00:00.000 --> 00:00:30.520
One of the things that can be quite hard to remember during design
is to keep in mind that you're in a bigger context.
It's easy to get focused on the device you're  designing for or a particular screen.
This isn't helped by the tools you use.
Typically, when somebody presents a design, what you see nowadays for a digital design,

00:00:30.520 --> 00:01:03.092
whether it's for a phone-based application or web-based application, is a wireframe.
And there are so many tools that help you generate these.
But of course, what that does is it focuses you on the screen, on the page,
not on the wider context in which it's based.
So, how can you try and focus on this? There's a lot more things in this context than the screen.
There's the things that happened before.
So, if you recall the scenario of Betty in the warehouse,

00:01:03.092 --> 00:01:30.000
the consignment arrived late; she'd had a bad night.
These all contribute to the context the person's in; so, all the things that have happened in the past.
And there's other people around. There's Betty's children, particularly the child who woke in the night.
There's Tony, who works in the warehouse as well, who noticed there was a problem.
Emma, who's on the night shift, who prepared the
crib sheets. So, a lot of other people around

00:01:30.000 --> 00:02:02.236
– some of those are about interactions that are  happening at the moment;
some of those connected past events. Some of those might influence it.
For instance, the boss or the client,
perhaps Betty has to engage with other people; if there's a problem with a consignment,
perhaps the delivery folks who provided it.
So, there's lots and lots of people involved as well.
The body – we are physically-embodied people;  we're not sort of eyes and fingers
to use a computer system; we're a whole person.

00:02:02.236 --> 00:02:33.331
So, again, recall that Betty is supporting this gear thing
on a balance between her hip and a slightly weak hand.
That does suggest, even without going... you can probably picture this,
somehow or other there's a computer screen, but without anywhere to put things out.
So, perhaps there are other... understanding a body
might suggest ways you redesign the space.
But clearly, there's issues about the body of the person involved, which influences things.

00:02:33.331 --> 00:03:03.216
Does somebody have to stretch a long way? That can make you think about things.
There's the physical environment as well. So, it was interesting. Betty had to
take the gear thing and bring it to the computer.
There were distances involved, and a warehouse is a big place.
If you're designing an office system, then you might not have to think about great distances.
But in a warehouse or an outside task there might be big distances involved.
Does somebody have to carry things like the way that Betty did?
Would it be better then, once you start  thinking about that,

00:03:03.216 --> 00:03:33.621
to have some sort of system where she might have something handheld to take to the part?
Not necessarily all of the system, but they might be doing just  something enabling them to scan what the part was
and then go back and have a look  at things, rather than have to carry it over.
Is it noisy or quiet? Is it hot or cold?
I mean, I'm guessing a warehouse might be on the chilly side,
but then there's lots of people and lots of activities, so maybe not.
Maybe – thinking of the body, maybe it gets hot.
And certainly it could be quite a noisy environment with forklift trucks around.

00:03:33.621 --> 00:03:55.376
So, again, you might think "Oh, we'll have a hands-free system and make it voice-operated."
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.
So, you have to keep this in mind, the whole  context.
Otherwise, the system you design that might look great in a wireframe
doesn't actually contribute and fit into the bigger picture.