<?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[Building FreshBooks - Medium]]></title>
        <description><![CDATA[Product, Design, and Development at FreshBooks - Medium]]></description>
        <link>https://medium.com/building-freshbooks?source=rss----3a7c8d75f488---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Building FreshBooks - Medium</title>
            <link>https://medium.com/building-freshbooks?source=rss----3a7c8d75f488---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 17:47:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/building-freshbooks" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Run Better Meetings]]></title>
            <link>https://medium.com/building-freshbooks/how-to-run-better-meetings-469218f37605?source=rss----3a7c8d75f488---4</link>
            <guid isPermaLink="false">https://medium.com/p/469218f37605</guid>
            <category><![CDATA[better-meetings]]></category>
            <category><![CDATA[run-better-meetings]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Tiff Nogueira]]></dc:creator>
            <pubDate>Tue, 02 Jan 2024 18:42:02 GMT</pubDate>
            <atom:updated>2025-04-09T02:41:31.743Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I will buy you a coffee if you aren’t getting glowing reviews about your meeting after following this guide. Seriously.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttps%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F1689888591%26show_artwork%3Dtrue&amp;display_name=SoundCloud&amp;url=https%3A%2F%2Fsoundcloud.com%2Ftiffany-nogueira-489799485%2Fhow-to-run-better-meetings%3Fsi%3D09c2f3372a6c407b8843a733fb44a8c3%26utm_source%3Dclipboard%26utm_medium%3Dtext%26utm_campaign%3Dsocial_sharing&amp;image=https%3A%2F%2Fsoundcloud.com%2Fimages%2Ffb_placeholder.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/1fe7116752fc35a58f7df0011be3c907/href">https://medium.com/media/1fe7116752fc35a58f7df0011be3c907/href</a></iframe><p>Before you continue reading, let’s make sure this article will be worth your time:</p><ul><li>Do you hold a leadership position in a recurring meeting?</li><li>Do you find meetings frustrating? Do they feel full of updates instead of anything substantial to move <em>the work</em> forward?</li></ul><p>If you answered yes to the above, continue on! You’ll leave with:</p><ul><li>2 key ingredients to create great meetings</li><li>4 tools to help you improve your meetings (including a copy-pasta-worthy meeting agenda template!)</li><li>The confidence to run great meetings that get glowing reviews</li></ul><h3>Why Some Meetings Suck</h3><p>Oh, the meeting. Sometimes dreaded; sometimes cathartic. What sets the great apart from the dull?</p><p>Some meetings feel like a waste of precious time. You know, the most scarce resource, the one we don’t have enough of? This is what the “should have been an email” crowd is feeling — this was an update and it didn’t require my synchronous engagement.</p><p>Worse yet is the meeting where nothing gets done. You could have sworn that marketing agreed to report back on the expected reach of our upcoming email campaign but no one else seems to remember. And now you have to either hope they own up to it or awkwardly call them out. But wait, aren’t you supposed to critique in private? Ugh, okay let’s just remind them and hope they bring it next week (marketers you know I love you, it’s just an <em>example</em>).</p><p>Another reason meetings suck? The right people don’t show up. You’ve worked hard to prepare something for the group, and whelp, your key stakeholder is missing in action. You’d better find out a way to update them, or worse, better wait until next week. Yikes.</p><p>My personal favourite is the meeting that gets canceled. It’s either an hour prior or 3 seconds prior and “Oops, I booked this but now it’s not happening”. It feels like a win in the moment, free time to get stuff done! But what does the canceled meeting say? It gives the impression that this group of individuals has nothing to work through. Which I find hard to believe for important folks like you.</p><p>Let’s recap. Some of the biggest issues around meetings are:</p><blockquote>Lack of engaging, thoughtful discussion<br>Lack of accountability<br>Lack of clarity<br>Lack of the right decision-makers<br>Lack of structure</blockquote><h3>Key Ingredients for Success</h3><p>To set up a meeting for success we need to consider 2 key ingredients:</p><ol><li>The right people</li><li>The right agenda</li></ol><h3>The Right People</h3><p>To have a successful meeting you need to get the right people to attend. Agree to a cadence that works for everyones schedule. Try to meet as often as is reasonable. Stick to it! Go ahead and send that calendar invite to block that precious time forevermore.</p><p>In Product, usually, your meeting will include your key stakeholders. At a minimum, you’ll want your Product Manager, Engineering Lead, and Designer present. For Leadership teams, this means you’re meeting with your peers and leader, and you have a separate meeting with your direct reports.</p><h3>The Right Agenda</h3><p>If you have the right people in the room, it’s our job as facilitators to ensure we’re talking about the most pressing issues.</p><p>A shared agenda with the same structure at each meeting is a game changer. It’s the secret to creating shared expectations that can transform a meeting into a capital-m-Meeting — the kind where things get done and it feels like a worthwhile investment of your time.</p><p>When we set up a consistent agenda for our meetings we are creating predictability. When you know what to expect in a meeting, you feel confident, prepared, and therefore comfortable. With that comfort comes a relaxed mind, which is key when you need to have difficult discussions or make tough decisions.</p><p>We can use frameworks and processes baked into our agenda that address the worst part of meetings and set the team up for success. These agenda ‘tools’ can unlock accountability, focus, and trust. Let’s review a few tools that can help us do just that.</p><h4>Build Focus</h4><p>The issues you choose to spend time on in your meeting matter. You want to use your precious time together to focus on conversations that require synchronous decision-making. Sure, yes, spend time getting your teammates up to speed on the latest developments if they are mission-critical, however, make sure you’re making time to get into the juicy issues that are holding your team back. The majority of the meeting should be about solving pressing issues.</p><p>One way to ensure you’re focusing on the most important issues is to spend a few minutes debating what the most important issues are before you dive in. Knowing that the team has chosen the most important issue to tackle minimizes tangents, and invites teammates to redirect to the issue at hand. Over time this exercise also builds a shared sense of prioritization amongst the team.</p><p>Once an issue is chosen as the priority, it can be very tempting to jump to solutioning. Resist the temptation! Spend time getting to the root of the issue. Introduce a framework like “5 whys” and ensure all parties are in agreement before you begin collaborating on solutions. If you find the same issue popping up week after week, it’s a sign you need to spend more time understanding the issue.</p><p>If you are having trouble finding the right thing to discuss, look to leading indicators that you can measure at the same cadence of your meeting. Once the group agrees that these are the right metrics, set targets, and monitor these KPIs. If the metrics aren’t hitting your targets spend time digging into the core issues as you see them.</p><h4>Build Accountability</h4><p>When we’re using our meeting to solve the most important issues, your tasks (or to-dos) that come from those solutions should be the most important things to complete.</p><p>What do you think will happen if, at your next meeting, you review the to-do’s you agreed to at the previous meeting? I’d expect that most items won’t be complete. This is normal, we all have competing priorities and a never-ending list of things that need to be done. However, let’s say that you continue to review to-dos three, four, or five weeks in a row. What will happen then? You’ll find that your attendees will complete their to-dos. In this situation, we’re faced with the impact of not completing our to-dos and the predictability of the meeting agenda prompts us to make an extra effort to move our work forward. We identify that we want to be the type of coworker who follows through on what we say we’ll do, but it takes a consistent process to show us how often we’re not delivering. <strong><em>Your agenda</em></strong> created accountability.</p><p>It’s not easy to be ‘that guy’. That guy who is reading to-do’s they <em>know</em> weren’t complete — especially the first few meetings after you’ve implemented this new agenda of yours. If a to-do isn’t complete, ask your teammate when they’ll have it done. So long as you come into this section with the right attitude the team will accept it and they’ll even begin to appreciate it. Remember, you’re doing this for the betterment of the team. To move your issues forward, and because as a leader, you want your team to hold you accountable to your own to-dos, too.</p><p>It is often unclear who is accountable for doing the work. If Carrie and I are both supposed to do something, then is it my fault it wasn’t done? Not really, no! Shared accountability is no accountability. To provide clarity for the folks in our meetings, we should spend time during the meeting to capture and review new to-dos. Everyone should have a shared understanding of what will get done and by what deadline and only one person should own that task. If a to-do is that two teammates should meet, assign responsibility to <em>one</em> of those people. If an issue is worth the time to discuss the next steps, it’s worth the time to clarify the details.</p><h4>Build Trust</h4><p>Here’s the secret to how I’m able to publish this article without a substantial coffee budget. To avoid bad meetings, we should regularly ask the team for feedback on the meeting itself. The way I do this is with the following question:</p><blockquote>I’m going to ask everyone to rate this meeting out of ten. Start with ten and deduct a point for each thing you wish had been done differently. I’ll ask you to share those reasons.</blockquote><p>You now have actionable items to make the meeting better for your specific team members and goals. Implement those suggestions! Iterate on the format, the reminders, and the agenda — whatever is suggested. By inviting attendees to give actionable feedback, and then acting on that feedback, the responsibility to create the ideal meeting is in turn owned by each attendee. This reinforces appreciation for their contributions and shows you value their attention.</p><h3>The Agenda</h3><ul><li>Review previous meeting to-dos (3 minutes or less — builds accountability)</li><li>Updates (3 minutes or less)</li><li>Issues<br>- Prioritize issues (5 minutes or less — builds focus)<br>- Identify the problem, then solution (the majority of the meeting!)</li><li>Review new to-dos (3 minutes or less — builds clarity)</li><li>Meeting rating out of ten (3 minutes or less — builds trust)</li></ul><h3>Let’s Recap</h3><p>Why do some meetings suck? What can we do?</p><blockquote>Lack of engaging, thoughtful discussion? <br><strong><em>Limit time for updates. <br>Spend time prioritizing issues as a group.<br>Choose issues that need synchronous discussion. <br>Focus on identifying the core issue before you jump to solving.</em></strong></blockquote><blockquote>Lack of accountability? <br><strong><em>Review the previous meetings to-dos at the beginning of each meeting.</em></strong></blockquote><blockquote>Lack of clarity?<strong><em> <br>Review new to-dos at the end of each meeting. Clarify expectations, and assign one person to be accountable for each to-do.</em></strong></blockquote><blockquote>Lack of the right decision-makers? <br><strong><em>Do what you can to get the right people to commit to attending on a regular cadence (quality is better than quantity).</em></strong></blockquote><blockquote>Lack of structure? <br><strong><em>Follow a consistent meeting agenda to set expectations and build trust.<br>Ask teammates to give feedback on the meeting itself, and implement ideas.</em></strong></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F26DNdV3b6dqn1jzR6%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F26DNdV3b6dqn1jzR6%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExYm80cDBmZ3MwcHcxMDloaXN0NWx5aTR4NnZvN2kzZTljOXpjN2Z6YiZlcD12MV9naWZzX2dpZklkJmN0PWc%2F26DNdV3b6dqn1jzR6%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/435260ce2a3998af5265320c2c00542f/href">https://medium.com/media/435260ce2a3998af5265320c2c00542f/href</a></iframe><p>Thanks for making it this far! Do you see a different problem with meetings? Do you have any tips and tricks? Please let me know in the comments.</p><p>My offer stands. If you implement these changes and you’re not getting glowing reviews, reach out, and I’ll do good on my offer of coffee.</p><p>These tips and processes are inspired by the Entrepreneurial Operating System outlined in the book, <a href="https://www.amazon.ca/Traction-Get-Grip-Your-Business/dp/1936661837">Traction by Gino Wickman</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=469218f37605" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-freshbooks/how-to-run-better-meetings-469218f37605">How to Run Better Meetings</a> was originally published in <a href="https://medium.com/building-freshbooks">Building FreshBooks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous Interview — How we do it at FreshBooks]]></title>
            <link>https://medium.com/building-freshbooks/continuous-interview-how-we-do-it-at-freshbooks-bd3eee6bf4?source=rss----3a7c8d75f488---4</link>
            <guid isPermaLink="false">https://medium.com/p/bd3eee6bf4</guid>
            <category><![CDATA[continuous-discovery]]></category>
            <category><![CDATA[freshbooks]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-interviews]]></category>
            <dc:creator><![CDATA[Victor Chen]]></dc:creator>
            <pubDate>Mon, 11 Dec 2023 02:53:07 GMT</pubDate>
            <atom:updated>2023-12-14T03:29:09.287Z</atom:updated>
            <content:encoded><![CDATA[<h3>How We Run Continuous Discovery at FreshBoks</h3><h4>Read on if you’re interested in waking up every Monday morning with a handful of interview sessions automagically booked in your calendar, with only one hour of setup work per month.</h4><p>This is a tribute to Teresa Torres and her fantastic book, <strong><em>Continuous Discovery Habit</em></strong>. This article is all about how to make continuous interviews happen. If you haven’t read the book itself, it is totally worth it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/0*YK9p6DjxgzerAZhi.png" /></figure><p>Before I begin, I’d like to share a research project I’ll use as an example in this article. This will help you better understand the reasoning behind each step.</p><blockquote>The project that the team is currently working on is called the FreshBooks AppStore. It is a standard third-party app marketplace that allows FreshBooks users to find and install apps that can extend the functionality of FreshBooks. As part of continuous discovery, the team is interested in learning how we can assist FreshBooks users in discovering the right apps, especially those who have never used an app before.</blockquote><h3>Part 1: Find the right target users, continuously</h3><p>Before conducting any research, it is essential to identify your target user. Whether you plan on conducting continuous interviews or not, narrowing down your target audience will ensure you receive high-quality feedback and insights. By defining a specific scope for your research, you can ensure that the candidates you select are relevant and can provide valuable information.</p><p>There are many tools available to filter the list of users in FreshBooks. I use Fullstory to apply multiple filters. For instance, my current research goal is to determine how users discover the right apps. Therefore, I have asked Fullstory to filter all the users who visited the FreshBooks AppStore and successfully clicked the install button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pli2CzSVvpzPtCH_RNsiPg.png" /><figcaption>Use Fullstory to identify the target audience.</figcaption></figure><p>Once you have a shortlist of users, depending on the tools and setup, you may need to gather more segment-related information about them. In FreshBooks, we import the user list into Looker to fetch segment information such as industry and app usage statistics. This helps me better target the right users I am interested in. For example, one of my current research assumptions is that users who have never used an app may spend more time picking up the right one. This means I need to talk to non-app users. So, I fetched extra app usage statistics from Looker and filtered out all the users who have already used apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pp9w3l6x-c1L0AfFTBDD4w.png" /><figcaption>User Looker to get additional segment or behaviour data</figcaption></figure><p>After filtering by segment data, we’ll next clean the user data to have a list for recruitment. At FreshBooks, we use Google Sheets for this task. We remove duplicate entries and clean up records with empty names or email addresses. This is the last opportunity to refine the user list based on the research goal. For instance, in this project, we are more interested in learning from paying customers. Therefore, we filter out all the trial users and download the user list with a maximum of 150 users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xxH3mGQkeIGWjcypk7fJzw.png" /><figcaption>Use Google Sheets to clean things up.</figcaption></figure><p>We aim to have 150 Users on our list because our invite-to-booking rate is around 5-6%. This means that if you invite 150 users at the beginning of the month, you can expect about 7–9 users to sign up. This translates to 2–3 users signing up each week. However, it’s important to note that the sign-up ratio may vary depending on the industry and customer base. Therefore, it’s recommended to experiment and find out the correct number of users for your specific industry or customer base.</p><p>You should have a final user list to send out the user research interview invitations. Before we do that, here is a summary of the steps to prepare the user list:</p><ol><li>Apply the right filter according to your research goal</li><li>Refine the filter to make a list of approximately 500 users (for this month)</li><li>Export and download the user list</li><li>[Optional] Collect more user data from Looker to focus on the right segments and behaviours.</li><li>Upload the user list to Google Sheets.</li><li>Remove duplications and further refine the list according to your research goal.</li><li>Export and download with max 150 users records</li></ol><p><strong>Protips (it’s all about save your work for next time)</strong></p><ol><li>Save as a segment filter in Fullstory for future reference</li><li>Save the looker query for future reference</li><li>Keep a record of the attributes of the user on your list for future reference (e.g. 0 app+paid)</li></ol><p><strong>Don’t do</strong></p><ol><li>Get a massive user list with few filters</li><li>Add way too many segment data that you don’t need. It will slow you down in decision-making.</li><li>Don’t invite more users than you need. It’s a waste of user attention.</li></ol><p>PS: You don’t need to have a specific customer segment in mind to start your search. You can start with a broad group and still gain exciting insights.</p><h3>Part 2: Setup the recruiting channel, continuously</h3><p>Before using recruiting tools to send out invitations, it’s important to block a weekly time slot in advance for your team. Discuss with your team to find the right time slot and create a placeholder event to block it. In the era of remote work, there are tons of meetings every day, so it’s better to save the time slot in advance to avoid any trouble. Once a user signs up for the time slot, you can easily update the event to confirm and notify the team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*AAajNJGBQ6DaZsTWsX4Rmg.png" /><figcaption>Block the timeslot and invite your team.</figcaption></figure><p>Now that we have everything prepared, we can use recruiting tools to send out invitations. At FreshBooks, we use userinterviews.com as our user research recruiting tool. It allows us to upload a CSV user list, which we prepared in Part 1, and send out invitations with branded email templates we set up in advance. It also handles scheduling. We input our available time slots, and users choose the best time that works for them. Once a user successfully schedules a session, userinterviews.com will automatically add the session to everyone’s calendar. There are many alternatives for recruiting, such as userzone, usertesting.com, Maze, and more. The point is to use a tool to save time for setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VeB_5X2qYzjWA8AP_mtMqg.png" /><figcaption>The recruiting tool is a big time saver.</figcaption></figure><p>Now that you have sent out the invitation to users, the next step is to join those user interview sessions and learn insights. Before we discuss the interview, here is a summary of the steps for the second part, where we prepare for the interview:</p><ol><li>Block weekly time slots for user interviews and invite anyone interested</li><li>Hold the time in everyone’s calendars as a Placeholder to begin with</li><li>Once you have the user signed up, please update it to Confirmed<strong> </strong>and update the Zoom link and who participates.</li><li>Use recruiting tools to automate the recruiting and scheduling.</li></ol><p><strong>Protips</strong></p><ol><li>Add buff time between two sessions. 15 mins is the right amount of time for our team.</li><li>Use the same Zoom link to avoid confusion. (hot tip: turn on the waiting room to avoid having your following interview join your current interview)</li><li>If you use userinterviews.com, set requested participants to more than you need to keep the project open and going.</li><li>It is expected that 2-3 people will not show up. To avoid this, you can invite attendees for each session closer to the actual session time instead of inviting everyone at once. This way, there will be less chance of no-shows.</li></ol><p><strong>Don’t do</strong></p><ol><li>Update your team at the last minute. It’s best to keep your team updated for no-shows or reschedulings.</li><li>Forget to pay the participant after the interview.</li></ol><h3>Part 3: Synthesis and record interview snapshots continuously</h3><p>You can schedule two weekly user interviews by following the steps in parts 1 and 2. This section focuses on how to document, synthesize, and share insights from the interviews.</p><p>During user interviews, it is recommended to have two interviewers - one to lead the interview and the other to take notes. At FreshBooks, we use Airtable to keep track of our interview questions and notes. A pro tip is to have a product manager and even an engineer join the session so they can exercise their empathy muscle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0b1nCuJY8UYS9GGlHSA0cg.png" /><figcaption>Airtable for note-taking</figcaption></figure><p>When scheduling interviews, it’s important to allocate time for reviewing and synthesizing the findings. You can also use this time to refine your interview questions if necessary. It’s crucial not to delay extracting insights from the interviews. Procrastination can lead to unnecessary stress and wasted time. So, make sure to prioritize this task, and you’ll thank yourself later!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/753/1*3-jUINaVmPDewZp8nLuBUQ.png" /><figcaption>Review notes on the same day.</figcaption></figure><p>As a team, agree to a snapshot layout and create a deck (one spot to hold them all!). We based ours off of the example in Continuous Discovery Habits, Teresa Torres (pg 68),</p><p>The interview snapshot includes owner information, company information, segmentation, a key takeaways section, important quotes, links to notes and recordings, and tags so you can easily search later. Looking for a <strong><em>public,</em></strong> professional photo of your interviewee?.</p><p>Make the interview summary scannable or include key takeaways for easy comprehension by others who were not involved.</p><p>Once done, remember to share your snapshot in your team slack channel!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f5LypupEUoRLwZJW40i0tA.png" /><figcaption>One of the snapshots we created</figcaption></figure><p>Looking back, I thought it was impossible to interview users every week throughout the project lifecycle. However, once the team was able to validate their assumptions on a weekly basis, we could never go back to the old waterfall design process that only talked to users at the “Discovery Stage.” The old process allowed so many wrong assumptions to be baked into the project without us even realizing we were wrong.</p><p>Glad to see you’ve made it this far. I hope you enjoy reading and successfully implementing it in your organization.</p><p>PS: Thank you, <a href="https://medium.com/u/11f23bf3fe30">Tiff Nogueira</a>. She is my PM partner at FreshBooks, and she co-wrote this article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd3eee6bf4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-freshbooks/continuous-interview-how-we-do-it-at-freshbooks-bd3eee6bf4">Continuous Interview — How we do it at FreshBooks</a> was originally published in <a href="https://medium.com/building-freshbooks">Building FreshBooks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Use the vision storyboard to keep the product team aligned and focused — Part 2]]></title>
            <link>https://medium.com/building-freshbooks/use-the-vision-storyboard-to-keep-the-product-team-aligned-and-focused-part-2-272be473009d?source=rss----3a7c8d75f488---4</link>
            <guid isPermaLink="false">https://medium.com/p/272be473009d</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[freshbooks]]></category>
            <category><![CDATA[product-vision]]></category>
            <dc:creator><![CDATA[Victor Chen]]></dc:creator>
            <pubDate>Wed, 30 Aug 2023 13:20:29 GMT</pubDate>
            <atom:updated>2023-08-30T13:20:29.495Z</atom:updated>
            <content:encoded><![CDATA[<h3>Using the Vision Storyboard to keep teams aligned and focused — Part 2</h3><p>To continue the <a href="https://medium.com/building-freshbooks/use-the-vision-storyboard-to-keep-the-product-team-aligned-and-focused-part-1-bc094de38ba1">previous article</a>, I will show you how to create a problem and vision story step by step. You can use this <a href="https://www.figma.com/community/file/1276923535543938806/Vision-Storyboard-Tool-Kit">Figma Template(Vision Storyboard Tool Kit) </a>to create one; please feel free to make a copy.</p><p>Now, let&#39;s get started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bB9XfsJgNZDzC-xKFo6TDQ.png" /></figure><h3>6 Steps to create a vision storyboard</h3><p>Step 1: <strong>Introducing characters</strong>. Add your cast to the left side of the board. And you need to decide who the main character is and who the supporting cast is for your story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vEJr3VMrZfXgTEQvr3CuMA.png" /></figure><p>Behind the scenes of the first step, the casting should be based on your user interview/research, and the character should be based on the personas you created for the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WkrK5Rb7iGoubIGRYWqbww.png" /></figure><p>Step 2: Add six boxes to the board because you want your story to be concise and easy to digest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BWQWbOJ5YJCaev1fGoMOyQ.png" /></figure><p>Behind the sense of step 2, we need six boxes based on <a href="https://bootcamp.uxdesign.cc/the-7-2-rule-the-real-science-behind-millers-law-that-will-shock-you-your-deepest-memory-4a35be25bb3b#:~:text=Miller&#39;s%20Law%20is%20a%20cognitive,the%20%E2%80%9Cmagic%20number%207%E2%80%9D.">Miller&#39;s Rule</a>, which is a cognitive psychology principle that states that the average person can only hold about 7 (plus or minus 2) items in their working memory at a time. This is also known as the &quot;magic number 7&quot;.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TSU81YEfKB1Jt5mB_-S5qQ.png" /></figure><p>Step 3: Write down the <strong>pitfall</strong> of the problem story, and make sure to use less than seven words. You know the &quot;magic number.&quot;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0z-zG4DacbmeQFKk72NJMw.png" /></figure><p>Behind the scenes of step 3, the pitfall is coming from our user research. We should understand our user&#39;s top pain points and which pain points are worth solving, which should be based on the journey map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cawfgnPF7SGrxqhl5wlKaA.png" /></figure><p>Step 4: Write down the background or context. As with any movie or novel, you need to set up a good backstory to bring your audience up to speed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rkkSkmJdvAANMRIWzPs7Ug.png" /></figure><p>Step 5: Write down the rest of the story. A vital thing to remember is to add the story&#39;s highlight somewhere in the middle. We usually call it the climax.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UpOSNqj-If5HJZtH7CS7oQ.png" /></figure><p>Behind the scenes of step 5, the typical structure of a good story looks like the chart below. The story begins with a good background story(<strong>a poor knight struggling in life</strong>), and then the main character rises to a challenge(<strong>accepts a mission</strong>), which usually leads to the climax of the whole story(<strong>fighting a dragon</strong>), and then either ends up with a pitfall(<strong>Tragedically dead</strong>) or a happy ending(<strong>saved the kingdom</strong>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ufT-wuWfC53jIcm8rRUqpA.png" /></figure><p>Step 6: Bring the story to life with your magic. To make this step easier for a designer like me who is not good at drawing or wants to make a storyboard a bit faster. I made this <a href="https://www.figma.com/community/file/1276923535543938806">storytelling toolbox template in Figma</a>. Feel free to check it out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3l3MM-voUJTUgwr7gVe_NQ.png" /><figcaption>This a storyboard I created for a FreshBooks Project</figcaption></figure><p>Now, let&#39;s look at the vision story. As a problem story is focused on describing the user&#39;s problem they experience today, the vision story is focused on picturing a <strong>day of the user&#39;s life in the future</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KvqWLCVfE8LwjhjK" /></figure><p>The structure of the vision story is similar to the problem story, and the content is different. In the vision story, you need to include a highlight as the story&#39;s climax and give it a happy ending so the user achieves the end goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qzHwH0AUn4mlecrZRdTKzw.png" /></figure><p>Below is an example of a vision story</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ETLDjh2tAbKWa6wWmVCKvw.png" /></figure><h3>Things to avoid</h3><p>Here are some things you should avoid when creating a vision storyboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*57keUfZOX2AAmFPT0YazfQ.png" /></figure><p><strong>Lack of emotion: </strong>Emotion is a key aspect of storytelling and also the key element of building customer empathy. Below is an example of what a lack of emotion storyboard looks like. 😱</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8EVqjNm8joQWzSCLBJHylA.png" /></figure><p><strong>Turn it into a lo-fi mockup:</strong> As a designer, it&#39;s very attempting to create screens, but remember, you have plenty of time to do that later. Now, you must force yourself to use as little UI as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZBKKqKgeszQbGW10uacU5A.png" /></figure><p><strong>Cover all the edge cases: </strong>We are used to writing product specs and creating fully functional prototypes. Naturally, you want to include all the edge cases. Remember that you should only have the one frustrating the users the most.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K1JRP418mfyOoBV6" /></figure><p><strong>Adding too many details: </strong>Similar to the point above, keeping the story on a higher level is necessary. Even you know all the details between scenes number one and number two. You shouldn&#39;t include them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EMFieQJzm8SQRH331gBNbw.png" /></figure><p><strong>Just use Journey Map: </strong>I see many designers, including myself, trying to use the journey map as a storytelling tool. It includes similar elements that a storyboard has, like the user&#39;s emotions, highlights and pitfalls. However, a journey map is built for a different goal. It&#39;s a user research tool and very much data-driven. So many details need to be included in the Journey Map, which will distract your audience and get into the weeds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S5ZIgzMM048YMQLLo6wgmg.png" /></figure><p><strong>Use as public-facing marking material</strong>: You shouldn&#39;t show a storyboard to an actual customer because they don&#39;t have the context we have, like the product strategy and vision we shared internally. The customer might get confused and feel unrelated to your problem story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3WbeFJfqi_2wQjkGYy9VvA.png" /></figure><p><strong>No real data backup: </strong>The problem story is the generalization of the real-world cases, and we should always be able to refer to the actual interview recording or user tickets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OUVjdaUTM8HkzSxbwOy3CA.png" /></figure><p>Creating a vision storyboard is an effective way to unify your product team. You can also use other tools, such as a video demo or a future-release article, to achieve the same goal. The key is establishing a clear vision and ensuring everyone on your team understands it. If you have similar experiences or alternative methods for demonstrating a product vision, please feel free to share in the comments. Enjoy!</p><p>PS: If you are curious about the integration I refer to in the storyboard example, you can <a href="https://appstore.freshbooks.com/details/acuity-scheduling">check out this link</a> for the released product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=272be473009d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-freshbooks/use-the-vision-storyboard-to-keep-the-product-team-aligned-and-focused-part-2-272be473009d">Use the vision storyboard to keep the product team aligned and focused — Part 2</a> was originally published in <a href="https://medium.com/building-freshbooks">Building FreshBooks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Use the vision storyboard to keep the product team aligned and focused — Part 1]]></title>
            <link>https://medium.com/building-freshbooks/use-the-vision-storyboard-to-keep-the-product-team-aligned-and-focused-part-1-bc094de38ba1?source=rss----3a7c8d75f488---4</link>
            <guid isPermaLink="false">https://medium.com/p/bc094de38ba1</guid>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[storyboard]]></category>
            <category><![CDATA[product-vision]]></category>
            <category><![CDATA[freshbooks]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Victor Chen]]></dc:creator>
            <pubDate>Wed, 10 May 2023 14:10:38 GMT</pubDate>
            <atom:updated>2023-08-30T18:06:05.740Z</atom:updated>
            <content:encoded><![CDATA[<h3>Use the vision storyboard to keep the product team aligned and focused — Part 1</h3><p><strong>TL;DR: </strong>It’s not easy to communicate your product vision with your team and leadership, and it’s even harder to get the team aligned on the vision and hope they can refer to it while making product decisions. In this article, I will share how I use storytelling to communicate product vision, keeping the team aligned and focused.</p><p>Let’s meet Mei, a product designer working on a fantastic SaaS product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ImD3k0LIMX3OxhoKmtRUog.png" /></figure><p>Like other product designers, she creates her design strategy with vision, strategy and hypothesis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MDSbhAM1_Wtq3OCC" /></figure><p>Everything goes well until she presents her strategy to the leadership group and her teammates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NdQ_fduDhCQRXG4z2Cy2EA.png" /></figure><p>The leadership group feels there is <strong>too much detail</strong> in the presentation, and it easily gets into the weeds rather than focusing on high-level design strategy. What wasn’t captured was the real gap between the user problem and the future vision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EcZOLX1q1cVHuPINWZNJTg.png" /></figure><p>On the product team side, everyone seems aligned. However, they’re all thinking about the execution detail differently, which leads to anxious last minus re-alignment meetings and potential rework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R2pSjwHUKNNuuo3BSRLngQ.png" /></figure><p>Mei feels frustrated. She wants to learn how to present user problems better, so the audience can <strong>grasp the user problem easily</strong> She always wants to present the future vision in such a way there is <strong>no room for misalignment.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_5e1qQzsErbbk782tYF4sA.png" /></figure><p>How can Mei accomplish this? Storytelling! There are two promises storytelling can offer. It <strong>explains the user problem vividly</strong>. For example, who doesn’t understand comic books? Even a kid can read it. Storytelling can also help <strong>visualize the future more tangibly</strong>, leaving little room for misalignment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cyhP-LZdyNxcIpOd3EPSiA.png" /></figure><p>If we look around the industry, many companies already use storytelling. In <a href="https://youtu.be/hlk8GsYkqi4?t=536">this video</a>, Jared shared his idea of product vision. It’s a “<strong>Flag in the sand</strong>.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wUQmefIuXLCF6BKrmKU6xw.png" /></figure><p><a href="https://vimeo.com/488270100/9ea773b1a5">Apple’s vision video</a> about the Knowledge Navigator (1987) inspired the iPad product line 23 years later. The Knowledge Navigator is not technically possible even in today’s standard, but it’s all about <strong>describing the experience</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eDXwhE_0VhepmtfGTYC5_Q.png" /></figure><p><strong>It’s critical to provide context.</strong> Airbnb is famous for using storytelling to map out the entire customer journey, even before and after using Airbnb. As you see in the canvas below, this added context makes it even more believable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3u7R909E-C4W6es2M6RRUQ.png" /></figure><p>With all the hype up, I hope you have bought into the idea of storytelling. You need to create two types of stories: a <strong>problem story</strong> and a <strong>vision story. In the next article, I will show you</strong> how to create a problem story and a vision story step by step.</p><p><a href="https://medium.com/building-freshbooks/use-the-vision-storyboard-to-keep-the-product-team-aligned-and-focused-part-2-272be473009d">Here is the link for part 2</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bB9XfsJgNZDzC-xKFo6TDQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc094de38ba1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-freshbooks/use-the-vision-storyboard-to-keep-the-product-team-aligned-and-focused-part-1-bc094de38ba1">Use the vision storyboard to keep the product team aligned and focused — Part 1</a> was originally published in <a href="https://medium.com/building-freshbooks">Building FreshBooks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Water faucets in the UK — Hide system complexity from the user]]></title>
            <link>https://medium.com/building-freshbooks/water-faucets-in-the-uk-hide-system-complexity-from-the-user-89656a68c02d?source=rss----3a7c8d75f488---4</link>
            <guid isPermaLink="false">https://medium.com/p/89656a68c02d</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Victor Chen]]></dc:creator>
            <pubDate>Mon, 08 Aug 2022 00:05:02 GMT</pubDate>
            <atom:updated>2022-08-08T00:05:02.326Z</atom:updated>
            <content:encoded><![CDATA[<h3>The UX of water faucets</h3><h4>How faucets in the UK DO NOT hide complexity from the user</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*xntjmtXiRftdvoYR" /><figcaption>Water faucets in the UK… yea not kidding</figcaption></figure><p>Bad product design is everywhere you look. Take British taps, for example. 🇬🇧 For the uninitiated, washing your hands in the UK often involves splashing together two disparate streams of water — one that is (I assume) sourced from melting ice caps 🧊, the other heated by the Earth’s molten core 🔥.</p><h4>Why is this?</h4><p>I asked my European colleague about his experience, and he replied:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/0*Kxm3x2URS8Shr2HH" /></figure><h4>What Do Experts Say?</h4><p>We asked Kevin Wellman, Chief Executive Officer of the Chartered Institute of Plumbing and Heating Engineering, why British faucets are designed this way.</p><p>“This tradition dates back to when hot and cold water were kept separate to prevent contamination through cross-connection,” he said.</p><p>“Coldwater came from a mains supply and was fit for drinking. Hot water would be serviced by a local storage cistern often situated in the loft.</p><p>“This caused an imbalance of pressures which meant that if incorrect taps and valves were installed, one stream of water could force its way across to the other.”</p><p>In layman’s terms: Having separate taps in the UK is easier and simpler to install and keep safe. But who benefits from this solution? The maker, builder, and government enforce this rule — yes, but what about the end user looking to wash their hands quickly?</p><h4>What’s The Underlying Logic Here?</h4><p>This is a typical example, and you can likely find similar experiences in your day-to-day life. People often design or build stuff to solve their problems… without necessarily considering the end-user. And it reminds me of <strong>Tesler’s law</strong>:</p><blockquote><strong>“Tesler’s Law states that a system’s total complexity is a constant that cannot be reduced. Instead, it must be dealt with, either in product development(by creator) or in the user interaction(by user).”</strong></blockquote><p>In the case of water faucets, the complexity is left to the end-user. The plumbing system can connect the cold water pipe to the cold water tap and the hot water pipe to the hot water tap, and then, well, it’s up to you how to get a pleasant water temperature out of it.</p><h4>More Examples</h4><p>I love showcasing scientific laws and principles out in the real world, so join me as we find more examples out in the wild:</p><p>An unexpected example coming from Apple: the infamous removal of MacBook Pro ports:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/663/0*tGlZElSogrBqTi4a" /><figcaption>You can feel the pain, can’t you?</figcaption></figure><p>The picture above may not be necessary if you’re like me and living with a pile of dongles. The I/O options like HDMI, SD card, USB, etc., are no longer available.</p><p>Before Covid, I needed to carry an adapter(pictured below)to go into meeting rooms, where only HDMI or DVI cables were available to me when presenting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/407/0*_AdluhOjwo_v6pTH" /><figcaption>Looks familiar, right?</figcaption></figure><p>After Covid, I needed to spend a month setting up my workstation, which looks like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1hBYIHaaUDaiE3SO" /><figcaption>Looks good at the front…</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yVUQlsn7-2OHcmnV" /><figcaption>But it’s a mess behind the scenes</figcaption></figure><p>Apple designed the new MacBook Pro to be thinner and lighter, but I believe there is a certain amount of complexity in handling the I/O between the MacBook Pro and other devices that weren’t addressed.</p><p>According to the Tesla law above, somebody has to deal with it — If not the designer or manufacturers, it falls on the end-users.</p><h4>Example From the Digital World</h4><p>Let’s move to the digital product world. You may be familiar with the image below if you are older than Generation Z. It’s the toolbar of well known Microsoft office product. It’s a great example of leaving complexity to the end-user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/0*hq-KhD64wqTQPm54" /><figcaption>The good old days</figcaption></figure><p>Don’t get me wrong. The Microsoft Office Suite has been a great product since its release, a huge productivity booster for users with its rich functionality. The image above shows all the features (good or bad) in the toolbar that do not apply to all users but show to all users. The designer of this product didn’t deal with this complex problem, which means the end-user needs to deal with it every day! I still have nightmares about that toolbar.</p><p>In comparison, below is an excellent example of Google Docs removing that complexity for the end-user, allowing them focus on the tasks at hand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/0*ECpI3-fQe5ue3xCK" /><figcaption>We can never go back, can we?</figcaption></figure><h4>Example from FreshBooks</h4><p>The Gmail Add-on removes the complexity of syncing information between Gmail and FreshBooks, allowing users to focus on the task and access key information at the point of the job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IdltDmDYmL_wkVT9" /><figcaption><a href="https://workspace.google.com/marketplace/app/freshbooks_invoicing_addon/35731807065">Check out this cool add-on</a></figcaption></figure><p>Before the Gmail FreshBooks Add-on app, when users received an invoice email or inquiry from their client, they needed to log in to FreshBooks and go to the client page, search and find the client, and then go to the client page to get an overall idea of how is this client financially. Whew! 5+ clicks. With the add-on, the complexity of syncing information is hidden behind the scene. Now, users can focus on the work that matters to their business.</p><h4>TL;DR: What Have We Learned?</h4><p>As a former engineer turned Product Designer, I want to emphasize that we shouldn’t leave a system’s complexity to the end-user. The whole product team, including engineers, product designers and product managers, should work together to hide the system’s complexity and make the product easier to use for the end-user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89656a68c02d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-freshbooks/water-faucets-in-the-uk-hide-system-complexity-from-the-user-89656a68c02d">Water faucets in the UK — Hide system complexity from the user</a> was originally published in <a href="https://medium.com/building-freshbooks">Building FreshBooks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do you know when a design fails a usability test?]]></title>
            <link>https://medium.com/building-freshbooks/how-do-you-know-when-a-design-fails-a-usability-test-3afbf0b8a4c4?source=rss----3a7c8d75f488---4</link>
            <guid isPermaLink="false">https://medium.com/p/3afbf0b8a4c4</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Jeff Kraemer]]></dc:creator>
            <pubDate>Tue, 21 Nov 2017 22:18:54 GMT</pubDate>
            <atom:updated>2017-11-14T20:49:59.300Z</atom:updated>
            <content:encoded><![CDATA[<h4>A handy technique I learned from the wrong job…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qYHq2dqUCYCyKrYd2KfGHA.png" /><figcaption>Task failure.</figcaption></figure><p><em>Originally published at </em><a href="https://www.webdesignerdepot.com/2017/03/how-do-you-know-when-a-design-fails-a-usability-test/"><em>WebdesignerDepot.com</em></a><em>.</em></p><p>Years ago, I spent an awkward patch of my career as an instructional designer, creating courses for online learning. It was a bad fit and I moved on happily, but one part of that job has made me a better UX designer: <strong>learning objectives.</strong></p><p>Learning objectives are simply what you want the student to learn by the end of the training. If there’s a test, the test questions should be based on those objectives — otherwise, what’s the point of the test?</p><p>The same approach comes in handy for figuring out whether a design has passed or failed a usability test. Just remember: it’s the design that’s being tested, not the participants.</p><p>What does the test participant need to do or say for you to feel confident that the design has succeeded? Do they need to track three hours of time for a particular project? Generate an invoice to a client based on that tracked time? Send the invoice? That’s your test criteria (which my <a href="https://www.freshbooks.com/invoice">FreshBooks</a> colleague Melina Stathopoulos named “success criteria”).</p><p>Of course usability testing is about observing how users complete tasks, but what will you get them to do, exactly? The beauty of these criteria is that they steer you away from vague testing goals like, “understand how time tracking works.” How will you know they’ve understood it? You get them to describe it. And once they’ve described it accurately, you can say that aspect of the design was successful.</p><p><strong>Success criteria help you twice over</strong>: they clarify whether your design is really successful, and they make it easier to share those results.</p><h3>Verbs are magical</h3><p>The book that taught me about learning objectives, George Piskurich’s <a href="https://books.google.ca/books/about/Rapid_Instructional_Design.html?id=DcmuNAEACAAJ&amp;redir_esc=y&amp;hl=en">Rapid Instructional Design</a>, offers a handy list of behaviours to start your success criteria.</p><p>For example, the objectives for comprehension might be “describe” or “demonstrate”. Again, “understand” is no good — you need them to <em>say</em> (that is, describe) or <em>do</em> (that is, demonstrate) something that proves to you that they’ve understood.</p><p>And then, at a higher degree of difficulty, a participant might “explain” or “organize”; at a higher level still, they might “create” or “evaluate”.</p><p>Whatever verb you choose to start your success criteria, <strong>the point is that you can observe whether or not a user has actually said or done whatever constitutes task success.</strong></p><h3>“By the end of this session…”</h3><p>So, when you’re planning your next usability test, and you’re working on tasks, start by asking, “What should a user be able to do with (or say about) this design?”</p><p>Then, you might write something like this:</p><blockquote>By the end of the session, the participant should be able to:</blockquote><blockquote>- Track three hours of time for a particular project</blockquote><blockquote>- Generate an invoice to a client based on that tracked time</blockquote><blockquote>- Describe the difference between tracking time and logging time</blockquote><p>Now you have three success criteria and, based on those, you’ve also got a pretty clear sense of what tasks you’ll need to give the participants.</p><p>One caveat: success criteria aren’t quite the same as tasks. Tasks have more context; they’re written to be read to the participant, and might include some context about the task, particularly if you’re steering them to find something in your prototype. For example:</p><blockquote><strong>Success criteria:</strong> Generate an invoice to a client based on that tracked time<br><strong>Task:</strong> “Now that you’ve tracked three hours on the Atlas project, show me how you would invoice Acme Products for your time.”</blockquote><p>Pretty similar, obviously, but <strong>success criteria are for you and your team; the task is for the participant</strong> in the context of the usability session.</p><p>And you’ll notice that one of the success criteria above is about describing something, rather than completing a task. It might be a follow-up question to a task. These are handy for validating whether your design’s mental model is clear to users. I’ve seen users find their way through a task, but then describe to me a mental model of the app which is at odds with how it was designed. That’s task success for one participant, but more importantly there’s an underlying problem with matching that participant’s mental model.</p><p>So, start with your success criteria, then write your tasks and follow-up questions based on your criteria.</p><h3>Stakeholders love success criteria</h3><p>Stakeholders don’t necessarily care about your process, but they really care about the results. And if your presentation of the results is vague, they will be rightfully irritated.</p><p>“The user managed to track a few hours, but we weren’t sure whether she understood that tracking time isn’t the same as logging it against a client…” Well, <strong>why aren’t you sure? Isn’t it your job to figure this out?</strong> You’re wasting their time, and not giving them clear direction on how to fix the UX problems — which is also your job, right?</p><blockquote>Success criteria help you twice over: they clarify whether your design is really successful, and they make it easier to share those results.</blockquote><p>We’ve had some success tracking success criteria in a simple table, and colour-coding the results. Like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ke5mAAk0s6zA2FOSZ5vFNQ.png" /><figcaption>We whip up a colour-coded table of results (green = success, red = failure) on our wiki. In the top row, we list participants; in the left column, we list our success criteria. It’s ugly, but quick and useful.</figcaption></figure><p>This is easy to scan, shows pretty clearly where the problems are, and grounds the results in the experiences of actual participants. We also list a bullet-point summary of results and a list of usability problems and recommendations just beneath it. At FreshBooks, we’ll zero in on those problems and iterate until we believe they’re solved. Your process might be a little different — maybe you’re a consultant handing over a report to a client, for example — but the benefits are the same.</p><p>We love to hear how our peers are practicing design. Do you use something like success criteria? If you try it, is it useful to you? Are you using some other method to track the usability of your designs? Let us know in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3afbf0b8a4c4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-freshbooks/how-do-you-know-when-a-design-fails-a-usability-test-3afbf0b8a4c4">How do you know when a design fails a usability test?</a> was originally published in <a href="https://medium.com/building-freshbooks">Building FreshBooks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Supercharge Your Survey with User Research]]></title>
            <link>https://medium.com/building-freshbooks/supercharge-your-survey-with-user-research-794066713995?source=rss----3a7c8d75f488---4</link>
            <guid isPermaLink="false">https://medium.com/p/794066713995</guid>
            <category><![CDATA[surveys]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Danielle Klein]]></dc:creator>
            <pubDate>Mon, 06 Nov 2017 17:00:20 GMT</pubDate>
            <atom:updated>2017-11-06T17:42:02.309Z</atom:updated>
            <content:encoded><![CDATA[<h4>Use qualitative insights to design an impactful survey</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dGWdGqCV4g3Kpf1HQqIyRw.jpeg" /><figcaption>When you need to answer a specific question at scale, surveys might be the tool for you. Photo by Edwin Andrade via Unsplash.</figcaption></figure><p>It seems like a simple question: how do you make your money? If every two weeks you get a paycheque, it’s easy to answer. But what if you have a side hustle, or you make some extra cash from ads on your website?</p><p>At FreshBooks, we know that our customers make their money in all kinds of ways—often, in more ways than one. To help them track it, we needed to figure out which ways were most common. And to do so, we decided to run a survey.</p><p>This wouldn’t be easy. Our customers don’t all speak about their revenue streams in the same way. Running a survey came with a high risk of customers not understanding the questions. (Not to mention the pervasive risks of running a survey, period — I see you, survey skeptics. Bear with me!)</p><p>Knowing this, I decided to reach into my UX toolkit to leverage some familiar qualitative methods to improve our survey and ensure it gave us meaningful data.</p><p><em>Disclaimer: Like any tool, surveys have their strengths and their limitations. A lot has been written about the risks of surveys — in particular, if you’re considering running one, start with </em><a href="https://medium.com/research-things/on-surveys-5a73dda5e9a0"><em>this piece by Erika Hall</em></a><em>.</em></p><h3>Start with user interviews to inform survey language</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FI8PFuF7ZlARGM%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FI8PFuF7ZlARGM%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FI8PFuF7ZlARGM%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="174" frameborder="0" scrolling="no"><a href="https://medium.com/media/f4aab17571895b86e4ed872e9c96cedf/href">https://medium.com/media/f4aab17571895b86e4ed872e9c96cedf/href</a></iframe><p>You say ad revenue, I say affiliate income. That’s how the old saying goes, right?</p><p>Before we ran the survey, <strong>we interviewed customers and learned the language they use</strong> to talk about their revenue streams. We spoke to 5 customers remotely, and reviewed emails from several others.</p><p><strong>This allowed us to make an educated first guess at writing the survey in our customers’ words</strong>. The language of our questions and the answer options were informed by this qualitative data.</p><p>If this sounds like a lot of work, take note — you may already have the data you need! In our case, we had already run some interviews and were able to leverage those recordings to take a first stab at a draft of the survey.</p><h3>Run a remote pilot study with users</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FMISlmVf6zpAiI%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FMISlmVf6zpAiI%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FMISlmVf6zpAiI%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/4ce91402b9230d1b1589a8e9956a3812/href">https://medium.com/media/4ce91402b9230d1b1589a8e9956a3812/href</a></iframe><p>I once had a professor tell my class that we would be <em>completely insane</em> to run a survey without piloting it. And while I cannot say for certain that I am not at least a bit insane, I am most definitely not completely insane, so I always pilot my surveys, and you should too!</p><p>After creating a first draft based on our initial interviews, <strong>we ran a small pilot study through remote user interviews with 5 customers</strong>.</p><p>We asked participants to do the survey and think out loud, and then we reviewed their answers with them to see whether they understood the questions. We iterated on the survey copy after each one.</p><p>It’s important to stay quiet while the customer takes the survey, and <strong>focus on testing the survey</strong>. I know it’s tempting to dig into their answers, but you are trying to learn if the survey is going to give you good data — not about that customer’s specific workflow.</p><p>The main function of the pilot is to help you edit. Don’t forget to kill your darlings (and by darlings, I mean non-sequiturs, incomprehensible rating scales and anything that makes your customers’ faces become this emoji: 😰).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3og0IKMmOZE88Ankty%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3og0IKMmOZE88Ankty%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F3og0IKMmOZE88Ankty%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="227" frameborder="0" scrolling="no"><a href="https://medium.com/media/5b1c56ecd189f02fbb2425303f71fe2c/href">https://medium.com/media/5b1c56ecd189f02fbb2425303f71fe2c/href</a></iframe><p>When we initially wrote the survey, for each question, we called out:</p><ul><li>What are we trying to learn?</li><li>How will we use this data in our design work?</li><li>What assumptions and/or biases are inherent in this question?</li></ul><p>With the pilot study, <strong>we were able to validate whether we could really learn what we wanted to from each question based on how users interpreted them. </strong>This helped us to ensure we got the data we needed by removing questions that we couldn’t learn from and refining those we could.</p><p>(On that note, one piece of practical advice: consider avoiding long form field answers if you can. It’s hard to review the data and learn from it. In our pilot, we saw that people will just put a space and ignore it at worst, or, often, write something you can’t really understand without talking to them. If you need to use them, be sure to test open-ended questions through a pilot study to see whether users are able to interpret them.)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FkRElxpRJfSCoU%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FkRElxpRJfSCoU%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FkRElxpRJfSCoU%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="212" frameborder="0" scrolling="no"><a href="https://medium.com/media/db4ccec9898c069ebb12662ae20cd876/href">https://medium.com/media/db4ccec9898c069ebb12662ae20cd876/href</a></iframe><h3>The survey is done — time for more research!</h3><p>Our survey answered our original questions around how our customers make their money. But naturally, these answers opened the door to a host of new research questions.</p><p>This is because <strong>there’s a limit to what we can learn from a survey about the why</strong> — why do our customers need this feature in context of their day-to-day workflow? (See, I haven’t forgotten you, survey skeptics!)</p><p>As design continues, the survey isn’t just a means to an end —<strong> it’s the beginning of a longer conversation with a rich pool of research participants.</strong> So don’t forget to ask if you can follow up! We tested prototypes with survey participants and took the opportunity to go over their survey answers with them to figure out what went unsaid.</p><p>Like many research methods, surveys work best when you pair them with qualitative conversations—both when you initially build them <em>and</em> when you analyze and use the data.</p><p>So, if you’re thinking of running a big old survey—fear not! Dipping into your UX toolkit and collaborating with customers can make surveys a powerful, essential part of your research process when you need to learn at scale.</p><p>S/o to Irfaan Manji, Product Manager, who I collaborated with on this survey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=794066713995" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-freshbooks/supercharge-your-survey-with-user-research-794066713995">Supercharge Your Survey with User Research</a> was originally published in <a href="https://medium.com/building-freshbooks">Building FreshBooks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bite-Sized UX: The Handiness of Assumptions and Hypotheses]]></title>
            <link>https://medium.com/building-freshbooks/bite-sized-ux-the-handiness-of-assumptions-and-hypotheses-b1880d7cad7c?source=rss----3a7c8d75f488---4</link>
            <guid isPermaLink="false">https://medium.com/p/b1880d7cad7c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jeff Kraemer]]></dc:creator>
            <pubDate>Thu, 10 Aug 2017 18:39:43 GMT</pubDate>
            <atom:updated>2017-08-10T18:38:59.808Z</atom:updated>
            <content:encoded><![CDATA[<p>At FreshBooks, our product team talks a lot about assumptions and hypotheses. What’s the difference, and why are they useful?</p><h4>Assumptions: “We assume…”</h4><p>An assumption is basically an informed guess… which might be biased, and which is definitively unproven. Assumptions lurk everywhere, and they’re often wrong. What’s really useful, then, is calling out assumptions so that we can turn them into falsifiable hypotheses.</p><p>In our design process, assumptions often come up when we’re brainstorming or critiquing a design. “A user would probably click on that button if it was a different colour,” one of us will say, and another will call out, “That’s a testable assumption.” Excellent! We have a test to run, which means we need a hypothesis.</p><h4>Hypotheses: “We believe…”</h4><p>A hypothesis is a bit more formal. It’s a way of stating an assumption in a testable form. We also call a hypothesis a “we believe” statement since we start our hypotheses with those words. For example, “We believe that making all our buttons purple will double conversion.” We can test that and learn whether our belief was right. By testing, we can spin our assumption straw into insight gold.</p><p>A key part of a sound hypothesis is that it’s falsifiable. For example, “We believe that users will love our purple buttons” isn’t falsifiable; it’s subjective. And (this is going to sound grouchy, but:) why do we care if they love them? Aren’t we trying to achieve a result? Our belief that a purple button will double conversion has a condition and result we can test — if the button’s purple, the conversion rate will double, and that’s quantifiably either true or false.</p><p>A hypothesis forms the backbone of our design sprints; the purpose of the sprint is to validate it. That’s why we usually end our brainstorming session at the start of a design sprint by agreeing on a hypothesis. The designer and product owner then test it within the week.</p><p>In short, when you identify an assumption, rewriting it as a falsifiable hypothesis will help you get data you can use. And what if your hypothesis fails? That’s great, because you’ll have learned something!</p><p><em>Thanks to Danielle Klein, Kiley Meehan, and Aaron Wright for feedback on this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1880d7cad7c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-freshbooks/bite-sized-ux-the-handiness-of-assumptions-and-hypotheses-b1880d7cad7c">Bite-Sized UX: The Handiness of Assumptions and Hypotheses</a> was originally published in <a href="https://medium.com/building-freshbooks">Building FreshBooks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using UX Research to Learn About Your Team]]></title>
            <link>https://medium.com/building-freshbooks/using-ux-research-to-learn-about-your-team-66facdbd7f6d?source=rss----3a7c8d75f488---4</link>
            <guid isPermaLink="false">https://medium.com/p/66facdbd7f6d</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Danielle Klein]]></dc:creator>
            <pubDate>Mon, 17 Jul 2017 17:37:43 GMT</pubDate>
            <atom:updated>2017-07-17T17:37:43.041Z</atom:updated>
            <content:encoded><![CDATA[<h4>A framework for asking questions to get up to speed as a new designer on an Agile Scrum team</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kQuCCZprTCscvGyvWvtw_Q.png" /><figcaption>Icons by Alex Muravev via The Noun Project.</figcaption></figure><p>When I joined the team at FreshBooks a couple months ago, I arrived equipped with lots of questions. I’m a naturally curious person and I was eager to understand how the other designers kept up with our fast-paced sprint schedule.</p><p>I wasn’t just working with other designers, though—I’m part of an Agile Scrum team, which includes a product owner, scrum master, developers and QA analysts. This was all new to me, as I had never worked on an Agile team before.</p><p>In our first few meetings, I felt like my teammates were speaking a different language. So I put my ethnographic research skills to work to better understand my teammates.</p><p>There were some key things I needed to proactively learn to get up to speed with the team. Let’s call these my research objectives:</p><ul><li><strong>Context:</strong> Understand what’s worked and what hasn’t in the past working with other designers.</li><li><strong>Objectives:</strong> Define our mandate and how it impacts the team.</li><li><strong>Practice:</strong> Identify ways I can add value in the team’s day-to-day activities.</li></ul><p>Using this framework, here are some questions I asked the team to better understand how I could contribute as a new designer.</p><h3>What is your previous experience working with designers?</h3><p>Just like you might ask users to reflect on previous experiences to recall their workflows, I asked my teammates to reflect on previous experiences working with designers. This allowed me to set context for my role on the team.</p><p>One developer on my team told me she was concerned about designers getting bogged down in technical jargon in the past.</p><p>I could see what she meant—for my first few weeks, I wondered whether I even needed to be in the room in Agile rituals like sprint planning and backlog grooming, given the focus on development work.</p><p>But my teammate told me that she wanted designers to be included in those conversations to share learnings from user research and advocate for design considerations.</p><p>I learned that my teammates don’t expect me to perfectly understand their development-oriented discussions, but rather, to bring my specific knowledge forward and to learn about technical constraints by being present.</p><h3>What are we trying to accomplish?</h3><p>Next, I wanted to understand the why — the spark that keeps the team motivated.</p><p>When I started my first project on the team, I dove right in, trying to catch up as fast as I could. But I soon realized that I wasn’t sure of the motivation behind the project—why are we doing this exactly? I needed to understand our business objectives.</p><p>By talking to my team and my PO in particular, I started to build my understanding of our mandate, and how the project fit into the broader product vision. Through these conversations, I also learned the value of the mandate for the team, as it provides them with a sense of the importance of their work for our customers.</p><p>Being able to connect our objectives to the project helped me to focus my conversations with the team around these goals, so that everyone felt grounded in the “why” behind our designs.</p><h3>How can I add value to our day-to-day work?</h3><p>By now, I had gained an understanding of the team’s workflow with designers and the problems they’re trying to solve through some informal desk-side “interviews”. The next step was to start test driving some solutions for how I could bring value to our day-to-day work.</p><p>My two key learnings from my initial research were what I outlined above:</p><ul><li>My teammates want the designer to be actively engaged in Agile rituals so that user research insights and design considerations are shared.</li><li>My teammates want to clearly understand the “why” behind our designs so that they can connect their work to the value it brings to FreshBooks.</li></ul><p>With these insights, I could start trying out some solutions, like bringing more detailed design updates to daily stand-up and posting a synthesis of our weekly research learnings in our team’s Slack channel.</p><p>And conveniently, Agile Scrum has a great feedback mechanism built in through retros, so I’ll be able to collect qualitative data from my teammates to inform iteration on these solutions every two weeks.</p><h3>Building shared understanding</h3><p>By applying UX research methods to learn about my team, I empathized with my teammates and discovered that there’s a need for a strong design advocate on an Agile scrum team.</p><p>I’m still finding new questions to ask of my team to help me understand how I can best work with them. In turn, I’m often responding to their questions as they build out designs.</p><p>Asking questions and finding answers collaboratively builds shared understanding and empathy, the currency of UX that propels Agile teams to work faster and better together.</p><p><em>This post was inspired by Jason Cashdollar’s post on “Questions to ask as a new designer on the team.” </em><a href="https://medium.com/facebook-design/questions-to-ask-as-a-new-designer-on-the-team-7e3ace0c787f"><em>Read it!</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66facdbd7f6d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-freshbooks/using-ux-research-to-learn-about-your-team-66facdbd7f6d">Using UX Research to Learn About Your Team</a> was originally published in <a href="https://medium.com/building-freshbooks">Building FreshBooks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bite-Sized UX: What Makes a Compelling Insight?]]></title>
            <link>https://medium.com/building-freshbooks/bite-sized-ux-what-makes-a-compelling-insight-2e3647c87c0e?source=rss----3a7c8d75f488---4</link>
            <guid isPermaLink="false">https://medium.com/p/2e3647c87c0e</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[insights]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Kiley Daniel Meehan]]></dc:creator>
            <pubDate>Fri, 14 Jul 2017 18:29:09 GMT</pubDate>
            <atom:updated>2017-07-16T12:27:51.676Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>How to tell an insight from an observation — in three minutes!</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ylsgi_X641NYFJOmCJaPzg.png" /><figcaption>Image by Freepik (”<a href="http://www.freepik.com/free-vector/coloured-bulbs-collection_894624.htm">http://www.freepik.com/free-vector/coloured-bulbs-collection_894624.htm</a>)</figcaption></figure><p><em>Welcome to Bite-Sized UX, where we’ll cover a fundamental UX concept in the time it’ll take to reheat your coffee.</em></p><p>As designers, we spend much of our time making sure that we’re solving the right problems. In order to know what the right problems are, we need to uncover insights about the people who are affected by these problems.</p><p>The best way to uncover these insights is through qualitative research: observing and speaking with the people who would benefit from a solution.</p><p>However, in the early days of my career, I had trouble distinguising insights from mere observations.</p><p>For example, imagine we’ve been out in the field chatting with office workers about their eating habits. We come back to the team with: “Young professionals are very concerned about eating healthy”. This is a good observation, sure, but not much of an insight on its own, and will hardly motivate a team to find the best solution. We have more work to do.</p><p>So, how can we make sure we’re uncovering compelling insights?</p><h3>Find the Ideal and the Tension</h3><p>The formula for uncovering insights includes two ingredients:</p><p><strong>Ideal &lt;but&gt; Tension = Insight</strong></p><p>Without an ideal, you can’t understand why your subject is struggling. Without a tension, there’s simply no problem to solve.</p><p>Let’s look at these ingredients a little closer:</p><h4>The Ideal</h4><p>First, you need to understand not only what your subjects are trying to achieve, but <em>why</em>.</p><p>In our case, what’s the motivation behind being health-conscious? Through probing interviews, and using techniques such as the <a href="http://www.designkit.org/methods/66">Five Whys</a>, we may find that at a surface level our subjects are motivated to simply look and feel good.</p><p>The deeper reason, however, may be a desire to boost their performance at work and <em>excel in their careers</em>, without the risk of crashing from junk food.</p><h4>The Tension</h4><p>If these professionals could already reach their ideal, we wouldn’t have a problem to solve. But there’s an obstacle in their way. Uncovering the tension that’s preventing them from reaching their goals is critical.</p><p>This may be tricky. As humans, we can be surprisingly blind to the obstacles in our own life. We also have a tendency to make do with less than ideal solutions that may be making our problems even worse.</p><p>Using techniques like <a href="http://www.practicalethnography.com/">ethnographic observation</a>, we’ll discover not what our subjects say they do, but what they <em>actually do</em>. In our case, this may uncover that the tension isn’t a <em>lack</em> of healthy food options, but a lack of <em>time.</em> Professionals struggle to discipline themselves into eating healthy food when a nearby food court offers cheap, fast food that can be scarfed during a short lunch.</p><h3>Putting it together</h3><p>Now that we’ve uncovered the ideal and the tension, let’s put them together into a succinct statement:</p><p><em>“Young professionals want to be able to feel healthy and energetic so that they can excel in their careers, but a lack of time to choose healthy options make it difficult to do so.”</em></p><p>It’s likely your brain is already jumping into solutions (“Catered vegan meals!” “Fruit bowls in every room!”). Now this is an insight that we can work with.</p><p>When you’re out conducting research, it’s easy to accept information at face value. Instead, by looking for both the <strong>ideal</strong> and the <strong>tension</strong>, you’ll have a better chance of emerging with a compelling insight — the first step towards solving the right problem and, naturally, changing the world.</p><p><em>Enjoy this nugget of Bite-Sized UX? Click the little heart to show your appreciation!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e3647c87c0e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-freshbooks/bite-sized-ux-what-makes-a-compelling-insight-2e3647c87c0e">Bite-Sized UX: What Makes a Compelling Insight?</a> was originally published in <a href="https://medium.com/building-freshbooks">Building FreshBooks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>