<?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 Daniel Spagnolo on Medium]]></title>
        <description><![CDATA[Stories by Daniel Spagnolo on Medium]]></description>
        <link>https://medium.com/@daniel_spagnolo?source=rss-5682ef1b4706------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FFCRiU0HlaUgrQpmYoh_Tw.jpeg</url>
            <title>Stories by Daniel Spagnolo on Medium</title>
            <link>https://medium.com/@daniel_spagnolo?source=rss-5682ef1b4706------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:01:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daniel_spagnolo/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[Overcoming implicit bias in your design process]]></title>
            <link>https://uxdesign.cc/overcoming-implicit-bias-in-your-design-process-f76c90ffb771?source=rss-5682ef1b4706------2</link>
            <guid isPermaLink="false">https://medium.com/p/f76c90ffb771</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[bias]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Daniel Spagnolo]]></dc:creator>
            <pubDate>Thu, 29 Oct 2020 11:12:13 GMT</pubDate>
            <atom:updated>2020-10-29T11:12:13.445Z</atom:updated>
            <content:encoded><![CDATA[<h4>5 steps to start making better products for a diverse audience.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7wKrtOCbgdGsTkFDcfxq8w@2x.png" /></figure><blockquote>“Our comforting conviction that the world makes sense rests on a secure foundation: our almost unlimited ability to ignore our ignorance.”</blockquote><blockquote>― Daniel Kahneman, <a href="https://www.goodreads.com/book/show/11468377-thinking-fast-and-slow">Thinking, Fast and Slow</a></blockquote><p>What’s missing from our perspective of who our users are, and what can go wrong for them, when we’re designing products?</p><p>In the solution space that we researchers and designers occupy, how can we find out what, and who, is missing from our knowledge? What will make our designs just work for a more diverse range of people?</p><h3>Everyone’s personal blind spot</h3><p>One of the things that stops us from creating for our diverse range of users is our own implicit bias. Implicit bias is the involuntary thinking that goes on below your level of awareness, and the shortcut your brain takes to associate feelings and thoughts to someone. Everything you’ve experienced in your life up to this point — the country, culture, and environment you’ve grown up in, from a child up to now — will shape the way you think and feel about others. You’ll instantly, and unconsciously, associate thoughts and feelings about someone purely based on their sexual orientation, race, ethnicity, language, physical appearance, or age without seeing any holes in your beliefs — until somebody else points out these holes, or you intentionally seek out ways to uncover this bias.</p><blockquote>“Scientists estimate that we do 95% of our thinking below the threshold of conscious thought”</blockquote><blockquote>— <a href="https://media.imaxws.com/912/howcustomersthink.pdf">How customers think</a></blockquote><p>All this makes sense for our brains from an evolutionary point of view. If we’d heard constantly from everyone in our tribe that tigers kill people, then we’d understandably appreciate an unconscious shortcut kicking in telling us to scamper if we saw anything that looked like a tiger in the bushes — even if it was just a trick of the light. We’d rather be slightly embarrassed and alive, than poking in the bushes with a stick and eaten. 🐅</p><p>The problem is that our brains have carried over this type of thinking into modern life — taking what you’ve heard directly from family and authority figures, and what you’ve indirectly consumed from media and advertising throughout your life — leading to only having a partial perspective of the world. This perspective of the only world you’ve ever known means that we can easily base our beliefs and decisions entirely on assumptions and perspectives we <strong>think</strong> are true.</p><h3><strong>Implicit bias characteristics</strong></h3><p><a href="http://kirwaninstitute.osu.edu/research/understanding-implicit-bias/">Research</a> states that there are five characteristics of implicit bias:</p><ol><li>Everyone possesses them (yes, even people like <a href="https://www.abajournal.com/news/article/implicit_bias_is_a_challenge_even_for_judges">judges</a> who are meant to be impartial and objective)</li><li>Implicit and explicit biases can reinforce each other</li><li>The implicit associations we hold are not necessarily the same as our declared beliefs or reflect the stances we take</li><li>We tend to hold implicit biases that favour our own in-group (though we can still hold bias against our in-group)</li><li>Implicit biases can be gradually unlearned 🎉</li></ol><p><strong>It’s the last point we should all be celebrating.</strong> By making concerted efforts to <a href="https://www.uxbooth.com/articles/resources-for-eliminating-bias-in-design/">poke holes</a> in our (and our teams) implicit biases we can find ways to make our designs work for a wider spectrum of users and minimise unintentional harm.</p><h3>Five ways to overcome your implicit bias</h3><p>Below I’ve listed five techniques that I’ve started to incorporate into my everyday design process/toolbox to try and uncover the implicit biases that myself, and the people I work with, are unaware of.</p><h3>1. Make personas challenge assumptions</h3><p>This will be the most controversial of things I’m doing at the moment. Everyone seems to have their <a href="https://www.imaginarycloud.com/blog/personas-and-their-jobs/">opinions</a> about personas — are they needed, not needed, or done in the correct way — but at some point you’ll find they’re a useful tool in your work.</p><p>Whether you’re lucky enough to work with a UX researcher, or you do the research yourself, we can always challenge people’s assumptions of your users by making your personas work a little harder.</p><p>A good way to do this is to remove any demographic information to avoid bias about the user from the start. Does your team really need to know that the primary user navigating your interface is a 29yr old female, who lives in London, and has a high income? This all just adds implicit biases to the mix right away.</p><p>What about the persona photo I hear you ask? I’ve been guilty of adding a cheerful stock photo in the past. I then went through a period of removing the photo completely, as I felt a stock photo was bringing preconceived notions of the user to the table. I’ve now started to question this thinking, and have decided to use photos of <strong>real</strong> users — someone who doesn’t meet the stereotypical view of who we think our users are. This is a great way to get your team to question any underlying assumptions when they see someone they don’t expect visually represented.</p><blockquote>“Photos are badly done at least half the time … but the right set of photos can help the (often very male and white) team remember that the whole user base doesn’t look like what they expect.”</blockquote><blockquote>— Kim Goodwin</blockquote><p>If you really don’t have access to photos of your real users then try<a href="http://tonl.co/"> tonl.co</a>. They’re a stock photo alternative company that does photography that challenges the usual stock photo norm of a white person/people laughing at nothing in particular.</p><p>But don’t just stop there. We can also use a name for our persona from an under-represented group as well. A persona is just a representation of the insights we’ve gathered about our users, so present them in a way that broadens everyone’s thinking of your “typical” user.</p><p><strong>A word of warning though:</strong> Don’t just do this as a box-ticking diversity exercise. Make sure you’re doing this to creatively challenge narrow assumptions about your audience and that you’ve actually included under-represented people in your research.</p><h3>2. Facilitate workshops that uncover more</h3><p>Conduct workshops with your team, and others, that challenge assumptions about our users, the product, and expected successful outcomes. Building these “checks and balances” types of workshops into your design process will help you uncover negative outcomes that could happen, but that you and the team won’t see with your “positive-vibes-only” glasses on. 🤓</p><p>Here are some workshop ideas to get you started:</p><h4>The pre-mortem</h4><p><a href="https://hbr.org/2007/09/performing-a-project-premortem">Performing a Project Premortem</a></p><p>Imagine that it is six months later and the project has been a spectacular failure. It hasn’t achieved what the team set out to do at all. Get participants to consider vulnerable, divergent, and under-represented members of your audience, how this product was exploited or used to cause harm to others, or how the product was misused — then get them to silently write down the reasons why and discuss. This helps your team steer away from these outcomes and towards better solutions.</p><h4>8-up sketching</h4><p><a href="https://www.nngroup.com/articles/how-to-get-stakeholders-to-sketch/">How to Get Stakeholders to Sketch: A Magic Formula</a></p><p>This is an oldie, but a goodie. Get eight participants to individually sketch out three ideas in three minutes to a “How might we…?” question. Then move the participants into pairs and get them to combine those six ideas into two sketches. Then each pair shows their two ideas to another pair, who also share their two ideas. Finally these four participants will combine their four ideas into one sketch. At the end of the workshop you end up with two ideas that have a little of everyone’s DNA or lived-experience in them — which will open them up buying into the design/strategy as they had a hand in it.</p><p>The more diverse the people in the room, the better the ideas as well. Get internal people from different departments (marketing, IT, customer service, etc) and different positions (managers, practitioners, juniors, etc). Bring in people from outside the company as well — use a cross-section of your users, especially those users who aren’t usually considered.</p><h4>Different user scenarios</h4><p><a href="https://cardsforhumanity.idean.com/">Cards for Humanity</a></p><p>This is a great online card game I recently discovered (created by the folks at Idean), and requires you to work out how your product can be used by different people with different needs. You’re dealt two cards, the first with a person and their needs, and the second with a situation this person finds themselves in, and your job as a team is to figure out ways your product could change to meet these user scenarios.</p><h3>3. Think accessibility from the start</h3><p><a href="https://a11yresources.webflow.io/category/articles">Articles - a11yresources</a></p><p><a href="https://slack.design/articles/accessibility-a-powerful-design-tool/">Thinking about accessibility</a> from the moment you start designing is going to be immensely helpful to break out of the “designing for yourself” mentality that we can easily fall into. <a href="https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/">As you design</a>, think about how someone with a permanent or temporary disability will be able to use your solution.</p><p>How will people with visual, hearing, cognitive, and motor difficulties use this design?</p><p>How will the environment affect how someone uses the product?</p><p>What are the many ways people could navigate through this?</p><p>Setting up <a href="https://guide.inclusivedesign.ca/practices/TestFrequently.html">regular usability testing</a> with a diverse range of under-represented and disabled people will also help you get away from designing for yourself. There’s nothing more humbling than putting your concepts in front of different people and seeing the idea that “everyone will understand” come unstuck, or seeing someone fail to navigate your product using a keyboard or screen reader.</p><p>Don’t see designing with accessibility from the start as a constraint. See it as something that will help you view your design from different perspectives, which will allow you to make better choices for your broad range of users.</p><h3>4. Explore the “unhappy paths”</h3><p><a href="https://modus.medium.com/who-pays-the-price-of-happy-path-design-36047f00c044">Edge Cases Are Real and They’re Hurting Your Users</a></p><p>Don’t just design for the happy path — find out and explore the unhappy paths as well. Don’t just write off the unhappy paths as an edge case that can be fixed later. These paths are the real-life stress cases that some of your users will go through, and it’s your job to think of, and solve, as many of these now before people are impacted.</p><p>How could people game the system?</p><p>How could they break it?</p><p>Who could use it to somehow harm others?</p><p>These are questions no-one ever really likes to ruminate on — we all want to imagine the wonderful positive impact our product will make and how it will make people’s lives better — but our positive intentions don’t offset any negative impact that can happen through our lack of thought. We can build much more robust and humane products that cater for much more diverse and real-life scenarios for people who aren’t you.</p><p>In an industry that is <a href="https://twitter.com/bgroovey/status/1319398207638601731">obsessed with speed</a> we need ways to actually question if we are heading in the right direction? Exploring the unhappy paths at the start of a project may slow you down slightly, but when you do start to accelerate you’ll know it’s in the right direction. There’ll be less need for reworking and backtracking later when the unexpected happens.</p><blockquote>“Intent does not erase impact”</blockquote><blockquote>— Tatianna Mac (<a href="https://www.youtube.com/watch?v=TzGfBV67Tac&amp;feature=youtu.be">“System of Systems” </a>video)</blockquote><h3>5. Educate yourself / Involve others</h3><p>(Okay I’ve sneakily made this two points, but I think they go together well. 😊)</p><p>One of the best ways to start overcoming implicit bias is to acknowledge that you have them in the first place. Uncover your biases by continually seeking out different points of view, looking at things from a different perspective, reflecting on what you’ve learnt, and committing to seeking out and changing your implicit bias.</p><h4>Educate yourself</h4><p><a href="https://implicit.harvard.edu/implicit/">Project Implicit</a></p><p>Start recognising your own implicit biases by taking a series of online tests. <a href="https://implicit.harvard.edu/implicit/">Project Implicit</a>, by researchers at Harvard, will measure your implicit bias associated with race, gender, sexuality, disability, and age.</p><p>The results will definitely make you stop and question yourself. When I took the association test the result came back that I was more inclined to associate unpleasant words with African-American names and faces, which is an uncomfortable feeling to have to sit with when I consider myself anti-racist.</p><p>Just reflecting on your personal biases means that you will be more aware when you do make snap decisions. Hopefully it will make you pause, and ask some deeper questions such as “Why do I think this?” and “If I looked at this from this different perspective would I still have the same feeling?”.</p><p>Don’t confuse this with constantly doubting yourself though (we’re designers — we do enough of that already 😅), this is more of a continual course correction of your thinking to achieve healthier outcomes for you and your users.</p><h4>Involve others</h4><p>Become a <a href="https://lovehasnolabels.com/actions/at-work">role model to others</a> by making sure that everyone has a voice and that different perspectives are involved in your design process. When running workshops or having conversations with your team and others, make sure that everyone’s voices and perspectives are being heard. This could mean just reaching out to someone in a meeting who’s not being included or following up with them later, to find out their view. Doing something as small as this reinforces that everyone’s opinion matters.</p><p>Also <a href="https://guidetoallyship.com/#the-work-of-allyship">learn to accept</a> that you will be wrong, you will make mistakes, you will say the wrong thing sometimes — and that’s okay. Admit you’re wrong, learn from it, and move on with extra knowledge that you’ve just unmasked a bit more of your own implicit bias.</p><h3><strong>Build better products</strong></h3><p>Obviously there are so many more design methods and tools that can be added to your design process to uncover implicit biases, but hopefully this small selection has sparked your interest in trying some of these methods and techniques.</p><p>For great design to happen we need to be able to reflect on our own implicit biases, uncover where things can break in our work, shift our perspective away from what we’ve always known, and meet the needs of more of our diverse users as early as possible — before unexplored and harmful impacts occur.</p><p>None of us are perfect, and we’re never going to uncover every scenario that could befall a user — but that’s no reason not to try and build better products for our diverse audience. 🙌</p><h3>Want to dive in deeper?</h3><p>Below are some of the great books I’ve read over the years that have shaped my thinking around inclusive design and exploring bias. Definitely add them to your reading list. 🤓</p><ul><li><a href="https://www.goodreads.com/book/show/44432844-ruined-by-design">Ruined by Design</a> — Mike Monteiro</li><li><a href="https://www.goodreads.com/book/show/38212110-technically-wrong">Technically Wrong</a> — Sara Wachter-Boettcher</li><li><a href="https://abookapart.com/products/design-for-cognitive-bias">Design for Cognitive Bias</a> — David Dylan Thomas</li><li><a href="https://abookapart.com/products/design-for-real-life">Design for Real Life</a> — Eric Meyer &amp; Sara Wachter-Boettcher</li><li><a href="https://abookapart.com/products/cross-cultural-design">Cross-cultural Design</a> — Senongo Akpem</li><li><a href="https://mismatch.design/shop/">Mismatch </a>— Kat Holmes</li><li><a href="https://www.goodreads.com/book/show/42238886-mindful-design">Mindful Design</a> — Scott Riley</li><li><a href="https://www.goodreads.com/book/show/41975945-future-ethics">Future Ethics</a> — Cennydd Bowles</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*g7zlZwlrHuwoUd5s" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f76c90ffb771" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/overcoming-implicit-bias-in-your-design-process-f76c90ffb771">Overcoming implicit bias in your design process</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[The clash of accessibility and branding]]></title>
            <link>https://uxdesign.cc/the-clash-of-accessibility-and-branding-cb44e24665e?source=rss-5682ef1b4706------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb44e24665e</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Daniel Spagnolo]]></dc:creator>
            <pubDate>Wed, 17 Apr 2019 13:52:58 GMT</pubDate>
            <atom:updated>2019-04-17T23:33:17.479Z</atom:updated>
            <content:encoded><![CDATA[<h4>Colour contrast: Who wins out?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jJAu2fKOPEh7lGkZMxfwQA@2x.jpeg" /></figure><p><em>Let me take you back to where it all started…</em></p><p>The company I worked for had recently rebranded and the design team was in the midst of incorporating the new brand colours into our shiny design system. One of the goals we had set ourselves was to meet, or exceed, <a href="https://www.w3.org/WAI/perspective-videos/contrast/">WCAG 2.0 AA colour contrast levels</a> (colour contrast needs to be a minimum of 4.5:1 ratio), and now the design team was debating if this standard could be ignored for a particular button.</p><p>The debate was over white coloured text looking better to us than black text on our deep coral accent colour. The black text met contrast standards, but didn’t look that great, while the white text fell well below AA contrast standards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*AwN3AR_M-c8dJ-jRrPDwPg@2x.jpeg" /><figcaption>The white text just “looked better” to us than the black 🤔</figcaption></figure><p>Even though the dark text is the one that passes contrast ratio standards, it just looks harder to see — like the copy is almost falling into the background colour — while the white text seems to stand out more.</p><p><em>So what’s going on here?</em></p><h3>Why care about colour contrast?</h3><p>One of the things that designers should be aware of is how to comply with accessibility standards to include as many people as possible. One way to do this is to ensure our designs have sufficient contrast between text and background colours for people to easily read. This is <em>not just</em> for people who have low vision or certain eye conditions, but also for those with older and cheaper devices, times when there’s direct sunlight or glare on screens, and when we’re in dark environments.</p><p>250 million people world-wide have a visual impairment, which includes anyone from legally blind to having less than 20/20 vision. We also have to remember that visual impairments aren’t just permanent, but can also be a temporary or situational impairment as well — meaning we will all suffer it at some point. A great example of different forms of disability has been put together by Microsoft for their <a href="https://www.microsoft.com/design/inclusive/">inclusive design toolkit</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*-DLj-1Oh17Wqut6J1ZdjHQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*h5-v0-ZaRKSroFrziVjrgw.png" /><figcaption>Different types of vision disability (illustration: Microsoft’s Inclusive Design Kit)</figcaption></figure><h3>What are others doing?</h3><p><em>So getting back to the design team discussion…</em></p><p>Inevitably the question was raised — “Do other companies have a similar problem?”, “What do they do about it?” and “Do they meet AA standards?”</p><p>Obviously the first company we thought of was Airbnb, as they had a very similar coloured button to ours. Whilst comparing yourselves to others should never be the go-to, we were curious to understand what others were doing. I put together a list of other well-known tech companies and looked at their primary button colours with the Sketch colour contrast plugin <a href="https://getstark.co/">Stark</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/1*3XO5RafDIxyqQivDeajpqw@2x.jpeg" /><figcaption>Even well known companies don’t have a button contrast ratio that would pass AA standards</figcaption></figure><p>As you can see a lot of well known companies don’t actually have primary buttons that meet AA contrast ratios. Most of these companies would no doubt have accessibility standards, but when it comes to something as simple as their primary button they fail the minimum contrast test. <em>(Not to pick on only one company here, but you can see that Trainline used to have button colours that met AA contrast standards, but sometime in 2017/18 they actually changed it…for the worse </em>🤔<em>).</em></p><p>I’m sure that every product designer at these companies would be aware of this simple accessibility downfall, but their hands are tied to actually be able to change anything. There could be any number of reasons for this:</p><ul><li>Maybe the branding was put in place long before they were there?</li><li>Maybe marketing has the final say on colours outside of the product UI?</li><li>Maybe they’ve attempted to change colours to be more accessible and couldn’t get internal buy-in?</li><li>Maybe they were just simply told “it’s always been that way” and to move onto more important things?</li><li>Maybe they’ve decided they don’t need to meet AA contrast guidelines (or that an A standard is good enough)?</li><li>Or maybe they’ve done plenty of usability testing and it’s never been mentioned/observed to be a major issue?</li></ul><p>All I can conclude from this is that branding is seen as a higher priority than accessibility…and I get why — visual branding is a big part of what makes a company recognised and loved by people, to change it after people have grown used to it could be seen as too big a risk.</p><p>The only way to avoid these situations is to prioritise accessibility and inclusion at the very start of a company. If you’re one of the very first designers in a company make sure that accessibility has a voice in the early stages so others don’t have to make a choice between accessibility and branding later on — don’t wait for the rebrand to happen to fix it. 😇</p><p><em>…oh…and what happened to the use of our accent button you ask? We decided in the end that it shouldn’t be used and we removed it from our design system. </em>🤓</p><p>While I was writing this, <a href="https://uxdesign.cc/@erickaseastrand">Ericka Seastrand</a> wrote an even better article which asked a similar question — and she’s done a fantastic deep-dive into it.</p><p><a href="https://medium.com/@erickaseastrand/orange-you-accessible-65afa6cf0a2">Orange You Accessible?</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%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/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb44e24665e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-clash-of-accessibility-and-branding-cb44e24665e">The clash of accessibility and branding</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[Monzo smart-oven]]></title>
            <link>https://blog.prototypr.io/monzo-smart-oven-922d0f994b9f?source=rss-5682ef1b4706------2</link>
            <guid isPermaLink="false">https://medium.com/p/922d0f994b9f</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[monzo]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Daniel Spagnolo]]></dc:creator>
            <pubDate>Mon, 14 Jan 2019 16:04:48 GMT</pubDate>
            <atom:updated>2019-01-22T16:06:32.334Z</atom:updated>
            <content:encoded><![CDATA[<h4>Oven-baked cookies are so much better than finance :D</h4><p><em>As part of the interview process with Monzo I was given the challenge to create a crazy Monzo oven experience.</em></p><h3>The brief</h3><p>After a crazy night out, Monzo’s CEO has decided to pivot the company from the financial market to the far more interesting field of kitchen appliances. In ~6 hours put together an MVP for a companion app (iOS) for this revolutionary Monzo oven.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rJR1JoaUatRzqmrdaEh-Kw.jpeg" /><figcaption>The Monzo smart oven app in all its glory (with appearance from coral “oven-thing”)</figcaption></figure><h3><strong>Understanding the problem</strong></h3><p>I started out with trying to understand what user problem the Monzo Oven and app were trying to solve:</p><ul><li>For people who are busy or preoccupied doing other things</li><li>For people who appreciate a home cooked meal want to come home to a cooked meal and appreciate it (the smell and taste)</li><li>For people who want to feel like they’re still contributing to “home-life”</li></ul><p>This really all fell underneath the umbrella of someone who is very busy, but knows they can conveniently cook or bake, while still doing other activities. This then informed the creation of my primary persona (below).</p><h3><strong>Research</strong></h3><p>I did a quick bit of research on the Internet of Things type products and connected ovens to get a quick understanding of the domain. Who knew that ovens were so advanced theses days — some even self-clean 😳 🤯 (what a world we live in!)</p><blockquote>“…living in a smart home with so many connected devices is annoying as hell.” — <a href="https://gizmodo.com/the-house-that-spied-on-me-1822429852">The house that spied on me</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yyHMzRSksIY_DE-YKe6vkA.jpeg" /><figcaption>I looked at June Oven and Nest to get an idea of the competition (direct and indirect)</figcaption></figure><p>Also looking at another “smart oven” called June, I came across this great quote from a review of it:</p><blockquote>“Cooking has always been a highly personal, multi-sensory experience, where trial and error is the only way to become the all-star cook most of us know as grandma.”</blockquote><h3><strong>Back to the user</strong></h3><p>With a little bit of domain knowledge tucked away in my head I went back to really trying to understand who the user could be and what were they trying to achieve.</p><p>What do people do when they cook? Where in the cooking process is the oven involved? What high level tasks can cooking be broken down into?</p><p>I came up with the 4 stages of cooking:</p><ol><li>Deciding what to cook</li><li>Preparing to cook</li><li>Cooking</li><li>Finished cooking</li></ol><p>What then does a user do in each of these stages? This is where I quickly sketched out a very simple journey of someone cooking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8GWBiUASziQCqTcY2WDa7A.png" /></figure><p>This is where I started to see that maybe each of these stages could also correspond to how an app flow could work as well — matching the mental model of the user. 🤓</p><h3><strong>Meet Andy</strong></h3><p>Andy was created as my primary persona type who would be using the app. Obviously he was created with all my own assumptions and biases, but I did make sure to to do sanity check of my thinking with my girlfriend (who loves to cook). 👩‍🍳</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AOwMHWYcfSdSWBwxse0w1w.png" /></figure><h3>So what is Andy doing?</h3><p>To understand how Andy would use this app I sketched two scenario’s for him. Doing this helps me understand the context, environments, external factors, motivations, and mentality that Andy could be going through and how I can improve the flow of the app for him.</p><h4>Scenario 1 — Working from home</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_UkYJjyvAxWPYiuyQWjV8Q.png" /><figcaption>Andy rushing around</figcaption></figure><h4>Scenario 2— Commuting to and from work</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yGuiRGoKDG-sDc_aJxayPw.png" /><figcaption>Andy looking after the family (does he have a wife? 😜)</figcaption></figure><h3>User flows</h3><h4>The vision</h4><p>This is the flow that would cover all of the stages and insights covered in the discovery process. This is always something to have so everyone is on the same page to what direction the product may take.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GnwlI70i1mQJLMkSBQ1m0g.png" /><figcaption>Would an oven that learns your cooking behaviours be creepy? 🤔</figcaption></figure><h4>MVP (or MDP) flow</h4><p>This is the absolute core flow and experience that the user needs to be able to successfully complete their task successfully. It should allow us to learn from it, but also provide value to the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TSltPj-PABGojyl5V1Q_Aw.png" /><figcaption>Green writing: The high-level user tasks. Blue writing: What the app should provide for the user</figcaption></figure><h3>Sketching up the screens</h3><p>Before I start pixel pushing in Sketch I want to have a solid idea of what screens I’ll be creating. This is where all the previous work in understanding who Andy is, what he wants to do, and some of the app use-cases really help. I’m able to quickly and confidently throw screen sketches together, know what is needed on each screen, and know what comes before and after each screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cjQ4mQwWj7q1C46BRFUBnA.png" /><figcaption>I make sure to list what each screen will need next to it based on the user flows and scenario’s</figcaption></figure><h3>High fidelity UI</h3><p>As I worked through designing the UI I made sure to keep at the forefront of my mind what Monzo is currently known for — personality, ease-of-use, and emojis! 😊 I also designed for the iPhone X as I thought this is probably the phone a tech savvy person like Andy would be using.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*snOi6ufQTxbrbEHNQIGhfQ.png" /><figcaption>These are the “ideal” states of each screen</figcaption></figure><h3>Prototype</h3><p>I created a very simple clickable prototype in inVision. One thing that is missing from this prototype is all of the in-between states that I would have normally have also included (eg. what would the screen state look like when a user has set a later start time?). 😅</p><p><a href="https://invis.io/J3FSKUWRVWA">https://invis.io/J3FSKUWRVWA</a></p><h3><strong>Assumptions</strong></h3><p>As with all design projects like this there are a bunch of assumptions I have to make as I go…so here are mine:</p><ul><li>Users will be willing to use an app to cook with an oven</li><li>Users will be early adopters of new technology</li><li>This is a stand-alone kitchen product — it is not connected to other kitchen products…yet 😉</li><li>Users aren’t interested in all the details of the sensors and inputs of the oven — they just want these things to work so they can cook!</li><li>People love Monzo because of their transparency, personality, and community — so the Monzo oven app should have these in it as well</li></ul><h3><strong>Next steps and ideas</strong></h3><p>What could be the next steps to take if this project was actually real? Well let’s gaze into my crystal ball and see: 🔮</p><h4>Challenges:</h4><ul><li>How do you know how something is cooking if you’re blind and can’t see the camera view? (talking thermometer, smell, etc?)</li><li>How do you account for all the different ways people check to see that something is cooked/baked/roasted? eg. springiness of cake, skewering meat, smelling, etc</li><li>What happens if no internet available / dropouts? (bluetooth connection if at home?)</li><li>What would success look like? What metrics can be tracked?</li></ul><h4>Further idea exploration:</h4><ul><li>The oven could work out how far Andy is away from home on his commute (via GPS on his phone) and start cooking when he is at a certain time/distance away</li><li>The oven could link to Andy’s calendar and let him know of quick recipes to cook if he’s busy eg. Coming back from airport, having a dinner party, friends coming over, etc</li><li>The oven “talks” to other connected appliances and can re-order or order certain foods based on consumption and recipes</li><li>The oven starts to learn how you like to cook different foods and adjusts over time to your preferred cooking style</li><li>Based on the weather and time of day the app gives recommendations on what you should cook</li><li>The app provides recipes that are recommended by others in the Monzo oven community</li><li>How could this work with an Apple watch?</li></ul><p>I really had fun putting this together in a day and I had fun in the interview with it as well 😉</p><p><em>I don’t work for or represent Monzo. I’m just a designer who likes to share what I’ve done with others — any critique or positivity most welcome :)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=922d0f994b9f" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/monzo-smart-oven-922d0f994b9f">Monzo smart-oven</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving the online queuing experience]]></title>
            <link>https://blog.prototypr.io/improving-the-online-queuing-experience-67acca9490d7?source=rss-5682ef1b4706------2</link>
            <guid isPermaLink="false">https://medium.com/p/67acca9490d7</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Daniel Spagnolo]]></dc:creator>
            <pubDate>Thu, 08 Sep 2016 14:12:30 GMT</pubDate>
            <atom:updated>2016-09-08T14:12:30.417Z</atom:updated>
            <content:encoded><![CDATA[<h4>A concept to make music ticket purchasing better</h4><p><em>As part of the interview process with Songkick I was given the challenge to create a better music ticket queuing experience.</em></p><h3>The problem</h3><p><strong>Currently, when there is a great demand for concert tickets, fans are placed in an online queue. Sometimes, the queues can take up to two hours and add a lot of stress to the ticket buying process.</strong></p><p>We’ve all been there, our favourite artist is touring and so when tickets go on sale we head online to buy them. Only to be confronted with (queue movie voiceover)… the <em>waiting queue</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bu_QsZzYNCfjOi-kykftgg.jpeg" /><figcaption>Every music fans nightmare…the dreaded waiting queue lottery begins.</figcaption></figure><h3>Breaking down the problem</h3><p>As at the beginning of all of my projects I like to dig deeper into the problem of the <em>why</em>. In this case I used <a href="https://www.wikiwand.com/en/5_Whys">the 5 whys technique</a> to try to understand the reasons fans get stressed while in a waiting queue and <a href="https://www.wikiwand.com/en/Mind_map">mind mapping</a> to visualise everything I could think of about the queuing process.</p><h4>The 5 whys</h4><ol><li><strong>Why are fans stressed in a queue?<br></strong>They don’t know if they will be able to get a ticket.</li><li><strong>Why don’t they know?<br></strong>They’re not getting any clear feedback that makes sense to them.</li><li><strong>Why doesn’t the feedback that is shown help them?<br></strong>It’s not telling them <em>what </em>they<em> </em>need to know.</li><li><strong>Why do they need to know?<br></strong>They are overloaded with unknowns and pressure.</li><li><strong>Why do the feel overloaded and pressured?<br></strong>They have feel they have <strong>no control or certainty</strong> over the process, but also this is something that is a big deal in their lives so there’s a lot of <strong>emotion and passion</strong> attached to the purchase.</li></ol><h4>Mind mapping</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uwmB3ivECuEdcjMsD4B_UQ.gif" /><figcaption>Getting out of my head everything I could associate with ticket queuing onto paper.</figcaption></figure><p>Getting an understanding of the problem led me to the challenges I would need to solve:</p><ul><li>What can I do to reduce the perception of wait-time in a queue?</li><li>How do I make people feel they are in control, and alleviate their concerns and doubts, when they are feeling stressed in a queue?</li></ul><p>These challenges then led me nicely into the research phase and what to focus on.</p><h3>Active time vs Passive time</h3><p>Time can be broken into two phases and people in each of theses phases experience time differently.</p><h4>Active time</h4><p>Time passes quicker in this phase as people are occupied with some kind of mental activity. This does not only have to be a pure thinking process though, like reading a map, but can also be a physical activity, such as running or riding a bike.</p><h4>Passive time</h4><p>Time passes more slowly in this phase as people have no control or choice over the waiting time. Examples of this are when you are standing in a queue or waiting for someone to come and pick you up.</p><p>People usually over-estimate the length of passive time, even if the time that has passed is the same as someone who is in the active phase. An example is if Chris takes ten minutes to cycle to Andy’s house and Andy is waiting for him to arrive, Chris will think it felt like a five minute ride while Andy will say it felt like a fifteen minute wait. Studies have actually shown that a passive wait feels 36% longer than an active wait.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ayAqBnaIjCUFTMs7xUunRQ.gif" /><figcaption>Active time always feels shorter than a passive wait.</figcaption></figure><p>Currently waiting in a ticket queue was purely a passive wait: so I had to work out what active events I could place into the wait to make it feel shorter?</p><h3>Amusement park queue design</h3><p>Waiting in long amusement park lines is a very similar experience to waiting in a online ticket queue so I wanted to understand what methods were employed in the design of these lines.</p><p>After reading through a multitude of articles I narrowed the design of theme park queues down to three methods that I felt applied to online ticket queues:</p><ol><li><strong>Waiting times are displayed<br></strong>The expected wait-time shown is always longer than the real wait-time so people feel happier when they finish in a shorter time</li><li><strong>There is always regular movement<br></strong>This way people always feel there is a sense of progression</li><li><strong>People are made to feel part of a story<br></strong>Being made to feel part of a story is part of the experience — the ticket purchasing stage is just the initial phase, the main phase is the concert, and talking about and sharing the concert experience is the final phase.</li></ol><blockquote>“The memory for the line can be enhanced both by adding positive experiences during the wait and by making the event at the lines termination incredibly positive”</blockquote><blockquote>- Donald Norman</blockquote><p>Reading through these articles also introduced me to David Maister and his work on the psychology of waiting times.</p><h3>Maister’s list</h3><p>Harvard school professor David Maister wrote the paper “<a href="http://davidmaister.com/articles/the-psychology-of-waiting-lines/">The psychology of waiting lines</a>” in 1985 (they still hold true today) and it lists eight propositions for the psychology of waiting in line.</p><ol><li>Occupied time feels shorter than unoccupied time</li><li>People want to get started as soon as possible</li><li>Anxiety makes waiting longer</li><li>Uncertain waits are longer than known waits</li><li>Unexplained waits are longer than explained waits</li><li>Unfair waits are longer than equitable waits</li><li>The more valuable the service the longer people are willing to wait</li><li>Solo waits feel longer than group waits</li></ol><p>Being able to answer each of these propositions I felt would be a great way to leave the ticket buyer with a positive and stress free memory of the queue waiting experience. So in what ways could I incorporate each of these propositions into my concept?</p><p>First though I needed to know who I would be designing for…</p><h3>The creation of an assumptive persona</h3><p>Songkick had only just been through the process of selling tickets to Adele concerts and throughout there had been numerous frustrations expressed online by fans.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VUCQUnbRKrGkSSh3amOuKw.jpeg" /><figcaption>Complaints and frustrations about the Songkick queuing process were everywhere online.</figcaption></figure><p>I spent some time going through tweets, Adele fan blogs, news stories, and reading reviews left by fans about the purchasing experience on the <a href="https://uk.trustpilot.com/review/www.songkick.com">Trustpilot</a> website. This helped me build up the assumptive persona of Millie and made sure that she was actually based on real people.</p><h3>Meet Millie — A true Adele fan</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r8FI6kHiMjPf3OnWEaAd0g.gif" /><figcaption>I can’t let Millie down with my concept…she needs those tickets now!</figcaption></figure><h3>Moving the flow around</h3><p>Sketching out the current Songkick ticket purchase flow and seeing where the queue flow was inserted (when required) helped me gain an overview of the whole process and see if there were any changes that could be made.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TJzBr7aJ09E4Ng-sDix76Q.gif" /><figcaption>Bringing the purchase screen forward in the process would become the active start phase.</figcaption></figure><p>Getting this high-level view allowed me to see that if I moved the purchase screen details to the beginning of the queue flow (instead of the ticket buyer having to do it at the end as currently done) then it would allow the queuing to start off with an <strong><em>active</em> <em>wait</em></strong> phase.</p><h3>The ideas wall</h3><p>As I was working through the research and discovery phase any ideas that I had I would quickly write on a post-it note and stick up on my lounge room wall <em>(the wall’s fine Mr landlord!)</em>. At the end of this phase I added and removed ideas, then grouped all similar ideas together to come up with methods of how I would address Millie’s frustrations and needs and also Maister’s list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AyIdsMAodJESLyp5PvRuLQ.jpeg" /><figcaption>Messing up the lounge room wall with ideas on post-its</figcaption></figure><p>This wall of ideas became the features I would incorporate into my concept:</p><ul><li>Progression bar</li><li>Expected wait-time</li><li>Position in queue</li><li>Bringing the purchase details forward in the flow</li><li>Give each ticket buyer a unique queue position ID</li><li>Ask the ticket buyer for mobile number to send queue updates texts</li><li>Use artist fact and quiz cards throughout the wait</li><li>Introduction of a character to bring an positive emotional feel to the flow</li><li>Use positive affirmation messages at certain points in the flow to keep ticket buyer encouraged and alleviate concerns and doubts</li><li>Finish with a positive ending to the waiting experience</li></ul><h3>Queue timeline comparison</h3><p>Comparing the new waiting queue timeline to the current version shows how I implemented active wait phases into the original passive wait to help the time in the queue pass quicker.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jjaifGIJJtaMooGyGEBsHw.gif" /><figcaption>A passive wait the whole time…ugh!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JvsOeWp9VmDSPYIn8ADc2g.gif" /><figcaption>Putting active events within the passive wait-time…yay!</figcaption></figure><h3>Millie’s scenario</h3><p>I chose to storyboard a scenario form Millie’s life to help define how the vision of the concept would work in a real-world situation. This helps to not only keep myself in-check (as I can continually keep referring back to this to make sure I’m not adding superfluous features), but is also great to help others understand how the concept will help their customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5_q3xexrKtVKv9uevCfDaA.gif" /><figcaption>Millie’s overcoming her obstacles while at work.</figcaption></figure><h3>The waiting queue flow</h3><p>Using the scenario as a basis I was able to sketch out user flows. These help me think about the ticket buyers decisions, the major parts of the concept, how these parts join together, and what happens if errors occur.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vfSiFIS3tzTAZiWQkTg5jA.gif" /></figure><h3>Sketching out the concept</h3><h4>Layout</h4><p>Using the current Adele page that Songkick employs I looked at what could be added or removed, what screen requirements would be needed for this concept, and how it could look on mobile and desktop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J9p-cSJS8W_ywn9jLZ-ZAQ.jpeg" /><figcaption>Sketching out the requirements for the screens</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oe-CWa6UtL6_3VXIWS5gJQ.jpeg" /><figcaption>Sketching out various different mobile views</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*04PsZQuU3r8IpP8A7DeqZw.jpeg" /><figcaption>Two more sketched versions of the mobile view with a desktop version</figcaption></figure><h4>Card system</h4><p>With the card system sketches I wanted to work on the layout of the cards, the language that could be used, and how the character I created would bring a positive feel to the flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*31hgBd4K5TLs-Q_iAWGeDA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FHJHBauO-HtF35QTFsDPNw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*vy30clHT--yrCUGobe8LIw.jpeg" /><figcaption>Sketching out the card layout, flow, and character poses/expressions</figcaption></figure><h3>Wireframing and Prototyping</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B_V1oGZdIEAsvDUCPjbbBw.png" /><figcaption>The whole flow can be seen in the prototype (see below for url).</figcaption></figure><p>I made a low fidelity clickable prototype from the wireframes which could be used for usability testing to validate the concept and discover what ticket buyers did not understand.</p><p><em>Note: I have only shown the wireframes for the entry flow into the queue. <br></em><a href="https://invis.io/GK8JB5K9H"><strong><em>To see the full clickable prototype of the whole flow click here.</em></strong></a></p><h3>Testing and measuring success</h3><p>As part of this concept I also thought about how I would test and measure success (via post-it notes on my lounge room wall again).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g6VlWNc_6O_99ZTmJz7NDQ.jpeg" /></figure><p>In my own personal brainstorming session I tried to figure out what would be the one qualitative and one quantitative metric I could use. Using the Google ventures <a href="http://www.dtelepathy.com/ux-metrics/#intro">HEART metrics</a> framework I was able to get to three good metrics.</p><ul><li><strong>Happiness of the user<br></strong>How does the ticket buyer feel towards the experience towards the end of the process? This could be done by having a question asked on one of the cards to keep a consistency and flow.<br><em>I felt that measuring this after they had got the tickets would skew the results towards positive as they had just completed their goal.</em></li><li><strong>Task success</strong><br>How many users make it through or drop out at each of the three stages of the progress bar?</li><li><strong>Engagement</strong><br>How many user interact and engage with the payment details and cards while waiting?</li></ul><h3>Answering Millie’s needs and Maister’s list</h3><p>My ambition with this concept was to be able to overcome each of Millie’s pain points and to integrate each of Maister’s eight propositions into the queue waiting concept.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SmMFNk2oA5bGMCy9IrG8AQ.gif" /><figcaption>I think I reasonably answered Millie’s concerns and Maister’s propositions.</figcaption></figure><h3>Moving the concept forward</h3><p>All of this concept still had to be validated of course. By breaking down the whole concept into smaller chunks to validate first ideas that did or didn’t work would be able to be seen sooner and fixed or changed. For instance the purchase details being brought forward in the flow or the progression bar could be tested first.</p><p>There were also other questions and challenges that arose during this project that I never had the time to answer:</p><ul><li>How do you deal with people who have been waiting for tickets for two of more hours?</li><li>What about people who are in the queue and tickets run out before they get to the end?</li><li>How would using this on a mobile work?</li><li>How could this work across devices? Eg. Millie has to leave the office and wants to continue her queue wait process with her mobile?</li><li>What would be the best way to leave a positive ending with the ticket buyers?</li></ul><h3>Reflections on the process</h3><p>Designing a concept by myself I find is an unusual experience, especially when I am so used to collaborating with other people when doing this in a commercial context. Without that external check on your own biases and introduction of other ideas there is always the danger of just designing for yourself. One way to combat this I find is to make time for discovery and research at the beginning. This allows a better understanding of the problem and who the users of the product may be, therefore cutting down on designing within my own personal echo chamber.</p><p>I’d also love it if online ticketing companies could come up with other ideas to rectify the queue waiting problem. Even an implementation of some of my concept ideas would make the experience slightly more tolerable. <em>Show the customer that you actually do think about their experience and care enough to make it better.</em></p><p><em>I don’t work for or represent Songkick. I’m just a designer who likes to share what I’ve done with others — any critique or positivity most welcome :)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67acca9490d7" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/improving-the-online-queuing-experience-67acca9490d7">Improving the online queuing experience</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Selfie postcard app]]></title>
            <link>https://medium.com/@daniel_spagnolo/selfie-postcard-app-b9edbea5caa3?source=rss-5682ef1b4706------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9edbea5caa3</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-challenge]]></category>
            <dc:creator><![CDATA[Daniel Spagnolo]]></dc:creator>
            <pubDate>Thu, 11 Aug 2016 15:30:46 GMT</pubDate>
            <atom:updated>2016-08-11T15:30:46.678Z</atom:updated>
            <content:encoded><![CDATA[<h4>iOS</h4><h3><strong>The brief</strong></h3><p><strong>Imagine a mobile app where you can take a selfie on the go and send a print to someone using a print company.</strong></p><p><strong>Duration: </strong>14 hours (spread over a week)</p><p><strong>Tools used: </strong>Pencil and paper, Google sheets, and Sketch</p><h3>My perfect process</h3><p>The following are the methods and process I would like to have used if given the perfect environment (does this ever happen?).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X6fMhjp0uFux71ZKZ6p9lQ.png" /></figure><h3>Back to the brief…</h3><p>The use context of the app being “<em>on the go</em>” was the most important aspect of this brief to me and my interpretation meant a product that:</p><ul><li>Is quick and simple to use</li><li>Let’s you get straight back to what you’re doing</li></ul><h3>Exploring my understanding</h3><p>I started out with some mind mapping to brainstorm any ideas related to a selfie postcard app and breaking the main users into three groups: the selfie taker, the selfie postcard recipient, and the printing company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*VC-tzLLiVLi3oL684BQ5mw.jpeg" /></figure><h3>Task analysis</h3><p>Creating a task analysis of how I thought a user would step through the whole process, from taking the selfie to purchase completion, raised the main concerns and issues I thought I really needed to solve with this app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sv8JSHPpBrGD7RtoYzECZA.gif" /></figure><p><strong>Main issues/concerns to overcome for the user:</strong></p><ul><li>What if I <strong>can’t remember</strong> someones postal address?</li><li>How can I <strong>easily and quickly pay</strong> while “on the go”?</li><li>Can I <strong>personalise</strong> my selfie?</li><li>How can I send a selfie postcard <strong>right now</strong> while I’m “on the go”</li><li>How do I know that my friend/family has received my postcard?</li></ul><h3>The competition</h3><p>I also looked at what companies within this space were doing (good and bad) to find any opportunities to differentiate this product.</p><p><strong>Opportunity:</strong> An app that can be used quickly and easily <em>in the moment.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mJZ8acP2EVHFLcVNNpR7wg.jpeg" /><figcaption>A very quick and dirty competitor analysis</figcaption></figure><h3>Creating a persona</h3><p>Before I start any project I want to know who is the primary user I will be designing for and what they want from this product. In this case I put together an assumptive persona of someone I thought would be using this app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MFQuMGGbduddLzKuWAJsZw.gif" /></figure><h3>What is Ashley’s story?</h3><p>I also wrote a scenario for Ashley so I could think about the main context of use for this app and how outside and internal factors would influence her. I would usually draw a storyboard of how this app would help Ashley at this point to help communicate the vision of the product to others.</p><h4><strong>Environment</strong></h4><ul><li>Jungfrau in the Swiss Alps</li><li>Travelling with some fellow backpacking friends</li></ul><h4>Mentality</h4><ul><li>Living in the moment and doesn’t want to have to remember to do later</li></ul><h4>Motivations</h4><ul><li>To surprise her sister with a selfie postcard of her skiing</li></ul><h4>External factors</h4><ul><li>Could be distracted by sun, snow, and friends</li></ul><h4>Event trigger</h4><ul><li>Has just taken an awesome selfie with the the Alps in the background</li></ul><h3>Simplifying Ashley’s task</h3><p>I then went back to my task analysis and thought about how I could simplify each of the stages of sending a postcard to someone if Ashley was using this app. What was the minimum she needed to do to send a selfie postcard and what app interactions could take place to help with this?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CiUpLg3aI8LP1dPDXoQJkw.gif" /></figure><h3>User flow</h3><p>The user flow of how Ashley will navigate the app from taking a selfie to sending the postcard — all on her mobile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BmvWhwTdQDXlajlK4vpmXA.gif" /></figure><h3>Sketching the concept</h3><p>Before putting pencil to paper I listed out what I thought each of the screens and states would be and what elements would go into each of these screens/states. Then it was onto sketching ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ujSG9kxN4nv7BIaOZVjFvA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3BtuK-sTedxH6LMc-hWLmw.jpeg" /></figure><h3>Wireframing</h3><p>The wireframing stage let’s me understand how layout, elements, and copy all work together and look on the screen and in the flow. At this stage in the process I usually like to start some usability testing with the wireframes as well to make sure I’m on the right path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M9VSFPZhekQELF0dvAgtKw.png" /></figure><h3>High fidelity</h3><p>Initially I had the selfie photo (blurred) as the background for most of the screens, but going back to Ashley’s scenario I realised that what was really needed was a simple high contrast UI that could be easily viewed when outside — be it sunny, overcast, or any other conditions. I decided to use a dark on light design with large readable text, icons, and interactions that could be easily carried out by holding it with one hand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wV5hGFvJ-PzwcvYvUEsEQQ.png" /><figcaption>Pictured from left to right: Choose a selfie, view selfie on postcard, and change location tag.</figcaption></figure><h3>Future exploration</h3><p>As with every design project there are a multitude of challenges that come up during the course of the project that you want to solve but they have not been given a high priority (or in this case limited time). The challenges I still want to solve for this project are:</p><ul><li>How will the on-boarding experience work? This flow is crucial in this concept to be able to gather important details to make the “in the moment” experience smoother.</li><li>What happens if wifi / data is unavailable or drops out?</li><li>When audio recording a message are there ways that the user could indicate a new paragraph and make use of emojis? Maybe this recording feature is too complicated and users would just prefer typing?</li><li>What would the text message template say? What would be the tone?</li><li>What about the interactions for other ways to upload a selfie into the app? Eg. The user could upload their selfie to the app straight from the Apple Photos library or maybe they could use Apples 3D touch technology. How would these interactions work?</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9edbea5caa3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CatchApp]]></title>
            <link>https://medium.com/@daniel_spagnolo/catchapp-c241907eec9d?source=rss-5682ef1b4706------2</link>
            <guid isPermaLink="false">https://medium.com/p/c241907eec9d</guid>
            <category><![CDATA[conversational-ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[concept]]></category>
            <dc:creator><![CDATA[Daniel Spagnolo]]></dc:creator>
            <pubDate>Mon, 01 Aug 2016 19:22:03 GMT</pubDate>
            <atom:updated>2016-08-01T19:22:03.805Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VyhSnebyz3BUNV9y7uUSrQ.jpeg" /></figure><h4>The process of designing an app concept</h4><p><em>A design challenge set by FutureLearn (an online learning platform) that was finished over a period of a week (while holidaying in Turkey at the same time!).</em></p><h3>The brief</h3><p><strong><em>Improve the learning experience whilst learning an online course.</em></strong></p><p>Looking at this brief I realised it didn’t really give much to work with in terms of a problem to solve yet. I could have easily sketched up some quick ideas, but without really being aware of what I did and didn’t know yet it would have likely just thrown up issues that somebody with a bit of experience would easily poke holes in. As a designer you need to be able to back up every decision you have made with the <strong><em>why</em></strong> — just saying “um…because I thought it’d look cool?” is not going to cut it.</p><p>From this brief I knew there were two things I needed to understand.</p><ol><li>What creates a <em>learning experience</em>?</li><li>How do people successfully learn?</li></ol><h3>Reframing the brief</h3><p><strong><em>What is a learning experience and how can it be improved when doing an online course?</em></strong></p><p>Reframing the brief this way took it from something broad to being:</p><ul><li>Much more refined and focused</li><li>A better awareness of which direction I wanted to take the research in</li><li>Easily use as a basis for any hypothesis and concepts that came out of my research</li></ul><h3>Down the research rabbit hole</h3><p>Mind mapping is a technique that I always use at the start of a project to get out of my head any connections and ideas I have about the problem and an understanding of what areas I could start researching as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aD7zdx9BpV4hwTxBmXDc2g.png" /><figcaption>Mind mapping out all the ideas and possibilities I can think of that relate to a learning experience.</figcaption></figure><p>From conducting some in-depth desk research and finding research studies and literature I started to get a better understanding around the two questions I had.</p><h4>What creates a learning experience?</h4><ul><li>Social interactions</li><li>Behaviour</li><li>Emotional state</li><li>Environment</li><li>Technology</li><li>Time</li></ul><p>I knew I needed to incorporate each of the experiences into the concept.</p><h4>How do people successfully learn?</h4><ul><li>Sharing and conversing with others</li><li>Reflecting on your own and with others</li><li><strong>Finding inspiration from stories and from people</strong></li><li><strong>Having fun and enjoying the learning journey</strong></li></ul><p>The last two of these points were really something I wanted to explore and thought it would be a great way to inject a bit of fun into the design task as well!</p><p>So how did I begin the process? Well, glad you asked — by trying to understand an online learner.</p><h3>Meet Sandra — The busy Mum</h3><h4>Creating an assumptive persona</h4><p>Even though I did not have access to FutureLearn’s online learners for this project I still needed to have an idea in my head of who a learner may be and therefore able to design for their needs (not mine). Of course on a real-life project you would always validate your assumptive personas as you don’t want to be building something that turns out to not actually solve anything for the customer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*C-jbQsqPxtY44ieGIawKgw.gif" /></figure><p>Sandra had two important needs to be met and some pain points that I needed to solve in this concept.</p><h4>Needs</h4><ul><li>She wants to feel like she is still progressing with her course even when she is busy</li><li>She wants to feel like she has not missed out on important or interesting student online discussions</li></ul><h4>Pain points / frustrations</h4><ul><li>She finds online discussion boards hard to know where to start if not using regularly</li><li>She can get disheartened if she feels that she can’t keep up with her study schedule if busy</li><li>She sometimes finds it hard to grasp new concepts (especially if tired)</li></ul><p>Now I had firmed in my mind who I was designing for I needed an overview of who was currently in the online learning space and what they were doing to help learners.</p><h3>The big two players</h3><p>I discovered that the two big players in the online market were <em>Coursera</em> and <em>edX </em>and so concentrated on working out if and how they may be letting down a learner like Sandra.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*RjvUA0QB0ZhemNpEpp51IA.gif" /></figure><p>The question I asked myself after this analysis was <strong><em>“What is the big difference between FutureLearn and these other players?”</em></strong> The answer? An app of course! (don’t groan). FutureLearn at this stage had no app, they just had a responsive site.</p><p>Looking at this from the point of view of how Sandra learns online I thought these two particular apps weren’t really going to help her in any way as she prefers to:</p><ul><li>Study for a few hours at a time</li><li>Use her desktop / laptop</li><li>Be at home so she can be uninterrupted</li></ul><p>So if I wanted to introduce an app that improved Sandra’s learning then it was going to have to be something different to what was being offered by the competitors.</p><blockquote>What kind of app would someone like Sandra use to help with her online learning?</blockquote><h3>A coincidental moment</h3><p>One of the books I just happened to be holiday reading while in Turkey was <a href="https://www.amazon.co.uk/How-We-Learn-unlock-potential/dp/1447286340"><em>How we learn </em>by<em> </em>Benedict Carey</a>. The book is a fantastic read on the counter intuitive ways that our brains learn and how laziness, ignorance, and distraction can actually help in the learning process…I’ll wait here while you go and order yourself a copy now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/453/1*WtcLNB28Q-hviclNUuxiEg.jpeg" /></figure><p>It was while I was reading this book that I came across something called the <em>percolation process</em>. What is the percolation process? To quote from the book:</p><blockquote>The process of stopping an activity after beginning it and then revisiting it at frequent intervals, which helps to improve and familiarise understanding by having concepts always “percolating” away in the subconscious.</blockquote><p>A little light went off in my head at this stage, I realised if I could incorporate into my concept Sandra being able to revisit a topic after first learning about it then it may well alleviate Sandra’s pain point of sometimes <em>finding it hard to grasp new concepts.</em></p><h3>The concept building blocks</h3><p>I now had the building blocks of how the concept would start to come together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*DMpoOc3KYTO387kCUji1rQ.gif" /></figure><h3><strong>The hypothesis</strong></h3><p><em>Presenting a “snapshot” of the most trending and interesting course related artefacts (discussions, articles, videos, tweets, etc) to an online learner will improve their learning and engagement with the course.</em></p><h3>Telling Sandra’s story</h3><p>With the building blocks of a concept formed and the creation of a hypothesis I really wanted to nail down how I thought this would play out with Sandra in a future scenario. How would it help her achieve her goals of <em>not missing out </em>and<em> feeling like she’s progressing even when busy</em>?</p><p>I have started using storyboarding methods in my process at lot recently as I find it helps to:</p><ul><li>Visually form the product vision that’s in my head</li><li>See if it makes sense to me and show to others to to get a reality check</li><li>Communicate to others how people will use the product</li><li>Quickly get everyone on the same page and avoid different interpretations from happening</li></ul><p>I’ve found Kevin Cheng’s book <a href="https://www.amazon.co.uk/See-What-Mean-Comics-Communicate/dp/1933820276"><em>See what I mean</em></a> indispensable in being able to the heart of storyboarding a vision really well and being able to get the focus the story into a maximum of eight frames for easier communication.</p><blockquote>At that length they’re easy to consume, yet they contain enough information both for internal and external communication — Kevin Cheng</blockquote><p>Before I even start sketching the storyboard I always make sure I know <em>where</em> the story is taking place, <em>how</em> the character is feeling, and <em>what</em> goal she is trying to achieve with the product. I do this by answering the following:</p><p><strong>Environment</strong></p><ul><li>Sandra is commuting to work in the morning on the train</li></ul><p><strong>Mentality</strong></p><ul><li>She is concerned she may have missed things since last time logging into the course</li><li>Thinking about all the things she has to get done today</li></ul><p><strong>Motivations</strong></p><ul><li>Has she missed anything important in the student online discussions?</li><li>She really wants to stay involved with the course even though she is busy</li></ul><p><strong>External factors</strong></p><ul><li>She only has about thirty minutes on the train in the morning</li><li>Distractions from other train passengers</li></ul><p><strong>Event trigger</strong></p><ul><li>Sandra’s been busy for the last few nights marking student exams and wants a quick catchup on what has been happening in her course</li></ul><h3>Sandra’s scenario</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fpl4aF44Aa-QBn8lDcNrdA.png" /><figcaption>Nothing like a good comic to get everyone interested.</figcaption></figure><h3>Content decisions</h3><p>I started to collate what type of course artefacts that I could show in CatchApp and what pieces of data would be the most useful for someone wanting a quick catchup on their course.</p><p><strong>Online course discussion</strong></p><ul><li>Most favourited comment</li><li>Most replied to comment</li><li>Favourite or reply to comment</li></ul><p><strong>Articles / videos</strong></p><ul><li>Course sections most read / watched or favourited</li><li>Other learners recommendations</li><li>Teacher recommended articles / videos</li></ul><p><strong>Motivational</strong></p><ul><li>Quote to inspire learning</li><li>Study tips</li><li>Course progression</li><li>“Pat on the back” content form reaching particular milestones</li></ul><p><strong>Twitter</strong></p><ul><li>Course hash tagged tweets</li></ul><p><strong>Notifications</strong></p><ul><li>Gentle pushes for set study times</li></ul><h3>The modularised flow</h3><p>Now that I had an idea of what types of data I wanted to show for each course artefact it was time to get down to thinking how Sandra’s journey would flow.</p><p>I made each artefact type in the flow modularised so they could easily be moved around, removed, or future modules added. So for instance if it was decided to add a quiz artefact with two or three questions around the subject your studying , then this module could then be easily slotted into the flow wherever it was deemed appropriate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H4EDoWLOD2ilqTniSsj5WA.png" /><figcaption>The app flow concept with different modules colour coded.</figcaption></figure><h3>Jumping on the conversational UI bandwagon</h3><p>I decided to wrap the concept into a conversational UI app experience at around this point in the process taking a little inspiration from the just recently released <a href="http://qz.com/613700/its-here-quartzs-first-news-app-for-iphone/">Quartz app</a>. I really liked how the designers had added a load of personality into the app and I wanted to inject that fun style into my concept as well.</p><h4>Why a conversational UI?</h4><p>This was something I wanted to try out and I thought was really a great opportunity to implement some personality into the app of fun, helpfulness, and motivating. Other reasons to to go in this direction were:</p><ul><li>Use of humanising friendly language</li><li>Mobile texting environment is something just about everyone is familiar with so easy uptake for most mainstream users</li><li>Use of emoji’s to convey a message</li><li>Ability to introduce other module types easily in the future</li></ul><p>I also played around with FutureLearn’s logo to come up with a friendly looking chatbot (or FutureBot as I dubbed him) that could be used in a messenger-style stream and I also sketched a few of the ways the <em>CatchApp</em> content could look.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*tK1meRYkDupuXr5rR48uNw.gif" /></figure><h3>Sandra’s trip through the app</h3><p>For the mockup of the UI I used a card based system within the typical messaging flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t5v4qWWmUSJmOf7QVQ0ztw.png" /></figure><h3>So how does CatchApp improve Sandra’s learning experience?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uF_kToOmGWZvMQRcCi0lgA.gif" /></figure><p>It can be summed up like this:</p><ol><li>Provides a quick “snapshot” of the trending discussions, articles, tweets, etc from her course</li><li>Helps her to learn better (through the percolation process)</li><li>It gently motivates her to complete the course — as she never feels she is “missing out” on something important and becoming less engaged.</li></ol><h3>Reflection on the process</h3><p>I always have a lot of fun with these design challenges, though there are a few really important things that are missing from it. Notably communication with a team containing various disciplines and getting their input into the process, not being familiar with the customers I am designing the solution for, and bringing a load of my own assumptions to the table. Being able to run my own product design process within a limited time also really helps put your product design process to the test and allows you to learn and try new things that you have always wanted to tryout as well.</p><p><em>I don’t work for or represent FutureLearn. I’m just a designer who likes to share what I’ve done with others — any critique or positivity most welcome :)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c241907eec9d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>