<?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 sinem on Medium]]></title>
        <description><![CDATA[Stories by sinem on Medium]]></description>
        <link>https://medium.com/@sinemerdemli?source=rss-3c7b91e7eba3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*lTNFLHB0D29EHzeV.jpeg</url>
            <title>Stories by sinem on Medium</title>
            <link>https://medium.com/@sinemerdemli?source=rss-3c7b91e7eba3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:11:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sinemerdemli/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[Designing a talkative hockey puck]]></title>
            <link>https://medium.com/@sinemerdemli/designing-a-talkative-hockey-puck-dbc2c9f6ec26?source=rss-3c7b91e7eba3------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbc2c9f6ec26</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[sinem]]></dc:creator>
            <pubDate>Tue, 11 Apr 2017 15:20:52 GMT</pubDate>
            <atom:updated>2017-04-11T15:21:06.753Z</atom:updated>
            <content:encoded><![CDATA[<p>You might have read that we had 2 weeks to play around with Alexa and build a sommelier skill to recommend wine pairings to your food.</p><p>There’s been so many blog posts written about the rise of chatbots and Voice User Interface (VUI), <a href="https://chatbotsmagazine.com/2017-will-be-the-year-of-the-killer-bots-c6c3dee2ec38#.h498gbcxl">some</a> even marking 2017 to be the year of the bots.</p><p><strong>This is new territory for both developers and designers. Developers are ramping up their skills to make machines take inputs and make sense of them better, while designers work on making the interaction less mechanic.</strong></p><p>Here are some points that might come in handy when you’re designing the next big Voice Activated App.</p><h3>1 ) Speaking to objects in public is still awkward</h3><p>Machines’ ability to get input and process better than before doesn’t mean it’s ready for public display. Despite the relatively advanced state of VUI’s, most people still feel uncomfortable talking to their phones or to a hockey puck.</p><p>The slightly robotic repetitive nature of the conversation, the high possibility that you’d be the only one on a bus making your shopping list out loud and concerns over privacy make VUI’s have great barrier of entry to public life.</p><p>Despite it being awkward to use in public, Alexa works quite well in private environments. Especially when it’s literally placed in context (i.e. the kitchen or your car), Alexa can make your life a lot better. Wynn hotels have an Alexa in every room to meet all your needs. By doing that they’ve practically given every room it’s own personal butler, with rapid googling skills. Customers are in the privacy of their rooms when arranging a call, asking for champagne or looking up entertainment nearby.</p><h3>2 ) The tools we’ve mastered for screens don’t really apply here</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u-57HpKKXUt5v3tRSFYsVA.jpeg" /><figcaption>Conversation Flowchart for Sommelier</figcaption></figure><p>Imagine all the accounts you have for apps that help your daily design tasks, I’m talking about tools like Sketch, Marvel, Photoshop, After Effects and many more. With screens and interactions gone, the designs we need to work out are in the invisible world of context and speech.</p><p>The powerful niche tools we’ve developed over the years won’t work, but the basics of design are still applicable. Human Centred Design (HCD) provides strong, invaluable tools and methodologies that needs to be applied in a different medium.</p><p>We used storyboards and flowcharts describing conversations as our main “deliverables” over the two weeks. Of course, there was a lot of testing and tweaks that happened over impromptu conversations. The initial vision for how (smart) the conversation would go went through a lot of change as we found out more about Alexa’s limitations and capabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O0kLbZSsSM3t6pxdY84w6g.png" /><figcaption>Script scenarios for different user inputs and Alexa responses</figcaption></figure><h3>3) Most of it is about making the unpredictable less painful</h3><p>We’re all familiar with big red error messages on our screens. Now it’s time to think about them in the context of VUI.</p><p>Speech mostly is linear, and in the context of using apps or websites there’s always an end goal. The goal with handling errors on VUI’s is to avoid errors before they happen. We don’t want to go down a path where users simply have to turn the app of and on again.</p><ul><li>Give an introduction to your app, explain what it’s good for and what users should expect to get out of it</li><li>Repeating the input is great for avoiding errors down the line, identifying miscommunications clearly will help users recover early on and will avoid ending up in a place where you can’t simply reply back.</li><li>Suggest the type of input users are expected to give so they’re not left in the dark thinking about formatting</li><li>Just like any good design practice, allow users to recover from mistakes and errors easily.</li></ul><h3>4) Don’t get too friendly. Acknowledge them as what they are: machines</h3><p>Every interaction, be it on a screen, with an AI or a human, depends on how the actual experience performs compared to the expectations that were set at the beginning.</p><p>Making your ‘intelligent machine’ a little too human would raise users’ expectations to a human interaction level, which is very-very difficult to deliver. Alexa, Siri and even more so with Google Now (as it doesn’t even have a human name), all have a non-human form and a slightly mechanic voice. They’re further away from resembling a primal robot, but not quite human either.</p><p>Humans are complex and unpredictable, aspiring to make a machine act like one is probably going to end up in a weird hybrid that can’t deliver on any point and will constantly disappoint.</p><h3>5) There’s a lot you can do, once you pass the “Hello World” phase</h3><p>Once the conversation evolves and is no longer like talking to a non-english speaker with hearing impairment; it gets to be quite fun. The more comfortable you are speaking to Alexa, the easier it understands you and the more enjoyable the interaction becomes.</p><p>As you establish the limitations and have accurate expectations from what the smart little hockey puck can do, you will start appreciating the clever comebacks and see opportunities to making Alexa a handy companion, who is always ready and eager to help.</p><h3>Resources</h3><ul><li>The Two Paths from Natural Language Processing to Artificial Intelligence<br><a href="https://www.linkedin.com/pulse/two-paths-from-natural-language-processing-artificial-jonathan-mugan">https://www.linkedin.com/pulse/two-paths-from-natural-language-processing-artificial-jonathan-mugan</a></li><li>Prototyping for Voice UI<br><a href="http://www.bbc.co.uk/rd/blog/2016-11-voice-user-interface-ui">http://www.bbc.co.uk/rd/blog/2016-11-voice-user-interface-ui</a></li><li>5 Design Tools for Voice UX<br><a href="https://blinkux.com/blog/5-design-tools-voice-ux/">https://blinkux.com/blog/5-design-tools-voice-ux/</a></li><li>Alexa Skills Kit Voice Design Handbook<br><a href="https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/alexa-skills-kit-voice-design-handbook">https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/alexa-skills-kit-voice-design-handbook</a></li><li>Alexa Skills Kit Voice Design Best Practices<br><a href="https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/alexa-skills-kit-voice-design-best-practices#handling-dialogue-errors">https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/alexa-skills-kit-voice-design-best-practices#handling-dialogue-errors</a></li><li>Listen up: designing for voice<br><a href="https://www.fjordnet.com/conversations/listen-up-designing-for-voice/">https://www.fjordnet.com/conversations/listen-up-designing-for-voice/</a></li><li>Voice Interaction UX: Brave New World…Same Old Story<br><a href="https://www.nngroup.com/articles/voice-interaction-ux/">https://www.nngroup.com/articles/voice-interaction-ux/</a></li></ul><p><em>Also published on </em><a href="http://www.itproportal.com/features/alexa-series-part-one-designing-a-talkative-hockey-puck/"><em>ITproportal</em></a><em> and on Red Badger’s </em><a href="https://red-badger.com/blog/2017/3/8/designing-a-talkative-hockey-puck"><em>blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbc2c9f6ec26" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Personas with context]]></title>
            <link>https://medium.com/@sinemerdemli/personas-with-context-f385e5d0a45a?source=rss-3c7b91e7eba3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f385e5d0a45a</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[sinem]]></dc:creator>
            <pubDate>Mon, 26 Dec 2016 10:57:12 GMT</pubDate>
            <atom:updated>2016-12-26T10:57:12.788Z</atom:updated>
            <content:encoded><![CDATA[<p>The Jobs to Be Done (JTBD) Framework is a powerful tool to understand customer context and innovate for success. In a market place full of distracted, unpredictable humans innovating takes more than knowing your customer demographics, you need to get into their heads and be prepared for the use of your product within the context of your customers’ lives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S7UpsOlwXplhT4ecsEmYzw.png" /><figcaption><a href="https://uxmag.com/articles/love-hate-and-empathy-why-we-still-need-personas">https://uxmag.com/articles/love-hate-and-empathy-why-we-still-need-personas</a></figcaption></figure><p>Personas have been here for a long time, they’ve been used across disciplines for different purposes but at the core they are about the people you’re trying to reach.</p><p>There’s no denying, personas are GREAT. They represent the end users for what we’re building and help us think of them as people rather than numbers on analytics reports. They bring everyone on the same page and help build empathy so the team know what they’re doing and for whom.</p><p>We’ve all been there. We get a brief, immediately hold meetings, talk about our data and build personas by giving names to stock images. These pretty infographics eventually make their way to the project wall and stay there until the blue tack wears off.</p><p>Apart from the very beginning of a project and a few appearances in weekly demos later on, the personas don’t really add much value to shape the course of the product.</p><p>The assumptions we’ve made at the beginning about Jane, who is 35 years old and lives in the suburbs with her 2 kids and husband, don’t really get validated until the product is delivered. At that point there’s very little correlation between Jane’s usage of our product and the fact that she’s a middle aged mother and wife and we can’t even tell whether a particular feature we’ve delivered was successful or not.</p><p>However it’s not Jane’s demographics that will help us deliver value and measure it’s success. The attributes of Jane have very little to do with why she needed that feature and how she would use it.</p><p>It’s time we accept that the persona + user story combo as we know doesn’t really work anymore and we should instead try capturing context for our customers.</p><p><strong>Context is king</strong></p><ul><li>Bananas or doughnuts?</li><li>Depends.</li></ul><p>Unless you have a clear inclination towards one, the choice is always dependent on the context you’re in. Are you hungry or are you in need for some emotional comfort? Is it payday or the end of the month? Did you sleep well or did the baby keep you awake all night?</p><p>Factors like these are the driver to most of our day to day decisions. Whether online or offline, our behaviours are strongly dependent on the context we’re in.</p><p><strong>Doughnuts for ten</strong></p><p>Let’s imagine we own a bakery famously known for making the doughnuts in town. We’re in the process of building an app to even out the demand we see at the shop which is very high in the morning but quite low throughout the day. The feature we’re building is to schedule orders so instead of buying doughnuts in the morning, customers can order them to be delivered midday, when they’ll be eaten.</p><p>There’s one type of customer in our persona list called Jane. Yes, it’s the same Jane I mentioned above. By looking at our data we see that Jane comes to the bakery in the middle of the day every few weeks and buys a box of doughnuts.</p><p>So the challenge for us is to understand why our heroine, Jane, bought a box of doughnuts in the middle of the day? How can we, as a bakery serve her better and potentially make her spend more and often with us? The classic persona structure falls short to explain why and how we might do this.</p><p><strong>Understanding Jane with Jobs To Be Done (JTBD)</strong></p><p>The JTBD, on the other hand, can help us understand Jane’s purchasing behaviour and build the app to serve that particular “job” the box of doughnuts is doing.</p><p>By asking questions like: What was Jane after when she walked into the bakery? Where else could she have that done? What need/ job was she trying to get done?</p><p>It turns out the campaign Jane was leading hit a major milestone that day and she wanted to celebrate with his team. So the job was to celebrate and do something nice for her team. She was on her way to lunch thinking about it and walked into the bakery to get some treats, it just as well could have been cookies from the coffeeshop across the road.</p><p>By rephrasing the user story this way, you open up possibilities to the way you can solve the same problem.</p><p><strong>How to write user stories for Jobs To Be Done (JTBD)</strong></p><p>Instead of going for the classic, that is full of assumptions and irrelevant facts that get dragged in by the persona,</p><blockquote>As a _(user)_ , I want to _(action)_ , so that _(outcome)_ .</blockquote><p>Try rephrasing the user story to include context. It becomes something like this</p><blockquote>When _(context)_ , I want to _(motivation)_ , so I can _(outcome)_ .</blockquote><p>(for more on this check out Alan Klement’s blog post on <a href="https://jtbd.info/replacing-the-user-story-with-the-job-story-af7cdee10c27#.sfxmr0hx8">Replacing the User Story with the Job Story</a>)</p><p>You’ll see that understanding the motivation and context gives a fresh perspective as to what products/services you could include, independent of the app, when and to whom to market them and how to talk about it. You might also find that the Jane’s and the John’s who were different personas are actually trying to “do” the same job.</p><p><strong>So what?</strong></p><p>We should start thinking of the context users of our product/service are in when they are using a particular feature. Writing the user story in a way to capture it will help with generating alternatives to how to help them accomplish that job and give ideas on how we can measure the impact that feature is having. From idea development to measuring success the JBTD framework will be the window to a specific user journey.</p><p>How do you write your user stories? Have you used JTBD? Let me know @sinemerdemli on twitter.</p><p>Also published on the <a href="https://blog.red-badger.com/blog/2016/12/15/giving-personas-some-context">Red Badger blog</a></p><p><strong>References</strong></p><ul><li>A great intro to the framework:<br><a href="https://www.youtube.com/watch?v=f84LymEs67Y">https://www.youtube.com/watch?v=f84LymEs67Y</a></li><li>Wonderful resource on all things JTBD<br><a href="http://jobstobedone.org/">http://jobstobedone.org/</a></li><li>Re-writing user stories for JTBD<br><a href="https://jtbd.info/replacing-the-user-story-with-the-job-story-af7cdee10c27#.pvkh9ji0a">https://jtbd.info/replacing-the-user-story-with-the-job-story-af7cdee10c27#.pvkh9ji0a</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f385e5d0a45a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Corporate Culture - a big pill to swallow]]></title>
            <link>https://medium.com/@sinemerdemli/corporate-culture-a-big-pill-to-swallow-989b2ef73312?source=rss-3c7b91e7eba3------2</link>
            <guid isPermaLink="false">https://medium.com/p/989b2ef73312</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[change-management]]></category>
            <dc:creator><![CDATA[sinem]]></dc:creator>
            <pubDate>Tue, 24 Nov 2015 16:01:55 GMT</pubDate>
            <atom:updated>2016-12-17T23:38:11.824Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mz814n1shYGGq5OIyH2BGg.jpeg" /><figcaption><a href="http://adsoftheworld.com/media/print/financial_times_sharks">http://adsoftheworld.com/media/print/financial_times_sharks</a></figcaption></figure><p>There are a lot of things that feed into the quality of your work life. As social creatures, the culture of our surroundings is one of the most important one.</p><p>Happy employees lead to happy companies, inspired employees make inspiring things. Yet I keep hearing sentences like “Ugh, work is work. I don’t really like it, but why should I?” and that’s always felt terribly wrong. Given we spend more that half of our awake hours at work, the culture at our workplace ends up having a great impact on our wellbeing. It affects our quality of work, our motivation, performance and mental state. Which got me thinking about the big question: How might companies create a place where people like to come back, in fact enjoy spending more than half their lives at? What do employees want from work so that it’s more than just work but also play?</p><p>Organisational culture cannot be built in a boardroom, isolated from the rest of the company and be served across the organisation. That trick simply won’t hold up.</p><p>Influencing social interactions are difficult, once they get going you, as an organisation, have very little control over the knock on effects. There are ways to nudge the direction though, <a href="https://hbr.org/2013/05/six-components-of-culture">John Coleman</a>’s article on Harvard Business Review talks about the 6 building blocks that affect corporate culture which is a good place to start thinking about factors affecting change.</p><h3>1- Vision</h3><p>The simplest foundational element of a culture is it’s vision. It gives purpose to the organisation and the work being done. Knowing what the purpose is also encourages a certain way of decision making. An organisation&#39;s vision statement will not only help orient employees but also communicate expectations to clients and stakeholders.</p><h3>2- Values</h3><p>While the vision statement sets purpose, values provide guidelines on how to get there. Values of a company are practical instructions that set behaviours and encourage certain mindsets.</p><p>Look at what employees feel strongly about, is it consistent throughout the organisation? Does everyone share a set of values which allow them to work harmoniously towards the purpose or do you need to check in with every decision that’s been made and make sure they come from the right place?</p><h3>3- Practices</h3><blockquote>“We are what we repeatedly do.” — Aristotle</blockquote><p>Doing over saying. Evidence of your culture can be seen in ways you do things, the processes you follow, incentives you provide and things you punish. It doesn’t really matter if you repeat your purpose, your values, put them on posters and hang them tall, if you don’t practice what you preach the words will only remain on the wall, they won’t become embedded in your culture and be part of your employees daily life.</p><h3>4- People</h3><p>The people in a company are the ones who make the culture and carry it on. It’s your second family, you see them more than your mom, dad or even your partner. Just like a family, employees that share or have the willingness to embrace the same core values as your company will stick together and support each other no matter what. They will enjoy being together, look forward to spending time with and learn from each other. That’s why cultural fit is a top requirement in recruitment, selecting who you bring in the <em>family</em> is a way to keep feeding your corporate culture but also ensuring that your employees are surrounded by like minded people who share their values.</p><h3>5- Narrative</h3><blockquote>“Any organisation has a unique history- a unique story.”-John Coleman</blockquote><p>All organisations have a history, narratives are powerful tools that tell the organisations story. They feed the culture, and deliver stories about key events that shaped the organisation into what it is now and the values it stands for.</p><p>Cultures feed on narratives, they provide not only a shared view of “what is” but also of “why is”.</p><p>Narratives can be formal, planned and organised or informal, they travel across the organisation and carry culture in narrative form.</p><h3>6- Place</h3><p>Ping pong tables anyone? Or colourful slides welcoming you at the lobby? Office furniture has been the most obvious signifier for corporate culture for quite a while now.</p><p>Our surroundings are invisible cues that trigger certain emotions and mental states. Our monkey brains scan the environment constantly and tell us whether we can relax or should be alert and ready for combat.</p><p>The layout and architecture can be used to facilitate new ways of working, Steve Jobs when redesigning the Pixar office, made sure the facilities like cafeteria and toilets were in a central location to encourage social interaction and spark ideas across team members.</p><p>Office space is the most tangible signals of an organisations culture. Each item along with its location repeatedly tells a story, just like a broken record it repeats a message over and over again. From the motivational posters on the wall, to the office chairs and the carpet. It can make or break the mood of an organisation and determine whether it’s as a place people desired to be in.</p><p>So have another look into your office, what does the lamp tell you?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*EtEcFr0R3FSlxA-Ebx9UBw.jpeg" /><figcaption><a href="http://www.home-designing.com/2011/06/pixars-office-interiors-2">http://www.home-designing.com/2011/06/pixars-office-interiors-2</a></figcaption></figure><h3>Keeping it all together</h3><p>So what do you do with these?</p><p>Just like in everything else, there needs to be consistency. To be able to shape and sustain a solid corporate culture, organisations should make sure the foundations are in the right place and that they work harmoniously. Any discrepancy between the building blocks will lead to mixed messages to employees and have knock on effects to overall business performance. Not to mention, you’ll end up with a big group of unsatisfied, underperforming employees that are constantly at the lookout for the emergency exit to get out the war zone as soon as possible.</p><p>Revisiting the foundation and taking a hard look on your what’s been embedded into the employees day would explain what the culture has become. Easier said than done, organisation can still influence how culture can be shaped, by carefully rethinking the building blocks the workplace can turn into an inspiring place where people want to be and perform their best.</p><p><em>Also on the </em><a href="http://red-badger.com/blog/2015/11/24/corporate-culture-a-big-pill-to-swallow/"><em>Red Badger blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=989b2ef73312" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I don’t like light boxes]]></title>
            <link>https://medium.com/@sinemerdemli/why-i-don-t-like-light-boxes-d5e5afd759eb?source=rss-3c7b91e7eba3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5e5afd759eb</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[sinem]]></dc:creator>
            <pubDate>Fri, 19 Jun 2015 16:07:35 GMT</pubDate>
            <atom:updated>2015-06-29T10:52:07.655Z</atom:updated>
            <content:encoded><![CDATA[<h4>Can’t bloody figure out how they work</h4><p>Light boxes. Popups. Modal windows. Not even sure if they’re all the same or different things. They are for designers a curse and blessing.</p><p>They are a go to solution for minimalist designs, because they they keep the screen tidy. They are magical pockets of secondary information you can hide until they’re relevant.</p><p>I can’t keep the blessing list longer because I have issues with them. Before lying down on a couch and diving deep into my unconscious self, I just want to get it out there.</p><p><strong>They are hard to get rid of. </strong>The magical information box that was pleasant when I needed it turns into an ugly barrier very quickly. It’s like an emotional rollercoaster. I’m happy to see it, but frustrated when I can’t make it go away, do I find a close button, do I click the black emptiness around it, what do I do if I can’t make both work, do I go back hoping it won’t popup again or just give up altogether.</p><p><strong>They are distracting and usually interrupt you.</strong> I’m talking about you sneaky newsletter signup forms, I don’t want to signup when I’m trying to read a post. Please stop harassing me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fC-urirzs7g_lD9HjeazMA.png" /><figcaption><a href="http://imgur.com/r/userexperience/xXHR0">http://imgur.com/r/userexperience/xXHR0</a></figcaption></figure><p><strong>They rarely work well on small screens. </strong>Uhm, have you heard of responsive design anyone? The big chunk of your traffic comes from lovely people who visit your website on their tiny screens, don’t make them struggle. Think about how they feel trying to figure out what to do when they see a black curtain drawn on the tiny text they’re struggling to read with a teeny white box peeking from the corner of their screen?</p><p><strong>They are hidden. </strong>and not so easy to find unless you’ve got a monkey jumping up and down on your keyboard clicking on everything. The secondary information might be just what I’m here for. I’m not here to play hot or cold.</p><p><strong>They are unreliable.</strong> Everyone seems to have a different view of how they work. Finding a way out is the biggest most annoying problem with light boxes. You end up feeling claustrophobic if you’re stuck with it, can’t find the close button and cannot simply get away from it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5e5afd759eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Smooth sailing]]></title>
            <link>https://medium.com/@sinemerdemli/smooth-sailing-ace7ec462635?source=rss-3c7b91e7eba3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ace7ec462635</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[ecommerce]]></category>
            <dc:creator><![CDATA[sinem]]></dc:creator>
            <pubDate>Sat, 06 Jun 2015 11:10:34 GMT</pubDate>
            <atom:updated>2015-06-06T11:10:34.997Z</atom:updated>
            <content:encoded><![CDATA[<h4>Designing businesses for consistent value</h4><blockquote><em>“Improving experience starts with every customer interaction. Your customers see you as a one entity.” -</em><a href="https://medium.com/@JBrezovsky"><em>Jiri Brezovsky</em></a></blockquote><p>This is a quote from his post <a href="https://medium.com/@JBrezovsky/stop-wasting-money-on-a-beautiful-interface-cd86bc41a486">Stop wasting money on a “beautiful” interface</a> it’s about the importance of improving the overall experience, rather than creating beautiful UI. It’s a brilliant and valid point, one which we at Red Badger think about a lot.</p><p>Even though a beautiful design, a high quality piece of software or sky-high conversion rates may seem like the ultimate goal of running a business, especially on a day to day basis, there is one crucial bit that shouldn’t be overlooked. That is to deliver value.</p><h3>I just want you to get the job done</h3><p>As a customer, I don’t care about how well your metrics are doing, whether or not you’ve met your sales goals or when the next software update is due.</p><p>I only care if I can get what I want from you or not. How much do I need to give [time, money, effort] vs. how much I get out of it.</p><p>In the end, if I want to get my hands on a new computer I want to decide which one is for me, where and how to buy it, and how to set it up and who to get in touch when something goes wrong. All of that should be easy peasy, but is rarely so.</p><h3>The times they are a-changin’</h3><p>Businesses have complex structures, they exist on multiple channels, partner with numerous 3rd parties and carry ways of working from the day they were established.</p><p>A business runs with the help of multiple ‘departments’ ranging from marketing, sales, merchandising, customer services, online, suppliers, logistics. There’s also a big board of stakeholders to please with the outcomes.</p><blockquote>“The problem [with designing in silos] is that customers don’t just care about individual touchpoints. They experience services in totality and base their judgement on how well everything works together to provide them with value” -<a href="http://rosenfeldmedia.com/books/service-design/">Andy Polaine et al.</a></blockquote><p>Each and every department has different targets and end-goals. They are usually focused on just one channel or a single touchpoint of the customers overall experience of a customer. The problem arises when the links between these individual touchpoints are left unattended, when they don’t appear on the targets because they are not tangible enough to make it to the boardroom. As a consequence, your customer’s experience with your business ends up being nothing but a broken, inconsistent and painful journey.</p><p>When you think about it there is only one simple <strong>relationship</strong> to focus on, whether you’re in the boardroom, at the shop floor or in the office developing the website; and that is the one between you and your customers.</p><h3>Love thy customer</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vS42sjk7z3FUJTup.png" /></figure><p>When it comes to deciding whether or not to come back, or to ‘recommend the service to their friends’ customers will not think about one interaction in isolation. They will think about how easy it was to use the website, how the staff treated them on the shop floor, they will consider the call they received by customer service team when their package was late all together. Overall their decision will depend on how easy it was to reach their end goal, the whole reason why they chose to get in touch with your business in the first place.</p><p>Keeping the bigger picture in mind at all times will allow you to have meaningful conversations when you’re collecting requirements. It also will give you a reason to talk to each other, regardless of your position in the business.</p><h3>Stop and ask why how who</h3><p>Before you get in your productive autopilot mode, stop and have a think about what the greater goal is.<strong><br>-Why</strong> are you doing what you’re doing?<br>-<strong>How</strong> might you make it better for the person at the other end?<br>-<strong>Who </strong>else might have an effect of the delightful experience you’re trying to create?</p><p>Go speak to your colleagues, your stakeholders, customers. Involve as many parties as you can. Make sure you, as a business, are giving the same message, have the same tone and same level of delightfulness for your customers throughout their journey with you.</p><p>Then and only then will your efforts count for something. Don’t forget, your profit, sales, conversion rates can only improve if you love your customer, try to make their journey with you as happy and valuable as possible because your customer will love you back. (and will most likely recommend you to a friend, if that’s what you’re after)</p><h3>further reading</h3><p><a href="http://www.servicedesigntools.org/">servicedesigntools.org</a> has plenty of methods you can use to think about your business offer as a whole. I would recommend checking them out. Or have a read through Andy Polaine’s book <a href="http://www.amazon.co.uk/Service-Design-Implementation-Andy-Polaine/dp/1933820330/ref=sr_1_1">Service Design</a>, it is delightful and one of the best you can find around.</p><p><em>Note: This post was originally published on Red-Badger’s blog. Check them out they’re awesome.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ace7ec462635" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best thing I’ve done with my life so far]]></title>
            <link>https://medium.com/@sinemerdemli/best-thing-i-ve-done-with-my-life-so-far-8176748a26d1?source=rss-3c7b91e7eba3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8176748a26d1</guid>
            <dc:creator><![CDATA[sinem]]></dc:creator>
            <pubDate>Fri, 15 May 2015 14:38:04 GMT</pubDate>
            <atom:updated>2015-05-15T14:38:04.947Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*hwxcViyhcFDsY45oLmDsZw.jpeg" /></figure><h2>Service design</h2><p>There are moments in life when you make decision, at time they don’t seem to have a particular importance but when you look back, you realise those moments were crucial decision points in your life. The choice you made then was in fact picking one path over the others and it lead you to where (and possibly who) you are now.</p><h4>Soul-scrapers</h4><p>For me that was at the Deloitte office back in Istanbul. In a sky high corporate plaza, I was mid way into my summer internship as a business consultant. I had just graduated form my Industrial Engineering course, had a masters course in Milan starting in a few months time. I had no justifiable reason for why I was filling an application form for the Service Design masters course in LCC. What was expected from me was to go get my shining masters degree in International Management and move on my path as a <em>business consultant.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*PwWbzDXeEXGRTzH-5PZE2Q.jpeg" /></figure><p>Yet I was there, filling out a form without thinking. The applications were closed, normally I would accept that and move on. But this time it was different, I sent an email to the course director, Alison, who still is an incredible tutor and mentor to me.</p><p>I attached my application, asked if I could apply and (almost apologetically) mentioned my lack of design background.</p><p><em>Would I fit in with the rest of the class? Would the design work be too much for my basic photoshop skills?</em></p><p>I didn’t know what to expect from the course but I was excited. I got my offer letter in a few weeks time, I deferred it and still went to Milan. I have no explanation for that, I suppose at the time it felt like a safe choice.</p><p>By the end of the first year I knew I wanted to go find out what that Service Design course was about. I resisted dropping out and completed my masters in International Management. In the 1.5 years I lived in Italy I had a lot of fun, had great food and wine, improved my toddler level italian and made loads of friends.</p><h4>and then I moved to London…</h4><p>I was sitting silently in a room full of architects, graphic designers, product designers as Alison told us about the course, it was the first day and I was terrified. I approached her during the break to make sure I wasn’t mistaken, and if it was still OK for me NOT to be a designer, she laughed and said it was ok. That was somewhat comforting for me, but I was still scared. I had spent all my life in tall glass buildings organised like a stack of cubes. I had been taught how to analyse balance sheets, draw process charts and optimise organisational processes.</p><p>Suddenly I was in this maze like building with flashy posters and photographs on the wall and studios full of colourful canvases. We were given sketchbooks and post-its and were asked to sketch our journey to school.</p><p><strong>I <em>LOVED</em> it.</strong> I loved everything about service design.</p><p>I loved the <em>human centred design</em>, I loved <em>stalking people </em>while they shop to discover their intrinsic shopping needs, I loved <em>visualising interactions </em>with stick figures and doodles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*gQilqfRP-t6Pbo0zV0TVZg.png" /></figure><p>I was amazed by the fact that there were a lot of components in designing services, from cognitive psychology to signalling, information architecture, usability, prototyping...</p><p>Most of all, I loved summing up the insights and outcomes with the <em>customer journey</em>, and the <em>service blueprint</em>. The big flow charts felt familiar but the content, the human centered aspect of it was such a relief.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*r_f8UGOvlID83IMK6BvZTg.png" /></figure><h4>Joining the two ends</h4><p>Until then, I had been taught about how things work from only one perspective: the organisation. It was always about reducing cost, increasing efficiency and profits. Now, it was clear that the one sided view wasn’t enough. It’s more about achieving a balance with business goals and human needs. It was about creating value, and making sure people (and the environment) are happy and healthy.</p><p>They didn’t talk about users in the glass boardrooms, design wasn’t even mentioned. It was a way to make things pretty so that more people would buy the perfectly marketed cost efficient products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*ccokaCcQKfXuATsI4czpWw.png" /></figure><p>That’s not what design is about. I still feel guilty thinking of myself as a ‘designer’. I can’t make pretty visuals, but I know that’s OK. I work with amazing designers, they help me dress up the boxes and arrows, together we make something of sensible and hopefully of value out of it all.</p><p>Design is about linking valuable moments with people, making the context and need fit the offer. Be it a poster, a website, a train journey or a chair. Yes it needs to be appealing, yes it needs to make money but that’s not all there is. I think we’re now starting to understand it. Just look at the considerable acquisitions in the past few months, big consultancies are now after design firms. I truly hope it doesn’t change the was design works, but helps bring the human perspective to boardrooms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/879/1*CjGiM6Ncju6MbahjRnQIsw.jpeg" /></figure><h4><em>It’s the arrows and the boxes. It’s the magic that happens when you let people play.</em></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8176748a26d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Sprint for a retail client]]></title>
            <link>https://medium.com/@sinemerdemli/design-sprint-for-a-retail-client-ebf923da4157?source=rss-3c7b91e7eba3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebf923da4157</guid>
            <dc:creator><![CDATA[sinem]]></dc:creator>
            <pubDate>Sat, 03 Jan 2015 13:27:31 GMT</pubDate>
            <atom:updated>2015-01-03T13:27:31.496Z</atom:updated>
            <content:encoded><![CDATA[<p>At Red Badger, we typically start projects by gathering insights and working out initial concepts. This allows us to understand the users, identify a scope for the project with clients and prepare design assets for development. Also known as ‘sprint zero’, it is an intensive week of absorbing as much as possible and coming up with a plan with the client working with us.</p><p><strong>Project Brief</strong></p><p>We were approached to design and develop a multichannel touch screen that would go in a retail store. Unlike most e-commerce projects, this one didn’t want more sale conversion or higher profits, it technically wasn’t even ‘e-commerce’. The goal was to improve in-store experience and increase customer engagement. Handed over a presentation as the project brief we could almost see the open-ended solution sea in front of us. Just as we were daydreaming about virtual shopping assistants, personalised product recommendations, we were hit by the expected launch date and resource plan allowing only 4 weeks of development and an expected launch in 6 weeks. This was going to be a very short pilot project with possibly many to come. We needed a tangible starting point to validate the concept and iterate as quickly as possible.</p><p><strong>Our Approach</strong></p><p>We decided to run a design sprint to kickstart the project. We wanted to come up with a concept we could test and validate before our developer joined the team.</p><p>The design sprint is an intensive week-long process of problem solving. Google Ventures runs <a href="http://www.gv.com/lib/the-product-design-sprint-a-five-day-recipe-for-startups">Design Sprints</a> for their portfolio companies to be able to make fast and predictable product design decisions. It doesn’t matter if the product/service is brand new, or is looking for a make-over; the whole point of a design sprint is to explore the problem in hand and come up with testable solutions quickly.</p><p>The design sprint combines design thinking principles with the lean methodology. Based on iterations and fast paced decision making and prototyping, the outcomes try to find the sweet spot between the three forces <em>desirability (</em>user), <em>availability (</em>technology), and the <em>viability (</em>marketplace/project scope).</p><p>The one hour planning meeting quickly turned into rapid sketching sessions and before we knew it we were already busy sketching out our ideas.</p><p><strong>Day 1</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*Mxk1jW9dI4Hd8JA3.jpg" /></figure><p>We started with the project brief and went through any material we had available. We looked into the best examples of multichannel implementations in-store, discussed the results from previous user research on customers and mapped out a high level user journey. By the end of the day we had defining keywords for the experience, dozens of bookmarked examples and the rough sketches of our <a href="http://www.fastcodesign.com/1672917/the-8-steps-to-creating-a-great-storyboard">Crazy Eights</a> sketching session.</p><p><strong>Day 2</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*JxSLb20YfN6RKa4x.jpg" /></figure><p>We spent the morning working on the sketches and refining the user journey. The official kickoff with our clients was in the afternoon, which would let us get an initial feedback on everything we had and the direction we were taking.</p><p><strong>Day 3</strong></p><p>By Day 3, we had quite a few sketches so we started to put in a digital format. To get initial feedback on some of our assumptions we used the projector in the office to see how the other Badgers reacted. We grabbed a few developers by the kettle and asked if any of the elements might cause headaches when it came it implementation. UX and Design worked closely at this stage, the transition from sketch to wireframe and then to design was almost at lightning speed.</p><p><strong>Day 4</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*R3jw6NxGhrAlP0rv.jpg" /></figure><p>Day 4 was testing day. We had been itching for some feedback to see if our assumptions were somewhat valid. We went over the wireframes before it was ready for testing. We mocked up a prototype by sticking an iPad and the homepage design on a piece of cardboard and went out for some user testing.</p><p><strong>Day 5</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*OawhGLRAfX0pAGtI.jpg" /></figure><p>By Day 5, the meeting room looked more like a ‘war room’ than anything. We iterated on the wireframes for the 4th time based on the user tests and flagged our technical requirements.</p><p>We had a clickable prototype that linked all screens for our first progress meeting. The meeting went well with positive feedback. Having a clickable prototype helped us discuss features that would have potential development risks.</p><p>By the end of the week we had enough information from users, the client and developers to put together a backlog of epics and list our technical requirements. The overall impact of the design sprint is still to be seen but for now it’s fair to say that it will stick with the Badgers for a while.</p><p><em>Originally published at </em><a href="http://red-badger.com/blog/2014/08/08/the-design-sprint-at-red-badger/"><em>red-badger.com</em></a><em> on August 8, 2014.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebf923da4157" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Tip of the week: Making UX part of the process]]></title>
            <link>https://medium.com/@sinemerdemli/ux-tip-of-the-week-making-ux-part-of-the-process-970d47f0a193?source=rss-3c7b91e7eba3------2</link>
            <guid isPermaLink="false">https://medium.com/p/970d47f0a193</guid>
            <dc:creator><![CDATA[sinem]]></dc:creator>
            <pubDate>Wed, 24 Dec 2014 10:30:56 GMT</pubDate>
            <atom:updated>2014-12-24T10:30:56.434Z</atom:updated>
            <content:encoded><![CDATA[<p>Design has gone a long way. Roles have expanded from being a last minute add ons to product strategy influencers.</p><p>Design is no longer seen as the last step of a process that makes a product <em>look pretty </em>to defining product scope. UX design as a profession has been creeping in businesses, as ‘user needs’ start being taken into consideration at board meetings. Now, managers are actually curious about their target users. They want to understand what makes them tick and what is a turnoff. This is all great, but too early to call it a day and go home…</p><h4>Mom are we there yet?</h4><p>No. We’re still not there yet. We seem unable to shake off the industrial mind set no matter how agile we are. Our industrialised minds are still programmed to deliver efficiently, we want fast returns to our investments and love performance charts that point upwards. We most certainly don’t like cards that go back, against the flow.</p><p>The question is: <em>How can UX and design be integrated in the development process?</em></p><p>At Red Badger, we work in agile. That means we talk to each other all the time (occasionally about work stuff), we change things, we question the decisions we made, check in with users and do it again until it is right. The designers, developers, testers they all sit together and work together.</p><p>However, that process of close collaboration is difficult to capture on the Kanban board. The project board is there for a reason, it should be a mirror to team activities, it should communicate the process and the goal we work towards. But does it really?</p><h4>Out of sight, out of mind.</h4><p>The issue with keeping UX as an isolated step in the process is that once the stories pass through and get closer to Done, the goals change. After a certain point, the goal becomes efficiency and you find yourself focusing on just delivering features, making sure they pass cross platform tests.</p><p>We’ve talked about how crucial it is to keep your personas close,if you haven’t seen that post do it-<strong>here and now.</strong></p><p>We suggested sticking a picture of ‘Bob’ next to your computer, on the wall, by the project board. Somewhere you pass, and will see-daily.</p><p>Always, <em>ALWAYS</em> keep in mind that there will be people using your product (unless of course your target group is animals, insects, aliens..) It is important to have check-ins with users, just like daily stand-ups, weekly progress meetings check-in with the greater goals the purpose of the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hwJWWkhWXc5ZnmGA_vhCXg.png" /></figure><ul><li><strong>Discovery: </strong>This is also a good point to discover why you should get started in the first place. Find out about the strategic goals as well as the technical feasibility. Test the concept, go and get a feel for what the intrinsic needs and behaviours are. What people might like doing, what do they enjoy, who do they follow and most importantly why they do so. Use this space and time to go wild. Explore and question everything.</li><li><strong>UX: </strong>You know the drill here. Use all the wisdom you have to get started.</li><li><strong>Design:</strong> Make sure the design reflects the brand direction, the look and feel is consistent with your intended messaging</li><li><strong>Dev:</strong> Check that the high-tech features make sense to people who will be using the product</li><li><strong>Test:</strong> Try to find out the different use scenarios, validate the assumptions you’ve made</li><li><strong>Done:</strong> Watch usage, do some proper testing, measure and watch behaviour. Use all the data you’ve collected to write up new use cases, start thinking about improvements</li></ul><p>Disclaimer: We’re still testing this out. It’s merely a suggestion rather than a solution- as always. Do try it at your own risk- we suggest collaboration over supervision.</p><p>Until next week..</p><p>Ta!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=970d47f0a193" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What we learned this week]]></title>
            <link>https://medium.com/@sinemerdemli/what-we-learned-this-week-3c560ff0641c?source=rss-3c7b91e7eba3------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c560ff0641c</guid>
            <dc:creator><![CDATA[sinem]]></dc:creator>
            <pubDate>Thu, 04 Dec 2014 14:26:12 GMT</pubDate>
            <atom:updated>2015-06-06T11:11:53.457Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX Tip of the week</h3><h4>Competitive analysis for mobile navigation</h4><p><em>The ‘UX tip of the week” series is a collection of posts written by the UX team at </em><a href="http://red-badger.com/"><em>Red Badger</em></a><em>. To check out all visit the </em><a href="http://red-badger.com/blog/"><em>Badger blog.</em></a></p><p>We started the week with user testing on an e-commerce site. It was all good until we asked people to find something, they had no idea how to work the side navigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*2UKeB5HrPg9Vz5f7huw1Cg.gif" /></figure><p>It became clear that users were struggling with it. You need to stop blaming the user at <em>some</em> point.</p><p>So we went back to the office and got our post-its out. It was time to take a step back and clear our muddy heads. We had been pondering on a particular question for a while:</p><blockquote>How might we make a mega nav useful on mobile?</blockquote><h4>The game plan</h4><p><strong>1-</strong> List out relevant websites that have a similar issue (in our case it was squeezing mega nav content into mobile navigation)</p><p><strong>2-</strong> Collect screenshots, the more you have the more ideas you can “steal” nope not that.. <em>borrow</em>.</p><p><strong>3-</strong> Break down the screens into it’s components. <strong>This is where the mighty post-it comes to play.</strong></p><p><strong>4-</strong>List out Pros and Cons for each. Identify your favourites.</p><p><strong>5-</strong> Sketch out the flow for each, find out how the users are lead to a particular Product Listing Page. How soon do they see the content?</p><p><strong>6-</strong> Compare flows. Visually comparing the flows let you highlight differences at a glance, it helps understanding (and communicating!) what works and what doesn’t.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pud5gARRx0KIsRl3Hzj6tg.png" /></figure><p><strong>6.a-</strong> If you can, go out and test the few examples with people, see if any alternative stands out, find out what people think.</p><p><strong>7-</strong>Show this to any stakeholder, it may be the client, it may be the designers, the dev team.. Talk about the issues users has, show the comparisons, think about what’s possible what needs more exploration..</p><p><strong>8- </strong>Identify what you like, what can be done, with a little help from the favourite features list- and try it out.</p><p>Taking a step back and looking around is useful. You clear your head, benchmark yourself among others and get to spend some play time.</p><p>Try it, you’ll feel better.</p><p>Until next week,</p><p>Ta.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c560ff0641c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>