<?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 Dylan Ortega on Medium]]></title>
        <description><![CDATA[Stories by Dylan Ortega on Medium]]></description>
        <link>https://medium.com/@dylan_ortega?source=rss-a067d126e0d6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*d-KhyFZoUbr8RWYD</url>
            <title>Stories by Dylan Ortega on Medium</title>
            <link>https://medium.com/@dylan_ortega?source=rss-a067d126e0d6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:35:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dylan_ortega/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[Identifying Pitfalls in Your UX Onboarding]]></title>
            <link>https://medium.com/enjoyhq/identifying-pitfalls-in-your-ux-onboarding-c9d6741dbde6?source=rss-a067d126e0d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9d6741dbde6</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Dylan Ortega]]></dc:creator>
            <pubDate>Thu, 20 Sep 2018 08:21:00 GMT</pubDate>
            <atom:updated>2018-10-16T14:10:10.767Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yfjvU6so-j9lJiViVskIMw.jpeg" /></figure><p>It doesn’t matter how visually beautiful your app’s onboarding UX may be if it fails to engage the user quickly and highlight the value of your product. Good design and attractive aesthetics can certainly help, but they are not substitutes for an intuitive, compelling onboarding UX.</p><p>Done right, onboarding UX appeals to the user. It creates a good, memorable first impression in the user’s mind that delights them and keeps them using your product. Without this strong initial engagement, even the best products can be overlooked or abandoned.</p><p>In this post, we’ll be looking at several practical ways you can improve your product’s onboarding UX and create richer, more engaging onboarding experiences for your users. We’ll be looking at several real examples of how different companies approach design choices in their products that you can use as inspiration for your own onboarding UX work.</p><h3>How to Avoid Common Onboarding UX Mistakes</h3><p>Just as no two products are exactly alike, every onboarding UX is unique. That said, we can use real-world examples of onboarding UX to identify some of the most common pitfalls to avoid.</p><h4>Reduce Friction</h4><p>One of the most common mistakes in onboarding UX is focusing on your product’s features instead of reducing friction in the onboarding process itself. It’s as understandable as it is common; after all, we all want our users to be as excited about our products as we are, and reiterating the features that make your product great throughout the onboarding process is one way to create and sustain that excitement.</p><p>However, there’s plenty of time to emphasize how your product’s features can make your users’ lives easier — and the onboarding process is <em>not</em> the time to do it.</p><p>For example, take a look at the screenshot of online image editing tool <a href="https://www.canva.com/">Canva</a> below, taken from Canva’s onboarding UX:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/835/0*klhGWrTEAn-kez0D.png" /></figure><p>After asking users to choose which version of Canva is right for them — an important step in ensuring users are directed into the most relevant pathway — all users have to do to sign up is enter an email address or use the app’s social login function.</p><p>That’s it. Canva doesn’t even ask users to verify the email address they provided.</p><p>This makes for an effortless, streamlined onboarding UX that eliminates friction and removes as many barriers between registration and creation as possible in as little time as possible. Canva really does love great design!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/839/0*5SlZmJaW35o2TJCM.png" /></figure><h4>Design for Discovery</h4><p>In 1981, the U.S. Department of Energy convened a meeting of some of the world’s preeminent anthropologists, behaviorists, engineers, and nuclear physicists to solve a unique problem — how to minimize the risk of exposure thousands of years in the future to nuclear waste stored in the Yucca Mountain Nuclear Waste Repository in Nevada and similar sites. The group was known as <a href="https://motherboard.vice.com/en_us/article/9aey95/radioactive-cats-and-nuclear-priests-how-to-warn-the-future-about-toxic-waste">the Human Interference Task Force</a>.</p><p>With a half-life of more than 700 million years, Uranium-235 — a common element in nuclear weaponry and energy systems — is deadly to all known biological life. As such, it has to be stored securely and safely deep in underground facilities essentially indefinitely, since there’s no safe way to dispose of the highly toxic substance.</p><p>This poses a unique dilemma: What if the meaning of the trefoil symbol, which is universally used to indicate radioactivity, were lost? How can we convey a concept like radioactive waste visually using symbols? Would human beings understand the trefoil’s meaning in 10,000 years? This was the problem that the Human Interference Task Force was asked to solve. (Proposed solutions ranged from the improbable, such as the formation of a monastic order of atomic priests who would oversee nuclear waste storage, to the fantastical, such as breeding genetically modified cats whose fur would change color in the presence of radioactive isotopes.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/341/0*sv1CCiDrFXrW2r3Y.png" /></figure><p>But what do radioactive waste, color-changing cats, and atomic priests have to do with discovery in UX design, you ask? We might not be tasked with warning future generations of the dangers of radioactive waste, but we do tackle similar problems every day in our UX work.</p><p>One of the most common pitfalls in UX onboarding is assuming that the user will innately understand the visual cues you’ve given them. Nothing will stop users in their tracks faster than an unfamiliar symbol, especially if that symbol is crucial to completing the onboarding UX.</p><p>For example, Instagram’s direct messaging function used to be accessed via this symbol:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/0*E3x1pJR7h6FCTaZx.png" /></figure><p>To the uninitiated, the meaning of this icon is far from clear. Most users could probably infer that this icon has something to do with messaging, given the icon represents an old-school inbox document tray, but this is a prime example of how trying to innovate and establish new aesthetic conventions can backfire horribly — particularly among younger users who may never have used a physical inbox document tray. Even if a user keeps using the product, these moments when discovery is interrupted by the unfamiliar can be very jarring, which can leave a lasting negative impression of the product as a whole. Instagram eventually retired this symbol in favor of the current paper airplane icon.</p><p>Google made the same mistake with its Translate web app. Functionally, Google Translate is an excellent product — but imagine how you might feel when presented with the following icon:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/0*NVRHApYqtKoZVJZN.png" /></figure><p>You may already know that this icon accesses Google Translate’s freehand draw function, which lets users write in freehand script the words they want to be translated. This feature is particularly useful when translating Indo-European languages such as Arabic, Hindi, and Farsi. However, for brand-new users, the purpose of this function may not be immediately obvious.</p><h4>Think Harder About Your UI</h4><p>One of the biggest problems with established design conventions is the mistaken assumption that just because a certain UI element is popular or common, it must be the right navigational element for the user.</p><p>Many UX practitioners and UI designers fall back on lazy design conventions when it comes to UI and navigation. Elements such as dropdown and hamburger menus might seem like logical design decisions, but in most cases, there’s almost always a better, more convenient choice that will help users do what they want to do.</p><p>Dropdown menus force users to click multiple times to make a single choice and increase the likelihood of the user making a mistake due to stacking several navigational elements in close proximity to one another. Similarly, hamburger menus might seem like a good idea because they allow us to fit a lot of elements into a relatively small space. However, hamburger menus also make it much easier for the user to forget that certain navigational and UI elements exist by concealing them. And, like dropdowns, hamburger menus also force the user to click multiple times to perform a single action.</p><p>These design missteps are hardly exclusive to small, scrappy startups. Not so long ago, Facebook also relied upon a hamburger menu in its News Feed product in its iOS mobile application. The hamburger menu worked well enough, but Facebook saw a significant lift in <a href="https://techcrunch.com/2013/09/18/facebooks-new-mobile-test-framework-births-bottom-tab-bar-navigation-redesign-for-ios-5-6-7/">engagement, user satisfaction, revenue, and perception of speed</a> among users when it phased out the hamburger menu in favor of a tab bar at the bottom of the interface:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/0*B9WVIx0AeyomTN4h.png" /></figure><p>When designing UI and navigational elements, empower your users by putting choices in clear sight. Users feel more confident when their choices are clearly visible. This not only helps your users feel better when using your product, it also boosts engagement. Not every element can be visible, but we should challenge ourselves as designers and work harder for our users whenever we can.</p><h4>Focus on engagement, not personalization</h4><p>One of the largest shifts we’ve seen in recent years in how we communicate with users and prospective users is <a href="https://blog.freshchat.com/create-a-great-customer-experience/">personalization</a>. Today, most digital communication is personalized to some extent, from dynamic keyword insertion in online advertising to personalized onboarding UX pathways.</p><p>However, just because we <em>can</em> make our products and communications more personal doesn’t necessarily mean we <em>should</em>.</p><p>Personalization alone is no substitute for a well-designed, compelling user experience. However, done right, <a href="https://www.voicesage.com/blog/sms-marketing-guide/">personalization can be a highly effective tool</a>. Online ad retargeting tool AdRoll does this very well with its automated performance report:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/0*ENXYxy2HtoUYa2y3.png" /></figure><p>This completely automated report is sent to AdRoll users every month and provides users with a summary of their performance across several key metrics. However, while many products offer similar functionality, AdRoll goes one step further by providing actionable, individualized recommendations based on a user’s performance report. This not only boosts engagement by empowering users to focus on achieving their personal goals, but also helps users understand how to use AdRoll more effectively by directing users to relevant help documentation if certain metrics are underperforming.</p><h3>Tread Carefully</h3><p>Onboarding UX is unique in that it has to accomplish multiple goals in a very short period of time. In many cases, genuinely innovative, useful products can inadvertently become victims of conventional wisdom by following design conventions that simply don’t make sense for a product or its users.</p><p>As with virtually all aspects of UX, onboarding is a delicate process that can push our skills as UX practitioners to their limit. Hopefully, the examples above have given you some food for thought for your next UX project.</p><p><em>Originally published at </em><a href="https://blog.nomnominsights.com/identifying-pitfalls-in-your-ux-onboarding/"><em>blog.nomnominsights.com</em></a><em> on September 20, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9d6741dbde6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/enjoyhq/identifying-pitfalls-in-your-ux-onboarding-c9d6741dbde6">Identifying Pitfalls in Your UX Onboarding</a> was originally published in <a href="https://medium.com/enjoyhq">Hungry for Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing Internal Feedback Loops]]></title>
            <link>https://medium.com/enjoyhq/managing-internal-feedback-loops-4c87cc332896?source=rss-a067d126e0d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c87cc332896</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Dylan Ortega]]></dc:creator>
            <pubDate>Wed, 19 Sep 2018 15:41:01 GMT</pubDate>
            <atom:updated>2019-02-27T20:03:57.315Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D-AHFwAkguZpi-KfhmlgwA.jpeg" /></figure><p>As part of the product team, you’re under tremendous pressure to deliver impactful products and features that can move the needle across multiple metrics, especially revenues.</p><p>This pressure sometimes shows up in the shape of sales teams pushing for features and changes so that they can win a contract. Sometimes it looks like emails from your executive team. And sometimes it looks like a stream of Slack messages from your marketing team sharing notes on an interview they did with customers last week.</p><p>Those inputs are valuable, to be sure. But you also need to have the space and clarity to look at them with strategic lenses, this is why it is important to find practical ways to help internal teams share their feedback and develop the trust required to know that they are being heard without having to react to that feedback immediately.</p><p>As one of our customers puts it:</p><p><em>Daniel Strazzulla, Product and Research Manager at Contentful</em></p><blockquote>“In every organization there are always hidden channels of communication. For example, you bump into somebody in the kitchen and the person says, ‘Hey, you should fix this thing.’ That feedback tends to be stored in people’s heads, and that creates a false expectation that something is going to be done. People are disappointed as a result.</blockquote><blockquote>These types of interactions, if not managed well, can result in teams not trusting one another, which diminishes collaboration.We spent a lot of time developing a proper understanding of how feedback moved through our organization and lived in our culture. We asked ourselves what the most effective ways to submit feedback were.</blockquote><blockquote>Ultimately, we’re all working on it together, so we need to make sure we’re all focused on the right things.If you push for a different way of doing things, maybe people won’t adopt it because they don’t think it works best for them. For example, if people like to submit feedback via Slack, then you have to find a way to work with that instead of forcing unnecessary changes.</blockquote><blockquote>There’s a reason why people share their thoughts with you in the kitchen. Maybe it’s because they don’t trust the regular channels.</blockquote><blockquote>I think it’s about having empathy with other teams. They are using their own tools and have different workloads and time constraints, so if you make people fill in a form or whatever method you like, you may be adding more complexity to their workflow or discouraging their efforts to share useful data with you.”</blockquote><h3>Mapping your internal channels</h3><p>Mapping your internal communication channels will help you understand where information can fall through the cracks and identify the most reliable channel to capture your team’s inputs.</p><p>It can be as simple as creating a matrix of the teams who provide feedback to the product team, the type of feedback they provide and the channels they normally use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n9bQKr_Mk3s69xbTvL-eGQ.png" /></figure><p>Remember, the goal here is to identify the easiest and most effective channels for internal teams to communicate with the product team. You may want to reduce the number of channels or funnel the information to a <a href="https://nomnominsights.com/product/">central place</a> without making it too hard for the rest of the organisation to share feedback.</p><p>Managing internal channels is only the first step. You want to also communicate how their feedback will be stored and how it will be considered. It goes both ways. You need to design processes that make it very easy to receive and share information both ways.</p><p>Mapping your channels is about more than just reducing information overload for the product team. It’s but also about reducing the anxiety other teams experience about whether feedback has been acknowledged.</p><p><strong>The rule of thumb here is to make it extremely easy to share feedback. Ideally, people won’t have to learn another tool to make it happen.</strong></p><p><strong>PROTIP</strong> 👉 Some of our customers find sending internal feedback via <a href="https://documentation.nomnom.it/article/JjR0aW8wa3-email"><strong>email easier</strong></a>, some use our <a href="https://documentation.nomnom.it/article/8TKJqTYpUN-slack"><strong>Slackbot</strong></a> so people don’t have to leave Slack to share feedback. Some build a <a href="https://documentation.nomnom.it/article/A3WWXkAMY7-typeform"><strong>Typeform</strong></a> or Google form for everybody to send feedback to the product team in a standardised way. Whatever channel you pick, it needs to be based on your understanding of how people currently share inputs and why they pick those channels to do so.</p><p>Once you have agreed with your team which channels to use to share feedback the next step is to build trust.</p><h3>Building trust</h3><p>Lack of trust is a common issue that often stops people from sharing their feedback with the product team. If they feel their feedback will not be heard or considered why would they share it?</p><p>A good way of approaching this challenge is to clearly communicate how their inputs will be stored, analyzed and considered within the product strategy.Client facing teams are not always familiar with the product development process or the prioritization criteria product teams use. It is always important to clarify that sharing feedback does not always mean executing on it. This is where expectations need to be managed.</p><p>If you can communicate how decisions are made within the product organization and how their inputs help that decision making, it is very likely the business will be more receptive to participate and provide their feedback or share feedback from the customers they talk to.</p><h3>Closing the loop</h3><p>Another way of building trust is to consistently close the internal feedback loop. Whenever your teams’ inputs were considered and used in the development process be intentional in sharing that outcome.</p><p>💡Getting internal teams to support your initiatives is not always easy; this is why we wrote <a href="https://blog.nomnominsights.com/the-product-managers-guide-to-change-management/"><strong>The Practical Guide to Change Management</strong></a>.</p><p>Change management is probably the single most important skill a product leader should master in her career. It is the skill that separates the majority from those who consistently and successfully bring together the entire organization to deliver the best product and experiences to their customers.</p><p>Understanding how change management works will transform the way you help your business communicate, how initiatives are prioritized, and <a href="https://blog.nomnominsights.com/the-product-managers-guide-to-change-management/"><strong>how you coordinate multiple departments and agendas</strong></a> within the organization. It is what will help you grow with the business as the business inevitably evolves.</p><p>Want to learn more about feedback loops and customer-driven development? Check us out at <a href="https://getenjoyhq.com/">https://getenjoyhq.com/</a> 👈</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c87cc332896" width="1" height="1" alt=""><hr><p><a href="https://medium.com/enjoyhq/managing-internal-feedback-loops-4c87cc332896">Managing Internal Feedback Loops</a> was originally published in <a href="https://medium.com/enjoyhq">Hungry for Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Spotlight — An Interview with Calliope Georgousi, Freelance UX Researcher]]></title>
            <link>https://medium.com/enjoyhq/ux-spotlight-an-interview-with-calliope-georgousi-freelance-ux-researcher-814a2afabf35?source=rss-a067d126e0d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/814a2afabf35</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[researchops]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Dylan Ortega]]></dc:creator>
            <pubDate>Tue, 18 Sep 2018 07:40:00 GMT</pubDate>
            <atom:updated>2019-02-27T20:05:23.561Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xgk4gMGjqUYZe8wbVYRy5w.jpeg" /></figure><p>Calliope has worked in UX for 5 years, holding a variety of different positions at companies large and small. We had the chance to speak with her about the various UX projects she’s tackled in the past, and where she sees UX in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*T9J8HuIhASYwdrDs.png" /></figure><p><strong>Sofia: Why don’t we start by talking a little bit about your background? What are you doing today, and what have you been doing the last two or three years?</strong></p><p><strong>Calliope:</strong> Today I’m in Hong Kong doing user research with Sutherland Labs. I’m mainly helping the senior researcher here, and essentially what we’re doing is an ethnographic study with the financial clients of Sutherland Labs in order to understand them, see how they use their tools and their processes, especially when it comes to working from home. I’ve been on this project since the end of June/beginning of July, and I will stay on this project until the end of October.</p><p>It’s an exciting moment because after Hong Kong I will be going to Japan, and I will be doing research there along with a senior researcher of Sutherland Labs. After that, I might be joining an airport company as a Manager UX Researcher. It’s an interesting time for me!</p><p>In the last year and a half I’ve been working as a freelancer with mainly startup companies through YunoJuno — they’re a platform for people to find freelance work. And before that, I was working for the government, with BBC, Three, and Accenture.</p><p><strong>Sofia: Some of our customers have internal research teams that struggle with sharing insights across their company. How do you manage the research process and share information?</strong></p><p><strong>Calliope:</strong> I manage the research process in a pretty traditional way — I give recommendations through usability studies and research findings that I’ve put in a presentation or a report document. Sometimes I might have the chance to create a video of usability studies with users so stakeholders can empathize — that’s what people listen to. What I’m hoping to do in my next role is create research museums, where people can actually go into a dedicated place with research walls and learn about findings on their own time, similar to something that Facebook has been doing.</p><p>I’d like to externalize all that information. When I saw what <a href="https://getenjoyhq.com/">EnjoyHQ</a> is doing, I found it quite interesting and intriguing. And I’d like to find out more in terms of how it can surface quotes, or different keywords so that we can support our research and say why we want to go where we want to go.</p><p><strong>Sofia: When you start a research project, how do you get into understanding the background of what the client wants to achieve?</strong></p><p><strong>Calliope:</strong> I start with a brief (if there isn’t one, I will create one and have it signed off) and then I gather existing and related work within the business and conduct an desktop review or competitive review depending on the time and budget of the project. I look for any commonalities that there might be, and start connecting the dots. Once I start to have a proper understanding of what the problem might be, I start thinking about how I can approach it in terms of research methods appropriate to the research problem I am addressing. Obviously, my first thought is to do some usability testing and go from there.</p><p>I will interview people, or we might have some group facilitation, and then I’ll try to collate information. We rely on keywords a lot in order to do affinity diagramming and to try to find commonalities to cluster themes and title those themes. One of the biggest problems that we all have, especially in bigger organizations where they have a lot of archives, is that the work gets lost in disparate locations and difficult to find, so the search function of <a href="https://getenjoyhq.com/">EnjoyHQ</a> looked appealing to me as a researcher.</p><p><strong>Sofia: What is the future of UX research at scale in companies, given that it’s becoming such a strong discipline?</strong></p><p><strong>Calliope:</strong> People are now talking about user research operations. And I see potential there. There was recently a workshop done in Brighton, where we were trying to understand what user research operations would be, if we established constant usability research like DevOps. What are you going to do with that archive? How are you going to assess that information and surface that information that was collected a year ago, or collate and connect that?</p><p>User research teams are starting to organize operations because if you’re running usability tests on a constant basis in your company, you’re going to need certain procedures. You’re going to need somebody who’s going to liaise with the users, find the users, or have an active database of users. You’re going to need somebody who’s going to do the recording of the user videos or the note-taking, somebody who’s going to be archiving everything. And you’re going to have a lot of files. You’re going to have files in Google Drive, in Dropbox, and in email requests.</p><p>You’re going to have people who are responsible for supporting the research, people who are going to be doing the research, people who are going to present on that research, and people who are going to be curating research, all those versions, and managing that content. If you’re going to have constant usability testing, you’re going to need that.</p><p><strong>Sofia: What is your advice for user research teams on the client side to make the most of their research and communicate it effectively?</strong></p><p><strong>Calliope:</strong> It depends on who I’m talking to — if I’m talking to a project manager, I probably need to explain the project to them in their terms. If I’m talking to a CEO, perhaps I could talk to her about why she needs to implement findings in terms of investment (ROI). If I have some findings or recommendations, I need to give those to the client in the shape of an actionable project, perhaps with costs and benefits in mind. It is important to empathize by speaking in their language, make the findings or next steps relevant and actionable. So, it really depends on who you’re talking to, each and every time.</p><p>Therefore you want to consider how to get those findings from research into actionable outcomes and next steps — something that the client can measure, something that they can do. Because a lot of times when we just give them a set of findings and a set of bullet points, but that’s going to reach their archive folder and it’s not going to get out very soon. Getting those bullet points out into actionable outcomes is much more important than adding recommendations.</p><p><strong>Sofia: What are the biggest challenges for UX researchers today?</strong></p><p><strong>Calliope:</strong> Research bias. A lot of times we have to abide by the person who’s giving us the project. So if a stakeholder is giving them the project, a stakeholder is expecting to hear something. We as researchers have to be mindful how we interpret the results and where is the bias.</p><p>Lack of standards and certified skillset. Methodologies are fudged, implemented poorly to cut time and people who get on the wagon of UX but have no related education but an inspiration to do the job. A UX practitioner needs to read and connect with the UX community to develop.</p><p>Lack of business understanding of the importance of the role. Still people are saying, “Yes, we really, really need a researcher. We have all this content. We really need somebody who will come and take it and do something with it.” It’s a trend to have a UX practitioner in your team nowadays. But when I have invited leadership to workshops, they didn’t come; some didn’t even think of cancelling. They don’t always understand how user centric their company could and should be yet, and it is our humble responsibility as researchers to speak their language to communicate that message.</p><p>What I’ve been told from senior researchers is to be patient and keep on doing your work in a consistent way and hopefully, they will start to notice and understand how user research makes a difference in their products and services as a more empathetic and mindful approach to marketing and SEO analytics or KPIs. I think the profession is still evolving even if evolution is slow. We have a lot of ground to win.</p><p><strong>Sofia: It’s hard for me to understand why an organization would invest in building a UX team and then not leverage it — why do you think this happens?</strong></p><p><strong>Calliope:</strong> Well, think of yourself getting a new gimmick or a new tool in the house. A lot of times you might be excited because it’s trendy, because it’s really cool, because other businesses have it. And, you know, if competitors have it, then you must have it, too. But a lot of times they don’t really understand how to utilize us best. I feel that maturity takes time, especially when people and companies are set in their ways. It’s difficult for them to bite that bullet and say, “Okay, you know, let’s make that change.” You know, it’s not easy. Sometimes it is even easier to let that person go than to spend time to understand the value and find ways to collaborate.</p><p><strong>Sofia: What do you think is the advantage of taking a career path like yours — what would you describe specifically as an advantage of actually being in and out of projects with different types of clients?</strong></p><p><strong>Calliope:</strong> I have to tell you that, you know, it hasn’t always been easy. Having worked with many different organisations It has given me a lot of breadth. And sometimes I wanted to dive deeper but I didn’t have the chance to. It has given me the flexibility to take knowledge from one client and implement that into another client. It has given me a lot of dots to connect so I can shape my understanding of the business world and how research done in different ways, if that makes sense. And it has given me a lot of resources and flexibility in my way of thinking. For example, I hear about what you do with <a href="https://getenjoyhq.com/">EnjoyHQ</a> and I’m interested and excited. At the same time, I’m connecting that with my work that is going on at the moment here in Hong Kong and I’m thinking, “Well, you know, how would that solution work for my current client?” And at the same time, I’m also thinking about a past client. “Oh, if I knew that, I would have suggested this.”</p><p>A lot of people have just been working with the same people in the same organization for a long time because it feels secure. Just like any other designer, I think they need to move into new grounds to start thinking anew, to start thinking fresh, to make new connections and paths in their minds.</p><p><strong>Sofia: Let’s say that I am a senior UX professional working for a large company. I don’t have the bravery that you have to go and change jobs, either often or completely. How can I involve myself in an environment where I can see better patterns or different patterns?</strong></p><p><strong>Calliope:</strong> Collaboration. One way to do it is through bringing diversity into your work environment. Collaborate with UX practitioners in different departments. Invite your vendors and collaborate closely with them. Join UX communities and follow their regular events on UX topics. I had the opportunity to bring UX brown bag Fridays when I was in BBC R&amp;D, bringing a UX topic on a video and sit down with designers and developers and have a Q&amp;A chat after the video. We even had conference calls with other UX departments to discuss. Another way to do it is by participating in testing yourself. As in, you be the participant in other usability tests and see how other people do it. Be a mystery shopper, do autoethnography as well. So if there’s a particular technology or something like this, try to take it yourself and create a diary study.</p><p>Observe yourself so you can understand how other people might have felt. There have been studies actually with researchers who even dressed themselves as their potential persona. In order to put themselves into their persona’s shoes. Also improvisation — I think my skills in acting have been transferable knowledge. Where can I improvise? How can I observe and then make connections?</p><p><strong>Sofia: Anything else that you would like to add related to knowledge sharing within the UX environment or making research more accessible to other people in the business?</strong></p><p><strong>Calliope:</strong> I think it’s important for us as researchers to read, read, read, read, read, because a lot of times we’re just doing and doing. But it’s important for us to get back to the books and reflect on our methods and enrich our skillset. Collaborate, see what other people are doing and connect with the community so we can learn from each other.</p><p><em>Originally published at </em><a href="https://blog.nomnominsights.com/interview-with-calliope-georgousi/"><em>blog.nomnominsights.com</em></a><em> on September 18, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=814a2afabf35" width="1" height="1" alt=""><hr><p><a href="https://medium.com/enjoyhq/ux-spotlight-an-interview-with-calliope-georgousi-freelance-ux-researcher-814a2afabf35">UX Spotlight — An Interview with Calliope Georgousi, Freelance UX Researcher</a> was originally published in <a href="https://medium.com/enjoyhq">Hungry for Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing SatisMeter + EnjoyHQ!]]></title>
            <link>https://medium.com/enjoyhq/introducing-satismeter-nomnom-cacc81504547?source=rss-a067d126e0d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/cacc81504547</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[customer-service]]></category>
            <dc:creator><![CDATA[Dylan Ortega]]></dc:creator>
            <pubDate>Thu, 09 Aug 2018 15:03:37 GMT</pubDate>
            <atom:updated>2019-02-27T20:08:51.034Z</atom:updated>
            <content:encoded><![CDATA[<p>Ever since the Net Promoter methodology was developed back in 2003, businesses have calculated their NPS scores to better understand customer loyalty and decrease churn. Nowadays, software makes it easy to gather scores and feedback so you can track NPS data over time and identify trends.</p><p>We’re excited to announce our integration with SatisMeter, the leading platform for capturing NPS feedback from customers. Integrating EnjoyHQ with SatisMeter allows you to consolidate NPS data alongside customer communication from other feedback channels, making it easy to conduct in-depth customer research and find valuable insights.</p><p>When you connect your SatisMeter data to EnjoyHQ, NPS scores and responses are automatically organized alongside any other customer data you send to EnjoyHQ. This allows you to organize your feedback in a repository, where you can highlight important conversations, tag feedback with keywords, and segment your customer research by detractors, passive users, and promoters.</p><p>If you’re already an EnjoyHQ customer, simply navigate to your integrations page and select the SatisMeter icon to get started — you’ll be doing your best customer research in no time!</p><p>If you’re not using SatisMeter yet, <a href="https://app.satismeter.com/register">click here to get started with a free trial</a>.</p><p>If you’re not an EnjoyHQ customer, but want to learn more about integrating your SatisMeter data, <a href="http://www.nomnominsights.com/satismeter">click here</a>. 👈</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cacc81504547" width="1" height="1" alt=""><hr><p><a href="https://medium.com/enjoyhq/introducing-satismeter-nomnom-cacc81504547">Introducing SatisMeter + EnjoyHQ!</a> was originally published in <a href="https://medium.com/enjoyhq">Hungry for Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Typeform + EnjoyHQ!]]></title>
            <link>https://medium.com/enjoyhq/introducing-typeform-nomnom-83b6b708c67a?source=rss-a067d126e0d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/83b6b708c67a</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Dylan Ortega]]></dc:creator>
            <pubDate>Thu, 26 Jul 2018 16:01:49 GMT</pubDate>
            <atom:updated>2019-02-27T20:12:29.769Z</atom:updated>
            <content:encoded><![CDATA[<p>Today we’re excited to announce our revamped Typeform integration! Ever since Typeform launched, consumers and businesses have used the product to create beautiful forms, surveys, and other information gathering vehicles (referred to as typeforms) to collect input from anyone and everyone.</p><p>A large part of Typeform’s success can be attributed to creating great experiences for everyone involved in using the product — building and launching a typeform is quick and easy, and interacting with a typeform is truly a breath of fresh air.</p><p>Businesses use Typeform for a ton of different reasons, but one of the main benefits is collecting information and feedback from their customers — in fact, some of <a href="https://medium.com/@mia/getting-real-survey-answers-out-of-smart-busy-people-778f5a98e4c6">Typeform’s customers say</a> their response rates and overall engagement increase dramatically when typeforms are used; this isn’t a surprise if you’ve ever compared the experience of answering questions built in Typeform to other survey and form builders. And while collecting feedback from your customers is great, what really matters is what you do with that feedback.</p><p>Our integration with Typeform allows you to centralize responses collected in Typeform alongside customer communication from other feedback channels like Intercom, Zendesk, Drift, and Jira Service Desk. This provides your product, design, and research teams with a robust feedback repository they can use to identify themes and trends, find product insights, and build better experiences.</p><p>If you’re already an EnjoyHQ customer, simply navigate to the <a href="https://app.nomnom.it/account/integrations">integrations page</a> and select the Typeform icon to get started. You’ll be doing your best customer research in no time! If you’re not using Typeform yet, <a href="http://www.typeform.com/signup/">click here</a> to sign up for a free account!</p><p>If you’re not an EnjoyHQ customer but want to learn more about integrating your Typeform data, <a href="http://www.nomnominsights.com/typeform">click here</a>. 👈</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83b6b708c67a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/enjoyhq/introducing-typeform-nomnom-83b6b708c67a">Introducing Typeform + EnjoyHQ!</a> was originally published in <a href="https://medium.com/enjoyhq">Hungry for Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Jira Service Desk + EnjoyHQ!]]></title>
            <link>https://medium.com/enjoyhq/introducing-jira-service-desk-nomnom-f4fc2d4ffc70?source=rss-a067d126e0d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4fc2d4ffc70</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[jira-service-desk]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Dylan Ortega]]></dc:creator>
            <pubDate>Thu, 12 Jul 2018 15:36:33 GMT</pubDate>
            <atom:updated>2019-02-27T20:13:32.072Z</atom:updated>
            <content:encoded><![CDATA[<p>Today we’re excited to announce our new integration with Jira Service Desk. Atlassian has a longstanding history of building great products, and Jira Service Desk has been the industry standard service desk platform since it was released back in 2015.</p><p>Integrating Jira Service Desk with EnjoyHQ allows you to organize your Jira conversations alongside feedback from other channels, giving you a more complete view of your customers. Centralizing customer data from multiple sources makes it possible to do in-depth customer research and find key insights into pain points, product issues, valued features, and much more.</p><p>In addition to pulling in support ticket conversations, you can also send custom attributes and labels to EnjoyHQ. This additional information can be used to further classify and/or segment your research within EnjoyHQ. If you use Jira Software for issue tracking, you can link customer feedback from within EnjoyHQ to projects in Jira Software.</p><p>Existing EnjoyHQ customers can <a href="https://app.nomnom.it/account/integrations">navigate to the integrations page</a> and select the Jira Service Desk icon to begin pulling in support tickets.</p><p>If you’re not a customer but want to learn more about integrating Jira Service Desk with EnjoyHQ, <a href="https://nomnominsights.com/jira-service-desk/">go here</a>. 👈</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4fc2d4ffc70" width="1" height="1" alt=""><hr><p><a href="https://medium.com/enjoyhq/introducing-jira-service-desk-nomnom-f4fc2d4ffc70">Introducing Jira Service Desk + EnjoyHQ!</a> was originally published in <a href="https://medium.com/enjoyhq">Hungry for Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Delighted + EnjoyHQ!]]></title>
            <link>https://medium.com/enjoyhq/introducing-delighted-nomnom-9443305b7710?source=rss-a067d126e0d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/9443305b7710</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Dylan Ortega]]></dc:creator>
            <pubDate>Thu, 05 Jul 2018 17:11:20 GMT</pubDate>
            <atom:updated>2019-02-27T20:17:20.002Z</atom:updated>
            <content:encoded><![CDATA[<p>Ever since the Net Promoter methodology was developed back in 2003, businesses have calculated their NPS scores to better understand customer sentiment. Nowadays, software makes it easy to collect scores and responses so you can track NPS data over time.</p><p>We’re excited to announce our integration with <a href="https://delighted.com/">Delighted</a>, the leading platform for capturing NPS data. <a href="https://nomnominsights.com/delighted/">Integrating E</a>njoyHQ with Delighted allows you to consolidate NPS scores and responses with customer feedback from other sources, making it possible to do comprehensive customer research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8c4zF0JjWufOdMCqJLnZqA.gif" /><figcaption>Highlight and share Delighted feedback with team members</figcaption></figure><p>When you connect your <a href="https://nomnominsights.com/delighted/">Delighted data to E</a>njoyHQ, NPS scores and customer feedback are automatically organized alongside any other feedback you send to EnjoyHQ. You can then do customer research across all of your sources and highlight important pieces of feedback, tag feedback with keywords, and segment your research by detractors, passive users, and promoters.</p><p>If you’re already an EnjoyHQ customer, simply <a href="https://app.nomnom.it/account/integrations">navigate to your integrations page</a> and select the Delighted icon to get started. You’ll be doing your best customer research in no time!</p><p>If you’re not a customer but want to learn more about integrating your Delighted data with EnjoyHQ, <a href="https://nomnominsights.com/delighted/">click here</a>. 👈</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9443305b7710" width="1" height="1" alt=""><hr><p><a href="https://medium.com/enjoyhq/introducing-delighted-nomnom-9443305b7710">Introducing Delighted + EnjoyHQ!</a> was originally published in <a href="https://medium.com/enjoyhq">Hungry for Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a customer research process]]></title>
            <link>https://medium.com/enjoyhq/building-a-customer-research-process-922a2585fd91?source=rss-a067d126e0d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/922a2585fd91</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[customer-research]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Dylan Ortega]]></dc:creator>
            <pubDate>Thu, 28 Jun 2018 13:29:31 GMT</pubDate>
            <atom:updated>2019-02-27T20:18:02.043Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MLqH_hb1ZYSr4LS0dYBROg.jpeg" /></figure><p>Customer research is an extremely broad term — like other high level concepts such as inbound marketing or product management, companies unpack the subcategories beneath these concepts in order to build tailored processes that result in key outcomes. In the same way that an inbound marketing team might prioritize long-form written content and webinars, a research team might find that surveys and customer interviews produce the best product insights. The takeaway is that successful customer research is going to look different for almost every organization, so let’s dive into some best practices and learn how to build a research process for your business.</p><h3>Customer Research Best Practices</h3><p>For the purposes of this post we’ll be breaking down best practices for both qualitative and quantitative research.</p><h4>Qualitative</h4><p><strong>Surveys:</strong> We’ve all been asked to take surveys for products we use. These surveys ask us questions that aim to tell researchers how we interact with products, how we feel about products, and where products fall short. Surveys can be extremely powerful when used correctly, but you have to be careful not to introduce bias to your customers with leading questions, unnecessary length, or even compensation for completing your survey.</p><p>ProfitWell wrote up some <a href="https://www.profitwell.com/blog/lessons-from-sending-5m-saas-customer-development-surveys">key lessons from sending over five million customer development surveys</a> — their suggestions are to keep surveys short (less than one minute to complete) and send them frequently rather than sending long surveys less frequently; ask meaningful questions that make it easy for your survey takers to provide feedback; and focus on building a community where <a href="https://nomnominsights.com/product/">customer feedback</a> and input are praised, rather than trying to incentivize survey takers.</p><p><strong>Customer Interviews:</strong> Interviews are, surprisingly, one of the easiest customer research tools to get wrong. So many people downplay customer interviews by thinking of them as an open conversation between yourself and your customer, but this mindset sets you up to fail. You need to treat customer interviews as important opportunities to get in-depth answers to specific questions. When someone agrees to an interview, they’re signaling willingness to talk about your product candidly; take advantage of this opportunity to learn what excites and engages your customer, but also what frustrates, annoys, or confuses them.</p><p><a href="https://www.dtelepathy.com/blog/products/how-to-craft-user-interviews-for-breakthrough-insights">Jason Amunwa has a great writeup</a> about how to prepare for customer interviews and find key insights. He goes into great detail about his process, but some key takeaways are to be intentional with your preparation and allow your interviewee to tell his or her story rather than just answering question after question.</p><p><strong>Customer Feedback:</strong> Most of your customers want you to succeed, and are willing to give you feedback as long as you make it relatively easy for them to do so. There are so many tools available to us that facilitate customer feedback conversations — chat and support tools like <a href="https://blog.drift.com/customer-feedback/">Drift</a>, Intercom, and Zendesk lend themselves to this task perfectly. When you receive feedback, your primary short-term goal will usually be to address that feedback with a solution, an alternative, or at the very least acknowledgement that an issue exists. But this feedback should also factor into a longer term goal of recognizing trends and themes within your feedback so you can recognize when big changes or shifts in your product strategy are necessary.</p><p><a href="https://blog.intercom.com/how-to-analyze-customer-feedback-and-make-it-actionable/">Intercom has some great suggestions</a> for organizing customer feedback for research purposes, with the main takeaways being to develop a code or taxonomy that allows you to easily find insights within your feedback. Just be mindful of your time, because creating this code and constantly updating a spreadsheet/document with each new piece of feedback can be very labor intensive. Sometimes it makes more sense to <a href="https://blog.nomnom.it/build-vs-buy-make-your-decision-carefully-a3005d0c2aab">find a product that will automate this entire process for you</a>, but more on that later.</p><h4>Quantitative</h4><p><strong>Engagement Metrics:</strong> Dedicated user researchers spend a lot of time studying how users interact with their products. There are numerous analytics tools that track user journeys, provide heatmaps, and generally track user behavior within your product. These tools are great for providing specific insights, as long as you pay attention to the sample size of the actions being measured. You wouldn’t want to rely on data from only a small subset of users when considering making changes to your growth or product strategy.</p><p><a href="https://mixpanel.com/topics/what-is-customer-analytics/">Mixpanel published a helpful guide</a> for understanding and leveraging customer analytics to build a better business. A main takeaway is the importance of pairing quantitative user behavior with qualitative data to get more complete picture of your customers. Interviews and feedback are great, but you can’t always trust your users to give you the full picture.</p><p><strong>Feedback Sentiment:</strong> Customer feedback is qualitative when taken at face value, but when feedback is aggregated and analyzed for trends and themes it starts to become quantitative. One of the best ways to leverage feedback for quantitative research is to organize feedback by sentiment. This can be as simple as organizing feedback into positive, neutral, and negative categories, or as complicated as creating a multi-faceted scoring system that is specific to your company. Regardless of the method you use, the key is to have some way of organizing and coding feedback for research purposes.</p><h3>Building and automating your research process</h3><p>To reiterate — successful customer research is going to look different for almost every company. The key is to have an actual research process that incorporates both qualitative and quantitative research so you can get a more complete picture of your customers. If you’re not doing any of the research listed above, start small and try to dedicate just one hour each week to learning more about your customers. You’ll build up from there and find key insights in no time.</p><p>Eventually though, all of your research activities are going to be difficult to manage due to the numerous feedback sources and overall volume of feedback. That’s where a product like <a href="https://getenjoyhq.com/">EnjoyHQ</a> can help. Not only do we aggregate all of your feedback in one place, we make it easy to organize and code your feedback automatically. If you want to find key insights faster and build better experiences for your customers, <a href="https://nomnominsights.com/">give us a try</a>.</p><p>If you found this post useful, please give it applause so others can find it 👏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=922a2585fd91" width="1" height="1" alt=""><hr><p><a href="https://medium.com/enjoyhq/building-a-customer-research-process-922a2585fd91">Building a customer research process</a> was originally published in <a href="https://medium.com/enjoyhq">Hungry for Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build vs. Buy — Make Your Decision Carefully]]></title>
            <link>https://medium.com/enjoyhq/build-vs-buy-make-your-decision-carefully-a3005d0c2aab?source=rss-a067d126e0d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3005d0c2aab</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Dylan Ortega]]></dc:creator>
            <pubDate>Tue, 26 Jun 2018 13:56:01 GMT</pubDate>
            <atom:updated>2019-02-27T20:19:41.758Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X6YZrAhoHTLWUPFamE3xEQ.jpeg" /></figure><p>If you’re considering building a tool as opposed to paying for a third party product, you probably fall into one of two categories: a founder/co-founder of a scrappy startup with limited financial resources who can hack something together over the weekend; or you’re at a more established company that can spare dev time to work on said tool. In either case, you shouldn’t take the build vs. buy decision lightly— depending on the complexity of the solution you’re trying to build, paying for a product can oftentimes <a href="https://baremetrics.com/blog/build-it-buy-it">save you time and money</a> in the long run.</p><h3>Resources and Opportunity Cost</h3><p>First, let’s touch on the concept of opportunity cost. If you’re unfamiliar with this concept, it’s essentially a way to quantify the cost of NOT doing something. When it comes to building a tool internally, the opportunity cost is measured by determining how the engineering resources could have been used had they not been dedicated to building an internal tool. As an example, let’s say you’re an engineer at a startup, and you spend 5 hours building an internal tool. The opportunity cost of that labor is 5 hours that could have been spent working on your product — a product that is likely your main source of income. In a world where resources are scarce, we have to make decisions about how to allocate resources, and if you allocate engineering time away from your main product, you run a higher risk of inflated opportunity costs.</p><p>Theoretically, the <a href="https://blog.madkudu.com/make-right-build-versus-buy-decision-3-simple-steps/">best way to determine whether to build or buy</a> is to estimate how much time it would take to build the tool internally. This estimate would allow you to calculate the rough cost of building the tool and compare that with the cost of buying an outside solution. But as anyone involved in building software knows, estimating development timelines is very difficult. I marvel at engineers’ abilities to create seemingly out of thin air, but even they have difficulty scoping the time requirements of a project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Q4Lg-uzfgqsN0nLCbvRxxg.jpeg" /><figcaption>Source: <a href="https://www.reddit.com/r/ProgrammerHumor/comments/642i38/estimation_skills/">Reddit</a></figcaption></figure><h3>Customization of Software</h3><p>Everyday we move closer to the peak of flexibility and customization in software. Technology makes it possible for SaaS companies to offer unique solutions to their customers. These custom solutions typically come at an extremely high cost, at least for now. But we’re seeing this customization trend continue, and soon we could see highly customizable software at all price points. If you choose to build a product in house, you’ll find yourself spending time maintaining or updating the software to fit your needs; in the next year or two you could see paid products offering the same level of customization, with none of the maintenance required on your end.</p><p>Consider also that some paid products will offer 80–90% of the functionality you need; in these instances, you have to ask yourself if building a similar product in house is worth the remaining 10–20%. You may even be able to get the job done by combining the functionality of multiple systems using a product like Zapier.</p><h3>Build vs. Buy for Customer Feedback Research</h3><p>Let’s consider a build vs. buy scenario for <a href="https://nomnominsights.com/product/">customer feedback research</a>. Now, it’s obviously important to consider the complexity of your customer feedback process. If you’re a startup, you probably get most of your feedback through chat and email; organizing customer feedback data from those two sources isn’t going to be very difficult or time consuming. But once your business is more established, you’ll probably take in feedback from a bunch of different sources. B2C products can receive feedback through chats, emails, app store reviews, surveys, and tons of other channels. B2B products might also incorporate feedback from customer calls and their CRM notes. When you consider organizing feedback from all of these different sources, you begin to realize the scope of work required just to get all of your customer feedback in one place.</p><p>Now consider the actual reason for centralizing all of your feedback — you want to conduct research that will lead to meaningful insights and better experiences for your customers. In order to do meaningful research across all of your feedback channels, you’ll need to organize the data in a way that makes it easy to query — this is no small task. You’ll also want your query results to be sortable so you can find insights from different types of customers. Maybe you’ll need to build team sharing features into the system as well; or perhaps you’ll want to build data visualization modules. Once you start down the path of building a system in house, you can easily fall victim to the sunk cost fallacy and continue building out the product to the detriment of your business.</p><p>Building a system with all of these requirements would take an immense amount of time — we know, <a href="https://nomnominsights.com/">because we built it</a>! Even if you built a similar system yourself, you would have to maintain it and build new integrations for each feedback channel you implement. If you’re a smaller operation that gets most of your feedback through chat and email, then you can probably get away with building this in-house. But if you’re dealing with higher volumes of feedback across multiple channels, the cost of building a customer research platform could get out of hand fast.</p><p><a href="https://getenjoyhq.com/">EnjoyHQ</a> helps teams find insights ands build better products. Learn more here: <a href="https://getenjoyhq.com/">https://getenjoyhq.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3005d0c2aab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/enjoyhq/build-vs-buy-make-your-decision-carefully-a3005d0c2aab">Build vs. Buy — Make Your Decision Carefully</a> was originally published in <a href="https://medium.com/enjoyhq">Hungry for Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving Complex Product Problems Using Corner Cases]]></title>
            <link>https://medium.com/enjoyhq/solving-complex-product-problems-using-corner-cases-59eb5b5d7dac?source=rss-a067d126e0d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/59eb5b5d7dac</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Dylan Ortega]]></dc:creator>
            <pubDate>Thu, 21 Jun 2018 13:06:02 GMT</pubDate>
            <atom:updated>2019-02-27T20:21:36.798Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fuz_sLRjcuaC5OViBD-r4Q.jpeg" /></figure><p>At SaaSFest 2017, Pluralsight’s Chief Experience Officer Nate Walkingshaw discussed using corner cases to build better customer experiences. I wasn’t familiar with corner cases as a concept before Nate’s talk, but the way in which he uses them to solve complex product problems resonates strongly with me. If you’re unfamiliar with corner cases, think of them as power users — someone who spends more time using or interacting with your product than almost anyone else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*6wmyvZzJV3CDLtvV-SB8JQ.jpeg" /></figure><p><a href="https://medium.com/@nwalkingshaw/mowing-your-product-lawn-d4bd23b2d4ad">Nate’s talk</a> was mainly about building better products by focusing on desired outcomes, and one example he used to illustrate his point was a lawnmower. On one of Nate’s daily runs, he crossed paths with two Parks and Recreation employees. The employees were mowing a park in Nate’s neighborhood, and as he ran by the park he found himself stepping on grass clippings that were littered on the sidewalk. Nate stopped and asked the employees why the clippings were strewn across the sidewalk, and he discovered that the bag that was supposed to hold all of the clippings got stuck as the employees went from mowing on a decline to a flat surface. Instead of dealing with the hassle of adjusting the bag every time, the employees simply removed the bag and left the clippings to be cleaned up after the mowing was done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*_e6iaDCANehBDdF3Ga0PWA.jpeg" /><figcaption>Source: <a href="https://www.slideshare.net/PatticusCampbell/nate-walkingshaw-mowing-your-product-lawn">Nate Walkingshaw — Mowing Your Product Lawn</a></figcaption></figure><p>The two employees that Nate spoke to are corner cases. They use a lawnmower more than almost anyone — not only do they spend more time using the mower, but they undoubtedly cut a larger area of grass than your typical homeowner maintaining his or her lawn. With that being said, mowing inclines, declines, and flat surfaces isn’t exclusive to these Parks and Recreation employees. There are lawns all over the world that have tricky surfaces, and if lawn mower manufacturers had studied the user behavior of these corner cases, they may have recognized the issue with the bag getting stuck and designed a better experience for the majority of their buyers.</p><p>You have corner cases in your business, and they can help you build a better experience for the majority of your customers. If you find yourself running up against a difficult product problem, consider reaching out to those users who spend more time interacting with your product than anyone else — they just might hold the key to unlocking your product success.</p><p>If you enjoyed this post, please give it some love so others can find it! 👏</p><p>EnjoyHQ makes it easy to gather insights from your corner cases so you can build better products. Learn more here: <a href="https://getenjoyhq.com/">https://getenjoyhq.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59eb5b5d7dac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/enjoyhq/solving-complex-product-problems-using-corner-cases-59eb5b5d7dac">Solving Complex Product Problems Using Corner Cases</a> was originally published in <a href="https://medium.com/enjoyhq">Hungry for Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>