<?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 Brandon Houlihan on Medium]]></title>
        <description><![CDATA[Stories by Brandon Houlihan on Medium]]></description>
        <link>https://medium.com/@brandonhoulihan?source=rss-d336eb620130------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ky4SD9OlO3lp2PpsyXriog.jpeg</url>
            <title>Stories by Brandon Houlihan on Medium</title>
            <link>https://medium.com/@brandonhoulihan?source=rss-d336eb620130------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:19:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brandonhoulihan/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[Impactful UX design work you should be doing in 2021]]></title>
            <link>https://medium.com/design-bootcamp/impactful-ux-design-work-you-should-be-doing-in-2021-139cbb7f8886?source=rss-d336eb620130------2</link>
            <guid isPermaLink="false">https://medium.com/p/139cbb7f8886</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Brandon Houlihan]]></dc:creator>
            <pubDate>Mon, 26 Apr 2021 14:01:09 GMT</pubDate>
            <atom:updated>2021-05-05T04:03:04.261Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A splash causing a ripple in water." src="https://cdn-images-1.medium.com/max/1024/1*1nW3GI2W6Mirk-3UFJrmkA.jpeg" /></figure><p>The role of UX Designer has become really complicated in recent years. There are so many things you <em>could</em> be doing it’s hard to tell what you <em>should</em> be doing. As a UX Designer these are a few things I recommend you focus on in 2021 to help you do your most impactful work.</p><h3>1. Written concepts</h3><p>I think of written concepts as product or feature ideas that omit visuals in place of words. An example of a written concept would be:</p><blockquote>“We are creating an application that will enable you to store a password and use it to sign in to other applications.”</blockquote><p>Writing and sharing what you intend to design will help you measure whether or not you will be providing value to users <em>before</em> you invest time in designing interfaces.</p><h3>2. Component references</h3><p>Rather than thinking about mock-ups as user interface specs, think of them as a reference to the components that will be used to build the interface. This is a subtle difference, but it’s an important one. Thinking about your work as a component reference is highly impactful for a few reasons:</p><ul><li>It will help frame design evaluations around the system that is being used to create the interface rather than specific instances of the UI. This will lead to more cohesive user experiences and less time spent designing across digital touch points</li><li>If there is a gap in the design system it will be easier to identify it and create a new component to fill that gap</li><li>If you don’t have a design systems established you will be laying the groundwork for one and promoting systems thinking</li></ul><h3>3. Front end design reviews</h3><p>The only way to ensure design will be seen in the way it was intended is to evaluate <strong>the same interface</strong> your users will interact with. You can do this by reviewing digital experiences on the front end, when designs have been built in code and have some functionality.</p><p>Front end design reviews should be conducted just like design reviews you already conduct with static mock-ups, but you will be reviewing the design after it has been built in HTML and CSS.</p><p>While conducting a front end design review do the following:</p><ul><li>Evaluate if the HTML and CSS match the design mock-ups. If it doesn’t, identify why and document what needs to be adjusted</li><li>Ensure that design, content, and web standards have been carried over from the mock-ups to the the HTML and CSS</li><li>If you designed the experience with a set of principles in mind use the front end design review as another opportunity to evaluate if the experience you created adheres to those principles</li></ul><h3>4. Interaction patterns</h3><p>No matter where you work or what you work on, it’s <strong>extremely hard</strong> to create cohesive digital experiences. Even when you use a design system there can be a lot of ambiguity about how to combine and use the components, which can lead to disjointed experiences.</p><p>To establish interaction patterns you first need to audit the existing UI. Using <strong>Edit</strong> functionality as an example, go through all instances of editing in the product and ask yourself these questions:</p><ul><li>What happens when an edit button is selected?</li><li>Does the page state change from read to edit?</li><li>Is the edit form displayed in a modal?</li><li>Is the edit form displayed in-line?</li><li>Is this consistent across all the product’s digital touch points?</li></ul><p>After conducting the audit identify where there are inconsistencies in the interactions and work towards establishing a way to complete the task with less variations. Repeat this process for other common tasks like creating, reading, and deleting.</p><h3>5. User jobs and stories</h3><p>For a product to be successful it needs to not only be usable, but also be useful. Design based on ideas and functionality might produce visually appealing and usable interfaces, but it doesn’t guarantee you will be creating something that meets the user’s needs. As a UX designer it’s your responsibility to learn your user’s needs and surface them throughout the design process.</p><p>Talk to your users. Try to uncover why they hired you and what they expect your product to do. Convert what you discover into user stories and put the stories <strong>right into your design files</strong> so you and everyone can see them. This will ensure you are putting the customer’s needs first when creating and evaluating designs.</p><h3>Conclusion</h3><p>The role of the UX Designer is continuously evolving to keep up with the industry so tray and stay flexible and continue to evaluate if the work you are doing is impactful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=139cbb7f8886" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/impactful-ux-design-work-you-should-be-doing-in-2021-139cbb7f8886">Impactful UX design work you should be doing in 2021</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Impactful UX design work you should be doing in 2021]]></title>
            <link>https://brandonhoulihan.medium.com/impactful-ux-design-work-you-should-do-be-doing-in-2021-7ac59c74c2fc?source=rss-d336eb620130------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ac59c74c2fc</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Brandon Houlihan]]></dc:creator>
            <pubDate>Mon, 26 Apr 2021 13:07:30 GMT</pubDate>
            <atom:updated>2021-04-26T13:55:22.935Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1nW3GI2W6Mirk-3UFJrmkA.jpeg" /></figure><p>The role of UX Designer has become really complicated in recent years. There are so many things you <em>could</em> be doing it’s hard to tell what you <em>should</em> be doing. As a UX Designer these are a few things I recommend you focus on in 2021 to help you do your most impactful work.</p><h3>1. Written concepts</h3><p>I think of written concepts as product or feature ideas that omit visuals in place of words. An example of a written concept would be:</p><blockquote>“We are creating an application that will enable you to store a password and use it to sign in to other applications.”</blockquote><p>Writing and sharing what you intend to design will help you measure whether or not you will be providing value to users <em>before</em> you invest time in designing interfaces.</p><h3>2. Component references</h3><p>Rather than thinking about mock-ups as user interface specs, think of them as a reference to the components that will be used to build the interface. This is a subtle difference, but it’s an important one. Thinking about your work as a component reference is highly impactful for a few reasons:</p><ul><li>It will help frame design evaluations around the system that is being used to create the interface rather than specific instances of the UI. This will lead to more cohesive user experiences and less time spent designing across digital touch points</li><li>If there is a gap in the design system it will be easier to identify it and create a new component to fill that gap</li><li>If you don’t have a design systems established you will be laying the groundwork for one and promoting systems thinking</li></ul><h3>3. Front end design reviews</h3><p>The only way to ensure design will be seen in the way it was intended is to evaluate <strong>the same interface</strong> your users will interact with. You can do this by reviewing digital experiences on the front end, when designs have been built in code and have some functionality.</p><p>Front end design reviews should be conducted just like design reviews you already conduct with static mock-ups, but you will be reviewing the design after it has been built in HTML and CSS.</p><p>While conducting a front end design review do the following:</p><ul><li>Evaluate if the HTML and CSS match the design mock-ups. If it doesn’t, identify why and document what needs to be adjusted</li><li>Ensure that design, content, and web standards have been carried over from the mock-ups to the the HTML and CSS</li><li>If you designed the experience with a set of principles in mind use the front end design review as another opportunity to evaluate if the experience you created adheres to those principles</li></ul><h3>4. Interaction patterns</h3><p>No matter where you work or what you work on, it’s <strong>extremely hard</strong> to create cohesive digital experiences. Even when you use a design system there can be a lot of ambiguity about how to combine and use the components, which can lead to disjointed experiences.</p><p>To establish interaction patterns you first need to audit the existing UI. Using <strong>Edit</strong> functionality as an example, go through all instances of editing in the product and ask yourself these questions:</p><ul><li>What happens when an edit button is selected?</li><li>Does the page state change from read to edit?</li><li>Is the edit form displayed in a modal?</li><li>Is the edit form displayed in-line?</li><li>Is this consistent across all the product’s digital touch points?</li></ul><p>After conducting the audit identify where there are inconsistencies in the interactions and work towards establishing a way to complete the task with less variations. Repeat this process for other common tasks like creating, reading, and deleting.</p><h3>5. User jobs and stories</h3><p>For a product to be successful it needs to not only be usable, but also be useful. Design based on ideas and functionality might produce visually appealing and usable interfaces, but it doesn’t guarantee you will be creating something that meets the user’s needs. As a UX designer it’s your responsibility to learn your user’s needs and surface them throughout the design process.</p><p>Talk to your users. Try to uncover why they hired you and what they expect your product to do. Convert what you discover into user stories and put the stories <strong>right into your design files</strong> so you and everyone can see them. This will ensure you are putting the customer’s needs first when creating and evaluating designs.</p><h3>Conclusion</h3><p>The role of the UX Designer is continuously evolving to keep up with the industry so tray and stay flexible and continue to evaluate if the work you are doing is impactful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ac59c74c2fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design-led planning in an Agile model]]></title>
            <link>https://medium.com/fidelity-design/design-led-planning-in-an-agile-model-98a6549b8f77?source=rss-d336eb620130------2</link>
            <guid isPermaLink="false">https://medium.com/p/98a6549b8f77</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[fidelity-associate]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Brandon Houlihan]]></dc:creator>
            <pubDate>Tue, 25 Feb 2020 13:59:28 GMT</pubDate>
            <atom:updated>2020-06-24T13:28:09.900Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Design-led planning in an agile model</strong></h3><h4>Design teams at Fidelity are improving the scheduling and prioritization of their work by making planning a design-led activity</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M7GqlI4PsEGL5M-ug_d8TA.png" /></figure><p>I’m a member of a design team that works with 4<strong> </strong>different Agile product teams. Each one of those product teams depends on us to conduct research, conceptualize products, design interfaces, and build interactive prototypes. Planning this amount of work would be hard enough if we were operating as a single, embedded product team—doing it as a resource that supports multiple product teams at the same time can feel daunting.</p><h3>Dependency meetings</h3><p>So how do we decide what to work on and when to work on it? We start by conducting dependency meetings with each of the product teams we work with. The meetings are scheduled at the beginning of each quarter and the goal is to establish the following things.</p><h4>1. An understanding of the products</h4><p>Before our team can commit to any work we need to understand the products we will be working on. Sometimes we start designing interfaces without fully understanding what we are working on. The reality is that our team can’t determine the correct design activities to conduct if we don’t understand a few high-level things about the products:</p><ul><li>The business goals</li><li>The product team’s roadmap</li><li>The users we are designing for</li></ul><h4>2. The state of the products</h4><p>The work our design team does also depends on where the products are in the product development lifecycle. To get a better understanding of this we ask the product teams these questions:</p><ul><li>Does the product currently exist?</li><li>Are we measuring the product?</li><li>Has any research been conducted on this product or a similar concept?</li><li>Has any design work been done?</li><li>Has any development work been done?</li></ul><p>Answering these questions helps us determine <em>what</em> we should be working on in the quarter. Sometimes a product is just a hypothesis in a Word document and the next best step will be to conduct a <a href="https://medium.com/fidelity-design/how-a-product-design-framework-guides-ux-research-de0e371384e9">Right Problem</a> research study to learn the unmet needs of our customers <em>before</em> we start designing the solution.</p><p>Other times a product is much further along and the only work that needs to be done is minor updates to an interactive prototype that has already been built. In this case we know that product won’t require a lot of work and our team won’t spend a lot of time or resources on it.</p><h4>3. The design work</h4><p>The work our design team <em>can</em> and <em>can’t</em> commit to doing will vary based on the structure of our team. Last year our team operated without a dedicated researcher for 6 months, so we couldn’t commit to as many research studies as we would have liked to during that time.</p><p>Not being able to commit to everything is totally acceptable. It’s better to set that expectation during planning, so product teams can accurately evaluate our team’s capacity to do work and adjust their timelines if needed.</p><h4>4. A schedule of the design work</h4><p>The last thing we do in the dependency meeting is create a schedule of when our design team will conduct and complete the work we committed to in the quarter. I’ll demonstrate how we’ve been doing this in the next section.</p><h3>Visualized planning with Mural</h3><p>Our team has had great success using <a href="https://mural.co/">Mural</a> to visually represent the work we commit to for the entire quarter. Mural is an effective tool because it’s simple to use, collaborative, and visual. The Mural we create during our dependency meetings looks like like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pr-34mjd0-kRTSoXuc98mw.png" /></figure><p>The Mural is composed of 3 main components:</p><ul><li>Epics</li><li>Sprints</li><li>Stories</li></ul><p>These are all terms used in Agile. I’ll do my best to describe what each term means so you can use them or create your own labels that work for your team.</p><h4>1. Epics</h4><p>Each row in the Mural represents an <a href="https://www.atlassian.com/agile/project-management/epics">epic</a> and the name of the product team building the epic. Think of epics as large bodies of work that can be broken down into specific tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1k0fE6lCVwZkq2EQx45AuQ.png" /></figure><h4>2. Sprints</h4><p>Each column in the Mural represents one sprint and the duration of the sprint. Think of sprints as short, time-boxed periods when your team works to complete a set of tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G7KWzZg0QHivTzDC6_iFpA.png" /></figure><h4>3. Stories</h4><p>We use sticky notes to represent the work our design team will commit to in the quarter. Each sticky note represents a small body of work, no larger than the size of an Agile story. We work with each product team to write and position sticky notes in the sprints (columns) to schedule when our team will conduct that work. The scheduling of our design work depends on 2 things:</p><ul><li>When the product teams need the work completed</li><li>Other work our team has committed to for the quarter</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*viPKChLmDALyXtjJaJ9Gww.png" /></figure><p>To speed up the process of writing and scheduling work, our team has created a set of template sticky notes based on the type of work we do most frequently. This saves us from having to write a new sticky note every time we add a task that is typically used in most stories. The template sticky notes don’t cover everything, so we always have to write some in manually.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V8lURh8-Fl58WbEa8ueQ1A.png" /></figure><p>We’ve also found it really effective to color code the sticky notes based on the type of work they represent. This allows us to quickly see where our efforts are being spent and signals where we might be over- or under-capacitated.</p><ul><li>Yellow = Research</li><li>Blue = Design</li><li>Pink = Development</li></ul><p>For example, if a sprint has a ton of yellow sticky notes it’s clear that we’ve scheduled too may research activities and some of that work will need to get moved to a later sprint. In the example below you can see that we need to adjust some of our research work from sprint 2 to sprint 4 or we’ll be at risk of not being able to complete the work we’ve planned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6XjMgTUByNRx1g9fAcqBjQ.png" /><figcaption>What it looks like when a sprint becomes over capacitated with research work</figcaption></figure><p>By the end of the planning, our design team and each product team have a clear view of what we will be working on throughout the quarter. In an Agile work environment, priorities often shift, so this schedule isn’t set in stone but it’s a great starting point.</p><h3>Closing thoughts</h3><p>It’s important to make the planning of design work our first priority before we begin the tasks of researching, conceptualizing products, and building interfaces. My team has found Mural to be an essential tool in this planning process because it allows for distributed teams to collaborate. Comprehensive planning allows our design team to smoothly coordinate with Agile product development strategies and effectively support multiple product teams at the same time.</p><p>#FidelityAssociate</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98a6549b8f77" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fidelity-design/design-led-planning-in-an-agile-model-98a6549b8f77">Design-led planning in an Agile model</a> was originally published in <a href="https://medium.com/fidelity-design">fidelity-design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started in Design Sucks]]></title>
            <link>https://blog.prototypr.io/getting-started-in-design-sucks-784b000709c4?source=rss-d336eb620130------2</link>
            <guid isPermaLink="false">https://medium.com/p/784b000709c4</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Brandon Houlihan]]></dc:creator>
            <pubDate>Fri, 13 Sep 2019 13:53:49 GMT</pubDate>
            <atom:updated>2019-09-13T14:25:20.113Z</atom:updated>
            <content:encoded><![CDATA[<p>I often see people sharing stories about how they are struggling to get their first design job. Know this, it’s not just you that’s having a hard time, everyone I’ve know has gone through this in one way or another. I want to share a story about particularly awful interview I had early on in my career that I thought I’d never get past.</p><h4>Putting Myself Out There</h4><p>In 2009 my wife and I moved from Massachusetts to North Carolina. I didn’t know anyone in NC and I didn’t have a job lined up. I had a few years of experience doing a wide variety of things including film production, front end development (CSS wasn’t a thing yet) quality assurance, and customer support. These jobs exposed me to working in the web industry. None of this was out of the ordinary back then, everyone working in the web industry did all kinds of weird and varying tasks. Although I didn’t have much experience I knew I needed to put myself out there and start applying for the jobs I wanted.</p><p>During my first year in NC I applied to a lot of jobs and didn’t get many interviews. The interviews I did get were somewhat uneventful, but there is one interview I will never forget because of how comically horrible it was! The job position was posted as a Flash Designer. This was pre-iPhone days and <a href="https://en.m.wikipedia.org/wiki/Adobe_Flash">Flash</a> was still a relevant and popular way to create websites because most people were viewing websites on desktop computers with browsers that supported Flash.</p><p>The job description was kind of vague. It sounded like the company needed someone to produce graphics and animations to be used in the creation of Flash websites. I didn’t fully understand what this involved but it sounded awesome, so I applied, and for some reason I actually got an interview! I didn’t have a portfolio at the time but I did have access to a computer and the internet so you know what that means…Photoshop tutorials!</p><p>Back in the early 2000s I had two main sources of learning, <a href="https://abduzeedo.com/">Abduzeedo</a> and <a href="http://blog.signalnoise.com/">Signalnoise</a>. Pretty much everything I learned about creating digital graphics in Photoshop came from those two blogs. Now don’t get me wrong, I learned a bunch of awesome techniques from those sites but what I learned wasn’t exactly the most practical knowledge to have when trying to get my first job as a designer. All I knew back then was I wanted to make visually interesting things for the internet, whatever that means.</p><h4>The Interview</h4><p>I show up to the interview and walk in to a very nice office. The scene was exactly what you would expect to see at a web design agency ten years ago. Exposed brick, artwork hanging on the walls, dudes in Star Wars t-shirts working on multiple monitors. I was pretty nervous but also excited! Upon my arrival I met the guy who would conduct my interview. Let’s call him “Steve” because I don’t remember his name and I don’t want to personally call him out. I sat down in Steve’s office and he began asking me questions about my interest in the job and my prior work experience. I thought I was doing well and everything was going normal then all of the sudden the interview got really awkward.</p><p>Steve started asking me about my experience developing websites with Javascript and PHP and if I could pull up a couple of live sites we could look at together. Not only did I not have any live sites to show him I didn’t even know what PHP was! In my defense I thought the position was more focused on designing than coding…guess not. I tell Steve that I haven’t built any websites but I did have design work I could show him. I proceed to pull out a folder containing prints of things I made from various Photoshop tutorials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gpPiHhENmhJyNQy0MK__yA.png" /></figure><p>One example of design work I showed Steve was a circular object I created by combining shapes, colors, and blending modes in Photoshop. I learned the technique from a tutorial on <a href="http://blog.signalnoise.com/2008/11/02/signalnoise-tutorial-the-o-series/">James White’s O-Series</a>. For the purpose of this post I tried replicating one of these objects in Sketch, which you can see in the example above. I think it came out alright!</p><p>I showed Steve a bunch of other things I made from tutorials, like gel buttons. Remember when <a href="https://www.sketchpad.net/aigel1a.htm">gel buttons</a> were the hotness? The worst offender in my portfolio was a poster I made featuring a couple of UCONN men’s basketball players. It looked like one of those bumper graphics you see on ESPN in between segments when 3–4 athletes are all in different positions and bright beams of light are shooting out from behind them liker lasers.</p><p>I thought my work was awesome because I had fun making it. Steve was kind of thrown off by what I was showing him. From here on out I don’t think he really knew what to do with me and honestly I understood why. I was interviewing for a position that I was not prepared or qualified for, I had no real world design experience, and I was showing him pages of irrelevant things I made from Photoshop tutorials. I probably shouldn’t have gotten that interview but there I was. Steve was not impressed and it showed.</p><blockquote>How was I ever going to get a job doing design work if one of my first interviews went so horribly wrong?</blockquote><p>I don’t remember the rest of the interview or even leaving the building but I do remember driving home feeling completely devastated. I emailed Steve the next day to thank him for meeting with me but unsurprisingly never heard back. I started to doubt myself and question if I was cut out for this industry. How was I ever going to get a job doing design work if one of my first interviews went so horribly wrong?</p><p>I let myself be upset for a few days then I got back to applying for jobs. It was slow going for a while but I continued to get interviews and with each interview I learned more about what skills I needed to work as a designer. I didn’t stop doing Photoshop tutorials, I just did different ones that were more focused on the type of work I heard companies say they were looking for during my interviews. Sticking with it paid off because several months later I finally landed a design job!</p><p>Getting started in design wasn’t easy for me…it straight up sucked! Ten years later I can write this post and laugh about some of the things I did and went through early on in my career. If you learn from your bad experiences and don’t let them slow you down you’ll eventually get where you want to be. If I can do anything to help you get started in design please let me know, even if you just want to share stories about how to get past awful interviews!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=784b000709c4" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/getting-started-in-design-sucks-784b000709c4">Getting Started in Design Sucks</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[Providing Value Beyond Visual Design]]></title>
            <link>https://brandonhoulihan.medium.com/providing-value-beyond-visual-design-46e419473077?source=rss-d336eb620130------2</link>
            <guid isPermaLink="false">https://medium.com/p/46e419473077</guid>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[advice-looking-back]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brandon Houlihan]]></dc:creator>
            <pubDate>Fri, 09 Mar 2018 16:38:16 GMT</pubDate>
            <atom:updated>2018-03-12T12:18:43.005Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qh9e2Xhd2f2kqSFDtS9pvw.jpeg" /></figure><p>There is a Slack team for designers in the Raleigh/Durham area that I participate in and last week one of the members asked a really interesting question to our general chat channel. This person asked:</p><blockquote>“What do you know as an experienced designer that you really wish you could have told yourself when you were just starting out?”</blockquote><p>I’m not sure I qualify as an experienced designer but this is how I responded to the question:</p><blockquote>“I wish I learned earlier on in my career how to provided value to the people and organizations I worked with beyond visual design.”</blockquote><p>The first couple years as a designer I was hyper focused on visual design. I spent all my time learning how to edit images, create icons, design interfaces, etc. This is how I thought I could provide the most value as a designer, but there were a lot of other things I could of been doing that I just didn’t know about or thought I didn’t have the ability to do. I’d like to share some examples of how I’ve provided value to people and organizations beyond visual design so that you can look for similar opportunities, regardless of where you are in your career.</p><h3>Setting and Sharing Operational Goals</h3><p>I always set and share operational goals for myself. These are my weekly or monthly goals that determine my design deliverables. I include the <strong>problem</strong> my work aims to solve,<strong> who</strong> I’m trying to solve the problem for, how much <strong>time</strong> I will spend on the work, and what <strong>form</strong> I will deliver it in.</p><p>This is what one of my weekly operational goals looks like. I share these goals with other designers and product team members during standup and check in meetings.</p><blockquote>People currently do not have a way to create new accounts without being invited to the app. I will design a new account creation flow and present it as an interactive prototype to the product team during next week’s check in.</blockquote><p>Setting and sharing operational goals is important to the people I work with because the goals set clear expectations for what I commit to deliver and when I will deliver it. The visual design work I do becomes far less valuable if my co-workers don’t know what to expect from me.</p><h3>Contribution to Design Process</h3><p>Operational goals are important, but getting work done isn’t the only way you bring value to an organization as a designer. The way in which we work has a large influence on the quality of work we produce and how efficiently we produce it. Some of the most valuable work I’ve done has come in the form of contributions to process. Here is an example of one of those contributions.</p><h4>Design Retrospective</h4><p>Most of the product teams I’ve worked with conduct <a href="https://www.scrum.org/resources/what-is-a-sprint-retrospective">sprint retrospectives</a> to acknowledge where the product development process is working and how it can be improved. A sprint retro consist of questions like these.</p><ul><li>What went well in the Sprint?</li><li>What could be improved in the Sprint?</li><li>What will we commit to improve in the next Sprint?</li></ul><p>Last year I started conducting<em> </em>quarterly<em> </em><strong>design team retrospectives</strong> with the team I was managing. This gave us a way to evaluate the work we were doing as a design team in the same way our product teams evaluated the work they did in a sprint. We adjusted the questions to fit our needs and it worked well for us. These are the type of questions we asked.</p><ul><li>What have we been doing well as a design team?</li><li>Where could we improve as designers?</li><li>Where could we improve our design process?</li><li>What should we start doing that we currently aren’t?</li></ul><p>Asking these questions and having open discussions around the answers helped us identify areas in which we needed to improve and made us commit to making those improvements by the time we held our next retro. You don’t need to be the person who introduces a process to help shape the way your organization works. Any contribution you make that helps define a process, no matter how big or small, is valuable.</p><h3>Creating Inclusive Design Culture</h3><p>Getting other people involved with design is a great way to show that you care about and can make a positive impact on company culture. Here are some quick and relatively easy ways I’ve been trying to include people who aren’t “designers” in my work and make design more inclusive.</p><h4>Usability Testing</h4><p>I always try to have developers in the room when conducting usability tests because their work has as much of an impact on a user’s experience as my work. When a developer sees someone using, and often struggling to use the product they built, they not only feel included in design process but also gain a sense of responsibility for the overall user experience of the product.</p><h4>Discovery Methods</h4><p>When I’m in the early stages of a design and conducting something like a <a href="https://methods.18f.gov/discover/design-studio/">Design Studio</a> I include people who are not part of the design team. This is a great way to make product defining<strong> design decisions</strong> more inclusive to everyone because discovery methods are extremely approachable and don’t require people to learn software in order to participate.</p><h4>Feedback Loops</h4><p>I find it shockingly easy to get stuck in feedback loops that only involve other designers. I’m guilty of this behavior and it’s hard to break out of it. Lately I’ve been trying to make more of an effort to show people outside of the design team what I’m working on and listen to their feedback. One of the quickest ways to make design non-inclusive is to disregard someone’s feedback simply because they aren’t a “designer”, but if you listen to everyone’s feedback with equal respect you’ll gather more diverse viewpoints on the work you are doing which in the long run will help your organization create better products.</p><h3>Closing Thoughts</h3><p>I’m sharing these examples with you because they are all things I wish I started doing earlier on in my career. If you have any questions about the examples I shared please let me know and if you have your own ways in which you provided value to the people and organizations you work with beyond visual design please share them, I’d love to read about it!</p><p>I talked about inclusive design and getting everyone you work with involved in design processes. I think this is an extremely important issue and one of the biggest blockers our industry faces when it comes to designing great products. If you find yourself or your organization treating design as something that’s inclusive to “designers” check out <a href="https://library.gv.com/@dburka">Daniel Burka’s</a> incredible writing on why <a href="https://library.gv.com/everyone-is-a-designer-get-over-it-501cc9a2f434">everyone is a designer</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46e419473077" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Expecting Expectations]]></title>
            <link>https://brandonhoulihan.medium.com/expecting-expectations-ad2eb2cd1099?source=rss-d336eb620130------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad2eb2cd1099</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Brandon Houlihan]]></dc:creator>
            <pubDate>Tue, 13 Feb 2018 16:26:35 GMT</pubDate>
            <atom:updated>2018-02-13T16:29:31.620Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CJVlSFeGyUP0rg4cye9hFQ.jpeg" /></figure><p><em>A story about how I’ve been using the analogy of a shopping at a grocery store to demonstrate that a user’s experience is not entirely in our control, why it’s not a bad thing, and how expectations can help us design better products.</em></p><p>The idea of <strong>designing experiences </strong>has become so widely accepted in the digital product world that we like to think we have control over the way people interact with and experience the products we make. I believe that if you are designing anything that will be viewed on a screen people are going to have expectations of how it should look and how they can interact with it, regardless of the way you design it.</p><p>It’s hard for teams, especially startups, to accept this. For years I too struggled to come to terms with this. It feels unjust to think that something or someone else can have an influence on the way people experience what I make. To help myself and the teams I work with get comfortable with this fact I’ve been using the analogy of a shopping at a grocery store to articulate how a user’s experience is not entirely in our control, why it’s not a bad thing, and how expectations can help us design better products.</p><h4>Digital products are like grocery stores</h4><p>I regularly shop at Trader Joe’s and Harris Teeter. I’m comfortable in these stores. I know what food they sell. I know where the food is located. I know how much the food will cost. I know how the cashier will speak to me during checkout. I can predict with pretty good accuracy what my experience will be like when shopping at these stores.</p><p>Sometimes I find myself in a grocery store that I’m unfamiliar with. <strong>SCARY STUFF</strong>. Let’s say I’m in Los Angeles and I need some spinach to make a salad, so I swing into Ralphs. I expect the spinach to be located on the far left wall in a cooler. The spinach should cost anywhere between $2.50 and $4.00. If it cost more I’m going to be pissed. I expect the spinach to have other vegetables around it that can be used to make my salad, like lettuce and carrots. When I pay for the spinach the cashier should ask me how my day is going and if I had trouble finding anything.</p><p>Maybe the spinach isn’t where I expected it to be. It might be located in the very center of the store with a huge sign at the end of the aisle trying to yell <strong>SPINACH</strong>. I might not see the sign and waste five minutes walking around aimlessly. Hopefully when I find the spinach it doesn’t cost five bucks because I’m seriously going to be pissed. When I go to pay for the spinach the cashier better be nice to me, but not too nice…I’m not hear to make friends.</p><p>The point I’m trying to make is that Ralphs can intentionally design every aspect of their store in a way that makes sense to them but I’m going in there with a clear expectation of what my experience should be like. How could I not? Shopping at grocery stores is something I’ve been doing my whole life. It’s an experience that’s deeply ingrained in my life, much like using websites and mobile applications.</p><h4>How to leverage expectations</h4><p>It’s important to remember that we are designing products for other people, not ourselves, and those people are going to have strong expectations of how things should look and work. Don’t fight this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*X1RUEuLTnULIpxOE378koA.gif" /></figure><p>A better way to approach this is to try and understand what expectations people have for the type of product you are designing. Talk to your users or target audience about <strong>other</strong> products they use. Find out how those products solve their problems and where they fall short. Include them in your design process to gain a better understanding of how <strong>they</strong> expect the information in your product to be organized. There are a bunch of <a href="https://methods.18f.gov/">discovery methods</a> you can utilize to get started.</p><p>If you are designing a grocery store talk to people about the grocery stores they currently shop at. Ask them where they think the spinach should be located and how much it should cost.</p><p>Digital product design is no different.</p><p>If you are designing an app for a clothing company talk to people about the apps they currently use to buy clothes. Ask them where they think the shirts should be located and how much they should cost.</p><h4>Conclusion</h4><p>Acknowledging and designing for expectations seems simple but it’s much harder in practice. If you are a designer the biggest thing stopping you from doing this is probably yourself. Try to be open to the fact that what makes sense to you might not fit the <a href="https://www.nngroup.com/articles/mental-models/">mental model</a> of the people you are design for.</p><p>This doesn’t mean you have any less control over the experience you are trying to create. Understanding what users expect from your product will help you make better informed decisions on how you can improve the experience and what downfalls of similar products you should avoid.</p><p>I’ll leave you with a very public display of what happens when a product is designed in a way that blindly ignores expectations.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FocBAa9Y0FSs%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DocBAa9Y0FSs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FocBAa9Y0FSs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9ff781322c6afc5eed8aba499dc84359/href">https://medium.com/media/9ff781322c6afc5eed8aba499dc84359/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad2eb2cd1099" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a User-Centric Organization by Taking Initiative]]></title>
            <link>https://brandonhoulihan.medium.com/building-a-user-centric-organization-by-taking-initiative-6add0793dae3?source=rss-d336eb620130------2</link>
            <guid isPermaLink="false">https://medium.com/p/6add0793dae3</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Brandon Houlihan]]></dc:creator>
            <pubDate>Thu, 02 Nov 2017 18:28:23 GMT</pubDate>
            <atom:updated>2017-11-02T18:28:23.277Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*94omKSY5Cx4JHKaf0ZvW5w.jpeg" /></figure><p>At our last <a href="https://www.meetup.com/intent-design">Intent Meetup</a> we held a panel discussion focused on what it takes to build user-centric organizations. The event took place at <a href="https://americantobaccocampus.com/district/11">Full Frame</a> theatre in Durham and was co-hosted with <a href="https://www.meetup.com/Ladies-that-UX-Durham/">Ladies That UX Durham</a>. I got the chance to participate in my first panel discussion alongside Julia Swenson of Willow Tree, Julie Grundy of Bronto, and Mark Ferencik of McKesson.</p><p>For those of you who couldn’t make it I wanted to share my thoughts on the discussion points. Spoiler alert, building a user-centric organization is a tough task and I’m still trying to figure out how to do it. I hope you can take some of what I’ve learned and apply it to your initiatives.</p><h4><strong>1. Tell us about your company, title, role and responsibilities in your job.</strong></h4><p>My name is Brandon Houlihan. I manage the design team at Ticketmaster Mobile Studio in Durham, NC. We are a small group of designers, engineers, and product managers who utilize new and emerging technologies to create digital products for Ticketmaster.</p><p>Some our products take the form of mobile applications. We are also building new products on Google Assistant , Amazon Alexa and Facebook Messenger. Most of our work is exploratory by nature. We try things Ticketmaster doesn’t have the time or resources to test in the mobile space or with new technology.</p><p>My main responsibility is to ensure the health and well being of the design team. I work with each designer on their operational and personal goals and make sure they are doing the type or work they want to be doing. Another part of my job is to make sure the design team is properly positioned within our organization and on each product team.</p><h4><strong>2. Share an example of how you have advocated for UX within your organization, your approach, and how something changed due to your efforts.</strong></h4><p>The thing I’m most proud of when it comes to advocating for UX is not any specific method I‘ve implement or work I did on a project. It’s more about how myself and the design team have intentionally changed the way we talk about user experience and the impact that’s having on our organization.</p><p>I’ve been a part of several teams who put a lot of the focus of “designing” the user experience…so much so that we often, unintentionally, omitted the people we were designing for from the design process. I’ve found it hard for teams to include users in the product development process if we speak about user experience as something we can “design” and predict the outcome of.</p><p>Simply acknowledging that users might not understand, or use a product the way you intended opens the door to include those users in the design process, through methods like interviews and usability testing.</p><p>Now I’m seeing more people on our product talking about what steps we can take to validate our assumptions about the products we are making. This is a subtle change in the way we talk about design, but it takes a real conscious effort to speak like this on a daily basis.</p><h4><strong>3. Tell us about a time you advocated for UX and failed. What happened? What would you have done differently if you had a do-over?</strong></h4><p>For a long time when I tried to introduce UX methods to the teams I was working on I only talked about how the end user would benefit from those methods. My efforts were often met with fierce objection, especially from product managers.</p><p>I would often get asked “what is your motivation for wanting to do this”. I would typically give a response like “I want the product to be as usable as possible”. I so badly wanted to advocate for the user that I never considered what benefits my initiatives would bring to the product team.</p><p>After several failed attempts, I realized that I needed to tie in business and operational benefits if I wanted to get everyone on board. I also realized that I needed to visualize what I was proposing. It really helps when people, especially product managers, can visualize where UX fits into the product development process and what benefits it provides to that process.</p><p>At the start of your next project try to convey early on that UX research methods will help the team understand whether or not the product they have set out to build is going to meet the needs of the intended audience. Talking to the user early on will save time on planning and development cycles.</p><p>Once you get that started you can follow up research efforts with usability testing to try and validate the team’s assumptions about the product they are building.</p><h4><strong>4. What do newer UX practitioners tend to misunderstand about taking UX initiative?</strong></h4><p>Taking UX initiative is not just about you, the designer, implementing user experience methods into your product development process. In order for those methods to catch on and stick, you need to get your co-workers involved in the process. You need developers and product managers to not only have interest in user experience, but also feel responsibility for it.</p><p>Building a user-centric organization is as much about culture as anything else and culture ins’t created in isolation. Take steps to include everyone on your product team in your efforts. Take developers with you when conducting interviews and performing tests. They will quickly see the impact their work has on the user’s experience and UX will start to become less of a thing the Designers do and more of a thing the organization embodies.</p><p>The other thing I’d like to mention is that almost everyone I know in tech is constantly trying to make their organization more user-centric. By reading articles online it’s easy to think that everyone else has user-centric design figured out and their organizations always do what’s best for the user. It’s simply not the case. If you are doing your best to make your organization more user-centric you should feel content with your efforts.</p><h4><strong>5. How do you know when to keep pushing an organization to be user-centric or when it’s hopeless and you should get out?</strong></h4><p>With any job you need to create opportunities for the things you want to do. While doing that you also need to obtain a balance between your efforts and life outside of work. It’s extremely important that you don’t internalizing every single struggle your organization has.</p><p>If your goal is to work as part of a user-centric organization and your efforts aren’t moving the company in that direction, take a step back to try and evaluate how much stress your efforts are bringing to your personal life.</p><p>If you go home after work and can’t hold a conversation with your friends or family without being stressed about your job it’s probably time to move on. Even if your efforts eventually make your organization more user-centric it’s not worth it at the cost of your personal relationships, nothing is.</p><p>You should also reach out to someone who works at an organization you consider to be user-centric and ask them questions about their experience there and how the organization operates. This will help you gain perspective on just how user-centric your organize is, or isn’t. It’s hard to tell just how bad things are, or how good they are at your job without perspective.</p><h4><strong>6. What UX initiatives are you working on right now at your current job?</strong></h4><p>I’m trying to research and establish new ways to do usability testing. One of our biggest blockers is trying to recruit testing participants. It takes time and is shockingly hard to get people to come into your office to test a product, even when you offer proper compensation.</p><p>We’ve been working on ways to do remote testing and somewhat less formal testing out in public spaces. Testing in public spaces is a bit limiting because you can’t perform certain methods of testing, but it’s a fantastic way to get your product in the hands of people outside of your office and observe how they use it.</p><h4>Closing Thoughts</h4><p>Building a user-centric organization is hard work and it’s going to take time. Human Centric Design is not just about the way you conduct work, it’s about the culture of the people behind the work. Get other’s involved with your initiatives and over time you’ll start to see change. Just make sure you keep a healthy work/life balance while doing so. If you want to talk about this more drop a comment. Thanks for reading 👍</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6add0793dae3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Give Successful Design Feedback]]></title>
            <link>https://brandonhoulihan.medium.com/how-to-structure-product-feedback-b7a28549ad0c?source=rss-d336eb620130------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7a28549ad0c</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brandon Houlihan]]></dc:creator>
            <pubDate>Mon, 15 May 2017 17:37:10 GMT</pubDate>
            <atom:updated>2022-02-10T14:50:29.207Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hhz8dHXpbD5Q7RYoJzykHA.jpeg" /></figure><p>Giving design feedback is a tricky thing. When done properly it can serve as a valuable tool that fosters positive relationships and improves the design. When done poorly it can feel like a personal attack and make designers hesitant to share their work. I’ll share the guidelines and structure I’ve been using to help me give more successful design feedback.</p><h3><strong>Guidelines</strong></h3><p>There are a few guidelines to follow when giving feedback that will ensure your opinions are not only heard but also trusted while helping the person receiving the feedback feel respected.</p><h4><strong>Don’t Make Generalized Statements</strong></h4><p>It can be really hard to avoid generalized statements about design, especially when you have experience in the subject matter and feel strongly about it. I have received and given many statements like this:</p><blockquote>“No one will understand how to use this.”</blockquote><p>When we speak like this we are implying that other people share our thoughts and experience. Before you start giving feedback make a conscious effort to recognize you are speaking for yourself and no one else. If other people involved have similar thoughts give them the opportunity to express those thoughts.</p><h4>Don’t make it personal</h4><p>The feedback you are giving is on the work, not the person or group of people doing the work. The difference between these two things is subtle but makes all the difference in how well your feedback is received. Avoid using words like y<em>ou </em>and y<em>our. </em>Here is an example of personalized feedback with a generalized statement:</p><blockquote>“Your check out page is really complicated, no one will understand how to use this.”</blockquote><p>Statements like this can come across like a personal attack and make it hard for others trust you and your feedback. When giving feedback try and remember you are evaluating the work, not the person.</p><h3>Structuring Feedback</h3><p>Now that we have a few guidelines to follow let’s talk about how to structure the feedback. When I’m giving a presentation I don’t go into it blindly. I want a game plan so I can deliver a clear point of view and won’t stumble over my words. Giving feedback is no different than giving a presentation. You can and should intentionally structure it. Here’s how.</p><h4><strong>1. Provide Context</strong></h4><p>Providing context gives the person receiving feedback insight into your goals and motivations, which will help them understand where your feedback is coming from. Describe <strong>what </strong>you were trying to accomplish.</p><blockquote>“I was trying to purchase a bag of coffee.”</blockquote><h4><strong>2. Describe What You Expected</strong></h4><p>We all have expectations of how things should look and work based on our own experiences. Describing what you expected to happen or see is a good way to frame your feedback — by clarifying your expected output or outcome, you’re also empowering the listener to more effectively empathize with your point of view. Speak about <strong>your</strong> experience and describe what <strong>you</strong> expected to see or happen.</p><blockquote>“I expected to see the buy button at the top of the page, because that’s where it is on a lot of the sites I use.”</blockquote><h4><strong>3. Describe What Actually Happened</strong></h4><p>What you expect to happen and what actually happens don’t always align. After describing what you expected to happen, describe what <strong>actually </strong>happened.</p><blockquote>“I was never able to find the button to buy the coffee.”</blockquote><p>Now the person receiving your feedback should have a clear understanding what you were trying to accomplish, what you expected to happen, and what actually happened.</p><h4><strong>4. Make goal based suggestions</strong></h4><p>If you want to productively give suggestions on how to improve the design, focus on the goal, not the solution to the goal. Leave the implementation of the goal up to the person receiving your feedback. This will show others you have confidence in their ability to address your problems and improve your experience.</p><blockquote>“My experience would be better if I was able to complete my purchase.”</blockquote><h3><strong>Putting It All Together</strong></h3><p>If you follow these guidelines and this structure your thoughts you will end up with an objective and precise statement that empowers the person receiving the feedback to address your concerns.</p><blockquote>“I was trying to purchase a bag of coffee and I expected to see the buy button at the top of the page, because that’s where it is on a lot of the sites I use. I was never able to find the button to buy the coffee. I would have had a better experience if I were able to complete my purchase.”</blockquote><p>Let me know how it goes and if you have any tips of your own for providing design feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7a28549ad0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Video Recording Hack For User Testing]]></title>
            <link>https://brandonhoulihan.medium.com/video-recording-hack-for-user-testing-67175b1cc86e?source=rss-d336eb620130------2</link>
            <guid isPermaLink="false">https://medium.com/p/67175b1cc86e</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[recording]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[videos]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Brandon Houlihan]]></dc:creator>
            <pubDate>Tue, 21 Feb 2017 18:45:02 GMT</pubDate>
            <atom:updated>2017-03-24T19:00:34.976Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a pretty cool hack I’ve been using to make recording video easier on myself and less disruptive to our participants during user testing. To do this you will need a room with a table, a laptop, <a href="https://support.apple.com/downloads/quicktime">Quicktime</a>, a phone with the app you are testing and sticky tack…that stringy stuff used to hold up paper.</p><p>📝 As always, make sure you get written consent from your test participants before you begin recording. Let’s get started.</p><h3>Recording Video</h3><p>1. Find a room with a table to conduct your test in. Position your laptop on the table so it’s facing the direction of the participant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gghGVlLcQBdapx5JOhuKVA.png" /></figure><p>2. Place two pieces of sticky tack on the table between the laptop and the end of the table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cuwpYEl5kxSTejqqu9U9rQ.png" /></figure><p>3. Push your phone down onto the sticky tack so it holds the phone in place. This is going to ensure the person using the phone won’t move it out of view of the camera when they are completing their task. Have the participant sit at the table with the phone easily in reach, facing the open laptop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*itbSKVjxG3_QIkZgqphYCw.png" /></figure><p>4. Open Quicktime and begin a New Movie Recording. <strong>Don’t forget to hit the red button to start recording! </strong>When the recording starts you will see yourself and your participant in the recording window.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IBMF-vRIkG3AHT4pl4Bgag.png" /></figure><p>5. Once you have started recording tilt the laptop down so the mobile phone becomes centered in the screen. This will keep the phone and the participants hand in the field of view so you can see what they are interacting with during the test. <strong>Don’t move the laptop from this position.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gzj5ggy0rwQnppSKMBOXHA.png" /></figure><p>6. Turn the screen brightness on your computer all the way down. This will make your laptop look like it’s turned off. This step is important because it prevents the participant from seeing their hand and the phone during the recording, which would be really distracting.</p><p>I’ve adjusted the position of my laptop in the example below to clearly demonstrate what it looks like to the user when the screen brightness is all the way down, but make sure you <strong>keep your laptop tilted down</strong> so it records the phone on the table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3DN2FoWaV9zRFxfNEsLwvw.png" /></figure><p>Now you have video recording, the laptop screen appears to be off (hack) and all you have left to do is run your test. I have found this recording method works particularly well when conducting a <a href="https://www.nngroup.com/articles/thinking-aloud-the-1-usability-tool/">Retroactive Think Aloud</a>.</p><p>8. When the participant is done with their task turn the screen brightness back up, stop the recording and save your video.</p><p>That’s it, you did it! You now have a surprisingly good recording of a person using your app without having to do any complicated camera setup or integrate with any third party apps. This also works well for recording interviews or follow up questions.</p><h3>Watching The Recording</h3><p>When you play back the recording you will notice it’s upside down and flipped on it’s side. This is easily fixed in Quicktime by selecting <strong>Flip Horizontal</strong> and <strong>Flip Vertical</strong> form the <strong>Edit</strong> menu.</p><p>If you have any questions about this recording method let me know, I hope this was helpful 👍 ✌️.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67175b1cc86e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>