Transcripción
Extracto de la transcripción automática del vídeo realizada por YouTube.
alright so you're in the session on design validation AKA how to psy class that's what's printed in a schedule and it's it's actually kind of a working title so i think meaningful design feedback is more that approach i'm going for
but anyway so you're here because you're interested in collecting designed feedback and maybe using it for your site and you know just ensuring it happens in some form so in this session will define what design feedback is and how do you collect it
how to use it that sort of thing and also i just like to thank these people they really helped with my session i did a lot of like chatting with them and on the other thing I did is I did I run through my session and they had some great feedback and I'm
big fan of feedback I asked them to focus on the content and the flow and because i don't get terribly excited by fonts so the great feedback okay so my name is Lisa Rex I'm a user experience researcher Murdoch whea formerly a sort of design editor
I've done front end I've done some site through polite building I thought was also a genealogy researcher which has been a kind of interesting juxtaposition with my current role but some of my biggest failures in my design career husband because I
didn't get the right design feedback the story that springs to mind is my first sort of like web design role I was tasked with building the internet and it's hard and so my friend and I we kind of got together and we we ran down to the kitchen we made
toast and we you know we're all excited and we we built the whole thing and then you know we showed it to people and we kind of missed the mark on content and visuals and yeah and the whole thing was scrapped so good lesson there so this is the design
team at aquia and we're definitely focused on products things like Acquia cloud aqua network commons spark drupal gardens and you know our process this this is the story basically of our process and it's definitely our process as a work in progress
but we're like we're growing we're learning we're adapting and it's actually really quite fun so these are you X interaction designers there their focus is largely on sort of the visual and the interactive part of things there they do a
lot of the design briefs and style guides and then they also do like the visuals and the prototypes and that's everything from you know wireframes to clickable prototypes so where we have lots of approaches to the way we do things and that's and we
just decide based on the needs of the project in timelines and then there's the UX research team and there's three of us at the moment we are doing the research planning and conducting the studies we do a lot of like sort of more basic studies like
kind of like click test if that seems appropriate and you know where we're actually talking a lot with our customer facing teams so support the account technical account managers so I mean this comes together with our feedback processes pretty pretty broad
we are mostly focused on the qualitative and not the quantitative so it's great to like use google analytics or clicktale or anything like that to see where people are clicking but it doesn't tell you the why of things so that's why we're more
focused on actually talking to people directly so design feedback is anything from you know written emails to tweets but actually we'd prefer like you know actual conversations with you know our stakeholders and users and potential users so yeah everything
from gut reactions to really planned studies the reason for this is that we you know we recognize that we are not necessarily our users and and that's the same for everybody you know you can't know what your users need until you talk to them so lots
of things you can learn from feedback one of the things i find really useful is the figure out the actual needs of your users so your brand new user he comes to your site things might be a little difficult to figure out but you know maybe over time it's
learnable the next time you come to see is like whizzing through great and then we have the power users usually comes along and she's been using your site or your product for a long time and you know she doesn't need all this kind of like introductory
stuff so it's working out like how their needs vary this is kind of a fun example from it's the drupal.org admin it's the user permissions page so it's not public facing but I think it's fun because most people don't get to see it you
know obviously what works for like a few doesn't always work doesn't scale so that's what i mean by scalability i mean like in the UI you see this a lot on forums and other social sites occasionally but as you probably know that devel- all will
let you like generate like reams of content and stuff of it into your theme and make sure nothing breaks so no it's and comments and users the other thing that you can learn is just whether your content is actually working this is a big deal that's
the main reason people are coming to your to your site or coming to your project you know just figuring out like what's the right amount and what they need is is the messaging right or they you know is the tone working for them you know maybe there I don't
know maybe it's like you're talking down to them or you know there's all kinds of things you can learn and then the other thing is sort of like the UI text so that's things like on your forms and you know just labeling can be confusing unless
you check with people so um I approached this talk like I did like I would a research project and I so I talked to nine different people seven of them were actual designers from around the Drupal community in and add aquia and I also talked to two product
managers because I thought they would have an interesting take on things so yeah I did interviews with them I look for some common themes so here's here's well first first um some quote from my colleague who's just super smart and he points out
that you know feedback is like sort of difference between design and art so with that in mind I was like yep okay so common themes for my interviews with these people number one is that design feedback is absolutely essential and what's interesting is
not all of them started off thinking that way you know when they're in your in your career as a designer you might think you got it all figured out but one of the one of them said like you know it's often as I think I'm right I'm usually not
so it happens and then the kind of the main reason that feedback is essential is that it just saves time like the faster you can like uncover problems before you start getting other people involved like you know making putting stuff into code the better talk
talk is cheap it's not always what they say it's what they do so this major airline that you decided that they would survey customers to find a few know the passengers to find out how they could improve their long-haul flights and in a survey one of
the questions was what sort of snack would you like amid flight and the overwhelming response was fruit so the researchers thought well let's ask the flight attendants so they did and the flight attendants were like no no no no no they want cookies warm
cookies so the researchers thought about this and they think I think they realize that their passengers were saying saying that they wanted fruit but they're probably at home surrounded by family thinking about being healthy and you know safe and it just
it was interesting like how you want to be able to observe your users not just ask them so the other thing that we learned from these talks is that during design feedback sessions people don't know quite how to behave they don't know what to say they
say too much so I'll talk about how we can deal with that okay so you may be familiar with this meme people see inspirational photos of like you know baking projects that professionals have done on pinterest it turns out it's harder than it looks so
people tend to think themselves a designer and you know turns out it's really quite hard so if you're gathering feedback with people just a little tip on raining in the designer and everybody there's there's a few reasons like it's wonderful
that they have ideas and I definitely take them all down but at the same time you know they probably don't have all the information they need such as like if there's been some existing research or design patterns or anything like that the other thing
[ ... ]
Nota: se han omitido las otras 4.246 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.