<?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 Oriol Bedia on Medium]]></title>
        <description><![CDATA[Stories by Oriol Bedia on Medium]]></description>
        <link>https://medium.com/@OriolBedia?source=rss-8e055a9d662c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*aoosff_kpkoPMgzinp8BZg.png</url>
            <title>Stories by Oriol Bedia on Medium</title>
            <link>https://medium.com/@OriolBedia?source=rss-8e055a9d662c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:09:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@OriolBedia/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[How to Manage 1-on-1’s for Growth?]]></title>
            <link>https://uxdesign.cc/https-medium-com-oriolbedia-empathy-wont-help-designers-grow-5d8ea087d72f?source=rss-8e055a9d662c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d8ea087d72f</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Oriol Bedia]]></dc:creator>
            <pubDate>Wed, 10 Jul 2019 23:35:53 GMT</pubDate>
            <atom:updated>2019-11-11T12:28:54.101Z</atom:updated>
            <content:encoded><![CDATA[<h4>Empathy won’t Help Designers Grow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-urAq0XXMQ4RSLRAiP600Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/bSpqe48INMg">Bernard Hermant</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>You’ve been fooled.</p><p>You’ve been told to mentor designers, and been given a “be-bold” growth “plan” with goals that only management understands.</p><p>You’ve been lied to.</p><p>You’ve been told in TED talks that if only you are nice, if only you deeply embrace the soul of young designers, you’ll be a great mentor.</p><p>They were full of s***! Empathy won’t help.</p><p><strong>What’s needed to help designers grow is to talk often, to encourage a learning mindset and challenge their progress with actionable goals.</strong></p><p>Sounds easy, right? That’s what I thought.</p><p>A year ago I was working at <a href="https://medium.com/u/b8403f57b0b8">Designit</a>, where I started to mentor designers. Our small Berlin office was developing, and we dealt with a big challenge: <strong>How to grow design talent?</strong></p><p>This challenge is bigger and bigger for tech firms since a few years. According to <a href="https://techcrunch.com/2017/05/31/here-are-some-reasons-behind-techs-design-shortage">TechCrunch</a>, companies across Silicon Valley have hired far more designers than ever before since 2013. In fact, between 2013 and 2017 the designer to developer ratio increased 2.5x on average. Imagine what’s the ratio in 2019?!</p><p><strong>There have never been as many designers mentored as there are today.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HHq5pgAlXYVpb9t88B_9jw.png" /><figcaption>Major tech firms have considerably grown the designer to developer ratio in the past years.</figcaption></figure><h3>What’s my solution?</h3><p>Simply said, 1-on-1’s. But wait, do you know what a 1-on-1 is? It’s a private meeting between a mentor and a mentee, used for multiple purposes. In this case, <strong>“1-on-1&#39;s for growth”</strong> <strong>are aimed at helping designers grow professionally.</strong></p><p>Today I’ll share how to manage 1-on-1’s for growth in three parts:</p><p><strong>1. Set-Up for Success:</strong> an explorative session to prep.<br><strong>2. Organize 1-on-1s:</strong> practicalities &amp; mindset.<br><strong>3. 1-on-1s for Growth:</strong> approach and questions to follow.</p><p><strong>The goal of these talks is that designers get a clear growth direction, develop confidence in their thinking, and ultimately become more self-sufficient.</strong></p><p>I’ve written this piece for senior designers that just started to mentor, and also for any designers to challenge their mentors.</p><p>Without further ado, let’s dig into it!</p><h3>1. Set-Up for Success</h3><p>When I began mentoring, I was eager to understand this challenge beyond my own experiences. I’ve asked friends and colleagues about their mentors. <strong>To my surprise, most mentors jump straight into 1-on-1s without preparation. This leads to lower mentee engagement.</strong></p><p>As my research continued, I discovered that one of the most important things about mentoring is understanding where to start.</p><blockquote>“<strong>It’s hard to encourage growth without knowing the abilities and shortcomings of your mentee.</strong>”</blockquote><p>That’s why before having the first 1-on-1 you should organize a 45-minutes session to: discover struggles and capabilities for growth and decide on a mentoring style. Let me explain.</p><p>Start setting the context of this session reviewing the expectations and results that your mentee’s position demands. These should be aligned with your lead.</p><p>Now, talk about your mentee’s strengths, weaknesses, opportunities, and threats— also known as <a href="https://en.wikipedia.org/wiki/SWOT_analysis">SWOT analysis</a>. This will help you understand their potential. Ask them to answer these questions in advance:</p><blockquote><strong>Strengths:</strong> What do you do well?<br><strong>Weaknesses:</strong> Where do you need to improve?<br><strong>Opportunities:</strong> What are your long-term growth goals?*<br><strong>Threats:</strong> What obstacles do you face?</blockquote><ul><li>Important! These goals will guide growth, and you’ll use them in 1-on-1s.</li></ul><p>A common pitfall with SWOT analysis is to mostly focus on personal qualities. The nature of these qualities makes it difficult for mentors to effectively guide growth towards specific skills that may define designers&#39; maturity. That’s why, you should frame this analysis in a few areas; e.g. core disciplines, secondary disciplines, qualities, foundational skills, responsibilities, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1GnYOmmjkKWtPcCoIXDo1Q.png" /><figcaption>Use this example of a “Competency Model” template when doing a SWOT analysis. Your organization can focus on other areas, based on the required skills that designers need to develop given your company’s needs. <a href="https://medium.com/shapingdesign/competency-model-576cb67a8943">Read more about this topic in this great piece</a> by <a href="https://medium.com/u/f91684fdc716">Jason Mesut</a>.</figcaption></figure><p>After this session, you’ll be ready to help your mentee grow. On top of that, you’ll understand what the best mentoring style is, given your mentee’s abilities and motivations. To do so, simply ask yourself:</p><blockquote>· How capable is your mentee of delivering what’s being asked?<br>· How motivated is your mentee to deliver what’s being asked?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fIMk9wjhUIK9a9f0a7eNNA.png" /><figcaption>The level of ability and willingness of your mentee will lead you to adopt the most suitable mentoring style. <a href="https://betterhumans.coach.me/how-to-start-coaching-anyone-on-anything-c0e9068fdf6f">Read more about these mentoring styles</a>–Thanks <a href="https://medium.com/u/4b14847d7a53">Chris Sowers</a> for this great piece about coaching!</figcaption></figure><h3>2. Organize 1-on-1s</h3><p>Start by deciding how often you’ll talk with your mentee. I recommend meeting every week for the first 2–3 months; after that, meet every second week. Next, create a document to log all 1-on-1s and share it with your mentee, it will help you track your mentee’s progress over time.</p><p>Beyond simple practicalities, you need to master these mindsets to lead 1-on-1s:</p><h4><strong>Curiosity</strong></h4><p>Advice-giving is overrated. 1-on-1 talks are not about you, they are about your mentee. <strong>Just listen, and motivate your mentee to answer their own questions.</strong></p><blockquote>“Ask yourself: Can you stay curious a little longer, and rush into advice slower?” — <a href="https://twitter.com/boxofcrayons">Michael Bungay Stanier</a>. Author of <a href="https://www.amazon.de/Coaching-Habit-Less-Change-Forever/dp/0978440749">“The Coaching Habit”</a></blockquote><h4><strong>Openness</strong></h4><p>Don’t organize 1-on-1’s in a room where you normally host meetings, or where you work. Break out the routine, find a comfortable place where it’s easy to be comfortable and share thoughts. — Try outside of the office.</p><h4><strong>Commitment</strong></h4><p>Make it a priority in your agenda, and don’t skip any sessions. This is a long and slooooow project.<strong> It will require to be repeated time and time again before seeing much results.</strong></p><h3>3. 1-on-1s for Growth</h3><p>My approach to 1-on-1s is inspired by <a href="https://en.wikipedia.org/wiki/Kolb%27s_experiential_learning">Kolb’s experiential learning</a>, published in 1984 and influenced by Gestalt psychology.<strong> His theory states that a person learns by doing, and contrary to popular methods, allows for reflection as a way to learn.</strong></p><blockquote>“If a person learns by doing, a mentor may help a mentee grow by motivating new &amp; challenging experiences.”</blockquote><p>Part of Kolb’s theory is the experiential <a href="https://en.wikipedia.org/wiki/Learning_cycle">learning cycle</a>. I used this model to shape the questions and the format of “1-on-1’s for growth”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*REke-dass0tr-ol_GNZ3Kw.png" /><figcaption>Kolb’s experiential learning cycle and its phases applied to “1-on-1s for growth”.</figcaption></figure><h4><strong>Today — 5 Min. (</strong>Concrete Experience)</h4><p>This is a soft start to know how your mentee is doing today. By doing so, you’ll better understand their feedback on the next questions. This is also the time to check your mentee’s progress — <strong>Look out for growth blockers.</strong></p><blockquote>💭 <strong>What’s on your mind?</strong></blockquote><blockquote>👊 <strong>How is it going with the action points?</strong> (From past sessions)</blockquote><h4>Yesterday — 5 Min. (Reflective Observation)</h4><p>Now, review the most relevant experiences for your mentee since the last session. Make sure they come to the session with three brief answers to each of these questions, listed by importance.</p><p><strong>These questions will help you understand your mentee’s preferred growth direction.</strong> You will be tempted to give advice, but remember to stay curious and just listen.</p><blockquote><strong>💘 What should continue happening?</strong></blockquote><blockquote><strong>💣 What shouldn’t happen anymore?</strong></blockquote><h4>So What — 10 Min. (Abstract Conceptualization)</h4><p>Listen to how your mentee interprets past experiences and turns them into learnings. This question will help them gain perspective about what happened and develop confident thinking. This section must also be prepared in advance, with one learning.</p><p><strong>Look out for strong conclusions, and ask “Why?”.</strong> Your mentee may need your support to reinterpret intense experiences and see positive influences.</p><blockquote><strong>🚀 What is your main takeaway?</strong></blockquote><h4>Tomorrow — 10 Min. (Active Experimentation)</h4><p>Enough of listening, this is when your help is most needed. To wrap-up, together with your mentee decide three new experiences towards their long-term growth goals. (These goals were mentioned during SWOT analysis)</p><p><strong>It’s important that your mentee thinks small, and sticks to the time given.</strong> If growth actions are ambitious, break them down into smaller actions.</p><blockquote><strong>👊 What’s the smallest growth action you can take until we meet again?</strong></blockquote><h3>Last Thoughts</h3><p><strong>My ultimate motivation to mentor is being part of transformative experiences, such as professional growth.</strong> It’s great that senior designers may be a source of guidance, knowledge, and inspiration.</p><p>Having an organized and effective growth process to motivate and guide young designers it’s hard work. Yet it’s great by all means. It gives senior and young designers responsibilities, strengthens teams culture, and empowers organizational progress — So, start today and keep it up!</p><p>After all, any process is like a design tool, <strong>it only gets better with practice.</strong></p><p>… If you enjoyed the read, please tap or click 👏 to help recommend this piece to others. Best regards from Berlin! Oriol.</p><p>[Thanks <a href="https://medium.com/u/d7226b25d73c">Caroline Arvidsson</a> for your feedback and proofreading. 💖]</p><h4>More UX Articles from Oriol Bedia</h4><ul><li><a href="https://uxdesign.cc/how-to-know-your-users-needs-2d24fb92a01e">How to Know Your Users’ Real Needs?</a></li><li><a href="https://uxdesign.cc/lipstick-on-a-ui-eb71d85c4a2f">Lipstick on a UI</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d8ea087d72f" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/https-medium-com-oriolbedia-empathy-wont-help-designers-grow-5d8ea087d72f">How to Manage 1-on-1’s for Growth?</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[How to Know Your Users’ Real Needs?]]></title>
            <link>https://uxdesign.cc/how-to-know-your-users-needs-2d24fb92a01e?source=rss-8e055a9d662c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d24fb92a01e</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Oriol Bedia]]></dc:creator>
            <pubDate>Sat, 17 Feb 2018 22:16:44 GMT</pubDate>
            <atom:updated>2019-07-11T05:49:22.475Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Framework to Understand the WHY in User Interviews</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-vU_zslz7CQdPv1aR7uwaA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/k_RYBedEvDw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daria Shevtsova</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Anyone who designs products and services knows how important it is to design with the user mind. These are old news. Ironically, up until a few years ago user research was ignored by most organisations.</p><p>As product designer I have gained research experience to support, organise, and lead research sessions for the past four years. I have collaborated with product teams within orgs who have heard about <a href="https://www.designcouncil.org.uk/sites/default/files/asset/document/ElevenLessons_Design_Council%20(2).pdf">this <em>“research-thing”</em> and how it could improve their design process.</a> However, they didn’t had a researcher in-house nor enough resources to get insights about their users.</p><p>What happened within these organisations while growing research efforts? <strong>Research was done anyhow by any team member.</strong></p><p>Organisations underestimated the time and effort needed to follow good research practices, causing research tools to be misinterpreted.</p><p>Up until now, orgs that followed such initiatives have developed not only faulty tools but also shallow research methods that don’t help any team member to understand users’ real needs.</p><p>The problem is: <strong>Orgs struggle to integrate a research culture from within.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*RvnBX672m8m2eVDvLhj9IA.jpeg" /><figcaption>Personas are a great example. Useful Personas are filled with behavioural data, but Personas can also become excellent office posters when are filled with *fluff* — <a href="https://blog.mailchimp.com/new-mailchimp-user-persona-research">Personas at MailChimp, 2013</a></figcaption></figure><p>Research is still seen as a magic wand that is only waved when problems arise.<strong> It isn’t used to challenge issues through hypothesis validation, but to force confirmation of user assumptions.</strong></p><p>I have experienced this problem often times during user interviews. When team members lead interview sessions they tend to ask <em>Why</em> too soon, and let participants go off the edges with stories they share. By doing so, they capture broad arguments that are interpreted in the best way needed to force confirmation of any assumption or hypothesis. Does it sound familiar?</p><blockquote><strong>To ask people WHY (too soon) is to ask people what they WANT.</strong></blockquote><p>Even if today’s orgs hire more and more research professionals, <strong>research is a must for product teams in general to nurture a better research culture.</strong></p><p>In this article I’ll take a stab at this problem. I’ll propose a research interview framework for POs, PMs, designers, developers, anyone who wants to do better research. Ultimately for you to understand your users’ real needs.</p><p>Inspired by “<a href="https://designyourthinking.com/getting-why-formula">Getting to Why</a>” from <a href="http://twitter.com/kartvee">@kartvee</a>, I’ll demystify the use of asking <em>Why</em> in user interviews and I’ll walk through examples of how to apply this framework.</p><h3>A framework to understand WHY</h3><p>The basic idea is simple. You have to understand <em>Why</em> before you ask <em>Why</em>. To understand <em>Why</em>, team members who do research should form theories or have a slight idea in their minds about the reason to participants’ behaviour before asking <em>Why</em>. <strong>Theories are formed by asking: <em>What/Who, When/Where,</em> and <em>How.</em></strong></p><blockquote>It‘s not people’s job to explain WHY, it’s your job as researcher to understand WHY</blockquote><p>Once these questions are answered and there is a slight idea of the reason to peoples’ behaviour, team members should ask <em>Why</em> to validate their theories and have reassurance about users’ real needs.</p><blockquote>“The best research questions are about past behaviour. We’re interested in actual behaviour, not a prediction of behaviour.” — <a href="https://twitter.com/jmspool">Jared Spool</a> from “<a href="https://blog.usejournal.com/net-promoter-score-considered-harmful-and-what-ux-professionals-can-do-about-it-fe7a132f4430">Net Promoter Score Considered Harmful</a>”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qGYL-fglmKBnv4XNT3xuAA.png" /><figcaption>The answers to these questions give us hints to understand parts of WHY</figcaption></figure><h3>Let’s put this framework into practice</h3><p>Before we start the actual research, and to ensure success of the interview sessions, it’s essential to set a <strong>research objective</strong>. To do so, product teams have to answer and align on a set of questions before talking to users.</p><blockquote>-What’s the purpose of organising this session?<br>-What do you want to learn about your users?<br>-What information will help to make a decision for the product?</blockquote><p>With a research objective ready, we can start with the actual research. <strong>Let’s imagine you are leading a user research interview for an online grocery service.</strong></p><h4>1. From WHY to WHAT and WHO</h4><p>The first questions to ask in an interview are always <em>What </em>and<em> Who</em>, these help uncover object and subject so that you can <strong>keep them in focus during the interview.</strong></p><p>By contrast, if I ask <em>Why</em> right after the introduction, the common problem I experience is a <strong>loss of control towards the research objective.</strong> Most participants are happy to tell you about a product they use, and they will often give long explanations about things that have happened to them.</p><blockquote>In short, stay away from asking people about their opinion.</blockquote><p><strong>Instead of…<br></strong>WHY do you buy groceries online?</p><p><strong>Ask…<br></strong>WHAT happens in your life before you order groceries? After?<br>WHAT does/doesn’t work for you when buying groceries online?<br>WHO are you with when you buy groceries online? WHO do you consult for advice?</p><p>The main goal is to understand who the subjects are, and what the objects are that drive people’s behaviour when approaching a topic — and how these fit into people’s lives.</p><p>Most importantly, if you ask <em>What </em>and<em> Who </em>questions, you’ll have the chance to <strong>uncover user motivations beyond competition.</strong> When you ask <em>Why</em> too soon people relate to products they currently use, and your research may end up focusing on competitors’ features rather than on people’s motivations towards new solutions.</p><blockquote>“People are aware of how the products they currently use fulfil their needs. But not about how new solutions could fulfil these differently.” — <a href="https://twitter.com/alanklement">Alan Klement</a>. JTBD Workshop, London.</blockquote><h4>2. From WHY to WHEN and WHERE</h4><p>Right after you ask <em>What </em>and<em> Who</em> it is tempting to fall into <em>Why</em> questions. But hold back and instead ask <em>When and Where</em> to <strong>frame people’s behaviour into specific contexts.</strong></p><p>By contrast, if I ask <em>Why</em> without previously setting the context, the common problem I experience is that later during the interview <strong>people contradict themselves.</strong></p><blockquote>What people say isn’t necessarily what they do.</blockquote><blockquote>“When Sony was introducing the boom box, the company gathered a group of potential consumers and held a focus group on what color the new product should be: black or yellow. After some discussion among the group of likely buyers, everyone agreed that consumers would better respond to yellow. After the session, the facilitator thanked the group, and then mentioned that, as a bonus, they were welcome to take a free boom box on the way out. There were two piles of boom boxes: yellow and black. (I bet you know where this is heading.) Every person took a black boom box.” — <a href="https://twitter.com/muldermedia">Steve Mulder</a> from “<a href="http://boxesandarrows.com/files/banda/long-live-the-user/Mulder_TheUserIsAlwaysRight_Ch3.pdf">The User Is Always Right: A Practical Guide to Creating and Using Personas for the Web</a>”</blockquote><p><strong>Instead of…<br></strong>WHY buying groceries online is a helpful solution to you?</p><p><strong>Ask…<br></strong>WHEN was the last time you bought groceries online?<br>WHEN is the best moment for you to buy groceries online? Worst?<br>WHERE do you find yourself when you buy groceries online?</p><p>The main goal is to understand the context. <em>When </em>and<em> Where</em> questions help you to learn about people’s past experiences, understand their decision-making process and ultimately to uncover their behaviour.</p><p>Before the interview session you can gather quantitative data about your users to have an initial understanding of the context, but be aware not to fall into the “SAY-DO” contradiction. <strong>By mixing quantitative and qualitative data you can better understand user’s real needs.</strong></p><blockquote>“Users don’t want simplicity, even if they claim they do. They want to understand. If you give somebody something they can understand the will say: See how simple it is.” — <a href="https://twitter.com/jnd1er">Don Norman</a> from “<a href="https://www.youtube.com/watch?v=Q97tg6-zGqA">UX Mastery Book Club</a>”</blockquote><h4>3. From WHY to HOW</h4><p>Once the research subject, object and its context are framed it’s even more tempting to ask <em>Why</em>, but you still need to ask <em>How</em>. This will <strong>reveal the nuanced circumstances of a given context.</strong></p><p>By contrast, if I ask <em>Why</em> at this point of an interview, the common problem I experience is that participants make up stories on the spot. Maybe they try to say what they think I want to hear, but it turns out we aren’t aware of the real reason behind our behaviours. <strong>Most people aren’t good at analysing and reflecting on their own actions.</strong></p><blockquote>If you ask people Why they will find a reasonable story to their behaviour.</blockquote><p><strong>Instead of…<br></strong>WHY do you buy groceries online from… (Context)?</p><p><strong>Ask…<br></strong>HOW do you do online grocery shopping on the weekend?<br>HOW does online grocery shopping fit into your family life?<br>*Is this HOW you often do it?/ Tell me about the last time you…?</p><p>*Note the last question, this will help reassure people’s behaviour. You will easily spot when people invent stories, and <strong>see the difference between a wished reality and given one.</strong></p><p>Ultimately, when people invent stories to answer <em>Why</em> questions, the answers you get will differ too much from participant to participant. <strong>You’ll struggle to find insightful patterns during the research analysis.</strong></p><blockquote>“We try to ignore opinions… these are worthless. They don’t repeat and require a huge sample to find trends. Cognitive behaviour repeats overtime already over a small sample.” — <a href="https://twitter.com/boltron">Nate Bolt</a></blockquote><h3>Final Thoughts</h3><p>This framework is the result of my research experience from the last years, where I’ve screwed up sometimes. As in my case, I expect anybody to be able to learn about research and integrate a solid and well-reflected methodology into their skillset.</p><p>I hope this research framework can help POs, PMs, designers, developers, and anyone to become better at research. Ultimately I hope it nurtures a good research culture, <strong>until</strong> <strong>organisations invest enough resources into research, and make it a TOP priority for truly user-centred design.</strong></p><p>Thoughts? I’m always looking forward to constructive feedback to improve my tools and methods. Let’s chat about it here, or reach out on <a href="https://twitter.com/oriolbedia">Twitter</a>. Hope you enjoyed!</p><p>Please tap or click ♥︎ to help to recommend this piece to others.</p><p>Best regards from Berlin,<br>Oriol</p><p>[Many thanks to <a href="https://medium.com/u/d7226b25d73c">Caroline Arvidsson</a> for her tremendous help to make this piece better, and to <a href="https://medium.com/u/bc02b1821659">Andy Jakubowski</a> for proofreading.]</p><h4>More UX Articles from Oriol Bedia</h4><ul><li><a href="https://uxdesign.cc/https-medium-com-oriolbedia-empathy-wont-help-designers-grow-5d8ea087d72f">Empathy won’t Help Designers Grow</a></li><li><a href="https://uxdesign.cc/lipstick-on-a-ui-eb71d85c4a2f">Lipstick on a UI</a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d24fb92a01e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-know-your-users-needs-2d24fb92a01e">How to Know Your Users’ Real Needs?</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[Lipstick on a UI]]></title>
            <link>https://uxdesign.cc/lipstick-on-a-ui-eb71d85c4a2f?source=rss-8e055a9d662c------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb71d85c4a2f</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Oriol Bedia]]></dc:creator>
            <pubDate>Mon, 13 Feb 2017 21:02:52 GMT</pubDate>
            <atom:updated>2019-07-11T05:53:24.736Z</atom:updated>
            <content:encoded><![CDATA[<h4>Can we design invisible interfaces to be useful smart products?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zpaOhuNi2iJm7_gGncwaag.jpeg" /></figure><p>Last year saw an explosion of a special kind of smart products: home assistants, driving devices, lighting &amp; security systems, etc — all devices activated by voice, gesture or <a href="https://ifttt.com/">automated through a chain of conditions</a>. Major topics in media technology and Google searches were “IoT” and “Bots” — and this Christmas <a href="http://phx.corporate-ir.net/phoenix.zhtml?c=176060&amp;p=irol-newsArticle&amp;ID=2232897">Amazon Echo sold 9x more units than last year</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8tyrvQyw8H32oW_4bJmQFA.jpeg" /></figure><p>What do these devices have in common? They have invisible interfaces, with some or no graphical user interface (GUI), <a href="http://www.nointerface.com/book">but never without interface</a>. Invisible interfaces promise frictionless and efficient smart products; ultimately intended to make our lives easier.</p><p>Here’s the rub, <a href="http://www.ibmbigdatahub.com/blog/why-over-two-thirds-internet-things-projects-will-fail">two-thirds of these devices fail</a> to deliver on their promise.</p><p><strong><em>While invisible interfaces aim to serve people beyond a functional purpose, they produce faulty user experiences that are overcomplicated with needless features and oversimplified with ambiguous interactions.</em></strong></p><blockquote><strong>Designers put lipstick on a UI and call it invisible interface.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*GMpl1dkO3mWQeh-nPWATGg.gif" /><figcaption>Do you think people want to move their fingers like a maniac at Starbucks to review their running stats? <a href="https://techxplore.com/news/2015-05-finger-gestures-smartwatch.html">This isn’t useful</a>.</figcaption></figure><h3>Beyond Graphical User Interfaces</h3><p>A first step towards a solution is to understand that invisible interfaces are pushing <a href="https://en.wikipedia.org/wiki/Ubiquitous_computing">ubiquitous computing</a> forward, thus <a href="https://en.wikipedia.org/wiki/Natural_user_interface#/media/File:CLI-GUI-NUI.png">user interfaces need to mature</a>.</p><p>Designers need to move beyond traditional practices to develop GUIs, where functionality is excessive and usability overemphasises guidelines over users. <strong><em>This design shift demands more than pixel perfect mockups and impressive prototypes; it demands that we design systems focused on people’s activities, goals &amp; motivations.</em></strong></p><blockquote><a href="https://en.wikipedia.org/wiki/Natural_user_interface">Natural User Interfaces</a> advocate for interactions that come naturally to people through the <strong>understanding of context of use.</strong> <strong>NUIs are more than just functional and desirable — they are designed for usefulness.</strong></blockquote><blockquote>“Technology is re-architecting itself around people.” — <a href="https://twitter.com/padday">Paul Adams</a>. VP of product at <a href="https://www.intercom.com/">Intercom</a>.</blockquote><h4>Invisible Interfaces as Useful Smart Products</h4><p>Today I’ll explain how to design smart products as NUIs, in other words, how to design <strong><em>useful smart products</em></strong>.</p><p><strong><em>I’ve taken the “</em></strong><a href="https://en.wikipedia.org/wiki/Flexibility-usability_tradeoff"><strong><em>Usability-Flexibility Trade-Off</em></strong></a><strong><em>” to show how affordances and context are fundamental elements to strike the right balance to create useful smart products.</em></strong> To wrap up, I’ll talk about <strong><em>Jobs-To-Be-Done</em></strong>, a research method which helped me unearth usefulness for better products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vkdIaJanQp4AsU9aqeB3cg.png" /><figcaption>Useful smart products start with a minimalist approach; making a better use of affordances and context to keep a balance between usability and flexibility.</figcaption></figure><h3>Usability → Affordances</h3><p>Usability problems happen when smart products are aesthetically simplified with reduced <a href="https://en.wikipedia.org/wiki/Affordance">affordances</a> BUT relying on a “cool” invisible interface. However, all too often, its hidden affordances offer little insight for interaction — all invisible usability remains useless. In short, lipstick on a UI.</p><p>People end up triggering actions they never intended and are left to learn by trial-and-error. Sounds familiar, doesn’t it?</p><blockquote>“The best products are as visible as they need to be to make the activity better.” <a href="https://twitter.com/odannyboy">Dan Saffer</a>. “<a href="https://medium.com/@odannyboy/the-myth-of-invisible-design-c67d590babe9#.c51pow89m">The myth of Invisible Design</a>” on Medium</blockquote><blockquote>The solution isn’t to add or remove affordances to improve usability flaws. <strong>Useful smart products offer alternative interactions modes, and each mode has a set of affordances that become useful as they adapt to people’s activities.</strong></blockquote><h4>Multimodal Interaction</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xtJTwSDsvuU8MiUQ3EiOWw.jpeg" /></figure><p>Amazon Echo is a useful smart product for one reason, its multimodal input modes. People can accomplish tasks by choosing the interaction mode that best suits a particular moment in their lives. For example, let’s take Echo’s shopping list feature. <strong><em>A user can add an item to a shopping list via:</em></strong></p><p><strong><em>- Voice Commands<br>- Voice Remote<br>- Alexa app<br>- Amazon’s website<br>- Automated tasks (</em></strong><a href="https://ifttt.com/amazon_alexa"><strong><em>IFTTT</em></strong></a><strong><em>)</em></strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6CeVDlkSqJo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D6CeVDlkSqJo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F6CeVDlkSqJo%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/17ae4b612f8d72324e90eabbb0fac92f/href">https://medium.com/media/17ae4b612f8d72324e90eabbb0fac92f/href</a></iframe><blockquote>“Design is a participatory activity, not simply dictating but allowing the user to evolve and shape the encounter so it is a co-creative opportunity”. — <a href="https://twitter.com/dourish">Paul Dourish</a>. “<a href="https://mitpress.mit.edu/books/where-action">Where the action is</a>.”</blockquote><h3>Flexibility → Context</h3><p>Flexibility problems occur when smart products are designed with little understanding about people’s goals &amp; motivations. The results are generic interfaces suited to everyone and no one, users don’t understand how such complex experiences could ever fit into their lives. Again, lipstick on a UI.</p><p><strong><em>These products become useless due to their broad functionality.</em></strong></p><blockquote>“All of the functionality in the world is useless if the useful functions aren’t present.” —<a href="https://twitter.com/jkolko"> John Kolko</a>. “<a href="http://www.thoughtsoninteraction.com/">Thoughts on Interaction Design</a>.”</blockquote><blockquote>As smart products are incrementally infused into every part of people’s lives, design folks need a deeper contextual understanding of users and how these devices play a part in their lives. <strong>Useful smart products do serve a functional purpose, but most importantly, an emotional and social purpose.</strong></blockquote><h4>People’s Purpose</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x10FeoUOU1v9AQdf_YiwCA.jpeg" /></figure><p>Many factors influenced the failure and success between Google Glass and Snapchat Spectacles: price, marketing and advertising, product strategy, etc. However, we can’t argue the fact that Snapchat released a product with a minimalist approach and the right amount of functionality. <strong><em>This smart product fits into people’s leisure time by fulfilling three purposes:</em></strong></p><p><strong><em>- Functional: Create and share snaps effortlessly, anytime.<br>- Emotional: Capture POV videos that feel like shared memories.<br>- Social: Promote a sense of community, visually identifiable.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*X6BT3v-VGof0rK60VTW7ow.gif" /><figcaption>On top of it, Snapchat solved the portrait vs landscape video argument forever. Circular video extends the usefulness of this smart product to the mobile device.</figcaption></figure><h3>Usefulness → Jobs-To-Be-Done</h3><p>Despite <a href="http://www.zdnet.com/article/user-experience-now-top-of-mind-even-before-software-is-conceived">72% of companies conduct research before beginning any design or software development</a>, the results of such research aren’t conclusive because it tends to focus on WHAT and HOW users experience a product.</p><blockquote><strong>An understanding of WHY people use smart devices and the underlying motivations when deciding to use a product will lead towards usefulness.</strong></blockquote><p>Personas are helpful to understanding motivation. But to be honest, the amount of insight gained often falls short and assumptions multiply. <strong><em>The solution isn’t better Personas, but better research methods. That’s how I discovered Jobs-To-Be-Done.</em></strong></p><blockquote>“People don’t want to buy a quarter-inch drill. They want a quarter-inch hole.” — Theodore Levitt, Harvard Business School Professor</blockquote><p>The concept is simple: We “hire” products and services to do things for us. This research method is based on detailed contextual inquiry, where the researcher “becomes a detective” during a JTBD Interview. The goal is to understand the job for which people would hire a product, uncovering their underlying struggles and motivations from first thought to final purchase.</p><p><strong><em>In my experience, Jobs-To-Be-Done reinforced the research analysis &amp; synthesis phase with solid motivational insights, while it helped to better inform design artefacts about the usefulness of products.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MaLkokcX8K-CoE6jk_ls7g.png" /><figcaption>Relation between JTBD interviews and its direct outputs along the design process. Thanks to <a href="https://jtbd.info/@lovskogen">Tor L. Bollingmo</a> — “<a href="https://jtbd.info/interviews-timelines-forces-job-stories-whats-the-difference-a90949d6cb0a#.x7nle6ige">Interviews, Timeline, Forces, Job Stories — what’s the difference?</a>”</figcaption></figure><p>For further reading, do check out:<br>“<a href="http://www.competingagainstluck.com/">Competing Against Luck</a>” — by <a href="https://twitter.com/claychristensen">Clayton Christensen</a><br>“<a href="http://www.anthonyulwick.com/publications">Jobs-To-Be-Done</a>” — by <a href="https://twitter.com/ulwick">Tony Ulwick</a><br>“<a href="http://www.whencoffeeandkalecompete.com/">When Coffee and Kale Compete</a>” —by <a href="https://twitter.com/alanklement">Alan Klement</a><br>“<a href="https://www.intercom.com/books/jobs-to-be-done">Intercom on Jobs-To-Be-Done</a>” — by <a href="https://www.intercom.com/">Intercom</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Df84LymEs67Y&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Ff84LymEs67Y&amp;type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d1fc192a1cc10b55d1c5f31bc3154559/href">https://medium.com/media/d1fc192a1cc10b55d1c5f31bc3154559/href</a></iframe><h3>Final Thoughts</h3><p><strong><em>Design is a tool for understanding people.</em></strong> That’s why the usefulness of any product we design is dictated by people’s experiences and not by the robustness of technology.</p><blockquote><strong><em>The deeper challenge for invisible interfaces is to humanise technology.</em></strong></blockquote><p>Interfaces that go beyond the glass demand that we observe with care, curiosity and feeling how people interact and communicate with the world. Most importantly, designers need to understand that this natural dialogue between people and the world is always reactionary and anticipatory at the same time. Just by creating experiences that accommodate such natural interactions we will make useful smart products finally see the day of light.</p><h3>Thanks for reading!</h3><p>Thoughts? Feel free to comment on this article, or <a href="http://twitter.com/oriolbedia">reach out on Twitter</a>. Please tap or click 💚 to help recommend this piece to others.</p><p>Best regards from Berlin,<br>Oriol</p><p>[Many thanks for proofreading to my friends: <a href="https://medium.com/u/33e7ad22b437">Kathryn Hing</a>, <a href="https://medium.com/u/fdf23eb06003">Yegor Zakharov</a>, <a href="https://medium.com/u/bc02b1821659">Andy Jakubowski</a>, <a href="https://medium.com/u/3a3941635fa1">Matteo Cavucci</a> — I truly appreciate your help.]</p><h4>More UX Articles from Oriol Bedia</h4><ul><li><a href="https://uxdesign.cc/how-to-know-your-users-needs-2d24fb92a01e">How to Know Your Users’ Real Needs?</a></li><li><a href="https://uxdesign.cc/https-medium-com-oriolbedia-empathy-wont-help-designers-grow-5d8ea087d72f">Empathy won’t Help Designers Grow</a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb71d85c4a2f" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/lipstick-on-a-ui-eb71d85c4a2f">Lipstick on a UI</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[How Can Design Organisations Innovate?]]></title>
            <link>https://medium.com/@OriolBedia/how-can-design-organisations-innovate-12fc0d0826ee?source=rss-8e055a9d662c------2</link>
            <guid isPermaLink="false">https://medium.com/p/12fc0d0826ee</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[cocreation]]></category>
            <dc:creator><![CDATA[Oriol Bedia]]></dc:creator>
            <pubDate>Thu, 28 Apr 2016 12:09:15 GMT</pubDate>
            <atom:updated>2016-04-30T07:31:21.797Z</atom:updated>
            <content:encoded><![CDATA[<h4>Co-creating a culture of value — Pt 2</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hPJwSdCjo089piFsf2CeUQ.jpeg" /></figure><p>In a <a href="https://medium.com/@OriolBedia/how-can-design-organisations-innovate-8288f5fa7c16#.odlkz526q">previous article</a> I talked about how to design organisations can foster innovation by increasing the team engagement along the design process.</p><p>The cornerstone to that engagement is what I call robust value, which encourages a culture of purposeful communications within multidisciplinary teams to grow shared ownerships as the project develops. <strong>Team members are the first people that have to engage with the design process to develop valuable and innovative experiences within their products or services.</strong></p><p>This time I’ll talk about how to co-create within organisations, to produce robust value, and how continuous conversations can help teams to focus and iterate on the purpose of design problems.</p><h3><a href="http://www.goodreads.com/quotes/15297-if-i-had-asked-people-what-they-wanted-they-would">Faster Horses. Cars. Faster Cars.</a></h3><p>Design organisations haven’t learned. <strong>They have modern tools and processes, yet operate under </strong><a href="https://en.wikipedia.org/wiki/Fordism"><strong>Fordism</strong></a><strong> principles regarding management, production and delivery.</strong></p><p>Yes, we are all agile but we measure how fast can we ship more software and keep on iterating. Yes, we do user centred design but our user research is biased and validates the ideas we already have. Yes, we do design thinking but we work in silo-based departments with a top-down vision.</p><p>Honestly, who has time for purposeful communication and co-creation?</p><p>It’s likely that if you are reading this article is because you know how it goes on a day-to-day basis: design organisations are often kept busy with work, by which I mean “actual work”, the kind that produces deliverables and design outputs for the project. Despite their pseudo-flat hierarchies, design organisations tend to find a single voice to dictate the product direction and quickly stuff the team with tasks to be ticked off and moved around on the white board. So, what’s the problem?!</p><blockquote>“For the sake of the user, we mastered the art of mistaking productivity for efficiency. Maximising the amount of design solutions, rather than their quality.”</blockquote><p>An efficient and innovative design process is the one that helps your team to keep in mind the design problems, elevating those problems throughout all phases of a project and <strong>considering when to add </strong><a href="https://medium.com/@OriolBedia/how-can-design-organisations-innovate-8288f5fa7c16#.odlkz526q"><strong>multidimensional, differential and constant value</strong></a><strong> along their internal design process. Ideally your design solutions should have a higher quality and value that ultimately improve the project outcomes.</strong></p><h3>It all starts with a “hey”.</h3><p>Co-creation helps multidisciplinary teams to focus and iterate on the purpose of design problems, most importantly, <strong>facilitates an open environment where team members feel included, are eager to participate and are willing to try the new tools and processes that a project may demand.</strong></p><p><strong>The only imperative to co-creation is to use continuous conversation between team members.</strong></p><p>For example along a project development you want to make sure to talk regularly with your team fellows, discuss the made assumptions and compose a shared road map to elevate design problems from different perspectives; motivating the team to efficiently react to change and readjust previously made decisions… please don’t just use Slack, get up and approach people to have a “real chat”.</p><blockquote>“When everything constantly needs approval, you create a culture of non-thinkers.” —<a href="https://twitter.com/jasonfried"> Jason Fried</a>. Founder &amp; CEO at <a href="https://basecamp.com/">Basecamp</a>.</blockquote><p><strong>Encourage and develop a culture of thinkers, where a team isn’t just hustling to solve a design problem, but generating discussions that question *<em>why*</em> a certain solution is the most valid one and which are the alternatives to it.</strong></p><h3>How to co-create.</h3><p>Co-creation is a steady process which is built over time by all team members, iterating on it by making use of conversations. In a nutshell, continuous conversations serve co-creation as a vehicle to motivate multidisciplinary teams to build shared purpose along the project development.</p><p><strong>To co-create and generate robust value over time, your team has to develop their internal design based on:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cFaQB0dHy_gq4VW6_dhwIQ.png" /></figure><h4>1. Reflect</h4><p>Modern design organisations are able to truly integrate failure within their design process as an element that inevitably arises very often. <strong>The question is, how does your team react and learn from failure?</strong></p><p><strong>What’s more, how do you integrate failure as an essential element to foster conversations and generate valuable insight?</strong></p><p>Co-creation helps to harvest a learning culture based on continual reflection-learning. Team members should always be checking what has and what hasn’t worked so well over the last few days, and how they might take these learnings to refine their design process.</p><blockquote>“Continual learning is the simple idea of understanding what did I learn today that I didn’t know before.” — <a href="https://twitter.com/jmspool">Jared Spool</a>. Founder <a href="https://www.uie.com/">UIE</a>, Co-founder <a href="http://centercentre.com/">CenterCentre</a></blockquote><p>Your and your multidisciplinary team have to develop and improve your own methods to detect failure, efficiently integrate the learnings and lately iterate on the actual design solutions.</p><h4>2. Listen</h4><p>If, for time I heard that a designer should be better at coding, brilliant at public speaking or mastering business principles, I earned a bitcoin, I would be rich by now.</p><p>Don’t get me wrong, I love bitcoins and I agree that designers should improve on all these skills… but there is one skill which comes first.</p><p>As soon as designers have an idea, they have a tendency to overhear others and get caught up in their own thinking. Simply put, most of the time designers don’t listen. <strong>That’s why I consider that before designers become better at anything else, they should simply become better listeners.</strong></p><blockquote>“The most effective teams are not those whose members have the highest IQs, but rather those whose members are most sensitive to the thoughts of others.” — <a href="https://twitter.com/alex_pentland">Alex Pentland</a>, <a href="https://www.media.mit.edu/">Director of MIT’s Human Dynamics Laboratory</a>.</blockquote><p>A fundamental step for you to build a fruitful co-creation process is being able to put design assumptions aside, in order to grasp what other team members are saying and openly discuss the design solutions that have been adopted so far.</p><h4>3. Adapt</h4><p>Another relevant aspect of co-creation is adaptability. When talking about internal processes, I can’t exclude leadership. In the case of co-creation I’ll refer to <strong>adaptable leadership.</strong></p><p>Yourself and each team member of a team must be able to self-manage a situation where he or she can contribute with valuable insights. <strong>Adaptable leadership mean that in a constant changing world, no single member can lead at all times and in all situations. Rigid rules are counterproductive for any team.</strong></p><p>This may be specially challenging for conventional team leads, who must facilitate the appropriate conditions and informations to all team members to operate under an adaptive approach; in which everyone is able to hold a greater shared responsibility while growing project ownerships and attachment towards their product or service.</p><blockquote>“Instead of telling employees what to do, senior managers will need to put in place key principles and guiding lights and allow them to act according to their intuition, making sure their workforce has the necessary capabilities.” — <a href="https://www.fjordnet.com/">Fjord</a>. <a href="https://livingservices.fjordnet.com/">The Era of Living Services</a>.</blockquote><p>What’s more, adaptability is an inherited concept of Lean UX, which is based on handling constant change and deciding whether the team needs to pivot in order to improve the actual design solutions.</p><p><strong>One last tip. Make sure that your multidisciplinary team is regularly talking to users to gather qualitative data, as well as quantitative data from usability tests and user research. Ultimately you and every team member will have a better understanding on how to internally adapt and balance to the given risks and possible opportunities.</strong></p><p>If you liked this article, feel free to drop a comment. Meanwhile, you can <a href="https://twitter.com/oriolbedia"><strong><em>find me on Twitter</em></strong></a> writing about design and sharing other random thoughts.</p><p>Cheers,<br>Oriol</p><p>Please tap or click ♥︎ to help to recommend this piece to others.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12fc0d0826ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Can Design Organisations Innovate?]]></title>
            <link>https://medium.com/@OriolBedia/how-can-design-organisations-innovate-8288f5fa7c16?source=rss-8e055a9d662c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8288f5fa7c16</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[cocreation]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Oriol Bedia]]></dc:creator>
            <pubDate>Tue, 16 Feb 2016 14:28:04 GMT</pubDate>
            <atom:updated>2016-02-16T18:42:23.715Z</atom:updated>
            <content:encoded><![CDATA[<h4>Co-creating a culture of value – Pt 1</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PqzBvOKco7ipd_wx0KesUQ.jpeg" /></figure><p>Damn! How many articles have you seen recently about digital disruption, upcoming future trends, the transforming digital landscape, and the Silicon Valley unicorn companies?</p><p><strong><em>Let me count them for you. Too many.</em></strong></p><p>In terms of innovation, it‘s fairly easy to be carried away by the overwhelming amount of advice being handed out. Don’t get me wrong, some articles do a better job than others, and there are valuable pieces of information out there. The problem is there is too much theoretical thinking about the ever-changing digital environment.</p><p><strong><em>The real challenge for design organisations is to foster innovation internally.</em></strong></p><p>Nowadays, it seems most of the design firms that are willing to innovate, read those articles and simply shake the <a href="http://giphy.com/gifs/games-questions-answers-hHcdWtXpNZi1O"><strong><em>Magic 8 Ball</em></strong></a><strong><em> </em></strong>to follow the first convincing answer, expecting to produce immediate innovation, right? — Wrong.</p><h3>So, how do we Innovate?!</h3><p>There is a lot being said about user-centred design, and how important user insights are to developing smart and meaningful design solutions. Agreed.</p><p>But what about the people who are behind the products and services? How do they drive the process to transform those insights into actual design solutions?</p><p>Raising innovation within a design company, requires <strong><em>improving how multidisciplinary teams manage the design-thinking process involved in developing products or services.</em></strong> They are the first people that have to engage with the design process in order to develop engaging and innovative experiences.</p><p>That’s why design organisations that want to innovate must, first of all, learn how their members can <strong><em>internally co-create a shared, differential, and constant value along the design process — what I call, robust value.</em></strong> And just after that, they can externalise that robust value, by shipping it within an innovative product or service.</p><p>In this article series, divided in three chapters, I’ll first talk about <strong><em>robust value</em></strong>. Then, during the second and the third chapter, I’ll tell you about <strong><em>co-creation and its foundations,</em></strong> as the basis to produce robust value.</p><blockquote>“Design creates culture. Culture shapes values. Values determine the future.” — <a href="https://en.wikipedia.org/wiki/Robert_L._Peters">Robert L. Peters</a>, Designer and Principal of <a href="http://circle.mb.ca/news">Circle</a>.</blockquote><h3>Robust Value</h3><p>This sentence from Robert L. Peters really gets my point across: <strong><em>I understand that one of the most important duties of any design organisation is to create traditions.</em></strong> And by a tradition, I mean a tradition as part of a culture that has an inherent value among the members of a design company.</p><p>And that’s why is so relevant that design organisation that want to innovate, develop an internal culture of value — which will ultimately foster innovation.</p><p><strong><em>So, let’s talk about how to do that with robust value.</em></strong></p><p>I define robust value as an extensive concept of value, which is created and shared within multidisciplinary agile teams that produce digital products or services. <strong><em>Robust value, implies that teams must think together and communicate with transparency to become over time a value creating system with a shared ownership. </em></strong>This concept can be used at all stages of a product or service development.</p><p>And why do I call it robust value? Because <strong><em>the more agile teams work on it, the more consistent and solid that value becomes.</em></strong></p><h3>Creating Robust Value</h3><p>The three essential attributes to robust value are:</p><h4>1. Multidimensional Value</h4><p>Multidisciplinary agile teams have a great advantage, because they combine <strong><em>people with</em></strong> <strong><em>different backgrounds and expertise</em></strong>. And yes, this situation gives them the chance to craft multidimensional value, by establishing a broader general vision across the process. That’s why agile teams have to make the most out of their wide expertise, and <strong><em>gather their knowledge around assumptions and from different points of view.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*RSLnRg6kUc1Pf2mkmmiCjA.jpeg" /><figcaption>Ideal set-up of a multidisciplinary agile team, where its members see assumptions from different points of view.</figcaption></figure><h4>2. Differential Value</h4><p>A differential value is an important factor as it’s distinctive in every agile team. It arises naturally as <strong><em>the sum of the diverse knowledge and ways of thinking possessed by the team members.</em></strong> An agile team can profit from their differential value by offering an authentic and genuine vision, <strong><em>which ultimately describes how and why a team adds a particular purpose to the design process.</em></strong></p><h4>3. Constant Value</h4><p>Agile teams have to<strong><em> challenge the purpose of every assumption that they produce at all the stages of a product or service development. </em></strong>The more they challenge their assumptions, the better they will, over time, identify and increase value to their processes and methods. So,<strong><em> when a value is constant, it provides a uniform level of consistency across a full product or service.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*KRA0W5L16R6u3_nGwbYHqg.jpeg" /></figure><blockquote>Authors become value generators and a reason for connecting people. — <a href="http://www.francescofranchi.com/about">Francesco Franchi</a>, “<a href="http://www.francescofranchi.com/designingnews">Designing News</a>”.</blockquote><p>So far you may like the concept of robust value — but you ask yourself, <strong><em>how can agile teams find the grounds to produce and develop robust value?</em></strong> The right answer is co-creation, which I’ll be speaking about in the next chapter. Stay tuned!</p><p>Cheers,<br>Oriol</p><p>This article series is the result of several interesting talks with my dearest friend,<strong><em> </em></strong><a href="https://twitter.com/matteomced"><strong><em>Matteo Cavucci</em></strong></a>. So this one is for you. Grazzie tanti!</p><p>If you liked this article (or didn’t), I’ll be glad to know what are your thoughts about it. Feel free to drop a comment, I’ll respond as soon as possible. Meanwhile, you can also <a href="https://twitter.com/oriolbedia"><strong><em>find me on Twitter</em></strong></a> writing about design and sharing other random thoughts.</p><p>Please tap or click ♥︎ to help to recommend this piece to others.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8288f5fa7c16" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>