<?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 Sarah Arnegard on Medium]]></title>
        <description><![CDATA[Stories by Sarah Arnegard on Medium]]></description>
        <link>https://medium.com/@sarah.arnegard?source=rss-d272facbbab4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_tbfuUC1gsbYEPG0mT8o6Q.jpeg</url>
            <title>Stories by Sarah Arnegard on Medium</title>
            <link>https://medium.com/@sarah.arnegard?source=rss-d272facbbab4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:44:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sarah.arnegard/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why you’re thinking about prototyping the wrong way]]></title>
            <link>https://medium.com/@sarah.arnegard/why-youre-thinking-about-prototyping-the-wrong-way-5bfc3b923432?source=rss-d272facbbab4------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bfc3b923432</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Sarah Arnegard]]></dc:creator>
            <pubDate>Wed, 23 Aug 2017 17:00:24 GMT</pubDate>
            <atom:updated>2017-08-23T17:00:24.037Z</atom:updated>
            <content:encoded><![CDATA[<p>Let me ask you a question.</p><p>If you were making a website, would you choose a framework or template before knowing what the website was for?</p><p>My guess is, you would never design a site or an app without understanding the goals first. You would base the functionality on what the users were trying to achieve.</p><p>Now imagine you have an idea for a new concierge app, and you want to know whether people would use it. What would you do?</p><p>If someone asked you if you knew how to “prototype” what would you say? “Yep, I know how to use Sketch, Invision, and Axure”</p><p>In digital design, the conversation about prototyping centers around tools for testing screens and UI. This is a problem for 2 reasons: First, there are often upstream assumptions that need to be tested such as, “will people pay for this product”. And second, not all products and services can be tested with screens.</p><p>Prototyping isn’t just a way to test UI or user flow concepts, but simply a method to test user behavior. You can use prototyping to validate problem-solution fit, pricing, or any other part of your business model.</p><p>Experiments aren’t one-size-fits-all. Neither are prototypes. It’s as important to understand what you are trying to learn before designing an experiment as it is to understand a problem before designing a solution. Instead of jumping straight into Sketch or Invision, let’s take a step back.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*FV-AbWeSOMyF4ODM3XoEag.gif" /><figcaption>This bunny is now offering a course on creative problem solving.</figcaption></figure><h3>Back to basics — What do you mean by “prototype” anyway?</h3><p>A prototype is an early proof of concept that we use to learn. A prototype can be used to gauge product market fit, test usability, or feasibility. It is related to the idea of the MVP, or minimum viable product. The MVP that Eric Ries describes in Lean Startup, refers to the simplest artifact needed to test product hypotheses. The term MVP, however, is now often used to refer to a product that has been implemented and is ready for a general release, or a “minimum saleable product”. For that reason, I prefer to use the word prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*qf-gHQllqBytQz8fRRuAcQ.gif" /><figcaption>Reducing uncertainty makes launch day less like this …</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*Y2iTsekda0dw6gxizIfGBg.gif" /><figcaption>… and more like this</figcaption></figure><p>At it’s most essential, a prototype is a tool to test hypothesis early, to reduce business risk. Don’t want to spend time and money building a product that doesn’t make sense, and people don’t want? Try making a prototype. When creating a prototype, you want to re-create the real situation you are testing, whether a buying situation or usage situation, as closely as possible to get the most accurate results. The name of the game is not “flashy demos”, it’s reducing business risk by eliminating as much uncertainty as humanly possible.</p><h3>Prototyping methods flow from what you are trying to learn</h3><p>As will any research questions, prototyping methods starts with hypotheses. ( If you don’t know where to start, fill out a business model canvas. Anything on there that hasn’t been tested is a hypothesis).</p><p>For example, say I have a hypothesis that “small cafe owners will fill out a 5 page form for the chance to get a loan, as it is still much easier than the bank’s process.” Since I want to test behavior, a prototype makes sense.</p><p>To test this, I could create a preliminary version of the paperwork. By using a landing page to market my loan, I could ask people to apply to be on the waiting list and prompt them to complete the application paperwork. I could measure the difference between people who click the link to apply and those who complete the process. If using paper forms, I could print them out and give them to potential customers, and see whether they would fill it out. At the same time, I could ask questions to help me understand whether they are in my target market. This is a version of a test sale that tests a specific hypothesis.</p><p>Another example — let’s say I wanted to make a new service that acts as a personal concierge for users. Maybe I want to eventually use machine learning to automate answers to user’s request. My hypothesis is that people will be willing to pay a certain amount for a concierge service through text messages. Maybe my first prototype is a signup page to gauge interest. Once I have a few users, I can have them text message this super awesome concierge bot, which is really me, at my phone number manually replying to them. Not only would I start to learn what kind of requests early adopters of this service would make, I would also see whether these uses were willing to pay me for the service. I would do this by simply responding to their request with a price, and see whether they wanted to go forward with the service. Quickly I would be able to figure out whether someone is willing to pay money for this product.</p><p>A prototype can be made of paper, code, or a manual version of your product. The point is to test your ideas with the least amount of investment necessary. It can be helpful to brainstorm multiple ways of testing a hypothesis, and then choose the one that will be the most accurate with the least effort. You can even repurpose existing service processes or code, but layer on different manual processes and/or product positioning to quickly test different offerings at small scale. Focus on what you need to learn, not the tools you use or making something flashy and cool, and you might be surprised by how much you can discover.</p><p>Do you have examples of creative ways you’ve prototyped and tested new products? Please share! I’d love to learn from you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/1*5NHmdhNlAiVOLU_6ts5irQ.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bfc3b923432" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Research is not “asking customers what they want”]]></title>
            <link>https://blog.prototypr.io/user-research-is-not-asking-customers-what-they-want-96f91687f6ae?source=rss-d272facbbab4------2</link>
            <guid isPermaLink="false">https://medium.com/p/96f91687f6ae</guid>
            <category><![CDATA[customer-interview]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[lean-ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Sarah Arnegard]]></dc:creator>
            <pubDate>Fri, 11 Aug 2017 15:36:55 GMT</pubDate>
            <atom:updated>2017-08-13T10:20:58.045Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s say we are trying to optimize a process our internal sales team uses. This mysterious and legendary process has oodles of steps we aren’t sure are necessary, legacy systems that have been human-centipeded together, and a sales team that has been using it for years.</p><h3>If you simply asked these customers what they wanted, what do you think would happen?</h3><p>Their current process is their entire context. It’s like asking a fish what vessel to refill his aquarium with. The users see the pain points of how things work today, and they’ve also gotten used to quirks and now take them for granted.</p><p>Sometimes users try to tell you what features they want, even if you don’t ask them. A user in an interview recently told me “The output needs to export to Excel.” When I asked why, they said “I always need to manually edit things in Excel because some of my clients use a target metric that isn’t available in the current system”.</p><p>Notice here, the user thinks they need an export to Excel feature, and if you built this, you would be building the wrong thing. Why? You failed to understand their problem: the current system doesn’t do the job they need it to do. Asking what a customer wants gives you a “what”, not “why”. Don’t forget: the user isn’t a designer or a product manager. The user sees and feels the pains of today. If you ask them what the product should be, they will often look at something that is their current system, but a step or two easier.</p><h3>So what should you do?</h3><p>Understand what the user is trying to do on a higher level.</p><p>What are the jobs they are trying to accomplish? What are the biggest pains and challenges with these jobs? What motivates them? In interview, center the conversation around these topics, not features and functionality. If users can’t stop talking about features, ask why they think they need those features to uncover the jobs they are trying to do. It also helps to let them know that you’re there to better understand what they do, not get a list of features. For example in my case, the job the user was trying to do was “Present a product plan that fit their client’s goals to win more sales”, which was an aha moment — uncovering a dependency on the end client’s goals. A related job the sales person does is “manage and improve relationships with clients”. When scoping the product, think about how to support the jobs you uncovered.</p><p>Your users are there to accomplish something, not use your pet feature. Observe and analyze their tasks and processes on a holistic level. It can be helpful to map the user’s current journey, along with their pains and successes along the way. Think about the system you are creating as a whole, and how it aligns to the jobs they are doing. If you want to truly solve problems, don’t force users to design for you. That’s your job.</p><p>Have you also seen people substituting “asking users what they want” for research? Or maybe you’ve done it yourself? Share your stories below!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96f91687f6ae" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/user-research-is-not-asking-customers-what-they-want-96f91687f6ae">User Research is not “asking customers what they want”</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Criticism is a gift]]></title>
            <link>https://blog.prototypr.io/criticism-is-a-gift-f7eda6edfb55?source=rss-d272facbbab4------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7eda6edfb55</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-community]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[criticism]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Sarah Arnegard]]></dc:creator>
            <pubDate>Fri, 07 Jul 2017 18:27:42 GMT</pubDate>
            <atom:updated>2017-07-12T12:33:44.247Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Kq4Hj0fMvgc23oKUI3vQA.jpeg" /></figure><p>I have regretted my choice of fine art degree at times for obvious economic reasons, but I’ve never regretting the experience of writing art criticism and analysis and undergoing weekly critiques. Yes we received feedback, but we also received criticism. At times, it was emotionally draining and there were days I wanted to cry or skip class. It wasn’t always “nice” and my teachers and classmates did not try to protect my ego. And thank God for that.</p><p>In Chris J. Davis’s recent post, <a href="https://medium.com/@chrisjdavis/the-critique-being-positive-7900e477bdc9">The critique &amp; being positive</a>, he touched on his experience as a fine art student, and how that taught him to deal with criticism. I had a similar experience, and until recently I assumed rigorous criticism was a foundational aspect of every art and design education. Reading his post inspired me to expound on the idea that criticism is a gift.</p><h4>Feedback Vs. Criticism</h4><p>I think most designers have heard or believe feedback is a gift that provides opportunities for improvement, and gives the recipient the sense that their work matters. While feedback is venerated in the design community, I’ve observed that criticism is often met with hostility.</p><p>Interestingly, feedback and criticism are often conflated despite being distinct concepts.</p><p>The goal of feedback to better help one achieve their goals as a creator, so by definition the goals and intentions of the creator matters.</p><p>Criticism, on the other hand, is “the analysis and judgment of the merits and faults of a literary or artistic work,” according to the Oxford English dictionary.</p><p>Criticism is not necessarily meant to help the creator. A critic analyses the content of a work. It is separate from the creator as a person.</p><p>In criticism it need only be the produced artifact, whether marks on the page, musical notes, or lines of code that is relevant — not the creator’s intention. It is about the work’s relationship with the viewer. Intention that is not communicated is lost. The work, the creation itself, is the message.</p><p>It was discouraging to pour my creative energy and intellect into something, and for the viewer turned critic not to understand it or like it. But through critics I gained tremendous insight. I learned so, so much. I learned about the critic’s point of view and connotations in my work I didn’t realize because I didn’t know the historical context. I realized I needed to improve my communication skills and better define the goals of my work. To the self aware, difficult comments and observations are the necessary floodlights to see one’s own blind spots.</p><h4><strong>Becoming vulnerable</strong></h4><p>Creating something and sharing it with the world can be scary. Something one creates can feel like part of one’s self, and it can be extremely painful to bare one’s self and receive negative criticism. We all fear rejection.</p><p>But what I learned is, criticism isn’t about <em>me</em>. It’s not about my intentions, my journey, and my experience, because none of that matters if those only exist in my head. If I understand the customer, but I don’t deliver a product that suits their needs, does it really matter that I understood them?</p><p>My work is the vessel of my knowledge and intentions made tangible. The work is an object that is separate from myself.</p><p>Once I learned this criticism became so much easier. I learned to have more empathy for my viewer and for my critic. I learned that critics can made me better. Yes, you too can learn to have a thicker skin, I promise. I’m not saying that criticism never makes me uncomfortable, or that I never have hurt feelings, but I’m aware it’s necessary and I’ll become better for it.</p><h4><strong>“But you can’t judge if you weren’t there!”</strong></h4><p>Work should speak for itself because you aren’t always there to explain, defend, and qualify. If you need to do those things, perhaps you should re-evaluate the work. Defenses and explanations may matter to the art historian, the curator, or in the business context, the board, your team, or your manager, but they probably don’t matter to the viewer and they don’t matter to customer. If you deliver something bad, the customer probably doesn’t care why, they just care that it’s shitty. And if someone tells you that be thankful they are honest and that they take the time to communicate at all.</p><p>If only people who know what you went through can judge the object you produced then why release it into the public square? When you do that, you consent to criticism.</p><p>If the only people who could criticise you were the ones who were there with you as you broke down on the floor of your studio or argued for more budget and failed, the criticism you receive would be so much less valuable. The majority of those consuming the work are probably not those people. And if they are, then, I have to ask you, don’t you want to reach a wider audience? Don’t you want to improve your craft and increase your value at your company? And if you tell me the business you work for thrives in spite of your craft, isn’t that rather cynical? Remember that you cannot reliably reach an audience you don’t understand.</p><p>Criticism is an opportunity to grow a thicker skin, to see things from a new perspective, and improve.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7eda6edfb55" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/criticism-is-a-gift-f7eda6edfb55">Criticism is a gift</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Questions Designers should ask when interviewing at a startup]]></title>
            <link>https://medium.com/@sarah.arnegard/10-questions-designers-should-ask-when-interviewing-at-a-startup-f7edfc54173e?source=rss-d272facbbab4------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7edfc54173e</guid>
            <category><![CDATA[ux-designer]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[interviewing-tips]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Sarah Arnegard]]></dc:creator>
            <pubDate>Sat, 10 Dec 2016 23:13:50 GMT</pubDate>
            <atom:updated>2016-12-10T23:14:30.780Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wo2c-67qpNP35Av3." /></figure><h3>Don’t get burned!</h3><p>Are you a young Product Designer or UX designer considering joining a start up as a the first design hire? Have you heard horror stories about working with startups? Are you wondering how to decrease your chances of getting burned, but not sure where to start?</p><p>Startups can be a black box — no reviews on Glassdoor, and no established history. It’s important that you interview them, just as much as they interview you. Use my questions to help you figure out if the startup is a fit for you, so you can avoid wasting your time.</p><p>My first full time design job was at a startup in Silicon Valley, and it was an amazing experience for me. But not all startups are created equal. I’ve also had terrible experiences working for and interviewing with startups. I’ve also consulted for my partner’s startup and been in and around the start up scene in Silicon valley and Sydney, Australia.</p><p>Here are the questions I use to evaluate a startup before I decide whether I want to work with them.</p><h3>10 Questions for your startup interview</h3><h4>For founders, or whoever is interviewing you</h4><ol><li><strong>Why (and when) was the business founded?</strong></li></ol><p>This gives insight into a founder’s motivations. It also tells you how they make decisions, and how they see the company.</p><p><strong>2.Who is your customer is what is the value proposition?</strong></p><p>First of all, you want to make sure they have actually thought about this. Does their value proposition make sense to you? Is it something you could get excited about?</p><p><strong>3.What is the long term vision for the company/product?</strong></p><p>First and foremost, shows the founder/ CEO <em>has a vision</em>. They are thinking about the value they can deliver to world, and are thinking big.</p><p>This also lets you know the overall direction the founder is thinking about. Perhaps their customer, value prop looks narrow now, but their vision is exciting!</p><p><strong>4. What is your business model?</strong></p><p>How do they plan to make money? An awesome idea that with no idea of how to get paid won’t last long. If they can’t answer this question they won’t last long or get funding.</p><p>Also, the business plan might have ethical considerations you don’t want to get behind. Example — and app that brings people closer together sounds great on the surface, but what if their business model is to sell personal data to ad companies.</p><p><strong>5.What kind of compensation are you offering and how much?</strong></p><p>I’ve met too many start up founders who want free work, to not include this. Don’t spend your time interviewing and doing design work for a job that pays less than you can take, let alone an “unpaid internship”. It’s common for startups to offer a salary that may be somewhat lower than market rates plus equity, they don’t have the same resources as larger companies. Don’t take equity in lieu of pay. Equity is a huge gamble, and even if the company does get acquired for millions, which is rare, preferred stock means you’re still unlikely to see a cent. If you want more detail about startup compensation, let me know and I’ll write a separate post</p><p><strong>6.What is the greatest challenge the company is facing right now?</strong></p><p>What are you getting yourself into? This challenge will become yours when you join the company.</p><p><strong>7. Describe company culture in 3 words?</strong></p><p>Founders set the tone for culture. This shows what they value, or at least what they say they value. Does their company culture align with what you are looking for?</p><p><strong>8. For the person you will be reporting to/ head of product — How do you see the product design process and it’s role within the business?</strong></p><p>Important for identifying whether you have approach design in similar ways and whether you’ll be able to work successfully together</p><p><strong>9. How are you funded?</strong></p><p>Does their story make sense? Do you think they’ll be able to deliver on their promises?</p><p><strong>10. Role and team team structure?- how many developers, marketers, sales, product? Who would I report to? Is the team remote or local? How do they see me fitting in to the team (Silo-ed by yourself or working between devs, product, and customers)?</strong></p><p>Does their idea of your role line up with yours? Is it contracting, part time, full time, and does this line up with their resources?</p><p>Where they put people resources can say a lot about their priorities and company culture. Do they have a huge marketing and sales team, yet have spent no resources on product hires? That may be a red flag they don’t value product development</p><p>Who will you be reporting to? As a young designer, I believe it’s important to have the support of head of product or product manager, especially if you don’t have experience in product management. I consider reporting directly the CEO a red flag, because he or she should be busy running the business, not dealing with the minutiae of product and design work.</p><p>Who would you report to will determine a lot of your job satisfaction. Someone who has your back and understands the product design process and can advocate for you will make a huge difference</p><p>Are you ok sitting alone in the office because everyone else works remote? Can you handle working with developers who work on the other side of the world and might not be the greatest with English?</p><h3>Conclusion</h3><p>Working at a startup can be one of the best experiences for a young designer, allowing you to level up your skills extremely fast, and allow you to learn more about product management, business, and software development roles. I would recommend working at a startup to any UX designer who wants a deep dive into the world of early stage products, as well anyone who wants the chance to wear many hats and discover their passion within the UX field.</p><p>I hope these questions helped you as you consider whether to take the plunge and join a startup.</p><p>Were these questions helpful? What are your favorite questions to ask in interviews? Have startup horror stories? Let me know in the comments or tweet me<a href="https://twitter.com/hey_arne"> @hey_arne !</a></p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7edfc54173e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>