<?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 JH Forster on Medium]]></title>
        <description><![CDATA[Stories by JH Forster on Medium]]></description>
        <link>https://medium.com/@jhforster?source=rss-e1c995cbc521------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wZsrswyJo_iEC9v7ZbXnUQ.jpeg</url>
            <title>Stories by JH Forster on Medium</title>
            <link>https://medium.com/@jhforster?source=rss-e1c995cbc521------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:26:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jhforster/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[Don’t fix MVPs that fail]]></title>
            <link>https://medium.com/userinterviews/dont-fix-mvps-that-fail-c0b4f412de47?source=rss-e1c995cbc521------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0b4f412de47</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[JH Forster]]></dc:creator>
            <pubDate>Thu, 17 Jan 2019 20:00:37 GMT</pubDate>
            <atom:updated>2019-01-17T20:00:37.516Z</atom:updated>
            <content:encoded><![CDATA[<p><em>As explained via a weird bridge metaphor!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pwHeJWPl63SScR41rzscIA.png" /></figure><p>Ever found yourself in this chain of events?</p><ul><li>You did exhaustive discovery research.</li><li>You found a real user pain point.</li><li>You iterated through dozens of sketches and prototypes to find a solution.</li><li>You cleverly identified a cheap way to build an MVP.</li><li>You launched it.</li><li>… <strong><em>And it flopped.</em></strong></li></ul><p>Where does one go from here?</p><p>Do you say to yourself — <em>“thank god we only built an MVP and not the whole thing.”</em></p><p>Or do you say —<em> “of course it flopped, it was too stripped down, let’s fix it!”</em></p><h4>My hunch is that lots of teams say the latter and that is almost always a mistake.</h4><p>Building products means dealing with uncertainty. Thankfully, we’ve developed ways of minimizing uncertainty — cheap prototypes, user research, and iterative development. 👊</p><p>This holy trinity of product development often results in creating a so-called <em>minimum viable product.</em></p><p>Despite all that you can learn through research and prototyping, there is still a knowledge gap. Confidence has increased and risk has been mitigated. This is all well and good.</p><p>But you still need to cross the chasm and see what happens once it is real. You’re at Point A and you have learned about Point B. But you still need to actually get there.</p><blockquote>“In theory, there is no difference between theory and practice. But, in practice, there is.”</blockquote><blockquote>Jan L. A. van de Snepscheut</blockquote><p>👆This is precisely why not all MVPs work. If we had successfully mitigated all risk in earlier steps, <em>why not jump right to building the full solution?</em></p><p>So we agree there is still some risk and we want to start small. A minimum product. <strong>But</strong> it also has to be viable. 🤔</p><p><strong>How exactly do you define “viable”?</strong></p><p>This part is <strong>really hard.<em> </em></strong>I think it is one of the hardest things a Product Manager does. You need to thread the needle between two opposing forces.</p><ol><li>Build it quickly and cheaply</li><li>Solve your users’ problem in a real and compelling way</li></ol><p>The first item is a little easier. Cutting scope and reducing functionality is pretty straightforward. It’s not always fun but most folks are pretty good at it.</p><p>It is the second wrinkle that makes this challenging because…</p><p><em>How will you know if the thing you decided to cut is the reason why users didn’t adopt the solution?</em></p><p>This what-if-anxiety can be haunting. This happens because the feedback you receive on MVPs is asymmetric.</p><p><strong>MVP is successful</strong>… you do not get a lot of <em>“this would have still worked without [blah]”</em> from internal or external stakeholders. It is mostly time for 👏 and 🙌.</p><p><strong>MVP is unsuccessful</strong>… you’re left with a lot of “what ifs.” You know, stuff like—<em>“maybe if we had invested in performance more so this wasn’t so slow we would have seen better adoption!”</em></p><h3><strong>I like to call this “the bridge is out trap.”</strong></h3><p>I’ll try to explain. We’ve learned users would like to get to Point B across the river. Unfortunately, there is a gap in the middle of the old bridge that crosses it. As an MVP, we’ve decided to build a small ramp and let people jump the gap for now.</p><p>In this world, you don’t ask a lot of questions after users careen towards the ramp and make it to the other side. You just take a deep breath after watching them catch some sick air.</p><p>But if they come up short? 😬 (Note: no users were killed or injured in this hypothetical example.)</p><ul><li><em>“What if we made the ramp larger?”</em></li><li><em>“What if we installed a radar gun with a sign to encourage users to speed up?”</em></li><li><em>“What if we required cars to weigh in before they can use the ramp?”</em></li></ul><p>This exercise is kind of fun. (Again, the users are not dead so it isn’t morbid, relax.) It is satisfying to trial-and-error your way to a fix.</p><p>Plus, let’s be real — product managers love ideating on solutions. <em>And</em> because this MVP-ramp was so stripped down in the first place there is lots you could conceivably improve about it. <strong>All the low hanging fruit.</strong></p><p><strong><em>And</em></strong>, there is kind of a sunk cost fallacy at play here too. We already built the ramp! Let’s fix it and try again!</p><p>Do you see where this is going yet?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4-_V6NMd2o6lj_8WJqMpbg.png" /><figcaption>Image courtesy of this fine <a href="https://www.amazon.com/Victor-Easy-Mouse-Trap-Pack/dp/B000HJ79Y4">Amazon product</a></figcaption></figure><p>Don’t fall for it. In this example, you didn’t just randomly build a ramp and cross your fingers. 🤞</p><p>You measured the gap. You asked users about the type of cars they drive. You knew the user’s average speed. You did some fancy physics calculations. AKA all of the earlier validation steps. You did these important steps first… right??</p><p>So if it didn’t work? Sure, you could try again. But this wasn’t some fluke failure. It failed despite a good amount of upfront diligence. Odds are it is going to require a significant investment to make it not fail.</p><p>Your MVP failed. Oh well. Big deal. It is part of the process. It is <em>why</em> you use this process.</p><p>Move on. Let it go. Don’t fix the MVP.</p><p>Maybe it is time to pilot a ferry service across the river? Don’t worry—if your users really miss the ramp, they’ll let you know <em>and then</em> you have permission to try again.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FbbW47lgC95I%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DbbW47lgC95I&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FbbW47lgC95I%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/e771c0f63c0245e0b676f72f87bb53b5/href">https://medium.com/media/e771c0f63c0245e0b676f72f87bb53b5/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0b4f412de47" width="1" height="1" alt=""><hr><p><a href="https://medium.com/userinterviews/dont-fix-mvps-that-fail-c0b4f412de47">Don’t fix MVPs that fail</a> was originally published in <a href="https://medium.com/userinterviews">User Interviews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 things I learned from starting a podcast]]></title>
            <link>https://medium.com/userinterviews/7-things-i-learned-from-starting-a-podcast-b9cfb1e0e718?source=rss-e1c995cbc521------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9cfb1e0e718</guid>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[JH Forster]]></dc:creator>
            <pubDate>Fri, 30 Nov 2018 16:04:18 GMT</pubDate>
            <atom:updated>2018-11-30T16:11:32.706Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FIq66DF-Jwhj-wGwSsvhig.png" /></figure><p>That’s right—talking about a podcast in listicle format. All the annoyingly trendy internet things. Look at me. I’m hip! I’m cool!</p><p>Anyway…</p><ol><li><strong>You’ll get numb to the sound of your own voice.</strong> This happened <em>much </em>faster than I expected. I love to talk but I hate hearing my own voice. I believe this is true for lots of folks. But don’t worry, this will go away quickly. Like, really quickly. This was a big surprise to me but it was a very welcome surprise.</li><li><strong>Editing audio files is fun. </strong>I am not a musical person, sadly, so I’ve never played around with audio editing tools before this. It was really rewarding to learn some new skills and get a grip on the editing basics. Never dismiss the value of learning new things. Plus, it was a good excuse to finally open the Garage Band app on my laptop that has been gathering dust for years.</li><li><strong>Get yourself a co-host.</strong> The credit for starting said podcast goes to <a href="https://medium.com/u/d8b1a64d2450">Erin H. May</a>. Would I have tried to do it on my own someday? In theory, maybe. In reality, no. Plus it is really nice to have someone who can help you sift the good ideas from the bad. I knew I had lots of ideas. Guess what? It turns out they are mostly bad.</li><li><strong>The little details matter a lot</strong> (note: I love this <a href="http://littlebigdetails.com/">blog</a>). It took some doing for us to learn how to interrupt one another, how to trim sections down to be more concise, fade music in and out, etc. I’m not suggesting we’re great, or even good, at those things yet. But even the small tweaks we’ve made have had a big impact on how it comes across. It feels more put together.</li><li><strong>Putting yourself out there is scary.</strong> To be honest, I had some concerns about what people might say. But it turns out people are kind—yes, even on the internet. People have been encouraging, thoughtful, and offered good suggestions. I’ve yet to be roasted… Even a small comment like “good name for a podcast” has meant a lot in these early, fragile days.</li><li><strong>Spend a lot of time brainstorming names.</strong> For one thing, it is fun to be unhinged creatively by tossing out idea after idea. It’s a valuable outlet to have when you’re getting frustrated by other things (see: editing audio &amp; little details). But more importantly, it is a good way to uncover what you want the podcast to be. Explaining why you don’t like a word or suggestion provides a lot of context on thoughts that’d otherwise stay buried in your head. Seriously.</li><li><strong>Publishing a podcast is an oddly cool milestone.</strong> I know, I know—anyone with a smartphone and some free time can make a recording and get onto the major podcast platforms. Really, I know this. There are a lot of podcasts out there, I get it. <em>But it still was a really cool moment!</em> I’ll die on this hill. It was a “first” for me and firsts are fun. Don’t believe me? I’ll let Kurt Vonnegut explain.</li></ol><blockquote>Practicing an art, no matter how well or badly, is a way to make your soul grow, for heaven’s sake. Sing in the shower. Dance to the radio. Tell stories. Write a poem to a friend, even a lousy poem. Do it as well as you possibly can. You will get an enormous reward. You will have created something.</blockquote><p>So check out Awkward Silences and let me know what you think. You could even be the first person to rip it to shreds if you want?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fanchor.fm%2Fawkwardsilences%2Fembed%2Fepisodes%2F1---Why-are-we-here-e2lfd0&amp;url=https%3A%2F%2Fanchor.fm%2Fawkwardsilences%2Fepisodes%2F1---Why-are-we-here-e2lfd0&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fanchor-generated-image-bank%2Fproduction%2Fpodcast_uploaded400%2F1093558%2F1093558-1543422466687-ecc5f7cc4b7e3.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=anchor" width="400" height="102" frameborder="0" scrolling="no"><a href="https://medium.com/media/344530719b25686a0fcd0f4e0cd1a6dc/href">https://medium.com/media/344530719b25686a0fcd0f4e0cd1a6dc/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9cfb1e0e718" width="1" height="1" alt=""><hr><p><a href="https://medium.com/userinterviews/7-things-i-learned-from-starting-a-podcast-b9cfb1e0e718">7 things I learned from starting a podcast</a> was originally published in <a href="https://medium.com/userinterviews">User Interviews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Research Hub Story]]></title>
            <link>https://medium.com/userinterviews/the-research-hub-story-406775f4a863?source=rss-e1c995cbc521------2</link>
            <guid isPermaLink="false">https://medium.com/p/406775f4a863</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[JH Forster]]></dc:creator>
            <pubDate>Fri, 17 Aug 2018 12:30:43 GMT</pubDate>
            <atom:updated>2018-08-17T13:16:02.745Z</atom:updated>
            <content:encoded><![CDATA[<p>A behind the scenes look at how we built our latest offering for user researchers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KHg2po3AN1jG83FzKGptBQ.png" /><figcaption>👆that’s me chatting with a researcher</figcaption></figure><p>A little prologue if I may… this has been my favorite thing to work on in my career. Has it gone perfectly? No. Did I make mistakes? Yes. Will it be successful? We’ll see… [<a href="https://www.linkedin.com/in/erinhollingsworth/">Erin</a>, VP of marketing here. Yes, of course it will be! 😅]</p><p>But it’s the closest I’ve ever been to users throughout researching, designing, and building a solution. And not just any users — UX, research, and product professionals from world-class organizations who were super engaged whenever we asked for input.</p><p>Plus, I got to build a tool for myself that I use all the time now. You’re not your user? HA!</p><p>Lastly, I did it all alongside an awesome team where we supported and challenged each other constantly.</p><p>Here’s the story of how we got here. To our big launch of <a href="http://userinterviews.com/research-hub">Research Hub</a>.</p><h3>What should we build next?</h3><p>The debate around how to determine what to build for your customers to meet their needs is a lively one. One school of thought is that you cannot simply ask your customers what they want because they don’t know (faster horses, anyone?). Others are more open to considering input from their users.</p><p>Regardless of your organization’s philosophical bent, if your customers are actively bringing the same idea to your doorstep over and over, you’d be wise to listen. This was the situation we found ourselves in a few months ago.</p><p>We’re in the business of recruiting targeted participants for user research, so we’re pretty accustomed to questions like “are you able to recruit x,y,z type of participants?” (<a href="http://userinterviews.com/recruit">Yes, btw</a> 😉). But we started noticing a trend of researchers asking us if we could handle all the recruiting and logistics when they need to talk to their own users. See for yourself:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uWiSi6ntJMYLy2DZ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sSvzSLYLCRrRajKd.png" /><figcaption>Email from <a href="https://www.linkedin.com/in/jlm418/">Jodi Martin</a>, Customer Experience Coordinator @ <a href="https://www.constantcontact.com/mainpage?utm_id=YAH-103969&amp;cc=YAH-103969&amp;utm_source=Yahoo&amp;utm_medium=cpc&amp;utm_campaign=PPC_BRAND_EMM_PERF_PROSP_PROSPECT_NULL&amp;utm_term=constant+contact+e&amp;utm_content=Constant+Contact&amp;pn=search&amp;kid=548f022d-a804-4766-b4a7-f88fe271f6b2&amp;keyword=286969552309&amp;adgroup=7508125277&amp;device=c">Constant Contact</a></figcaption></figure><p>This was an exciting development for a number of reasons.</p><p>First, we genuinely care about our researchers and here they were with a pain point that we were well positioned to solve! And sure, selfishly, we had this exact same problem ourselves and didn’t mind the idea of building a tool to make our lives easier, too.</p><p>Second, we know different types of research require talking to different types of users. Prospective users, our bread and butter at User Interviews, are great, but sometimes talking to existing users is even better (imagine you’re redesigning a core workflow in your app — kind of important to hear from users who rely on that workflow).</p><p>If we can make it easier for researchers to do both in a single place then we’re reducing friction and making it easier to talk to the right users at the right time, all from one place.</p><p>Everyone should do more research. Talking to people, learning things — it’s the best (provided you’re not getting bogged down with tedious logistics, of course 😜).</p><p><strong>Anyway, we were excited</strong>. But thankfully we didn’t get <em>totally</em> ahead of ourselves.</p><h3>Wait, so what exactly do they need?</h3><p>How’d we answer this? C’mon, we talked to our users. Well, <em>technically</em>, we surveyed our users first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/353/0*Lb6Kzd0Uw5fzFpOR.png" /><figcaption>The first survey we used</figcaption></figure><p>We emailed a group of our more active customers and framed filling out this survey as “becoming a design partner” on the solution. This was intentional as we wanted to view these responses as high intent. We figured if they care about this problem enough to volunteer to help us solve it, then that’s a strong signal.</p><p>We had 44 design partners almost overnight.</p><p>This was great because it covered a lot of vectors where we thought the right solution to this problem might deviate. Are you the only researcher at a company or part of a large research team? Do you work for a large company or smaller company? Are you restricted about contacting your users for feedback? Etc. It seemed like any number of things could impact how you go about engaging with your own users for feedback and we had our bases covered.</p><p>From there, we tossed together an <a href="https://www.userinterviews.com/blog/veteran-designer-nicola-rushton-interviews-us-as-we-interview-her">interview outline</a> of questions (<a href="https://docs.google.com/document/d/1D3ojqDKID4us8DmCZsj7AJbXtXbU58rNkkJSX-yAnlM/edit?usp=sharing">check it out here if you’re curious</a>). The goal of these conversations was 100% discovery. How are people solving this problem currently and what are their biggest pain points?</p><p>We spoke to 12 users during this initially discovery phase and a few clear themes emerged.</p><h3>Themes</h3><p><strong>1. Researchers are clever.</strong></p><p>We heard about a wide variety of homegrown solutions for recruiting their existing users. MacGyver would be proud. Allow me to paraphrase a bit…</p><p>“We use this tool to contact them but survey them through another tool, manually vet responses, and use this scheduling tool for the people we like. Incentives? That’s always kind of a mess.”</p><p>These solutions, of course, were never perfect and everyone had a complaint about some part of it. But this showed that recruiting their existing users was important enough that they weren’t waiting around for a solution. They were out there creating solutions. It also taught us a ton about the nuances that people care about. It was like having dozens of MVPs already in market to learn from 😍. Some researchers even went as far as screen sharing with us to really show how it worked or mock recruiting us through their process and tools.</p><p>Yea, I know — our users are the best.</p><p><strong>2. Researchers are also empathetic.</strong></p><p>No surprise here, but it came through loud and clear how much they care about their user’s experience even when recruiting them. They were often asking us just as many questions as we were asking them.</p><ul><li>“How will this be branded? Will it say User Interview or have my company’s info?”</li><li>“Do my users have to make an account on your site or can they just submit their info?”</li><li>“What’s the experience like for users who apply to participate but don’t get selected for a spot? How do I let them know what’s going on?”</li></ul><p>And so on. I’ll say it again — our users are the best. We’re legit spoiled.</p><p><strong>3. Tracking and coordinating who you’re contacting is a nightmare. For everyone.</strong></p><p>Even if you’re the only researcher in a small organization, tracking when you last contacted someone for feedback… and when they last responded… and when they last actually participated… and so on is a ton of work.</p><p>This was a huge light bulb moment for us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*5Wkoqu3Wi1Q4PtLA.png" /><figcaption>Did I do this meme thing right?</figcaption></figure><p><em>Just a quick sidebar here</em> — obviously I know and believe user research is hugely valuable. It is literally what I do for a living. That said, it still feels nice to occasionally get clobbered over the head with an insight and have an “ah ha!” moment. This was one of those. We all need a little reinforcement now and again.</p><p>Ok, where was I?</p><p>Hearing stories over and over again of spreadsheets that fall out of date, or systems that don’t talk to one another, or simply not having the time to do it was eye opening. People who had a system for tracking either hated it or admitted it wasn’t totally accurate. Others didn’t even bother pretending to track this information (this is sneaky my favorite group — skip the bullshit 👊).</p><p>Let me explain why this was a significant insight. Up until this point, we had really only been thinking of the solution as one-off, on demand type thing. You need to talk to users for feedback on something, and here is a tool that makes the process easier. Now we had discovered there was a lot of value in also helping organizations connect the dots between studies and make sure they are not over contacting the same users. Better yet, our solution was naturally well positioned to do this exact thing.</p><h3>Ok, let’s build everything!!!</h3><p>Alright, that wasn’t our exact thought process but our enthusiasm combined with all of our new insights did cause us to get a little carried away. We started sketching and kept sketching and then sketched some more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YaREEo7hAItb-LM_.png" /><figcaption>Trust me, there are more sketches. I don’t own a wide angle lens and how many of these photos do you really want to look at?</figcaption></figure><p>‍So far, so good. This is a fun part of the process after all. But like most fun things in life, they can also be a little dangerous and you can get yourself into trouble if you’re not paying attention.</p><p>If I’m being honest (I am), we made a few mistakes during this phase of things.</p><p>The biggest one we made was the most obvious. We started trying to fix everything. You know, only like the cardinal sin of product development. No big deal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/0*ut2viJJTc9H8Nw2h.png" /></figure><p>To be fair, the feedback and insights we collected about how researchers recruit their existing users really did touch on the entire recruitment process, which is what our product does. So all of these tangential ideas and proposals weren’t really even all that tangential (uh oh, I’m justifying it again…).</p><p><strong>Tl;dr</strong> — we lost our focus for a bit.</p><p>Then we caught ourselves, shelved a bunch of awesome ideas that we will revisit later, and got back to the task of making it possible for researchers to use our tools to recruit their users.</p><h3>Pricing — Let’s talk about Pricing</h3><p>Another area that proved irresistible to us early on was pricing 💸. This actually wasn’t some profit driven obsession. It was a matter of our current business model <em>not feeling right</em> for this new solution. I know that sounds squishy and emotional for a quantitative and scientific thing like pricing but hear me out.</p><p>We charge a <a href="http://userinterviews.com/pricing">flat recruitment fee per participant</a> that we recruit for a researcher from our audience. This can be framed different ways but it is largely a sourcing fee. It didn’t make a ton of sense to us to charge researchers the same way when they are recruiting their own users.</p><p>It was an itch we couldn’t stop scratching. On the whole, this wasn’t unproductive or entirely misguided. The mistake was that we spent too much time on it, too early in the process. If I could do it over again, I would have waited until the solution was better defined before getting into pricing. Now, even with this knowledge, in an alternate reality do-over, would I actually have the willpower to delay these conversations? Unclear.</p><h3>Process Mitigates Time Lost</h3><p>The good news is that we hedged our bets such that these mistakes didn’t cost us much. How? Sequencing. How you stagger and parallelize things is really important in product development. I think sometimes people are hesitant to discuss it because it can sound a little “waterfall-y” on the surface. And doing anything that can be seen as sympathetic or supportive towards waterfall development processes, gets you kicked out of the cool kid club these days. <a href="https://twitter.com/johncutlefish/status/1022906021491032065">Or does it</a>?</p><p>Don’t let that scare you, thinking about how the various pieces will come together with your team is a valuable exercise.</p><p>In our case, we knew all along that storing another organization’s user data in our system was going to mean we had to absolutely nail security and privacy. There was no question about the importance of this area. The architecture investments to do that did not have a lot of dependency on the workflow or UI choices we were debating so we put the development team to work. This gave them a little more breathing room to make sure the User Interviews audience of participants and any organization’s population of users were totally separate and isolated.</p><p>And it gave the rest of us a little breathing room to recover from the aforementioned mistakes we were busy making 😬.</p><p>The developers got started on the infrastructure. The rest of us ironed out the remaining details to make a credible prototype and started getting feedback.</p><p>We ended up having 26 sessions where we showed researchers some iteration of the prototype we kept evolving, day to day, week to week.</p><p>Suffice it to say, the prototype changed a lot from the original version and we learned a ton. I won’t bore you with all the details. Here are a couple of the highlights.</p><h3>Some things we learned in validation testing</h3><p><strong>1. Screeners — not always required</strong></p><p>Researchers have other means of targeting and qualifying their own users for a given study so collecting additional contextual data can sometimes be a hindrance rather than a plus. Not much else to say on this one. Makes sense.</p><p><strong>2. One thumbs up for tracking “activity stats” on users; two thumbs up for tracking those stats in an intuitive format</strong></p><p>We took our best guess at what “activity stats” would be helpful to track — last invited, last applied, last participated — and that guess was quickly validated. A fun, small detail that we learned was providing the data in an “X days since” format was more useful to researchers than providing the date itself. It better fit their mental model of suppression rules (i.e. “I don’t want to invite anyone who has been invited within the last 30 days”) and saves them from doing annoying “date math” (the User Interviews team can attest — “date math” is a serious pet peeve of mine).</p><p><strong>3. Organizing their users is important, but flexibility and simplicity rule</strong></p><p>Our very earliest prototype included the notion of organizing users onto specific “panels.” This paradigm was inspired by “customer counsels” or “customer advisory boards” researchers had referenced in the discovery conversations. Conceptually, “panels” resonated but lots questioned followed. “Can the same user be on two panels? How do their activity stats get tracked in that case?” In comparison, a flexible approach that allowed researchers to apply labels, create custom attributes, filter on attributes and labels, then save these filters to build any kind of list did not generate these type of questions and handled a wider variety of use cases. Perfect.</p><p><strong>4. Providing paths for their users to “opt in” to providing feedback outside of a study is valuable… but hard to solve.</strong></p><p>Researchers loved the idea of giving their users a persistent way to “opt in” to providing feedback and knowing who had explicitly opted in. We tried to crack the case on this one. We really tried. But there wasn’t a single approach that fit the different use cases for different researchers. Custom landing pages, embeddable forms, on-site intercepts, etc. We will definitely come back to this topic but it was beyond the scope of a v1 effort.</p><h3>Should we ship it? We should ship it.</h3><p>As the solution was coming together, we planned to do a lot of internal dogfooding of early versions as soon as we could. Remember, this is a problem we have too! There were <em>SO MANY TIMES</em> when we were trying to get feedback on this solution where we wished the solution already existed so we could use it to schedule these very feedback sessions. Heady stuff.</p><p>But the more we thought about this the more we realized we should open it up to our users too. After all, shipping things before you’re totally comfortable is how you accelerate learning. And our users cared enough about this problem to spend a lot of time with us giving their input throughout the process.</p><p>We slapped some duct tape on what we had built so far and opened up a beta for anyone interested.</p><p>What did the beta look like on day 1?</p><p>It consisted of a functional but limited project builder that lacked some of our normal tools. We had a CSV importer tool that could only accept email, first name, and last name as fields. It also sometimes did not parse the file correctly and failed silently. There was not yet any concept of tracking which users had been contacted across a company. Plus plenty of other small hacks that we jammed in behind the scenes during the final few days of testing.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fta83CqOoRwfwQ%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fwreck-it-ralph-ship-ta83CqOoRwfwQ&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fta83CqOoRwfwQ%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="332" frameborder="0" scrolling="no"><a href="https://medium.com/media/7ff39f820441812f5a85b9c55393d784/href">https://medium.com/media/7ff39f820441812f5a85b9c55393d784/href</a></iframe><p>I think this is, hands down, the best decision we made throughout the entire process. It was also, by far, the most intimidating. Any time you build something, you know where all of the little flaws lie and you wish you could fix them all before anyone else uses it. But that’s a fool’s errand. No product is perfect or ever really can be. We all know this on an intellectual level.</p><p><strong>Emotionally?</strong></p><p>It’s <em>a </em>little different. Shipping a barely functional version of a product to a group of UX, research, and product professionals — aka my peers who I respect deeply — was scary. Like really, truly, legitimately scary.</p><p>Like most things in life when you decide to set your fears aside, it turned out to be amazing. No, things did not go perfectly. But we got questions, suggestions, and bugs pointed out to us regularly. Internally, it gave us a renewed energy and sense of urgency. We even had some people who — *gasp* — told us how much the beta was already helping them and saving them time.</p><h3>Look at some of the unsolicited feedback we received.</h3><blockquote><em>“We just finished a round of user interviews and enjoyed the experience. I definitely plan to use your service again.”</em></blockquote><blockquote><em>- </em><a href="https://www.linkedin.com/in/shafiqshariff/"><em>Shafiq Shariff</em></a><em>, VP Product, </em><a href="https://pangeamoneytransfer.com/"><em>Pangea Money Transfer</em></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/0*n4sueWL4avB38j7m.png" /><figcaption><a href="https://twitter.com/cassietorda">Cassie Torda</a>, UX Designer, Egnyte</figcaption></figure><blockquote><em>“We really like being able to upload our own customers as participants — this has proven to be super successful for us, and really easy to use.”</em></blockquote><blockquote><em>- </em><a href="https://www.linkedin.com/in/brandie-ward/"><em>Brandie Smith</em></a><em>, Senior User Researcher, </em><a href="https://www.metromile.com/?content=10420485540&amp;matchtype=e&amp;campaignid=132816266&amp;adgroupid=4554491126&amp;device=c&amp;network=o&amp;msclkid=9cbac88fa3d9195d2ebc93e73b0e219c&amp;utm_source=bing&amp;utm_medium=cpc&amp;utm_campaign=2016B_S_Brand_AllStates&amp;utm_term=metromile&amp;utm_content=metromile"><em>Metromile</em></a></blockquote><h3>We also learned a lot.</h3><p>Here’s an example — we didn’t bother setting up our usual messaging tools for these private projects because a) we assumed they wanted to own the communication channels with their users and b) it is slightly more complicated because their users do not have User Interviews accounts.</p><p>Well, it turns out that people want to be able to message their users through our tools. Fair enough. We are in the process of adding that functionality.</p><p>Another small thing we missed — requiring a monetary incentive payment. This is kind of an embarrassing one because it affects our own usage of the tool… we often offer our researchers free participant credits to use on future projects as a thank you for speaking with us. And yet, somehow, we didn’t account for this upfront 🤦‍. Don’t worry, we’re busy fixing this too.</p><p>Categorically, we learned the most about how researchers wanted a centralized participant database of their users to work. As noted above, this functionality did not exist <em>at all</em> on day one of the beta. As users launched private projects during the beta and uploaded their users into our system, they developed stronger points of view on how the participant database should work based on real world use cases. So we made it possible to bulk apply labels to users while importing a CSV, set up the ability to add custom fields of data on users, and built out robust filtering tools. All of these things came directly from user feedback.</p><p>Relatedly, we discovered that a lot of researchers wanted to import large lists of users upfront, outside the context of a specific project. We introduced the ability to upload a CSV directly to their participant database and beefed up our architecture to support much, much larger imports.</p><p>Lastly, we were able to better understand concerns around privacy and data security. Something as seemingly simple as being able to delete a user was a huge win to alleviate concerns here, and came from beta user feedback. Clearly a researcher should be able to remove a user from our system. That’s a no brainer.</p><p>But what if that user had previously participated on a project? How did the researcher expect to see that record when they went back to the project after deleting the user? Well, we found out and now that use case is covered.</p><p>Going through rounds of penetration testing and other technical security review measures were valuable for the new feature set as well. Always nice to learn your app can meet the standards of a corporate IT security team during a beta release.</p><h3>So that’s pretty much everything, but we’re not done.</h3><p>Today is a big milestone for us. ✅</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FYEL7FJP6ed008%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fhappy-fathers-day-fathersday-YEL7FJP6ed008&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FYEL7FJP6ed008%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="321" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd1eb7f981b20cf61237c8907f7b105e/href">https://medium.com/media/dd1eb7f981b20cf61237c8907f7b105e/href</a></iframe><p>Launch days are fun. They are also the first step of a longer journey. Or, I guess, technically the second step if you already had a beta? 🤔</p><p>As I mentioned earlier, we had <em>a lot</em> of other ideas we’d like to get to after talking so extensively to our users. So the plan is very much to continue talking to users, continue iterating on the solution, and continue to solve our users’ problems (as they relate to user research, at least).</p><h3>Learn more about Research Hub + Give us feedback</h3><p>If you’d like the more focused, concrete explanation of what we’re actually launching then I’d encourage your to check out my colleague’s post.</p><p>If you want to sign up for a free 2-week trial, <a href="https://www.userinterviews.com/research-hub">you can do that here</a>.</p><p>If you’d like to sign up to give us feedback on Research Hub or future products, <a href="https://www.userinterviews.com/beta">sign up here</a>.</p><p>If you’d like to become my best friend then send me your thoughts or feedback on our app or user research in general, comment below and we’ll catch up. ✌️</p><p><em>Originally published at </em><a href="https://www.userinterviews.com/blog/the-research-hub-story"><em>www.userinterviews.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=406775f4a863" width="1" height="1" alt=""><hr><p><a href="https://medium.com/userinterviews/the-research-hub-story-406775f4a863">The Research Hub Story</a> was originally published in <a href="https://medium.com/userinterviews">User Interviews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[26.2 Reasons Why Talking to Users Is Like Exercising]]></title>
            <link>https://medium.com/userinterviews/26-2-reasons-why-talking-to-users-is-like-exercising-af5c0d0fe8f3?source=rss-e1c995cbc521------2</link>
            <guid isPermaLink="false">https://medium.com/p/af5c0d0fe8f3</guid>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[JH Forster]]></dc:creator>
            <pubDate>Wed, 14 Feb 2018 17:43:54 GMT</pubDate>
            <atom:updated>2018-02-14T18:30:12.818Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the past few months, I’ve been running more than ever. Coincidentally, I’ve also been talking to more users than I ever have in my career. Given my penchant for reading articles with silly conceits, especially ones that mix lessons from different disciplines together, it was only a matter of time until my brain started connecting exercising and user research. Low and behold, one morning, during a run no less, I started drawing parallels between the two. So here are 26.2 reasons why talking to users is like exercising, and what we can learn from each to inform our approach to the other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MJFZ8d348VzWpUu2.png" /><figcaption>That’s me, 2132.</figcaption></figure><p>1. You know it is one of the most important things you can do but it is shockingly easy to put off and justify focusing on other things instead.</p><p>2. Making the commitment to do it and showing up are often the hardest parts.</p><p>3. It’s a good idea to keep your initial enthusiasm in check. Focus on building a healthy, sustainable routine rather than burning yourself out.</p><p>4. It’s hard to get started but easier to maintain once you’re in a good rhythm.</p><p>5. Because once you’re actually doing it, it is usually more enjoyable than you expected, especially the natural high that follows a good session.</p><p>6. You’ll still get a lot of out of it, even if you’re not particularly good at it when you’re just starting out.</p><p>7. There is almost always a way you can do it by yourself and for free if you’re creative and motivated.</p><p>8. But it can be more effective to practice with others as you challenge and motivate one another.</p><p>9. And sometimes a few smart investments will be worth every penny.</p><p>10. Experiment by doing. Try a variety of things to see what you like and what aligns with your specific goals and constraints. Don’t let people fool you, there is no one size fits all approach.</p><p>11. You’ll learn that making yourself uncomfortable is okay and, actually, a good thing.</p><p>12. You don’t have to specialize either. Variety will keep you engaged, make you more versatile, and prevent burnout.</p><p>13. Be sure to pay attention to your form and technique. By simply being mindful and aware you’ll notice a lot of signals that can help you avoid developing bad habits.</p><p>14. When you’re just getting started, it can be really helpful to have a mentor or a coach to give you support, feedback, and encouragement.</p><p>15. Once you know what you’re doing, it can be really helpful to become a mentor or a coach to someone who could use your support, feedback, and encouragement.</p><p>16. Even when you’ve gotten really good at it, there will still be times where it completely humbles you.</p><p>17. There will be days where, no matter what, you don’t feel like doing it. That’s okay. Show up anyway and often you’ll be surprised at what happens once you get going.</p><p>18. Even when things don’t go so well (which will happen), you’re still better off by having showed up and put in the effort.</p><p>19. If you feel like you’re hitting a plateau, set a new goal and let others know about it.</p><p>20. It is important and healthy to give yourself breaks. Use that time to rest and reflect. Don’t forget, growth actually occurs as you recover.</p><p>21. Keep a log of your journey, how far you’ve come, and what you’ve accomplished so you can use it for motivation when you’re feeling flat.</p><p>22. You can’t do it all at once — progress takes time and happens in small increments — but the compounding effect over time is profound.</p><p>23. Measure yourself against yourself. It can be defeating to constantly compare yourself against other people.</p><p>24. Doing it consistently will lead you towards other positive unexpected and seemingly unrelated outcomes.</p><p>25. Look for ways to find efficiency in your process and improve how you prep, but don’t mistake shortcuts and hacks as a replacement for doing the work. <a href="https://www.youtube.com/watch?v=JB2di69FmhE">7 minutes abs</a> can only take you so far, after all.</p><p>26. You know there is a difference between people who say they could do it if they wanted and people who actually do it.</p><p>Lastly… c’mon, you didn’t actually think there would be a .2 item for this silly clickbait title, did you?</p><p>Alright, alright: fine, here is a closing thought.<strong> The big .2 finale.</strong></p><p>26.2. At some point, you’ll inevitably annoy the people around you as you talk about how great it is and how everyone should do it.</p><p><em>Originally published at </em><a href="https://www.userinterviews.com/blog/26-2-reasons-why-talking-to-users-is-like-exercising"><em>www.userinterviews.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af5c0d0fe8f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/userinterviews/26-2-reasons-why-talking-to-users-is-like-exercising-af5c0d0fe8f3">26.2 Reasons Why Talking to Users Is Like Exercising</a> was originally published in <a href="https://medium.com/userinterviews">User Interviews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for your user’s users]]></title>
            <link>https://medium.com/userinterviews/designing-for-your-users-users-bb859e91f727?source=rss-e1c995cbc521------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb859e91f727</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[JH Forster]]></dc:creator>
            <pubDate>Mon, 28 Aug 2017 20:21:02 GMT</pubDate>
            <atom:updated>2017-08-28T20:50:30.855Z</atom:updated>
            <content:encoded><![CDATA[<p>We caught up with the Head of Product Design at Appcues to hear his thoughts on how to keep downstream users top of mind.</p><p><em>“Other side of the table” is a series by </em><a href="https://www.userinterviews.com/"><em>User Interviews</em></a><em>. This week we’re featuring one of our favorite design leaders, </em><a href="https://medium.com/u/f9b99958ab0a">Tristan Harward</a>, <em>who works on a product with some unique challenges. He gives us a glimpse into how </em><a href="https://www.appcues.com/"><em>Appcues</em></a><em> stays focused on all of their users, gets everyone involved in research, and onboarding mistakes to avoid.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/149/1*JI-mElA7jTah9svYAPcxPg@2x.jpeg" /><figcaption>Tristan Harward, Head of Product Design @ Appcues</figcaption></figure><p><strong>Let’s get started with the basics, can you tell us a bit about yourself? Where you live, hobbies, family, etc.</strong></p><blockquote>I live in Somerville, MA with my wife and the best little miniature goldendoodle named Izzy. Outside of work I love pretty much anything creative — photography, poetry, music, art, cooking, woodworking, cleaning (hey, it makes things look good!).</blockquote><p><strong>What’s your current role and how did you get there?</strong></p><blockquote>I’m currently head of Product Design at <a href="https://www.appcues.com/">Appcues</a>, which is a cool small company in Boston that helps non-engineers create great onboarding and communication experiences within their product.</blockquote><blockquote>I got the job via twitter: the CEO found me and one coffee led to another. Before that I was at Localytics for a couple years learning the ropes from some incredible designers.</blockquote><p><strong>Switching gears a bit — what’s the best random thing you’ve found on the internet recently (preferably with links)?</strong></p><blockquote>Gotta say the roundup of everything having to do with the eclipse, especially <a href="https://www.youtube.com/watch?v=G10m2ZZRH4U">this video</a> that really gives you a sense of what it was like to be there in the path of totality.</blockquote><p><strong>And what’s your most useless skill?</strong></p><blockquote>I’m really good at making sure that no Slack channel’s unread indicator survives for long.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*JK-NJse5T1mmPmXnrsqJfQ@2x.png" /></figure><p><strong>Alright, switching gears. Appcues plays in an interesting space where your product is being used by your users <em>and</em> your user’s users. How do you think about both of those groups while designing?</strong></p><blockquote>Great question. I’ve run into the same interplay before working on other B2B products, like at Localytics. It’s unique because you’re part of a value chain, and part of your customers’ customer experience, which adds extra complexity and responsibility.</blockquote><blockquote>I like to handle this by making various models. The best way to tell you what that means is by passing along <a href="https://medium.com/@cwodtke/five-models-for-making-sense-of-complex-systems-134be897b6b3">this great post from Christina Wodtke</a>. Basically, like an architect might build a model of the building before the real thing, you can make high-level models of how your product will fit into the landscape.</blockquote><blockquote>The first step is research. For the B2B link, you have to do double—both your customers, and their users—and then think about what lines up across all your customers’ users to make coherent product decisions out of it. It’s not simple.</blockquote><blockquote>In the end, I like to visualize all of that abstract stuff so it’s easier to understand. In the past I’ve make a map on a single page showing bubbles with our product, our customers, and their users, how things connect, and what’s generally true of each group, which helps start the right discussions. It’s a challenge, but I also think it’s one of the reasons B2B design is so much fun.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*E03pJAXXbICrJG51Xzi3pQ@2x.png" /><figcaption>A simplified model of a B2B2C company’s concerns.</figcaption></figure><p><strong>Getting even more meta — how have you used the Appcues product to help new users learn how to use Appcues? What have been the biggest things you’ve learned from iterating on that over time?</strong></p><blockquote>Yeah, this is one of my favorite topics. We dog-food our own product as much as we can, and it’s one of our biggest sources of learning and experience.</blockquote><blockquote>We announce and teach all of our new features with Appcues, and by doing that we’ve learned not only how we use our own UI and how our users experience flows, but also in how our company handles the collaborative process of making them. I think it’s hard to get a feel for what happens outside software, and what I’m realizing first-hand is that there’s a lot of interplay between different roles and responsibilities even within our relatively small team, and that definitely makes me reflect on our customer experience.</blockquote><blockquote>The other thing we’ve used Appcues to do with great success is recruiting for our user testing and research. We have the highest success rate by far when we ask people in-app if they want to sign up; it just pales in comparison to emailing people, and the folks we get are engaged users who have great insights.</blockquote><p><strong>You guys just launched an awesome new resource — </strong><a href="https://www.reallygoodux.io/"><strong>Really Good UX </strong></a><strong>— what has been the most useful takeaway for your own growth as a designer through compiling all those examples?</strong></p><blockquote>I think it’s this: keep your eyes open. One of the core habits we have — the one that spawned Really Good UX — is posting any examples of UI we like that’s in any way related to what Appcues <em>could</em> do in a slack channel. This channel has been building up for years, it often gets multiple posts per day, and it’s become a huge idea board for solving problems in our wide UI space.</blockquote><blockquote>For Really Good UX, we loved that resource so much that we wanted to share it with the world in a really focused way. I love how blunt it is: it’s not about deeply analyzing UX or understanding all the research or the team behind it, it’s just about keeping your eyes open and your visual gears moving, and there’s something to that simple habit.</blockquote><p><strong>What is the biggest mistake you consistently see made across products in terms of how they handle onboarding for new users?</strong></p><blockquote>Absolutely positively one big thing: onboarding your product, not your user. I think the default take is that the user should know all the ins and outs of your software and how it works, but the first step isn’t knowing how it works — it’s convincing users to stick around to find out, and then guiding them through solving the problem they actually care about.</blockquote><blockquote>Users don’t care about your product or its features, they care about getting what they need done.</blockquote><blockquote>So, if your onboarding helps them get to their dream destination quickly and clearly, they’ll love it, and it’ll work. If tours are showing them every flashy landmark and turn-off on the side of the road that they don’t care about, then they’ll get annoyed and turn them off. It’s less about whether you use tooltips or pulsating dots, and more about what they’re focused on.</blockquote><blockquote>I think that’s the root cause of the annoying onboarding horror stories everyone has experienced, and we’re thinking about how we can educate our own customers better on foundational skills so we nip that problem in the rear for the good of the whole internet. <a href="https://www.appcues.com/blog">Our blog</a> is a great resource for this honestly — and we want the product to bring more of that content in. That’s the dream.</blockquote><p><strong>Back to some user research specific questions — what is your favorite “war story” from a user research session you were involved in?</strong></p><blockquote>I was pretty moved one time when I was interviewed myself (on the other side of the table, wink wink). The call was pitched as a user test, but when I got in it was very clear I wasn’t the right audience for the research, and the questions had nothing to do with my work or how I used their product. I could tell the interviewer was getting frustrated with me, we wrapped up quickly, and I felt so embarrassed and demeaned by the whole process.</blockquote><blockquote>It really underscored for me how treating your research subjects with empathy and understanding their environment and situation are so important, and not just to treat them like a vessel of information you want to extract — lessons I took into my own research.</blockquote><p><strong>There has been a big surge in “design thinking” recently, how would you like to see that trend continue to evolve?</strong></p><blockquote>I’m really glad that design itself is becoming more familiar to more people, and less of a black box. That’s what I want to see continue: for people to understand design as a working practical system rather than a set of magical powers.</blockquote><blockquote>Instead of a mystery art, I want people to think, how do I take all of what we know, make some good models, use them to get creative, and make something that’s working, valuable, and joyful? It’s hard to get to that point because there are a lot of moving parts and barriers and difficult-to-measure things, but I think more people can break it down and get it, and I want to keep encouraging that optimism that we can make this process work in many contexts.</blockquote><p><strong>In what ways do you deviate from the conventional wisdom around user research?</strong></p><blockquote>Including more people and more roles in the interview process. I’ve been in situations at past companies where the owner was fairly protective of the sacred research process (I’ve even been that person). At Appcues, there was already a <a href="https://medium.com/appcues/three-meetings-that-changed-everything-db5832239648">pretty solid user testing and research process</a> when I arrived that our CEO, <a href="https://medium.com/u/15c5d7d051c1">Jonathan Kim</a>, had set up, with a monthly “User Testing Day,” where the whole product and engineering team was interviewing users. It broke down my assumptions about what it means to be a user researcher.</blockquote><blockquote>It took some getting used to, but I’ve gotten to the point where it’s more about helping other people do better interviews and learn, than doing all the research myself, and that’s been a sea change. It’s no longer just about gaining knowledge, but also drives motivation and transparency and helps more people get a direct connection to users and problems. It’s a bit magic.</blockquote><blockquote>When I started trusting the developers more, trusting users to handle unorthodox situations (like an interview with 4 people on the call), things worked out even when I didn’t expect them to. People are flexible. I’m impressed at how well our team runs interviews, how smart and resilient our users are, and how much fun it is. It’s not perfect, but it’s easy to see that the upsides greatly outweigh the downsides.</blockquote><p><strong>What do you think is the biggest mistake people make when approaching user research?</strong></p><blockquote>Not forming a good connection or building enough empathy from the start. That part of an interview where you talk about the user’s background and experience and job or whatever profile fields you want to capture — it’s a huge opportunity. You can gain empathy and context, guide what you ask in the future and how you ask it, and build a rapport so the rest of the interview is multiplied. I think a relaxed, happy person who knows you have their back and aren’t judging them will get so much deeper on any topic.</blockquote><blockquote>My goal is to make an honest human connection with the person on the other end, and set it up so it’s all but guaranteed that you get truth and honesty just oozing out of the conversation. In my experience, that happens more often when I achieve a good connection early on. I fail to do that as many times as I succeed, so it’s not easy, but it’s worth shooting for.</blockquote><p><strong>After years of doing user research, what is biggest lesson you’ve learned? The type of thing you wish someone had told you about when you were getting started.</strong></p><blockquote>So many things, but I think the biggest one I wish I had been told when getting started would be, just to talk to as many users as you can.</blockquote><blockquote>Just do it.™</blockquote><blockquote>You can learn all the little tips along the way, but nothing takes the place of experience and practice. Drop all your fears and schedule 5 calls this week and just do your best, get feedback, mess up a lot, and try it all again next week.</blockquote><p><strong>Let’s wrap up with some quick hits. How do you like to prep right before sitting down with a user for a research session? Any habits that you find effective?</strong></p><blockquote>I love having everything all prepared (mise en place) and printed out or written on plain sheets of paper. I take notes and scribble all over everything. It’s like driving a car made in 2005 vs one made today — I want the 2005 one with all the physical dials and switches in the same place so I’m never fumbling and can focus on the road without looking at the screen.</blockquote><p><strong>What tools do you use during sessions? For interview guides, notes, recording, prototypes, etc.</strong></p><blockquote>Our interviews run the gamut from exploratory research, to specific usability tests, so we use a variety of tools based on what we’re trying to do. Paper is my thing for guides and taking notes, and for any printouts I try to stick to one page Google Docs so they print nicely and I’m not turning pages. For prototypes, often InVision, and sometimes for more interactive needs, raw HTML and Javascript. We use Zoom for remote calls, recording, and screen/mouse sharing.</blockquote><p><strong>How do you and your team document and share the insights you collect from user research?</strong></p><blockquote>The first is just our process: we get more people to participate. All engineers are listening to the calls and getting the insights first hand. Beyond that, we record all the calls using Zoom and have them all in one Google Drive folder to go back to, and I try to summarize conclusions and send out an email after our monthly user testing day. We also have Slack channels where I’ll post random things I heard on calls, or interesting notes.</blockquote><blockquote>One of the coolest things I did recently was to go back to a round of research I did three months prior, and listen to everything over again. I was doing it for a round-up presentation on the topic, but I learned so much I didn’t expect. I had a whole different perspective on what users were saying, and all my biases at the time seemed less important. Highly recommended.</blockquote><p><strong>Are there any tricks you use to make participants feel relaxed or more expressive during sessions?</strong></p><blockquote>I love this question, because I think it’s so important. I’ll double-down on what I said earlier about using the initial intro to build a rapport. I like to ask them questions around the basic questions to get them to open up a little, then make sure to empathize and relate. For example, I might ask someone, “what’s your role?” and they might respond, “I’m the VP of Product.” A good follow-up could be, “How did you get to the role you’re in?” or, “How do you like that role?”—any number of things just a little deeper. Eventually, you might land on something you can relate to and get passionate about — at that point you don’t want to hide it, but open up and genuinely relate.</blockquote><blockquote>I think the most recent time this happened was when I was interviewing a product manager and found out she was really interested in learning how we did user research (relevant) and that’s why she signed up, and we geeked out together for a couple minutes on that. It was easy to relate and made the rest of the interview more light-hearted and effective.</blockquote><blockquote>One other thought — you won’t get through to everyone, so if it doesn’t work out, don’t sweat it too much. It’s just part of life: there’s a ton of variation among people, and you can’t build a connection with everyone. This is one of many reasons to build a diverse team that can relate to and understand more of your users in a deeper way.</blockquote><p><strong>That’s everything. Thanks again for taking the time and I’m looking forward to seeing how you continue to improve Appcues (which, full disclosure, I use and love)!</strong></p><blockquote>Thanks so much! This was fun.</blockquote><p>Need more? Follow <a href="https://medium.com/u/f9b99958ab0a">Tristan Harward</a> on Medium (or on <a href="https://twitter.com/trisweb">Twitter</a>).</p><p>As always, remember — this concept is basically an <a href="https://medium.com/userinterviews/introducing-other-side-of-the-table-8814d5950610">experiment</a> for us at <a href="https://www.userinterviews.com/">User Interviews</a> to have some fun with our users. If you have feedback, questions you’d like us to ask, or people you think we should interview — let us know! It’d be awesome to hear how we can make it better.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fa01ceb%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fa01ceb%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/667eddcc0451be5738f6151fdd90cbf6/href">https://medium.com/media/667eddcc0451be5738f6151fdd90cbf6/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb859e91f727" width="1" height="1" alt=""><hr><p><a href="https://medium.com/userinterviews/designing-for-your-users-users-bb859e91f727">Designing for your user’s users</a> was originally published in <a href="https://medium.com/userinterviews">User Interviews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Geordie Kaytes is on the other side of the table]]></title>
            <link>https://medium.com/userinterviews/geordie-kaytes-is-on-the-other-side-of-the-table-755a3309018d?source=rss-e1c995cbc521------2</link>
            <guid isPermaLink="false">https://medium.com/p/755a3309018d</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[JH Forster]]></dc:creator>
            <pubDate>Wed, 16 Aug 2017 17:07:42 GMT</pubDate>
            <atom:updated>2017-08-16T18:55:19.832Z</atom:updated>
            <content:encoded><![CDATA[<p>For our first installation, we’re checking in with the founder of <a href="https://www.heroicteam.com/">Heroic</a></p><p><em>“Other side of the table” is a series by </em><a href="https://www.userinterviews.com/"><em>User Interviews</em></a><em>. This week we’re featuring one of our favorite design strategists, </em><a href="https://medium.com/u/a26d053347da">Geordie Kaytes</a><em>, who has done a little bit of everything in his career. He has just embarked on a new venture to help organizations manage the difficult transition of becoming more design driven.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/211/1*9I_GDb_XbdWNGfRVdBDjcg@2x.jpeg" /><figcaption>Geordie Kaytes, founder of Heroic</figcaption></figure><p><strong>Let’s get started with the basics, can you tell us a bit about yourself? Where you live, hobbies, family, etc.</strong></p><blockquote>I live in Salem, MA with my wife Janna and dog Opie, who is currently sitting on my feet. We spend most of our free time exploring the North Shore and going to events where we’re the youngest people there by 40 years.</blockquote><p><strong>What’s your current role and how did you get there?</strong></p><blockquote>I’ve recently started a new company called <a href="https://www.heroicteam.com/">Heroic</a>, where we’re helping companies make the big organizational changes needed to become truly design-driven. Up until recently, I was Director of Strategy at Fresh Tilled Soil, a UX design firm in Watertown, MA. Think of Heroic as “teaching you to fish”, and Fresh Tilled Soil as “serving you the sushi”. Each is valuable in different ways, but at this point in my career I’m more interested in creating permanent change at the company level than I am in directly designing more digital products.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XrkHRQgh9RDkgq32mkJ08A.png" /><figcaption><a href="https://www.heroicteam.com/">https://www.heroicteam.com/</a></figcaption></figure><p><strong>Switching gears a bit — what’s the best random thing you’ve found on the internet recently (preferably with links)?</strong></p><blockquote>My favorite tech analyst recently posted a map of the best place to watch the eclipse from a Waffle House: <a href="https://twitter.com/CBinsights/status/896763220509249536">https://twitter.com/CBinsights/status/896763220509249536</a></blockquote><p><strong>And what’s your most useless skill?</strong></p><blockquote><a href="https://en.wikipedia.org/wiki/Circular_breathing">Circular breathing</a>.</blockquote><p><strong>Alright, let’s get into it — what is your favorite “war story” from a user research session you were involved in?</strong></p><blockquote>We were doing in-lab user testing for the Logan Airport website, and one of our testers asked to use the bathroom. While she was out of our sight, she ransacked the office kitchen and took all the snacks.</blockquote><p><strong>There has been a big surge in “design thinking” recently, how would you like to see that trend continue to evolve?</strong></p><blockquote>The first big shift was Agile, where we admitted that we don’t know what the solution looks like until we’ve tried to build it. We’re now trying to layer on Design Thinking, where we admit that we don’t even know what the PROBLEM looks like. I fear that we’ll go down the same cargo-cult path Agile did, where it became highly systematized and the true precepts were forgotten.</blockquote><blockquote>At its best, “design thinking” is about realizing that we designers don’t have all the answers. It takes a lot of confidence and maturity to admit that, and I don’t think most companies are there yet. It also requires a major shift in mentality, which isn’t going to happen on its own. That’s one of the big reasons I started Heroic — not to hit people over the head with “you should be doing design thinking”, but to actually plan that organizational transformation for them, and help them execute on it.</blockquote><p><strong>In what ways do you deviate from the conventional wisdom around user research?</strong></p><blockquote>You’re supposed to start with broad, exploratory ethnography and contextual inquiry to build up a sense of the user’s goals and activities, then use that to inform your design ideation. I don’t love this rule. I feel like I get a lot more out of the interview if it’s based on discussing some kind of design artifact, no matter how wrong or off-base that artifact is.</blockquote><blockquote>So, for early-stage interviews, I generally put together some potential design solutions based on my limited understanding of the issue at hand. People LOVE telling you that you’re wrong, that you don’t understand, that this stupid thing you’ve made could never work. Those are the best conversations, because they let you really drill down to, “well, why not? What am I missing?” You get a lot of insights that way, because people don’t really know what is obvious about their experiences and what isn’t.</blockquote><p><strong>What do you think is the biggest mistake people make when approaching user research?</strong></p><blockquote>It takes a lot of training to suppress the instinct to “sell” your company’s solution or point of view during a user research session — especially in a startup, where you are so immersed in your vision &amp; elevator pitch that it’s hard to avoid uncorking it in the direction of your interviewee. This is why startup CEOs are the WORST at conducting user research. They just believe too hard. They should listen to every research session, but shouldn’t conduct them.</blockquote><p><strong>After years of doing user research, what is biggest lesson you’ve learned? The type of thing you wish someone had told you about when you were getting started.</strong></p><blockquote>Be smart about your panels. One time we almost shut down a product build because users kept hating on it during testing. Reviewing our recruiting demographics, it turned out that almost all the testers’ profiles matched a persona type that we had already identified as unlikely to find value in the product. We wanted to test with a few of these people to validate that assumption, but because we weren’t careful about quotas, we ended up with way too many of them.</blockquote><p><strong>Let’s wrap up with some quick hits. How do you like to prep right before sitting down with a user for a research session? Any habits that you find effective?</strong></p><blockquote>Nothing crazy. Bio break. Water. Clear throat. Review facilitator guide. Make sure video conferencing software works.</blockquote><p><strong>What tools do you use during sessions? For interview guides, notes, recording, prototypes, etc.</strong></p><blockquote>We use <a href="https://zoom.us/">Zoom</a> for conferencing and recording. For interview guides and notes, we run everything off Google Docs. We use Google Sheets to organize recruiting.</blockquote><p><strong>Are there any tricks you use to make participants feel relaxed or more expressive during sessions?</strong></p><blockquote><a href="http://www.betaboston.com/news/2015/08/28/user-testing-that-mixes-cocktails-and-coding/">Just the usual</a>.</blockquote><blockquote>Otherwise, nothing too special. Remind them that we’re testing the product, not them, and that there are no wrong answers. I like to say that they’re “doing us a huge favor by helping us find issues now when they’re cheap to fix.” I even say this when the issues AREN’T cheap to fix, because at least it’s better to know about them!</blockquote><p><strong>How do you and your team document and share the insights you collect from user research?</strong></p><blockquote>We usually have the research recordings transcribed and pull out key quotes. Since we’re a small team, we don’t have a huge need to socialize &amp; formalize the findings — basically everyone involved in the product design can listen to or read the interviews directly, and probably should.</blockquote><p><strong>That’s everything. Thanks again for taking the time and hope you keep crushing it at Heroic!</strong></p><blockquote>Thanks — this was fun!</blockquote><p>Need more? Follow <a href="https://medium.com/u/a26d053347da">Geordie Kaytes</a> on Medium (or on T<a href="https://twitter.com/didgeoridoo">witter</a>) and check out his <a href="https://www.heroicteam.com/">company</a>.</p><p>Lastly, this concept is basically an <a href="https://medium.com/userinterviews/introducing-other-side-of-the-table-8814d5950610">experiment</a> for us at <a href="https://www.userinterviews.com/">User Interviews</a> to have some fun with our users. If you have feedback, questions you’d like us to ask, or people you think we should interview — let us know! It’d be awesome to hear how we can make it better.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fa01ceb%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fa01ceb%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/667eddcc0451be5738f6151fdd90cbf6/href">https://medium.com/media/667eddcc0451be5738f6151fdd90cbf6/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=755a3309018d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/userinterviews/geordie-kaytes-is-on-the-other-side-of-the-table-755a3309018d">Geordie Kaytes is on the other side of the table</a> was originally published in <a href="https://medium.com/userinterviews">User Interviews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing “Other side of the table”]]></title>
            <link>https://medium.com/userinterviews/introducing-other-side-of-the-table-8814d5950610?source=rss-e1c995cbc521------2</link>
            <guid isPermaLink="false">https://medium.com/p/8814d5950610</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[JH Forster]]></dc:creator>
            <pubDate>Wed, 16 Aug 2017 01:52:38 GMT</pubDate>
            <atom:updated>2017-08-16T01:52:54.219Z</atom:updated>
            <content:encoded><![CDATA[<p>Our new series to highlight our favorite design thinkers and learn about how they approach user research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X94hKI44tA5qtLlCIf_K8Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/oKlhoijT2JM?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Breather</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>tl;dr</strong></h3><p>We’ve decide to try out a new experiment (feedback welcome!). Every week or so, we’re going to interview someone we respect and admire to hear their thoughts about user research. We’ll publish the conversation here on Medium so we can all learn from one another (tbd if we will all sing kumbaya together as well).</p><p>We’re calling this series the “<strong>Other side of the table.</strong>” Sign up below if you’d like to be notified about new interviews.</p><h3>more verbose context</h3><p>All of us who work at <a href="https://www.userinterviews.com/">User Interviews</a> believe in the ability of conversations to fuel positive change. <em>Hopefully that’s kind of obvious</em>. We don’t head off to work every day to make it easier and more affordable to connect to the exact right participant whenever you need for just any old reason…</p><p>Anyways, it dawned on us recently that we’re fortunate to be in kind of a unique position. Our customers basically give us access to a huge network of design thinking leaders from the best tech companies, design agencies, and product consultancies in the world.</p><p>So we wanted to see if we could do our small part to help give back to that community of users. And we figured — what better what to do that than interviewing them about their own thoughts on user research?</p><p>Plus, if we’re being totally honest, it sounded fun to flip the script on people who are usually facilitating interviews and turning them into the interviewee instead. As in “we’re putting Larry King on the <em>other side of the table</em>” (a touch cheesy <em>and </em>a dated reference, we know).</p><p>We’ll learn as we go but we’re hoping each interview will be as unique as the person answering the questions. Maybe some people will want to discuss how they win over skeptics on the benefits of qualitative research and others will get into the nitty gritty around their favorite tools and apps to use to facilitate remote sessions. We’ll see!</p><p>If nothing else, it’s always fun to share user research war stories with other people who can relate since we’ve all had a session or two where things went a little off the rails…</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fa01ceb%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fa01ceb%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/667eddcc0451be5738f6151fdd90cbf6/href">https://medium.com/media/667eddcc0451be5738f6151fdd90cbf6/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8814d5950610" width="1" height="1" alt=""><hr><p><a href="https://medium.com/userinterviews/introducing-other-side-of-the-table-8814d5950610">Introducing “Other side of the table”</a> was originally published in <a href="https://medium.com/userinterviews">User Interviews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A few reflections on my first month leading a Product org]]></title>
            <link>https://medium.com/@jhforster/a-few-reflections-on-my-first-month-leading-a-product-org-5d406c8447db?source=rss-e1c995cbc521------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d406c8447db</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[JH Forster]]></dc:creator>
            <pubDate>Fri, 21 Jul 2017 16:27:36 GMT</pubDate>
            <atom:updated>2017-07-21T17:56:39.415Z</atom:updated>
            <content:encoded><![CDATA[<p>(Or the advice I wish someone had shared with me ahead of time)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jXfjzPW18mXpJbma2RN_pw.jpeg" /><figcaption>A picture I took in Acadia National Park that felt appropriate</figcaption></figure><p>I joined a startup, <a href="https://www.userinterviews.com/">User Interviews</a>, as the VP of Product in mid-June. Coincidentally, I had also been reading <a href="https://www.amazon.com/Product-Leadership-Managers-Products-Successful-ebook/dp/B07285Z141/ref=sr_1_1?ie=UTF8&amp;qid=1500573900&amp;sr=8-1">Product Leadership</a> by <a href="https://medium.com/u/3972c26f38bd">Martin Eriksson</a>, <a href="https://medium.com/u/8b1bfe45609e">Richard Banfield</a>, and <a href="https://medium.com/u/bec2aaf72f28">Nate Walkingshaw</a> at the time. This fortuitous combination led to a lot of insightful self reflection as I was getting up to speed as the first dedicated Product hire at the company. In the spirit of <a href="https://medium.com/u/953c6fa40696">Austin Kleon</a>’s urge to “<a href="https://www.amazon.com/Show-Your-Work-Austin-Kleon/dp/076117897X/ref=sr_1_1?ie=UTF8&amp;qid=1500575544&amp;sr=8-1">Show Your Work!</a>” (which I also found inspiring) I wanted to document and share the lessons I’ve taken away from the experience thus far.</p><p><strong>Immerse yourself in everything… <em>but</em> don’t try to do everything</strong></p><p>To be effective in a Product role, you need to be able to consume a fire hose of information. You need to be able to take inputs from all possible areas — customers, prospects, design, engineering, sales, marketing, competitors, adjacent industries, consumer trends, etc. — and somehow connect the right dots to find the opportunities worth pursuing.</p><p>To be effective in a Product role, you need to be able to focus. You need to be deliberate about what the team is tackling at any given point in time and ruthlessly ignore distractions. You know your team is most effective when you’re all pulling in the same direction towards a specific, measurable goal.</p><p>This is why onboarding can be difficult for Product hires. I deliberately tried to expose myself to all parts of the business as quickly as possible. I wanted to know the fabric of the organization and how all the various threads connected. And don’t be mistaken, this was an effective approach. The challenge with this approach, however, is that you’re seeing a multitude of things for the first time with fresh eyes. For Product thinkers this inevitably means that you’re seeing opportunities everywhere you look and starting to be overwhelmed by your own ideation.</p><p>In order to avoid being paralyzed with ideas (and perhaps by how much work lays ahead), let me refer you to the next point.</p><p><strong>Be opinionated… <em>but</em> flexible</strong></p><p>Once you’re able to form relatively cohesive thoughts on the product — start sharing them. During my career, I’ve found that sharing your thoughts before they are “ready” is a great way to build a collaborative, trusting environment. Plus, c’mon, if you’re reading this then you’re familiar with the latest in design thinking, lean methodologies, and all of that. Rapid iteration is your friend, <em>especially </em>when it comes to your own emerging perspective on a product.</p><p>My approach to this was to start a document where I could store all my emerging opinions and ideas as I had them. The initial goal was to have a reference for myself. Pretty quickly, I was able to refine this into a <em>somewhat</em> coherent set of ideas that I could easily share with others, which I did.</p><p>This was uncomfortable. At that point, I had been at the company for less than two weeks in a role where I was being tasked with leading and building the Product function. I felt pressure to come across as impressive and make a good early impression. Despite that, I knew the benefits of establishing the right working style were more important than my ego. So I shared the document in all its rough draft glory with the co-founders with the following preface.</p><p><em>Disclaimer — I’m deliberately sharing an early and rough draft on my emerging product thoughts because it should accelerate our thinking and alignment here. There are undoubtedly bad ideas included below. That’s okay — just explain to me what I’m overlooking. The more debates we can have and items we can align on before any of these ideas go any further, the better.</em></p><p>My rationale for doing this was simple. I knew that the people who had dedicated themselves to building this company for the past 2 years were going to be the thought partners I needed. It was hugely helpful. They quickly pointed out dynamics I was overlooking, suggested alternatives that might be easier to pursue, shared customer feedback I hadn’t heard, and started adding their own thoughts to the document to give me a richer perspective on their thinking.</p><p>The alternative of arrogantly working in a silo to polish my nascent thoughts might have felt productive but would have ultimately backfired.</p><p><strong>Me:</strong> <em>“Here is a slick presentation of an idea I’ve overworked and I’m now presenting with unfounded confidence.”</em><br><strong>Them:</strong> <em>“Yea, we tried that 6 months ago. It was a complete flop.”</em></p><p>Don’t fall into that trap. Remember, you’re new. A learning curve is expected. Just be humble about it and do everything within your power to accelerate it.</p><p>And despite being new, you can still do the following.</p><p><strong>Find ways to add value immediately… <em>but</em> not at the expense of longer term thinking</strong></p><p>At an early stage company, simply being another pair of hands to do work is materially valuable. Leverage that. Identify ways to be helpful from the start. Maybe you take over testing the new feature that was already being developed. Or facilitate the logistics of an upcoming sales call. Or organize the customer feedback they’ve been collecting. Trust me — there is plenty you can do to be helpful that will be directly relevant to your role.</p><p>In my case, I took over some analytics that needed to be run, made introductions to people in my network who might be target customers, and made a pull request to add Google Tag Manager to the site. Nothing earth shattering but important tasks nonetheless.</p><p>That said, don’t lose sight of the fact you’re ultimate ability to add value hinges on big picture thinking. The roadmap you create and priorities you set are the levers that will move the organization forward in a significant way. Be deliberate about finding a balance and setting boundaries. You were brought in to establish for the vision for the product, not to be an intern.</p><p>Without an established vision, you’ll be making reactive decisions instead of strategic decisions. Be conscious to regularly pull your head up to avoid only dealing with urgent day to day issues.</p><p>I found there are plenty of things you can do to help yourself manage that balance.</p><p><strong>Add process / structure… <em>but</em> only where it is valuable</strong></p><p>Look, I get it, nobody wants to be the person to come into a small organization and immediately start scheduling meetings and adding a ton of process. So don’t be that person.</p><p>But there is no reason to be process-phobic either. One of the most valuable things I did was setting up a weekly roadmap review with the co-founders. This forces me to synthesize and refine my big picture thinking every single week. It also ensures they’re engaging with me in the most valuable way possible— “what customer problem should we be solving next?”</p><p>We’ve already iterated on the format for these discussions a few times and started to land on a template for tracking new ideas in a consistent way. And it is letting us get ahead on the solutions which will require more research. We’re still in the early days here but we can already feel our sprints becoming more focused as a result of this process.</p><p>Just don’t get carried away. Remember, you were likely compelled to join the company <em>because </em>they’ve been successful without you around. You don’t need to mess with things that are already working effectively. Things will evolve anyways as the company continues to grow and you’ll have an outsized impact on that evolution so don’t make the mistake of thinking things will be set in stone if you don’t change them right away.</p><p>This type of stuff can rock the boat a bit because you’re starting to assert how you engage with the rest of the organization, which means this last point is perhaps the most important.</p><p><strong>Be proactive about establishing your role… <em>by</em> having candid conversations</strong></p><p>If you’re the first product hire in an organization then it means there isn’t an established product playbook.</p><p><strong>Remember</strong>— <em>that’s why it is exciting</em>.</p><p>But that’s also why it requires work. You need to actively manage the situation and make sure everyone in the organization is comfortable discussing your role and providing constructive feedback on how it’s evolving. Your ability to succeed is positively correlated to the frequency and honesty of these conversations. It is no different than the success of the product itself and the dependence on regular customer feedback.</p><p>I actively looked for interactions that, at the least, warranted a “hey, is that how we want this to work long term?” type of exchange. I found a simple question along those lines naturally prompted a productive conversation about roles and responsibilities while there was a recent example for everyone to consider. Sometimes we aligned over a few quick emails and other times we agreed to keep monitoring things and discussing it.</p><p>We’re starting to align ahead of time on the design expectations of a given feature so I have autonomy to make the day to day decisions while it is being implemented. A small tweak, but one that has increased clarity and made us a bit more effective.</p><p><strong>Anyways, that’s all I got… I’m sure I’ll learn a bunch more as more time passes!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d406c8447db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Product Manager? What is that?”]]></title>
            <link>https://medium.com/@jhforster/product-manager-what-is-that-8d9861c4af22?source=rss-e1c995cbc521------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d9861c4af22</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[JH Forster]]></dc:creator>
            <pubDate>Tue, 06 Jun 2017 22:08:06 GMT</pubDate>
            <atom:updated>2017-06-06T22:16:22.250Z</atom:updated>
            <content:encoded><![CDATA[<p>aka let’s see if I can articulate what I do for a living…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1N1OlNxjofKU5AkO6URPKQ.jpeg" /><figcaption>photo credit <a href="https://unsplash.com/search/road-trip?photo=0iLl1Qgxz64">Jaromir Kavan</a> via unsplash</figcaption></figure><p>Let’s start with a confession — I never quite know how to explain to people what I do as a software Product Manager. Well, don’t get me wrong, I can babble buzzwords and jargon from job descriptions until the other person gets bored. I know how to give <em>that</em> answer.</p><p>But in terms of thoughtfully explaining it to someone if they’ve never worked for a technology company and had a chance to see someone in the role day to day then it can be hard to think of an appropriate analogy. Especially if you’re also trying to provide insight into what’s required to do the job well.</p><p>The analogy I’m most fond of relies on setting up a slightly absurd premise around a hypothetical road trip. It seemed like it was time to flesh it out fully and see if other people found it helpful. So without further ado…</p><p>Imagine you’re in a car with a few friends — Doug the Designer and Erin the Engineer — and you know you need to head from the East Coast to the West Coast. Except you have little money, no GPS, do not know the exact destination, and there is no specific deadline for your arrival but you know it’d benefit you to get there in an expedient manner. Finally, let’s assume the car runs okay but it could use a fair bit of work. How do you get started?</p><p>Well, Erin is focused on evaluating improvements or making repairs to the car. Doug has thrown himself into iterating on possible routes, talking to people every time we stop to get feedback, and generally trying to help find clarity on where you need to go. It looks like you’re the driver of this grand adventure. Congratulations — you’re going to learn what it is like to be a PM.</p><p>Now, don’t get too excited. <em>You’re not in charge.</em> This simply means there are going to be a lot of inputs on this trip and someone needs to be responsible for making decisions.</p><p>I realize those statements seem to contradict one another. I’ll try to explain. You’re empowered to make decisions because people are letting you make decisions. This road trip is a team endeavor and everyone has a job. You’re job happens to be “make decisions” but don’t start thinking it’s more important than the other jobs. All of the jobs need to be done well for this trip to be successful.</p><p>But how do you know if you’re doing your job well? For starters, you don’t have to worry about making the “correct” decision every time. Remember, this is a world of imperfect information informing a near infinite set of options — there won’t be an objectively “correct” decision in that atmosphere. This isn’t a math problem set.</p><p>But you will need to exhibit “effective” decision making. I’ll explain what I mean but, first, let’s look at some of the types of decisions you might be faced with on this road trip.</p><p><em>The windshield wipers have broken unexpectedly but there is no rain in the forecast and there is no traffic on an oft congested road. When do you pull over to have them repaired?</em></p><p><em>(unexpected bugs in your software that are not yet affecting the business)</em></p><p><em>The person who gave you the last set of directions said it was “definitely Exit 22… or 23” that you needed to take. Do you stop to find someone else to ask to for confirmation or do you keep going with your best guess since both exits are going in the right ultimate direction?</em></p><p><em>(the team has come up with two interesting concepts to solve a problem for users)</em></p><p><em>Half way across the country, you come across a great deal for a used trailer, which would allow you to haul more supplies and be more comfortable in the car, but to use it you’d have to completely replace the rear bumper and install a trailer hitch over the course of a few days. Is this a good time for the investment or do you press on without it?</em></p><p><em>(the product has matured but you’re starting to feel the pain of earlier tech debt)</em></p><p>So what constitutes “effective” decision making in these examples? Erin thinks the windshield wipers need to be fixed asap and Doug is indifferent and so on. On an individual basis, it might seem difficult to evaluate each decision and it is! How are you supposed to know how you’re doing as the driver?</p><p>Simple, you don’t have to evaluate each decision. You need to periodically answer two broader questions.</p><p><em>Are we still heading the in the right general direction at a rate that is faster than our comfort level?</em></p><p><em>Are people still excited about this journey and motivated to continue?</em></p><p><strong>That’s what I do as a Product Manager and what you’re doing as the driver on a fictitious road trip — find ways to keep moving quickly in the right direction with a motivated team. That’s the crux of it.</strong></p><p>It’s not easy but it’s straightforward.</p><p>These two questions happen to be easier to measure across a collection of decisions than they are on individual decisions. That’s okay. In fact, this is a good thing as measuring every single decision is exhausting and time consuming. Don’t bother.</p><p>Further complicating the evaluation of individual decisions is the fact some “effective” decisions will inevitably put the group’s success above a particular team member’s point of view or interests. If you’re doing your job well then this won’t be a surprise. You’ll know when making the decision that it’s going to bother Doug, so getting immediate feedback from Doug on that specific decision isn’t adding a lot of value in the moment (though speaking with him 1 on 1 to explain your rationale is valuable). Instead, having Doug reflect on how things have been going in 2–3 weeks when there are more decisions and data points for him to consider will yield a much sharper perspective on how you’re doing.</p><p>But you don’t have to worry about these complexities.</p><p>Simply asking a team to report how happy they are with the progress made over some recent time period and how motivated they are at the moment and you’ll get a quick and reliable assessment of your decision making.</p><p>This is why a successful PM needs to be an “effective” decision maker (going in the right direction) and skilled at team management (keeping people motivated).</p><p>Those are the two most important aspects of the job in my opinion. It happens those two things are a bit nebulous and highly contextual hence why I contrived this whole example. To put it in road trip terms — are you making good time on the trip and does everyone still want to be in the car?</p><p>Now, don’t get me wrong. A successful PM will have a well rounded skill set outside of these two attributes. Relevant domain expertise is a huge advantage (i.e. knowing how to drive a car). Some level of proficiency within design and technical areas will make you more flexible in how you can help the team (i.e. being able to change a tire or read a map). Strong relationships will all parts of your organization will allow you to connect dots you might otherwise miss (i.e. getting honest input from people outside the car). Attention to detail, good communication skills, etc. — the list is long.</p><p>Anyways, enjoy your respective road trips and I hope you trust your driver.</p><p><em>P.S. — This analogy is a work in progress. Let me know what you think! I’d also be curious how people might extend it to further capture other aspects of being a PM for a software company.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d9861c4af22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My year in reading — 2016]]></title>
            <link>https://medium.com/@jhforster/my-year-in-reading-2016-ee2b4286b47b?source=rss-e1c995cbc521------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee2b4286b47b</guid>
            <category><![CDATA[goodreads]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[running]]></category>
            <category><![CDATA[2016]]></category>
            <dc:creator><![CDATA[JH Forster]]></dc:creator>
            <pubDate>Sun, 08 Jan 2017 02:09:12 GMT</pubDate>
            <atom:updated>2017-03-22T13:27:44.523Z</atom:updated>
            <content:encoded><![CDATA[<p>And other assorted ramblings.</p><p>I managed to read more in 2016 than I ever have before in a single year. Hard to say <em>exactly</em> how this happened but there seem to be a handful of factors. For one, I’ve simply rediscovered (or maybe discovered?) how much I enjoy reading over the past few years so, in many respects, this year was a continuation of that trend. I also consciously set a goal on Goodreads at the beginning of the year. The goal was arbitrary (35 books seemed good?) but I definitely found it motivating throughout the year. Perhaps the biggest factor was a logistical one. My wife and I moved into our first home in May and suddenly I had an hour a day on a train while I commuted. The train rides weren’t always productive but, even still, that’s a lot of newfound time well suited for reading.</p><p>There were also two subtler changes in my mentality towards reading. In retrospect, these two small things were meaningful. It turns out I had a few mental blocks that were unnecessarily constraining how I approached reading.</p><p>First, I discovered it was <em>okay</em> to read more than 1 book at a time. Who knew? This never seemed like a reasonable idea to me before and I’m not sure why. I keep up with multiple TV shows simultaneously, read a variety of articles throughout a day, jump between projects at work, etc. But for some reason, I felt required to finish one before I started another. The flaw in this thinking is that what I want to read in a given situation varies. i.e. I’m not exactly excited to continue reading a productivity or management book while I’m in bed before sleeping but I’d be happy to jump back into an engaging story. By reading 2–3 books of varying genres and styles at the same time, I always had something that suited my mood when I found myself with time to read.</p><p>Second, apparently it is okay to read for short bursts. I viewed reading as an activity where I needed to set aside 20 or 30 minutes where I’m able to start and stop at natural points (like the end of a chapter) or it’s not worth it. So if I found myself with 5 spare minutes, it never occurred to me to read a few pages. Changing my thinking here led to two positive outcomes. One is obvious — I suddenly had a lot more windows in my day where I felt like reading. The second is more subtle — by reading a few pages and abruptly cutting it off when I ran out of time, I found myself eager to get back to the book to finish whatever plot line or thought I had abandoned. It was like creating mini cliff hangers for myself.</p><p>Anyways, here is a rapid fire assessment of the books I read this year. Listed by the rating I left on Goodreads after finishing it (which I generally still agree with now). <a href="https://www.goodreads.com/user/year_in_books/2016/2591452">A more visual summary can be found here.</a></p><h3>5 of 5 stars</h3><p><strong>Bowerman and the Men of Oregon: The Story of Oregon’s Legendary Coach and Nike’s Co-founder</strong><br><em>Moore, Kenny</em><br>Full disclosure: I find the story of Prefontaine and the somewhat related founding of Nike fascinating. Regardless, Bowerman was an eccentric guy with his own code and had a lot of success on his own terms.</p><p><strong>The pmarca blog Archives</strong><br><em>Andreessen, Marc</em><br>This is geared a bit more towards someone interested in starting company but still very interesting to anyone working in the tech industry, especially at a start-up. It covers an impressive range of topics and gets to important insights in a succinct way.</p><p><strong>Creativity, Inc.: Overcoming the Unseen Forces That Stand in the Way of True Inspiration</strong><br><em>Catmull, Ed</em><br>It turns out a perceptive business leader surrounded by excellent story tellers can put together a great read… It teaches you about management, leadership, and creativity in a way that’s compelling because it grabs your emotional attention.</p><p><strong>Deep Work: Rules for Focused Success in a Distracted World</strong><br><em>Newport, Cal</em><br>Very, very thought provoking. I need to find ways to apply more of the thinking there. It is perhaps a bit dramatic and over the top at times but does a good job making the overall point.</p><p><strong>Player Piano</strong><br><em>Vonnegut, Kurt</em><br>This book could (should?) be an episode of Black Mirror. A good reminder we should make sure technology changes society for the better.</p><p><strong>Don’t Make Me Think, Revisited: A Common Sense Approach to Web Usability</strong><br><em>Krug, Steve</em><br>Great job of outlining general principles without being so specific that it becomes dated.</p><p><strong>The Little Book of Talent: 52 Tips for Improving Your Skills</strong><br><em>Coyle, Daniel</em><br>Honestly — hard to say why I gave this 5 stars as I can’t explicitly recall any of the specific tips now but I enjoyed the outline this provided at the time. I’ll probably re-read it since it is a quick read and obviously the tips resonated with me as I was consuming it.</p><p><strong>Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days</strong><br><em>Knapp, Jake</em><br>Great outline of the Google Ventures approach to quickly prototyping ideas and it is full of wise suggestions, interesting examples, and specific advice.</p><p><strong>High Output Management</strong><br><em>Grove, Andrew S.</em><br>I went through a really well designed 1.5 year long course called “Manager Development Program” offered by former employer Vistaprint. It helped me tremendously as I began managing direct reports for the first time. To take nothing away from that program, I think reading this book alone could have delivered a majority of the same value. It is that good.</p><h3>4 of 5 stars</h3><p><strong>A Man Without a Country</strong><br><em>Vonnegut, Kurt</em><br>This was a timely read. I read it a little after Trump won the election and the mix of dark humor and cynicism here was comforting. Probably not the best starting point if you’re new to Vonnegut’s writing but it scratched an itch I needed scratched.</p><p><strong>Welcome to the Monkey House</strong><br><em>Vonnegut, Kurt</em><br>Fun collection of short stories from my favorite novelist.</p><p><strong>The Last Lecture</strong><br><em>Pausch, Randy</em><br>Hard to critique this book. It is inspiring how admirably he and his family handled such a difficult situation. The deep, dark cynical part of me couldn’t help but read it from the perspective that it was written for his kids for their emotional and financial benefit.</p><p><strong>Racing the Rain</strong><br><em>Parker Jr., John L.</em><br>This is the prologue to “Once a Runner” which is an amazing read if you have any connection to cross-country or track. Start there. If you enjoy the character Queston Cassisy then this is also worth a read.</p><p><strong>Again to Carthage</strong><br><em>Parker Jr., John L.</em><br>This is the final book in the Quenton Cassidy trilogy. I’d probably say it is the second best of the bunch as it deals with some more interesting emotional arcs that the character is facing in adulthood.</p><p><strong>Anything You Want</strong><br><em>Sivers, Derek</em><br>Admittedly, I read this one because it was one of the shortest books on my “to read” list and I was running out of time to hit my goal. That said, it is a really amazing collection of approaches to life and business. It is much more thought provoking than I expected and easy to recommend given it is so to the point.</p><p><strong>The Design of Everyday Things</strong><br><em>Norman, Donald A.</em><br>Phenomenal introduction to general design principles, especially for an outsider. It significantly broadened how I view the role of design. My only criticism is that I loved the first half of the book but felt a bit less engaged by the end.</p><p><strong>Hooked: How to Build Habit-Forming Products</strong><br><em>Eyal, Nir</em><br>As I’ve thought about this book more in retrospect, I’ve soured on it a bit. The framework he has created is worth considering. The examples are compelling. I struggle with how much predictive power his framework has in reality. Hindsight bias has to be in play when retroactively pointing out why successful products were successful and shoe horning it into a framework.</p><p><strong>Influence: The Psychology of Persuasion</strong><br><em>Cialdini, Robert B.</em><br>This feels on the opposite end of the spectrum compared to a book like “Hooked” for me. It is a compilation of relevant research into a cohesive guide. It is less of “here are a bunch of theories I have applied to well known examples” and more of “here is a thematic set of research findings that you may be able to adapt and apply in your own situation.”</p><p><strong>Gone Girl</strong><br><em>Flynn, Gillian</em><br>Made me realize I should sprinkle in a few more “best sellers” into my queue. It is such a different type of reading experience than most things on this list and variety is important.</p><p><strong>God Bless You, Mr. Rosewater</strong><br><em>Vonnegut, Kurt</em><br>I’m actually note sure how to concisely describe my thoughts on this book. It touches on wealth and society’s expectations for people in a way that feels more relevant in our current culture. I’ll leave it at that.</p><p><strong>Mother Night</strong><br><em>Vonnegut, Kurt</em><br>“We are what we pretend to be, so we must be careful about what we pretend to be.” It turns out that the explicitly defined moral of this story pretty much sums it up.</p><p><strong>Steal Like an Artist: 10 Things Nobody Told You About Being Creative</strong><br><em>Kleon, Austin</em><br>Kind of gimmick in terms of the format but lots of empowering thoughts urging you to find creative outlets. I find myself liking the author’s perspective on things the more I’ve followed him online.</p><p><strong>Show Your Work!: 10 Ways to Share Your Creativity and Get Discovered</strong><br><em>Kleon, Austin</em><br>Same gimmick as above but if you work in a job where your online presence could be an asset then it’s worth a read. It made me realize the importance of accumulating an authentic online representation of myself over time (perhaps why I’m writing posts such as this one…).</p><p><strong>Duel in the Sun: Alberto Salazar, Dick Beardsley, and America’s Greatest Marathon</strong><br><em>Brant, John</em><br>Despite living in Boston and having an above average interest in running, I didn’t know about this race until coming across an old article online. The fuller story explained in the book is sad but riveting.</p><p><strong>What I Talk About When I Talk About Running</strong><br><em>Murakami, Haruki</em><br>I love the way he writes and much of his thinking aligns with how I think about running myself (but articulated more beautifully).</p><p><strong>Food Rules: An Eater’s Manual</strong><br><em>Pollan, Michael</em><br>I like to play armchair nutritionist so I read a lot about it online. Nothing in here shocked me or felt like a revelation but it’s a nice, pragmatic summary in a concise format.</p><h3>3 of 5 stars</h3><p><strong>Eat That Frog!: 21 Great Ways to Stop Procrastinating and Get More Done in Less Time</strong><br><em>Tracy, Brian</em><br>Another list style book. The ideas here felt thin and uninspired.</p><p><strong>Design Sprint: A Practical Guidebook for Building Great Digital Products<br></strong><em>Banfield, Richard</em><br>This is a solid book but I had previously read Sprint by the Google Ventures team, which probably jaded my perspective. If you love design sprint methodologies then give it a read. If not, only reading Sprint will suffice — reading both within a few months felt like overkill.</p><p><strong>The Warrior Elite: The Forging of SEAL Class 228</strong><br><em>Couch, Dick</em><br>I have a small obsession with the mythology around the intensity of Navy Seal training. I enjoyed the stories in the book but something about it felt a little harder to get through than it should have.</p><p><strong>Running &amp; Being: The Total Experience</strong><br><em>Sheehan, George</em><br>For whatever reason, this just didn’t click with me the way Murakami’s reflections on running did. My guess is the writing style.</p><p><strong>Getting Things Done: The Art of Stress-Free Productivity</strong><br><em>Allen, David</em><br>I have mixed feelings on this book. Agree with getting things out of your head and written down instead. Agree with handling less than 2 minute tasks in the moment rather than processing them through some sort of to-do list. Part of me struggles with such a specific system, however. Reading this helped me in a lot of ways but I can’t say I’m a full convert.</p><p><strong>Extreme Alpinism: Climbing Light, Fast, and High</strong><br><em>Twight, Mark</em><br>Not entirely sure why I decide to read this book. For some reason, I expected it to be more about mountaineering adventures. Instead, it is pretty technical in terms of specific recommendations not relevant to me and a bit of braggadocio from the author. Not really the book’s fault but I wasn’t the right audience.</p><p><strong>The Bulletproof Diet: Lose up to a Pound a Day, Reclaim Energy and Focus, Upgrade Your Life</strong><br><em>Asprey, Dave</em><br>I agree with a lot of the general principles here — fats can be healthy, sugar intake should be limited, and intermittent fasting has lots of interesting potential. My problem with the book was the author. It feels like a pitch for his particularly brand of snake oil and unnecessarily sensationalized. There are better messengers for this type of dietary advice.</p><h3>2 of 5 stars</h3><p><strong>Pain</strong><br><em>Middleman, Dan</em><br>I found this after exhausting many of the popular running books people recommend. The story is okay. The description of some of the races and of the runners’ mentalities resonate pretty well. But it it relies on a lot of lazy tropes and cheesy phrases (i.e. “puke couch” and “hardcore” get used way too much) that don’t make it an enjoyable read.</p><h3>1 of 5 stars</h3><p><strong>Sting</strong><br><em>Brown, Sandra</em><br>This was an audiobook I listened to with my wife during a road trip. It is pure trash. I guess it was trying to be a “romantic mystery” except the romantic plot line was stupid and the mystery wasn’t interesting. We did have a lot of fun making jokes at the book’s expense, however.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee2b4286b47b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>