<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Gaia Riva on Medium]]></title>
        <description><![CDATA[Stories by Gaia Riva on Medium]]></description>
        <link>https://medium.com/@g.n.riva?source=rss-b9196e202e9a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NZ2jskbuKH65-eKdyGdJ1g.jpeg</url>
            <title>Stories by Gaia Riva on Medium</title>
            <link>https://medium.com/@g.n.riva?source=rss-b9196e202e9a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:24:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@g.n.riva/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why user-centred design is not the same as blindly listening to users]]></title>
            <link>https://uxdesign.cc/why-user-centred-design-is-not-the-same-blindly-listening-to-users-with-comic-75918109feca?source=rss-b9196e202e9a------2</link>
            <guid isPermaLink="false">https://medium.com/p/75918109feca</guid>
            <category><![CDATA[comics]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Gaia Riva]]></dc:creator>
            <pubDate>Wed, 08 Jul 2020 15:29:08 GMT</pubDate>
            <atom:updated>2020-07-23T13:27:09.973Z</atom:updated>
            <content:encoded><![CDATA[<p>“People need to understand that if we listen to every user out there we’ll end up with a Frankenstein product” — that’s what I was told a while back by a senior stakeholder.</p><p>It made me think. Do we still have people that work like this in 2020? Are there secret pockets of underground groups that go around blindly listening to what everyone says and then works on that basis? Is this what people think when they hear that they need to be user-centred culture?!(The <a href="https://www.gov.uk/service-manual/design/making-your-service-more-inclusive">Gov site </a>explains this better than I ever could).</p><p>Just in case there are people out there that do think that user-centred = listen to anyone’s opinion, then let me explain.</p><h3>What user research actually looks like</h3><p>So let’s start with the basics. User Research is NOT blindly listening to everything that users tell us. Here is the (very simplified) reality of how user research actually works.</p><figure><img alt="Comic of a researcher gathering users needs for a car and designing something based on input and business requirements" src="https://cdn-images-1.medium.com/max/1024/1*ra9WcEzEnoVKBpSwNb7EAA.png" /></figure><p>As you can see we didn’t build a car with wings + strong + fast + electric blindly following what ALL users are telling us. What we did instead is to review the ideas raised by users, discarding the ones that don’t apply to our business vision or limitation of technology etc…</p><p>My comic is simplistic I know — research is not just asking questions to people, we don’t simply report verbatim what users tell us and we don’t go from research to production without getting the users involved again but let’s just keep things very simple for now.</p><h3>When “people” aren’t even users</h3><p>I just wanted to include another quick clarification — members of staff are not users so don’t treat their feedback as if they were.</p><p>Staff knows too much. They know about your mission, they know the target, they know your challenges, they have their own agenda, etc…</p><p>Same goes for family and friends.</p><p>Here is an example from an experience that we had with a client years ago. We had done a site redesign for an Membership based professional body — the type of organisation that you might be a part of if you work in a particular sector. We received feedback from the acting-CEO — “the homepage is boring, even my wife says so”. Now there are many problems with this statement — first of all the wife in question is not part of this organisation so she will probably find the whole site and content pretty boring not just the homepage. Because she is not the user.</p><p>The other problem is that the acting CEO fully understands what his organisation does so seeing an explanation of what the organisation does every time he lands on the homepage is boring to him. What he is not taking into account here is that homepage of websites like these are visited by “new users” people who have no idea what the organisation does, if it’s for them and what they would get out of it. So if I know nothing about your organisation and when I see your site I see the news about your change in management and your annual gala I will still be just as confused about what you do and I might even give up there and then. “Old users” on the other hand, so people that are already members on the other hand don’t even see the homepage — they go straight to the information about the membership, classes, CPD points etc…</p><p>I would encourage anyone to spend some time thinking about what their work is based on and where that information come from. Was it from people around the office that have seen our new prototype? Was it solely based on the senior stakeholder opinions? If it is then think again and make sure that you get real users voices into your work and invest on having that research done upfront by a professional.</p><h3>Yes, but I already know that users want an electric car</h3><p>I am the first one to agree that designing a product is not<strong> just </strong>listening to the users, it involves common sense or a new technology developed that we just know users will love.</p><blockquote>But here is the thing: you can base your whole work on an assumption or you can verify that assumption before putting in the work.</blockquote><p>I have seen businesses in various sectors, different sizes, private and NFP all make the same mistake. Work towards a solution having no foundations as to whether their assumptions are actually right. Now that costs a lot. It costs resources, money, time and it can really affect morale too.</p><p>When you pay attention you can see it all around you. Companies that think that women will LOVE this product if we just make it available in pink and purple. We KNOW that women love pink and purple. Or we KNOW that users will read this pop-up message that explains the page to them, we don’t need to change the design. Or this icon is so OBVIOUS everyone will get it. Or make it red and flashing that will grab people’s attention.</p><p>Other times the assumption IS correct but it’s just not that important for users and our real opportunity as a business was somewhere else and we are missing it.</p><p>So I hope that I have clarified the difference between research and blindly listening to the users and more importantly made a case for why skipping user insight is a risky gamble.</p><p>If you want to hear more about I help business getting real user input into their work, <a href="https://www.linkedin.com/in/gaia-riva/">let’s talk</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75918109feca" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/why-user-centred-design-is-not-the-same-blindly-listening-to-users-with-comic-75918109feca">Why user-centred design is not the same as blindly listening to users</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Importance of user input— the basics (in comic format)]]></title>
            <link>https://medium.com/@g.n.riva/importance-of-user-input-the-basics-in-comic-format-a914698e1e16?source=rss-b9196e202e9a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a914698e1e16</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-sprint]]></category>
            <category><![CDATA[comics]]></category>
            <category><![CDATA[usability-testing]]></category>
            <dc:creator><![CDATA[Gaia Riva]]></dc:creator>
            <pubDate>Wed, 19 Feb 2020 16:39:45 GMT</pubDate>
            <atom:updated>2020-02-19T16:39:45.451Z</atom:updated>
            <content:encoded><![CDATA[<h3>When to get user input— the basics (in comic format)</h3><h4>Have you ever wondered how user insight should fit into defining solutions to our user problems? Well today is your lucky day!</h4><p>Let’s go through the steps for producing user-centred design work one step at the time for a VERY fictitious case scenario. We want people to change light bulbs so we start by asking:</p><blockquote><em>Why aren’t people changing lightbulbs?</em></blockquote><h3>Research</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fNdv07FwSMd1y6EWupYy0A.jpeg" /></figure><p>We start with user insight so that we can develop an idea that is actually helpful for our users.</p><blockquote>After all a great product that doesn’t solve a need is not a great product</blockquote><p>Research can take many forms: depth interviews, diary studies, surveys. Sometimes we collect meaningful stories (qualitative research), sometimes we collect numbers (quantitative research). Sometimes we do research ourselves (internal) or sometimes other people have already done it (external).</p><h3>Solution definition</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qVlXRaBNL67iBl36i2FwBw.jpeg" /></figure><p>Once we have done our research and we have insight into our users problems and opportunities we can start to think about solutions for those. In a lot of companies these days this generally happens in a <a href="https://www.thesprintbook.com/how">sprint format</a>. A sprint is a way to come up and test ideas within a week so that by Friday we can validate whether our solution actually helps our users — we call this value testing.</p><h3>Value testing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pR6UnbeFc9u2WWiDuiXJeg.jpeg" /></figure><p>So we have gathered information about our users and we have an idea of the solution that we decided on. At this point we only have a vague representation of our idea — it can be a prototype a design or even some drawings on a piece of paper. The whole idea is to test the concept fast and cheaply.</p><blockquote>What we are testing at this point is: would something like this help our users in achieving X?</blockquote><p>If the answer is “No”, we try again and the best part is that we didn’t waste much time on it. If the answer is “Yes” then we move onto usability testing.</p><h3>Usability testing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zQ7m4WW9Sk2T6TtaCK30Hg.jpeg" /></figure><p>At this point we know that our idea would be valuable to users now it’s al about designing the best version of it. This is when we go into the details of the solution: is the button obvious, is the wording right, is the journey clear.</p><p>As you can tell it is <strong>very important</strong> to not skip or reverse these 2 steps. We don’t want to be looking at buttons and wordings before we are sure that our idea will actually help users. This would mean wasted time and effort but it will also lead to retrofitting a benefit to the users for something that we have already designed (instead of the other way around).</p><p>Once we have this perfected and we feel confident we move into building it. At this point we also want to define what success looks like: this can be a number we want to reach or a qualitative measure — more likely than not it’s a combination of both.</p><h3>Monitor and Reviewing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DmALy2wvm3Zcd5XxQjMlNA.jpeg" /></figure><p>You would think that by the time we launch our idea it is bound to be a success. The reality is that we always need to monitor how we are doing and not assume that everything we launch is right the first time around. <a href="https://global.g.cookpad.com/pages/Monitoring/">Monitoring</a> performance allows us to make tweaks and amends based on how users are using our feature so that we can make it better and better. And if the feature doesn’t perform like we were hoping then we should rethink it altogether or remove it.</p><p>Of course there are edge cases and exceptions to the rule but I hope that this quick overview shows how important user insight is into designing something that really works for our users!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a914698e1e16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we streamlined our processes]]></title>
            <link>https://medium.com/@g.n.riva/how-we-streamlined-our-processes-779d7deedd2b?source=rss-b9196e202e9a------2</link>
            <guid isPermaLink="false">https://medium.com/p/779d7deedd2b</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[lean]]></category>
            <dc:creator><![CDATA[Gaia Riva]]></dc:creator>
            <pubDate>Thu, 07 Feb 2019 12:18:59 GMT</pubDate>
            <atom:updated>2019-02-07T12:18:59.416Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b9W6I0XydG7zo-6F" /><figcaption>Photo by <a href="https://unsplash.com/@fancycrave?utm_source=medium&amp;utm_medium=referral">Fancycrave</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A couple of months ago, our MD Claire Moyne asked Mike Dunn and I to review our internal process with the aim of streamlining them to increase efficiency and productivity. You might think that sounds boring, but I was thrilled! I’ve been itching to get my teeth stuck into this and was excited to get started.</p><p>First things first, we named the project: “<a href="https://en.wikipedia.org/wiki/Lean_thinking">Lean</a> Edo”.</p><p>The purpose of the project was: to improve our reporting and reduce the amount of manual tasks.</p><p>We started off by interviewing key people within the organisations and ask them simple questions:</p><ul><li>What data do you need?</li><li>Why and what is it used for?</li></ul><p>Notice that we didn’t ask about existing systems/spreadsheets or the challenges they create. We purposely left the way things are are out of the equation so we could understand the need.</p><p>To illustrate existing inefficiencies, we mapped out current internal processes and the results were more shocking than I expected. We’d been using great products — Salesforce, Harvest, Basecamp — paying good money for them but not utilising their full potential. This resulted in us creating alternative manual documents (namely spreadsheets!) to cover the reporting that we didn’t know how to do automatically. We were also creating processes for the sake of it and doing nothing with the data.</p><p>For example, we uncovered that we’d been exporting all our new project details from Salesforce into a spreadsheet. <strong>Yes you read that right.</strong> We had automated data in a lovely CRM and we had been exporting it into a spreadsheet, involving manual work and the added risk this unnecessary step entails for years. And no, it was not an automated export either. Do you think that is crazy? Me too, but I really encourage you to think about some of the tasks that you do every day and you take for granted, and I bet that you can find a similar story to tell. If you don’t let’s go for a coffee, I want to talk to you!</p><p>Having created a clear map of the way things were, all we needed to do was unpick things one by one and identify recommendations. To give you a flavour, here are some actions that we identified:</p><ul><li>Bring our won work into Salesforce and ditch the spreadsheet</li><li>Agree all tasks for people to log their timesheets consistently</li><li>Look at integrations between Salesforce and Xero to automate the creation of invoices</li><li>Create a Salesforce account for every consultant and ensure they are trained and confident in how to use it.</li></ul><p>However the <strong>key recommendation</strong> was a shift in culture to ensure that we don’t end up in this mess all over again.</p><p>Processes should be evolutionary but we had failed in taking the time to review them to ensure they are always as efficient and streamlined as possible, and instead accepted them as they were. For years we had been creating a multitude of spreadsheets rather than stopping and thinking about the best way to save, report on and use the data.</p><p>This approach meant that we ended up with the need to dedicate a chunk of time and energy to reviewing years of this tangled mess, instead of having people organising, reviewing and reiterating small parts of each process regularly over time.</p><p>We also noticed there was a sense of fear around our systems with an attitude of <em>“I-am-not-technical-enough” </em>holding people back. All the systems we use have pretty straight forward UIs and are built for people like you and me. What was highlighted was that dedicated time was needed during the onboarding process to get new starters confident and adept at using these systems instead of finding their own way, or creating their own anthology of spreadsheets.</p><p>Of course cultural change takes time, but already we’ve started to observe people around the whole organisation saying to each other <em>“Do we really need that spreadsheet?!”</em> or <em>“Could it not be done in Salesforce?”</em> which is a <strong>huge</strong> step forward.</p><p>So, do you want to be more lean in your way working? Here is my suggested approach:</p><ol><li>Start by asking what reporting you need</li><li>Map out your current ways of working and show the hours spent on this</li><li>Identify pain points, time wasters and added risks</li><li>Make a list of recommendations to address those pain points</li><li>Train your organisation on how to avoid being in the same mess in the future</li></ol><p><em>If you’re interested in exploring in more depth ways in which organisations work, I encourage you to join me and Mike for the monthly </em><a href="https://www.meetup.com/ReinventingWork/?_cookie-check=jELv1AcJnbOzUFgV"><em>Reinventing Work</em></a><em> meetup held at Edo’s office in central Bristol.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=779d7deedd2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Boredom can help your creativity]]></title>
            <link>https://medium.com/@g.n.riva/boredom-can-help-your-creativity-e1694df3a76b?source=rss-b9196e202e9a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1694df3a76b</guid>
            <category><![CDATA[creativity]]></category>
            <dc:creator><![CDATA[Gaia Riva]]></dc:creator>
            <pubDate>Thu, 07 Feb 2019 11:11:43 GMT</pubDate>
            <atom:updated>2019-02-07T11:14:01.081Z</atom:updated>
            <content:encoded><![CDATA[<p><em>“All good ideas come in the shower” — </em>Ever heard that one?</p><p>It’s believed that when you’ve just woken up, your mind is fresh and allowed to wander, and often creativity and eureka moments come to you. I wonder if this is because dull moments when you’re in the shower or on the bus you are, in fact, just a little bit bored. You know you’re having one of those moments when you read all the ingredients on your shampoo bottle and notice that you can actually peel off the label and there is <em>more</em> boring text behind it.</p><p>The idea that being bored is good for creativity is not something that I have invented. I first heard the idea in a <a href="https://www.ted.com/talks/manoush_zomorodi_how_boredom_can_lead_to_your_most_brilliant_ideas/transcript">Ted talk</a> and then from other people, like <a href="https://www.invisionapp.com/blog/questlove-creative-quest/">Questlove</a> and <a href="https://qz.com/1020976/the-scientific-link-between-boredom-and-creativity/">Jordan Rosenfeld</a> who welcome boredom into their life.</p><p>We all know that high-speed internet and our smartphones are killing boredom by entertaining us at all times. Here is a challenge for you: take a bus and see how many people are on their phones or have their earphones in, versus the number of people that are simply looking out of the window. Hey, I am one of those — forever with headphones in listening to podcasts, like Ted Talks, ironically telling me how I need to let myself be bored. I justify this to myself by thinking<em> “At least I am not scrolling through pages of boots and dresses”</em>.</p><p>Except when I am. Instead, I am <em>“enriching myself by hearing very interesting things from very clever people”</em>. The reality is that I am one of those people that have 30 tabs open at all times, get easily restless and need to be doing things like crochet in front of TV (because I am cool like that), consistently avoiding boredom. But I am wrong. It’s important to have moments when nothing happens, when you let your brain go blank and settle into being bored. That’s why meditation and mindfulness are booming lately. We’ve forgotten how to do nothing.</p><h3>Boredom within UX</h3><p>As a UX Consultant, there are a few moments when I am not on my phone or laptop, I am not listening to anything, in fact I am trying to shut out some of the music that we play in the office and I am staring at a wall of post its. Bored.</p><p>Recently I was working on personas having just spent two days making sense of interviews and survey results and collating everything to produce meaningful representations of their audiences.</p><p>All of that part was fine, the problem was the pictures. The dull stock imagery you have to choose from when putting together a persona is, in fact, boring. As my colleague once told me <em>“Every time I look for images, I lose the will to live”</em>. The reality is that having a picture of someone crossing their arms on a white background often doesn’t add much to the representation of a persona apart from giving it a face. These also tend to generate personal opinions like:<em> “I think that Gina would be a more sporty and active person. Not so classy if you know what I mean”</em> or <em>“I thought that John will be more the polo top kind of guy”</em> and then you go off looking for a stock image that does the job. Often it doesn’t matter, because the picture is not as important as the content of the persona. I’m not alone in questioning the value of plain stock imagery — many <a href="https://alistapart.com/article/see-what-i-mean">people and companies</a> have done so too.</p><p>As I am staring at the post its (bored) I started to think about all the other <a href="https://mrjoe.uk/persona-pictures/">articles</a> that have been circulating in the UX team about using drawings, comics, anything else but a stock picture to represent that audience and I let my mind imagine what that would look like.</p><p>So, I took a pad, drew some funny faces and then borrowed some paper from the printer and a marker, and then I shared a picture on Slack with my colleague with the caption <em>“A little bit controversial but what about something like this?”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*6G4Yi79g0COqxM-YNK4EGw.png" /></figure><p>He loved them. I drew some more and then add them to the personas. Out of boredom came a productive couple of hours, instead of wasting the same amount of time browsing the internet for generic imagery.</p><p>Whether or not you agree with, or even like, the hand-drawn personas, one thing is certain: if I had been head down in ‘I-must-finish-these-personas-asap’ mode, then I would have never taken the time to come up with an alternative, more creative method to represent them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ccV_EgqIPnJpVXxNqZzRlA.jpeg" /></figure><p>Here are my suggestions about how to build in boring moments to bring about creative ideas:</p><h3>Take the time to take a step back</h3><p>Move away from your work, make yourself a coffee/tea, then sit and revisit your work. Taking those few minutes before getting back to it will reset your brain into a more objective way of thinking.</p><h3>Use commuting time</h3><p>Whether walking or on a bus, let your mind wander. Instead of mentally writing your shopping list, allow your mind to roam. If it settles on a piece of work, then try not obsess over the detail, but instead allow your mind to expand and consider the bigger picture.</p><h3>Think cross-discipline</h3><p>Don’t only have team meetings with your team. Catch up with other departments, ask them about their work, their processes and then take some time to reflect.</p><h3>Use your out-of-office skills</h3><p>We all have hobbies and other things that we like doing outside of work. Whatever they are they can probably lead to some creative take on your day to day job. If you’re a chess player and also a developer, that might make a nice blog post about how playing chess exercises your brain in thinking about changes in code and the knock-on effect that it might have on other work.</p><p>I encourage you to live and work by the motto “there has got to be a better way”. If something is frustrating and seems counterproductive, instead of habitually moaning to colleagues about it, think of a better way to go about it and follow it through.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1694df3a76b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From producer to user experience consultant]]></title>
            <link>https://medium.com/@g.n.riva/from-producer-to-user-experience-consultant-4694aac87169?source=rss-b9196e202e9a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4694aac87169</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[producer]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Gaia Riva]]></dc:creator>
            <pubDate>Thu, 07 Feb 2019 11:05:39 GMT</pubDate>
            <atom:updated>2019-02-07T11:05:39.545Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XBuczIbuOuxoYT62" /><figcaption>Photo by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Hi, my name is Gaia and I am a User Experience Consultant. They say that the first step is acceptance and sometimes I need to pinch myself as I still struggle to believe that I have made it into UX.</p><p>The reason why that’s not so obvious to me is because, until not so long ago, I was a Senior Producer here at Edo. I have been here for quite some time (6 years and counting) and through the years I have learned so much, was given more responsibility over time and of course promotions that went with it, building a nice career that I was proud of.</p><p>And still part of me couldn’t shake the question <em>“How did I end up here?”.</em></p><p>I studied Economy and Sociology when I was a teenager and when it came to my University choice I preferred the latter over the former (to my parents despair). The truth is that I loved my degree! I was fascinated about how society shapes all of us in so many ways that we are so often unaware of and whether it was gender, art or cognitive sociology it didn’t matter to me — I took it all in.</p><p>When I finished my degree I was faced with the hard reality of the job market. When I went to a recruitment agency with my shiny CV their comment was <em>“At least you can speak some languages, we can do something with that”</em>. And they did — I landed a soulless job in a customer service centre doing data entry and answering phones to angry hospital staff.</p><p>I wasn’t discouraged and I decided to reshape my degree into something with more market value by enrolling in a Marketing MSc. After all, marketing is the sociology of selling things to people (definition completely invented by yours truly). The problem was that I didn’t want to sell things to people (again to my parents despair).</p><p>Eventually, I landed a great job in Client Services at Edo and I still remember the first time that I was introduced to UX by my colleague. The conversation was something like:</p><p><em>“I am in the UX team”</em> — he said</p><p><em>Blank face</em> — me</p><p><em>“The user experience team”</em> — he explains</p><p><em>Still blank face</em> — me</p><p><em>“You have never heard of UX? That’s interesting!”</em> — which is British for ‘where-have-you-been-all-your-life’</p><p>Since then I’ve learned a lot about UX and the more I learned about it the more I could recognise a lot of what I had studied in my degree — Listen to your users in a humble way and without prejudice, don’t ask leading questions, leave silences to let the person think, gather quantitative evidence…</p><p>As a Producer I loved to work on UX projects. I would witness all their research and then see how it magically become something tangible: a persona, an experience map, a website. I was fascinated.</p><p>So eventually, my admiration became interest and I started to crave more involvement in all of the UX projects until I took the decisive step. I changed team!</p><p>I’m now going to share my key learnings from my transition from Producer to UX consultant:</p><h3>Soft skills take time, hard skills are “easier to learn</h3><p>When I first started in UX I wasn’t worried about presentations or talking to users but the idea of having to produce deliverables was much more frightening. That’s because I was used to talking to clients as a Producer but with Sketch, I didn’t know where to start. It turns out that it’s much ‘quicker’ to explain to someone how to use a software than teach things like “read the room”, “understand internal politics of the people that you will be talking to”. I had already learned many of the softer skills previously and it took much more time to get the hard skills right.</p><h3>You’re already empathetic — that’s half of the job done</h3><p>As a Producer my role was to represent the client within the company. You have to keep empathy at all times especially when it gets frustrating (and let’s be real here it does sometimes). That empathy is key when you are a UX consultant. You will need it when talking to users of course but also when listening to the client, their needs, what they know and what is new to them.</p><h3>UX consultants are passionate because they care</h3><p>Are you worried that you are not as passionate as the consultants that you have met? That’s fine, the passion will come with the job. I genuinely believe that all of our consultants are so passionate about their work because they spend hours talking to people, listening to their stories, their issues and what they need. Once you have listened to all of their stories we identify what will make their lives better, what will help them, what they need. So when it comes to reiterating our findings to our client of course we feel passionate, because in that moment we are representing all of their users!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4694aac87169" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 reasons why Brexit needed some UX]]></title>
            <link>https://medium.com/edo-insights/5-reasons-why-brexit-needed-some-ux-3f4c59968516?source=rss-b9196e202e9a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f4c59968516</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[brexit]]></category>
            <dc:creator><![CDATA[Gaia Riva]]></dc:creator>
            <pubDate>Mon, 28 Jan 2019 10:20:45 GMT</pubDate>
            <atom:updated>2019-01-28T10:20:45.794Z</atom:updated>
            <content:encoded><![CDATA[<p>I know your brain probably switches off when you see the B word by now, so sorry to bring it up again but hear me out. And if you agree give it a clap!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*46LBpYGPx67ClKKL" /><figcaption>Photo by <a href="https://unsplash.com/@samuelzeller?utm_source=medium&amp;utm_medium=referral">Samuel Zeller</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In a moment where we are living in limbo waiting for some sort of decision I can’t help but look back at how it all happened. What was the chain of events that lead to where we are and how can we learn from it? And when I did my first thought was, we could have done with some UX in all of this! Here’s why.</p><ol><li><strong>Doing research for the wrong reasons</strong></li></ol><p>It could be argued that the decision to hold a referendum was not taken in the best interests of the UK population (the users). Whatever the outcome, it was likely to be divisive and cause significant tension.</p><p>In other words, the decision was driven by organisational needs and not user needs.</p><p>It was called because of internal party tensions that had been going on for years. The idea was to call a referendum so that we could close the conversation once and for all — although that plan backfired.</p><p>This is like me deciding to do research into banning avocados from brunch menus just because I don’t like them. I am not serving a purpose for the wider population, it’s a self serving reason.</p><p><strong>2. Asking the wrong question</strong></p><p>When I do a survey or prepare for an interview I need to take multiple factors into account: the audience that I will be targeting, the questions that I would ask them, how those could be interpreted, ensuring that there is no bias etc… The main goal though is that the insight I will collect needs to be enough for me to do something tangible with it and make informed decisions.</p><p>Asking if people wanted to leave the EU was not enough. How do you want to leave? Was it a hard Brexit that people wanted? Did they want to be like Sweden? Were they really expressing a general discontent with Westminster instead? The “Leave” answer was just not enough to be able to do anything tangible with. However, the government went full steam ahead drafting a solution based on their own assumption of the “how” people wanted to leave.</p><p>This is like me going ahead and asking people, “Have you had enough of hipster ingredients on brunch menus?” When people say “yes” I am none the wiser about what I should do: are they thinking about avocados? Were avocados the real problem all along? Or is it the vegan sausage roll? Could it be the streaky bacon? Despite all of these outstanding questions I am going to say that yes, people have voted and avocados should be banned from all brunch menus!</p><p><strong>3. Asking the wrong people</strong></p><p>Asking me to vote on something that will have repercussions on pretty much everything (international law, economy, migration, citizenship, foreign relations) is something that I am just not qualified to answer.</p><p>It’s like as if I ask a group of cooks, what would you need from an app to record blood pressure? I should be asking a medical audience, they are qualified to answer and they can tell me what the problem is.</p><p><strong>4. People weren’t rightly informed</strong></p><p>If I haven’t briefed my users properly then their answers are not valuable for my research. Worse still, I could be creating bias in the research.</p><p>For instance if I ask my research question as follows:</p><p><em>Avocados are the root of all evil in this country. They destroy the environment, have a huge carbon footprint, involve deforestation and even worse are preventing millennials from buying houses.</em></p><p><em>With that in mind, would you like to remove avocados from all brunch menus?</em></p><p>You can see that even though the question itself is not biased the context that I added around it will have an effect on the answers that I will get. So in the same way if I think that leaving the EU will save our NHS then I am more likely to say “let’s leave”.</p><p><strong>5. Not starting with the insight</strong></p><p>After the deal was rejected earlier this month, Theresa May decided to ask all the MPs what sort of Brexit they were supporting. Since we are two months away from the deadline my first thought was “you always start with the research”.</p><p>This is the equivalent of me designing a whole app and once it’s complete and people say that they don’t like it I go back and ask them, ‘What did you actually need?’</p><blockquote>Turns out <a href="https://www.economist.com/leaders/2018/12/08/the-best-way-out-of-the-brexit-mess">the Economist agrees with me</a>, “Parliament cannot agree on what kind of Brexit the people want. Rather than guess, it should ask them.”</blockquote><p>So: if I started a research project that didn’t help your purpose, asked the wrong question, to the wrong people, and then miss briefed the participants, would you pay me for the work that I have done?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f4c59968516" width="1" height="1" alt=""><hr><p><a href="https://medium.com/edo-insights/5-reasons-why-brexit-needed-some-ux-3f4c59968516">5 reasons why Brexit needed some UX</a> was originally published in <a href="https://medium.com/edo-insights">Edo Insights</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Empower your employees to make decisions — even the important ones]]></title>
            <link>https://medium.com/edo-insights/https-medium-com-edo-insights-empower-your-employees-to-make-decisions-advice-process-d0fea45da00e?source=rss-b9196e202e9a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0fea45da00e</guid>
            <category><![CDATA[reinventing-organizations]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[teal-organizations]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Gaia Riva]]></dc:creator>
            <pubDate>Thu, 17 Jan 2019 11:36:00 GMT</pubDate>
            <atom:updated>2019-01-17T11:36:00.816Z</atom:updated>
            <content:encoded><![CDATA[<h3>Let your employees make decisions: even the important ones</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r8v58_EI8O5gxD1j" /></figure><p>This is a video from a lightning talk that I did last year at UX Bristol 2018. In only 5 minutes I explained what the advice process is and why it makes (so much) more sense than traditional decision making processes.</p><p>The <a href="http://www.reinventingorganizationswiki.com/Decision_Making">advice process</a> is something that I came across whilst reading Frederic Laloux’s book ‘<a href="http://www.reinventingorganizations.com/">Reinventing Organisations</a>’. It’s a fascinating book and I would highly recommend if you wish to free your organisation from traditional ways of working that crush your potential. I couldn’t cover all the great things that Laloux explores in his book so I decided to concentrate on one thing instead:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F281657195%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F281657195&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F715821519_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/b7fbd00907055a1c80ad51735bd3b136/href">https://medium.com/media/b7fbd00907055a1c80ad51735bd3b136/href</a></iframe><p>I chose the advice process because that is probably one of the building blocks if you wish to change your organisation structure. The key points that I cover in my talk are summarised below.</p><p>Traditional ways of decision making don’t work:</p><ul><li><strong>Top down:</strong> managers making decision means that sometimes they will need to make decisions on things that they are not experts in or not knowing enough about what it involves.</li><li><strong>Consensus:</strong> is a lengthy and sometimes impossible process.</li><li><strong>Voting:</strong> although is better than the previous two it still asks the opinion of people who are not qualified to make that decision.</li></ul><p>Enter the advice process, a new method by which any of your employees can make a decision as long as they follow these simple rules:</p><ul><li><strong>Seek advice from the experts:</strong> they know more so start by hearing them out and fully listen.</li><li><strong>Consult the people who will be directly affected by your decision:</strong> not everyone might be affected by your idea, it might be restricted to a team or a department, don’t cast your net unnecessarily wide.</li><li><strong>Ponder what you have heard and go for it:</strong> you might decide to drop the idea, change it and go through the process again, or you might decide to go for it anyway.</li></ul><p>I would also add that is important to create a safe space where all of your organisation feels that they can be brave and if it doesn’t go as planned you will all learn from it and try again instead of simply shutting things down or pointing fingers.</p><p>It seems simple enough but it is <strong>powerful</strong>! Imagine all your employees having access to credit cards, suggest new processes, new tools, new machinery, different ways of working (like our<a href="https://www.edo.co/our-thinking/introducing-nine-day-fortnight"> 9 day fortnight</a>). The possibilities are endless.</p><p><em>Want to talk more about the advice process or reinventing your organisation? </em><a href="/service/mailto:hello@edo.co"><em>Drop me a line</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0fea45da00e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/edo-insights/https-medium-com-edo-insights-empower-your-employees-to-make-decisions-advice-process-d0fea45da00e">Empower your employees to make decisions — even the important ones</a> was originally published in <a href="https://medium.com/edo-insights">Edo Insights</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>