<?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 C. Kyle Jacobsen on Medium]]></title>
        <description><![CDATA[Stories by C. Kyle Jacobsen on Medium]]></description>
        <link>https://medium.com/@kylejacobsen?source=rss-fb8c27eef70f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*J0B5gnbw9UYuS5KIfQVJyg.png</url>
            <title>Stories by C. Kyle Jacobsen on Medium</title>
            <link>https://medium.com/@kylejacobsen?source=rss-fb8c27eef70f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:59:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kylejacobsen/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[Pay Yourself First — Finally!]]></title>
            <link>https://medium.com/@kylejacobsen/pay-yourself-first-finally-8b81f7786dd1?source=rss-fb8c27eef70f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b81f7786dd1</guid>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[payday-loans]]></category>
            <category><![CDATA[lending]]></category>
            <category><![CDATA[payroll]]></category>
            <category><![CDATA[payroll-software]]></category>
            <dc:creator><![CDATA[C. Kyle Jacobsen]]></dc:creator>
            <pubDate>Thu, 23 May 2019 17:20:06 GMT</pubDate>
            <atom:updated>2019-05-23T17:20:06.777Z</atom:updated>
            <content:encoded><![CDATA[<h3>Pay Yourself First — Finally!</h3><h3>Traditional pay cycles just don’t jibe</h3><p>So think about this, our entire lives financial know-it-alls have been advising us to <strong><em>“pay yourself first.”</em></strong></p><p>I don’t know about you, but here’s how it works for me:</p><ol><li>First, I get paid 2–3 times a month,</li><li>then, I pay my bills,</li><li>THEN, I save what I can.</li></ol><p>Yes, I know pay yourself first budgeting is a concept about focusing on saving first but this ☝ ️sure doesn’t feel like I’m actually paying myself first.</p><h3>Changing behaviors is difficult</h3><p>Changing behaviors is one of the hardest things to do in life. At one point or another each of us deal with something which forces us to consider a change and whether physical exercise, financial management or a focus on relationships, we all are all experimenting and trying to improve.</p><p>As a creator of products, I’ve learned that building a product is ultimately about changing behaviors and being successful isn’t easy. Until now, my career has been focused on micro-behaviors (think easier/better user experiences) however at Everee we are focusing on impacting one of the biggest behavioral challenges out there: financial management.</p><p><a href="https://medium.com/@kylejacobsen/pay-employees-evereeday-c3eeaa61446f">Pay Employees Evereeday!</a></p><h3>But with Everee it’s possible</h3><p>At Everee we believe employees should get paid when they want. And why not? If an employee has provided value to their employer they should have the option to get paid immediately. With Everee’s <a href="https://www.everee.com/pay-your-way/"><strong><em>Pay Your Way</em></strong></a> feature employees can choose their own payday which means you can work on Monday and get paid on Tuesday — nice, right?</p><p><a href="https://medium.com/@ron.ross/hey-dad-i-have-to-pay-rent-today-f1af95af5114">“Hey Dad…I have to pay rent today.”</a></p><p>So for me, each day I can take my daily earnings and disperse it into a variety of saving tools and it feels amazing! The days of paying others first is over. Of course, I still pay my bills on the 1st and 15th (probably like everyone else) but because I get paid every day<strong> </strong>I actually pay myself first, every day.</p><p><strong>The result: With Everee my saving habits are more aggressive than ever and this is the kind of life changing experience Everee provides.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*JMDmY_0T_3anwfaqT7IiRw.png" /></figure><h4>We’re on a mission to humanize and modernize the HR and payroll experience for small businesses. Check us out at <a href="https://www.everee.com/">everee.com</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b81f7786dd1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pay Employees Evereeday!]]></title>
            <link>https://medium.com/@kylejacobsen/pay-employees-evereeday-c3eeaa61446f?source=rss-fb8c27eef70f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3eeaa61446f</guid>
            <category><![CDATA[payday-loans]]></category>
            <category><![CDATA[payroll]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[payroll-software]]></category>
            <category><![CDATA[lending]]></category>
            <dc:creator><![CDATA[C. Kyle Jacobsen]]></dc:creator>
            <pubDate>Mon, 11 Mar 2019 17:09:33 GMT</pubDate>
            <atom:updated>2019-03-11T17:09:33.288Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong><em>There are more payday lending stores in the United States than there are McDonalds</em></strong></h3><p>Now if that stat didn’t get your attention this one should: there are also more payday lending stores than <a href="https://www.nbcnews.com/business/economy/there-are-more-payday-lenders-u-s-mcdonalds-n255156">Starbucks</a>. How, in the United States, is this possible? How is it that short-term predatory lending has sunk its teeth so deeply into our economy?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/0*2zy5bbGQ0QEzhM3a.jpg" /><figcaption>Don’t take it</figcaption></figure><p>Obviously, there are many reasons why lending, like payday / title loan and check cashing companies, exists at such a large scale — there is need. When you look at the data you will find <a href="http://press.careerbuilder.com/2017-08-24-Living-Paycheck-to-Paycheck-is-a-Way-of-Life-for-Majority-of-U-S-Workers-According-to-New-CareerBuilder-Survey">78</a>% of Americans live paycheck to paycheck. The impact: consumers spend <a href="https://www.cnbc.com/2019/03/08/when-your-car-is-a-ticket-to-short-term-cash-and-long-term-hardship.html">$30 billion</a> on these kinds of loans with rates of up to 300–400%.</p><p>Want to understand the toll it takes on the lives of those who take the money? Check out this recent Planet Money story where a nurse from Detriot talks about how she turned to a short term loan and how she ended up losing her house:</p><p><a href="https://www.npr.org/sections/money/2019/02/25/697873308/payday-loans-and-debt-traps">Payday Loans And Debt Traps</a></p><h3>Legacy payroll processing companies don’t help</h3><p>One of the primary reasons payday lending exists is because the process of payroll (businesses paying employees) is archaic and has changed little in the last 60+ years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/0*GjgsGxJy3uV_SzQ5.jpg" /><figcaption>Legacy payroll processing circa 2019 (yep, they still exist)</figcaption></figure><p>Look, they are called “payday” lending companies for a reason. Legacy payroll applications and processes (pictured above) simply take too long to get employees their money and this gap is what payday lenders prey upon.</p><blockquote>As an example, federal employees get paid every 2 weeks — and 2 weeks in arrears. This means that anyone starting a federal job will get paid every other week but they will have to wait at least 4 weeks to get their first paycheck. Why?</blockquote><p><strong><em>The payroll processing market needs a complete overhaul. </em></strong>Sure, legacy payroll providers did not create the predatory lending market but they’ve done nothing to alter the conditions which allow these lenders to thrive.</p><h3>Everee is different</h3><p>At Everee we believe employees should get paid when they want. And why not? If an employee has provided value to their employer they should have the option to get paid immediately. I mean, it’s not 1950 anymore so there’s no reason we should have to wait 2–3 weeks to get paid, right?</p><p>If we can send money immediately via apps like Venmo, PayPal, or Zelle, employers should be able to pay employees on a faster schedule. With Everee’s <a href="https://www.everee.com/pay-your-way/"><strong><em>Pay Your Way</em></strong></a> feature employees can choose their own payday. So work on Monday, get paid on Tuesday and stay away from the loan sharks (errr, payday lending store).</p><p>I realize Everee may not solve all the reasons people seek-out payday loans but we plan on giving people a better choice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zpgwqv87G2N6Ho5acusJCw.jpeg" /></figure><h4>We’re on a mission to humanize and modernize the HR and payroll experience for small businesses. Check us out at <a href="https://www.everee.com/">everee.com</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3eeaa61446f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Why and How of Creating a Product Wall]]></title>
            <link>https://medium.com/@kylejacobsen/the-why-and-how-of-creating-a-product-wall-2082ea166b8d?source=rss-fb8c27eef70f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2082ea166b8d</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[deve]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[C. Kyle Jacobsen]]></dc:creator>
            <pubDate>Wed, 31 Jan 2018 15:33:29 GMT</pubDate>
            <atom:updated>2018-02-13T02:15:27.516Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I1IIKzBRRABPeyqm85kg5A.png" /><figcaption>Derek Newbold, CTO (L) and Shaun Ritchie, CEO (R) in front of the Teem Product Wall</figcaption></figure><blockquote>“Kyle, product development is a black hole. I don’t know what is being researched, built or released.”</blockquote><p>As a product manager, this is a something I’ve heard many times throughout my career. So when I arrived at Teem in March 2017, I wasn’t surprised to hear it again. Sales, Support, CSMs, and Marketing didn’t know what was being developed and it was making it hard for them to predict and prepare. And the by-product was that others were losing confidence in product development.</p><p>Now to be fair, the product development team had previously tried using tools, like Jira, to share project status information but it wasn’t working. And let’s be honest, there just isn’t a software solution for this problem.</p><h3>So, we went analog.</h3><p>I ran to the office supply store, bought supplies and we got to work providing clarity to the entire organization. Before we get to the “how” of building a wall, let’s talk about why I recommend doing this:</p><ol><li>Transparency: Sometimes it was uncomfortable but exposing information helped us gain the trust of those who depend on your success (most notably, sales). If you are open to sharing information, you create an opportunity to have a candid dialogue with others.</li><li>Discipline: The Product Wall will keep you focused. As new ideas come up (and they do everyday) we can point to the Wall and ask, “what should we take down?” As a product leader, I love this!</li><li>Resources: If we, the product team, feel like we need to go faster we can point at the Wall and explain to the exec team that we need more resources. There really isn’t a better resource to start such a conversation.</li><li>Communication: We needed to host conversations about product development progress and the Wall is a perfect backdrop to do just this. Plus, it is interactive (anyone can look at designs) at anytime.</li><li>Readiness: This is the best part about it. As projects progress through product development, everyone else can anticipate what is coming. Development can anticipate work coming from the Product team. Support can expect changes as Development gets closer to Beta. Marketing and Sales can get ready as items near production.</li></ol><h3><strong>How we built our Product Wall at Teem</strong></h3><p>The purpose of the Product Wall at Teem is to tell a story. That story is: 1) the company vision and strategy 2) product strategy 3) who we are building for (personas) 4) what we are building (roadmap) 5) what is in research (discovery, design, test) 6) what is being built 7) what is in beta 8) what has been released. Anyone should be able to read this story from left to right / top to bottom.</p><p>We began by commandeering an area of the building which everyone had access too. We didn’t build this in an area near product development but rather, close to sales. We also selected an area which could serve as gathering place — which it ultimately did.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lxPFmoZV5vmiOJiOPf3oew.jpeg" /><figcaption>Our first company-wide product standup. Dal Adamson is using the Product Wall as our tool to communicate all the good stuff.</figcaption></figure><p>In fact, just weeks after putting up our first version of content Teem started to host town hall styles meetings with the Product Wall as a backdrop.</p><p>Our first version was really basic. We had some early stage personas (we’ve since iterated and expanded) and using a very basic board we began to describe:</p><ol><li>Build: anything the development team is actively working on (WIP). Eventually we began to post designs to accompany each sticky.</li><li>Beta: anything we are internally testing (alpha) or externally validating (beta).</li><li>Release: anything we recently released to production.</li></ol><p>This was our MVP. Later we added more detail to our Research section but this was enough to start using this new tool.</p><h4>Sidebar:</h4><p>The black horizontal line across the “Build” section (which, if you are curious, is actually electrical tape) was a critical piece early on in our Product Wall. If you look at an even earlier version of the wall (below) you will see that “Build” was loaded with a lot of stickies — 23 to be exact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*2wEtvWDJ2IQzyjpn4utXqw.png" /><figcaption>We had too much in WIP and had to reduce that!</figcaption></figure><p>Each of these large stickies represented a project and for our size of company, 23 items in WIP was insane. So, in an effort to normalize we limited the space (which explains the horizontal line) to just 7 large stickies (or 7 items in WIP). Why 7? Because it was better than 23 — there was nothing scientific about this. The result on making this decision was impactful and I’ll share that story for another day. So, by using our Product Wall we were able to visualize all the WIP and reduce the chaos everyone was struggling with. Once we got everyone comfortable with doing less that horizontal line came down.</p><p>While we were starting this project, I was meeting with the executive team to understand our company vision and strategy. I did this because we needed to find alignment between vision, strategy and work. For more on how I accomplished that check out this <a href="https://blog.prototypr.io/product-plan-my-first-90-days-at-teem-df42c48baed3">article</a>.</p><p>Eventually, we added our company vision and strategy along with our product strategy, roadmap and details about items in research which you can see below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0p9Ur2lz0fXN0lKIPdHnoQ.png" /><figcaption>Anyone can understand what Teem is about by taking a look at the Product Wall. It tells the company story from left to right / top to bottom.</figcaption></figure><h4>Sidebar:</h4><p>Adding a sticky to the Product Wall, particularly the Research section, only means that we are making a commitment to research this and nothing more. The likelihood that this project makes it to the Build phase is high but there’s always a chance that our research reveals a problem and we need to either delay or kill any intention to build.</p><h3><strong>Along the way, we began to include others!</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8ZkTfgkv13o_qcoKiqr5Lw.jpeg" /><figcaption>Harley Jessop preparing our first version of the Idea Wall.</figcaption></figure><p>If you create a Product Wall, you should expect people will ask how they can influence it and here’s my suggestion on how to do this.</p><p>Create another space nearby where anyone can add ideas, but not just any ideas. The ideas need to aligned to your company vision, strategy and product strategy. This is a great way to keep everyone focused on the vision and strategy of the company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SWU-ZFwIzFvsJqBKpDk-qQ.jpeg" /><figcaption>Our first version of the Idea Wall before others added new ideas. We had old ideas all tracked in all kinds of applications but added them here before we asked others to add ideas.</figcaption></figure><p>Getting started with this is simple but time consuming. Your product team should have some record of ideas not yet built. Expect that those ideas are spread out and in many different tools — at Teem they were in emails, Slack messages, Jira, old excel docs and verbal conversations. We (the product team) got together and transcribed everything and added them to our Idea Wall and then we asked the rest of Teem to add to it.</p><p>Then we provided instructions to everyone and asked that they share. Note that we do a bit of education on basic software development too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*IIXxHHTASgrTOpATcP_s2w.png" /></figure><p>The goal is to review the ideas with those who submit them and then agree on the relative priority together — this way we set a clear expectation of when we may do something.</p><h3><strong>Making small stickies into big stickies</strong></h3><p>The first question I always get when giving tours at Teem is how do we transition the small stickies (ideas) into big stickies (product wall). This, of course, is the prioritization process that each of us go through and to be honest — nobody has mastered this. But, it is important that you make sure everyone knows when their ideas get transferred to the Product Wall. Here’s an example of how I recently used Slack to communicate progress:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wknGfIq5vswj5oHA2ESDXw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S0UtpjFHXKAvr2yTggt4aw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1M3fNwI3WGcJccEkpDP3DA.png" /></figure><h3>Quick summary and acknowledgements</h3><p>I like to argue there is no better steward of the company’s vision and strategy than your product team. And I’ve learned that if you create a Product Wall you will find it easier to keep your company focused on the big picture and avoid distractions.</p><blockquote>If your team is in SLC and wants a tour of Teem hit me up at kyle.jacobsen@teem.com</blockquote><blockquote>Also, post your “stickies” in the form of comments below and share how you keep everyone up to date on your product development progress.</blockquote><p>Finally, I didn’t do this alone. We have an amazing product team and they each have contributed to the making this an amazing place to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SSIaOen7zVGv7ubb8tMuvA.jpeg" /><figcaption>From L to R: Deanna Walters, Dal Adamson, Kyle Jacobsen, Ingemar Wiemer, Harley Jessop and Morgan Willams</figcaption></figure><p><strong>This story is published in </strong><a href="http://blog.usejournal.com/"><strong>Noteworthy</strong></a><strong>, where 10,000+ readers come every day to learn about the people &amp; ideas shaping the products we love.</strong></p><p><a href="http://blog.usejournal.com/"><strong>Follow our publication</strong></a><strong> to see more product &amp; design stories featured by the </strong><a href="https://usejournal.com/?/utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_campaign=guest_post&amp;utm_content=kyle_jacobsen"><strong>Journal</strong></a><strong> team.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2082ea166b8d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Plan: My First 90 Days at Teem]]></title>
            <link>https://blog.prototypr.io/product-plan-my-first-90-days-at-teem-df42c48baed3?source=rss-fb8c27eef70f------2</link>
            <guid isPermaLink="false">https://medium.com/p/df42c48baed3</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[C. Kyle Jacobsen]]></dc:creator>
            <pubDate>Fri, 07 Jul 2017 14:27:13 GMT</pubDate>
            <atom:updated>2017-07-12T12:38:58.797Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7dyhwGyOe3vZBCAkQfJ9OQ.png" /></figure><p>In March of 2017 I joined <a href="http://www.teem.com/">Teem</a> to build a new product group and introduce and implement product management practices. Teem needed more predictability with their product development efforts and I committed to solving these problems. While interviewing with the executive team I proposed to understand, focus and improve <em>six main areas:</em></p><ol><li><em>Vision &amp; Strategy</em></li><li><em>Team &amp; Work Alignment</em></li><li><em>Communication</em></li><li><em>Users &amp; Personas</em></li><li><em>User Centered Design Practices</em></li><li><em>Professional Development</em></li></ol><p>The following post describes why these topics are important for all product leaders, what we achieved and the problems we faced. I also include a week-by-week account of our first 90 days so you can see how we progressed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*bGFe3K3IGKmyURY_dlVQwg.png" /></figure><h3><strong>1. Vision &amp; Strategy</strong></h3><p>This is the first thing every product leader should understand when joining a new company. What is the vision of the company and how does this translate to strategy and the product? Without this, success is impossible because you need to know what direction to take the product (where to invest). Don’t be surprised if you find there isn’t much alignment here so don’t hesitate to jump in and create something.</p><p><em>Here is what I did to learn about vision and strategy at Teem:</em></p><ol><li>I spent a week interviewing the executive team starting with the CEO. I asked each of them the same set of questions regarding vision and strategy and compared results.</li><li>I then interviewed the next level of management to compare results. No surprise really, but I found deviations from what I heard from the executive team. Just in case you are asking… yes, I did share this information with the executive team.</li><li>Next I analyzed where the development team had been investing resources. Please note that even if a team is aligned to the vision and strategy it doesn’t mean their work is aligned — more about this below.</li></ol><p>Before any product leader can make an impact, they must understand if there is a vision / strategy, if people believe in it and if they are staying <a href="https://medium.com/@kylejacobsen/staying-disciplined-e33365c10e6d">disciplined to achieve it</a>. The first two are easy, the third is incredibly hard.</p><p>In the end, we formalized our product vision (which is really a product centric view of the company vision) in Week 12.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*Xq--_oWJETdkhs0BccJ_NA.png" /></figure><h3><strong>2. Team &amp; Work Alignment</strong></h3><p>Wow, this is where all the emotions lie so trust me, there is no right way to do this but there are plenty of wrong ways. At this point I understood the vision and strategy but were we disciplined enough to achieving it? And were we aligned to make it happen?</p><p>Face it, as product leaders we are ultimately responsible to provide a product vision which aligns with the company vision (sometimes influencing the company vision) but more importantly, staying disciplined to achieve it. And before we can expect to change any aspect of team and work alignment we must realize the importance of building trust (just getting to know people). While building trust I asked a lot of questions like:</p><ol><li><em>Are teams working on the right items?</em></li><li><em>Are the right people working on these items?</em></li><li><em>Do they have the right tools?</em></li><li><em>Do they have enough people?</em></li><li><em>Are they aligned in a productive manner?</em></li><li><em>Do they have the right skills?</em></li></ol><p>At Teem we were doing a great job but needed to improve team and work alignment. So we made slight adjustments and here are some of our learnings:</p><p><strong>On team alignment:</strong> I’m going to guess that most teams are either aligned by Users/Personas or by projects. Whatever the case, you need to make sure you have the right mixture of skills, personalities and people on each team. Consider working with your development lead(s) to pull this off and expect that it’s going to take a significant amount of time.</p><p><strong>On work alignment:</strong> Consider this, identify the critical work (rely on the work you do for Vision and Strategy exercise) and share why it is critical for the company success. Ask the teams if they agree on this critical work and invite them in to discuss how they would solve these problems. I have found that asking for help and advice builds trust and makes the transition to critical work much easier.</p><p>Expect false starts. This part sucks but be ready to experience failure. People will say one thing and do another and this is probably because you haven’t done enough to gain their trust. <strong>I made this mistake</strong>. Don’t let this deter you. Get to know everyone better (especially their concerns) and work to get them aligned with the critical work items.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*lfrwjsOBHdg-ASQI6B3IaQ.png" /></figure><h3><strong>3. Communication</strong></h3><p>This is probably the easiest of the six problems to solve and it’s something you can start solving immediately. I’ve learned that a successful product team is the hub of every business and thus communication from this team is critical. Confidence in a product team is a tricky thing and poor communication will erode any confidence others have in your team.</p><p>At Teem there was a lot of talk about “black holes” regarding product development work so this is where we started our efforts. We set out to make communication simple and predictable for all of our audiences.</p><h4>Tools for communication:</h4><p>Personal plea: can we please stop trying to retro-fit tools we use to track project progress for communication purposes? Face it, if you are using Jira or Trello it’s not going to succeed.</p><p>As product leaders we should be experts at delivering great user experiences so why not apply this skill internally? True, it may be easy for <em>US</em> but what about those who need the information? At Teem we use a method which is simple and accessible at all times which is centrally located in the building and accessible to all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WsFyY4W47P_h1JMB-rXSRA.png" /><figcaption>Version 1 of our product wall (obviously some content is confidential)</figcaption></figure><h4>Cadence of communication:</h4><p>This. Is. Simple. Find a cadence for each group and stick to it. Daily, Weekly, Monthly, Quarterly — whatever works. Make it predictable for everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*wlNUm362jHWKFpD_ZRag2Q.png" /></figure><h3><strong>4. Users/Personas</strong></h3><p>The age old debate over personas is something I don’t want to hash out — not here. But let’s just all agree, our teams should have a shared understanding of the buyers and users of our product. At Teem we know who our user is but as we learned more, we realized the need to start focusing on other users.</p><p>We began by speaking with every group in our organization: marketing, sales, developers, CSMs. We talked about buyers vs users and how the user role changes based on other variables, including market size.</p><p>Once we had a basic understanding, we started talking directly to users and validating our assumptions. When we were done we complied our findings in a simple, publicly displayed document.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*UBDUpw8TIFArMyQSyWz4ug.png" /><figcaption>This is Chris, one of our users</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*neWeC4GvyuMO17_x5DX4Jg.png" /></figure><h3><strong>5. User-Centered Design Practices</strong></h3><p>Teem needed this desperately.</p><p>Simply put, this is a process by which you connect those designing and building the things with those that use the things. If done correctly, your team will be able to create a solution which will solve the major issues of the market while not over-engineering solutions.</p><p>There are many different approaches to User-Centered Design practices and they can be summed up into three basic stages:</p><p><strong>Discover</strong> or learn about the problem directly from the users, <strong>design</strong> a<strong> </strong>solution based on what you learn and <strong>test</strong> the design before you have the development team build something</p><p>To help introduce the concept of User-Centered Design practices we put up a poster explaining the process and I worked closely with the product team to implement practices supporting it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ddwz3ulP2oRe_ZD5Ss-yOw.png" /></figure><p>Looking for a solid User-Centered Design practice? I recommend checking out Nate Walkingshaw’s <a href="https://medium.com/directed-discovery/5-reasons-why-you-should-use-directed-discovery-be36caec488d">Directed Discovery</a> process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*AXJvm4X2J0Hi_UuoC5OvDQ.png" /></figure><h3><strong>6. Professional Development</strong></h3><p>Ok, this is a no brainer. We should be in the business of turning product managers into product leaders. I’m not going to spend time pretending to be the best professional development leader but I’m certainly working towards that goal! Here are two areas I plan to focus on:</p><ol><li><em>Is the product team getting better at practicing product management and UX?</em></li><li><em>Is the product team able to inspire and motivate others?</em></li></ol><p>I believe if I can get these two basic questions right, I will help this product team grow into leaders and nothing satisfies me more than helping others grow.</p><p>So my first 90 days at Teem has passed and we are off to a great start. The next 90 days will bring about a deeper and more intense focus on each of these items and mentorship for the product team.</p><p>Check out the weekly breakdown of our first 90 days (below) and a huge shout out to those who made this happen: <a href="https://medium.com/u/fd5ec2cd2ca0">dal adamson</a>, <a href="https://medium.com/u/ebf9a7d41c07">Harley Jessop</a>, Deanna Walters and Morgan Williams. Also, thanks to those who have given us this opportunity: <a href="https://medium.com/u/59b65e0c6964">Shaun Ritchie</a> and <a href="https://medium.com/u/768c1818c4c8">zach holmquist</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*p2qfBdcwiCNaPKpCjzEdaw.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df42c48baed3" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/product-plan-my-first-90-days-at-teem-df42c48baed3">Product Plan: My First 90 Days at Teem</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guide: The Process I Follow to Arrange Research Calls With Users]]></title>
            <link>https://blog.prototypr.io/guide-the-process-i-follow-to-arrange-research-calls-with-users-fd220eb3706b?source=rss-fb8c27eef70f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd220eb3706b</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[market-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[C. Kyle Jacobsen]]></dc:creator>
            <pubDate>Sun, 20 Nov 2016 18:34:28 GMT</pubDate>
            <atom:updated>2016-12-06T16:36:30.776Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m a product manager and I create software for enterprises so this means I do a lot of research. And let’s be honest, there is a ton of information you can get from inside your organization (support, sales, customer relationship teams, executives) but none is more valuable than what you learn from your users. So when fellow product managers learn that I speak with users 5–7 times a week I always get a lot of questions.</p><ul><li>How do you get permission to contact clients?</li><li>What tools do you use to make it easier?</li><li>Do you offer incentives for these users to join us?</li></ul><p>Here is my process on how I make it easy for myself while creating a nice experience for our users.</p><h4><strong>1. Compile a list of users</strong></h4><p>The people I’m contacting are actual users and I’m really fortunate because it’s all in Salesforce so pulling a list is simple. Now some of you may be asking how I got permission from our organization, namely sales, to contact users? Well, it wasn’t an easy process.</p><p>First, you need to look at it from the perspective of the sales and relationship teams. Their livelihood depends on the relationship with their clients so they need reassurance you aren’t going to mess it up. Start by targeting reps that are influencers inside those teams. You know the type, everyone looks at these individuals as thought leaders even if they aren’t an actual people manager. Take time getting to know them and explain to them who you want to speak with and why you want to speak with them. Don’t be afraid to invite them to join the calls as a silent participant. If there is one thing I hear from the user at the end of every call it is, “thanks for asking me to do this.” This influential sales rep will quickly see the value of these interactions before long they will share this with peers which will open up your opportunity for more calls.</p><p><em>Note: Don’t forget to record your calls and share them with the entire team. If you provide them [sales? coworkers? who?} with something consumable like a recorded video they are going to be throwing clients your way.</em></p><p>Now, once I have my list of users I segment it based on my needs. When I pull the initial list it’s totally random but there are times I need to talk to a specific segment of the persona. For example, users from large accounts, users from small accounts but large TAMs, mid-sized accounts or perhaps something else.</p><p>Once it is segmented I drop it into Google Sheets — you will understand why I use Google Sheets in just a few minutes.</p><h4><strong>2. Messaging matters</strong></h4><p>Next step is to create the message and believe me when I say that messaging matters. You must give users a compelling reason to join you. Let’s start with the message I’ve found that works best for my persona.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8J5Naj0uYAuudoPwhi1G1g.png" /></figure><p><strong>Subject Line</strong>. If you are like me you get all kinds of emails each week where people are asking to speak with you — most of the time they are trying to sell you something. Do what you can to avoid the style and language they use. To do this I do three things: <strong>identify the company I work for, I give them a topic and I tell them they can “speak with a product manager 1:1.”</strong> There are those who suggest you should identify yourself as a member on the research team versus the product team, presumably in an effort to not bias the potential user, but I’ve experienced a 10% improvement in recipients opening my email when I use the words “Speak 1:1 with a Product Manager” with no noticeable impact on the actual interview.</p><p><strong>The body</strong>. Keep it brief but give them a reason to join. Notice I tell them what we want to speak about. Be careful to use language they are familiar with — I know it’s obvious but don’t use project code names. Look for language your internal teams (sales, support) use because it’s likely those terms originally came from your users. Also make it clear to the user that they have a chance to help “shape the design” of the products. At Pluralsight we get such great information from our users — they are the real designers of this product and it explains why we have a world-class NPS rating.</p><p><strong>Time</strong>. This part is a lie. I tell them 30–40 minutes but it’s always 60 minutes or more. Don’t feel bad about misleading the user here because once they are on the call they will enjoy the experience.</p><p><strong>Teaser</strong>. Don’t be afraid to show a little “leg” to the recipient. Images are a quick way to connect and if they don’t like what they see then they have a reason to join a call. Make sure you don’t share the entire prototype. All they need is a little taste.</p><p><strong>Scheduling</strong>. Make it easy for them to find a time which works for their schedule. I will address this in a minute.</p><p>Finally, notice that I’m using Gmail — there is a reason for this which I’m about to address. I will also talk about the response rate I expect with this kind of message.</p><h4><strong>3. Mail merge to save time</strong></h4><p>You have your contacts and your message ready. Next up is to send the message and I recommend using a mail merge. There are many mail merge tools out there but if you are using Gmail go with Yet Another Mail Merge (YAMM). It’s a Chrome extension and so very easy. The great thing about YAMM is it provides simple reporting so you can understand how effective your message is working. Here’s an example of a report on a message I sent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*REgCJr6WkoVcBYLl1mLhgA.png" /></figure><p>Note, it also tells me the status of the email so I can re-send:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*w0TY9kb2PrwCEHufW1Xx7A.png" /></figure><p>Here is a great tutorial for getting started with YAMM:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FSzGkAQJSgJU%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DSzGkAQJSgJU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FSzGkAQJSgJU%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4f372be4c90167e0d68015647cc8e14c/href">https://medium.com/media/4f372be4c90167e0d68015647cc8e14c/href</a></iframe><h4><strong>4. Arranging a day and time</strong></h4><p>Now for my favorite part. Arranging a day and time with a client is not an easy task. There is loads of back and forth and when you are dealing with people in different time zones the conversation can last for days. I use <a href="http://calendly.com/">Calendly</a> to make this easier. It is another Google plugin and it makes the process easier. If you noticed in my sample email I share a link with the user and stated, “secure some time which fits your schedule.” When the user clicks on that link they get this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*8AgflHKlxC9NWChKYOOvMw.png" /></figure><p>From there there can select a time which works for them:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*ns9kRbqAhjgr6ZT3i3qxfw.png" /></figure><p>When someone books time I get an email notification and a calendar booking. Done. All I need to do is invite my team members and that’s it.</p><p><em>Tip: don’t forget to keep your calendar updated and set your available time. When I first started using Calendly I didn’t eat lunch the first few days because people were scheduling over my lunch hour so block your calendar accordingly.</em></p><h4><strong>5. Response rate, what to expect</strong></h4><p>Now for the numbers. With this process I get:</p><ul><li>36% email open rate</li><li>10% click on my Calendly link</li><li>6% schedule rate.</li></ul><p>Here is a simple graph of what I expect:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*DKh0ebY8ENyWNguK4cC5gQ.png" /></figure><p>Knowing this helps me be efficient with my time because if I want to talk to 20 users I need to pull a list of about 350 people. From there I send out invites 50 at a time any more would overload my schedule and I’m guessing lower my schedule rate because users would see very little availability on my schedule.</p><h4>6. Incentives</h4><p>And now for the question which I’ve never understood, “Do you offer incentives to the people you want to speak with?” No, absolutely not. Just think about how you would feel if someone was offering you something in exchange to speak with them. Would you trust them? Would this bias you in any way? Other than the chance to help us design a better experience for them I don’t offer incentives — this should be incentive enough.</p><h4>7. Preparing for the call</h4><p>Now, all I have left is to research the user and get to know a bit more about them. Here are two things I always do- and it’s kinda creepy:</p><ul><li>Check LinkedIn. I do this to understand a where they are in their career. Are they new in their career? How many jobs have they had? What does their career arc look like? Anything which can validate who I’m speaking with and how closely they are aligned with our persona.</li><li>Check their recent activity in our app. Going into the call I know what they do and how frequently they do it. Once we jump into the call I ask them questions to validate what I know and guess what? They aren’t completely truthful about their activity.</li></ul><h4>8. Tools to host the call</h4><p>This part is a bit tricky. The persona I primarily speak with is an employee at businesses. They don’t always have the opportunity to download anything because their IT security teams have locked down their laptop. So, if you want to record these calls, see the person you are speaking with or if you want to watch them interact with a prototype here are some suggestions around this:</p><ul><li>Low-fi Wireframes or Mocks: If the artifact for our call is something simple I use a regular video conferencing tool (for me, they are all the same) because we can see the user, share screens and record the call. So the day before we are scheduled to meet I update the meeting invite and add a link to the call. I also explain to the user we are going to host the meeting on a video conferencing tool and encourage them to confirm that the tool will work for them. As a courtesy I include a link for the tool’s download site like <a href="https://www.bluejeans.com/downloads">https://www.bluejeans.com/downloads</a>.</li><li>Prototype or Mocks: If the video conferencing tool doesn’t work or if the artifact is a clickable prototype I use Invision Liveshare. I like this tool because we can communicate with the user over the phone or VOIP and I can see what they are clicking on. However, this tool does not offer video nor can you record it. Even so, it’s a great tool because it doesn’t require a download and you can still get a great sense of the success of your design. And yes, I’ve tried using a video conferencing tool combined with Invision Liveshare and it was a complete disaster.</li></ul><p>There’s a definite market opportunity here and perhaps someday once of us can solve it. Until then, be creative.</p><ul><li>If this wasn’t enough and you are looking for more information on this topic check out the <a href="https://soundcloud.com/weneedanothermeeting">We Need Another Meeting!</a> podcast which I co-host with <a href="https://medium.com/@JoshJTT83">Josh Tolman</a>.</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F296027646%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fweneedanothermeeting%2Fhow-we-arrange-user-research-calls&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000196683976-2ywr7y-t500x500.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/c4c61408aafc2ed1c748a83dccb73374/href">https://medium.com/media/c4c61408aafc2ed1c748a83dccb73374/href</a></iframe><ul><li>If you are looking to continue beyond this topic I suggest this case study in <a href="https://medium.com/@kylejacobsen/if-you-aren-t-testing-your-designs-you-should-be-fired-468454524ffa#.wnoxjnkxi">design testing</a>.</li><li>Also, if you have tips, recommendations or questions share in the comments below.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd220eb3706b" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/guide-the-process-i-follow-to-arrange-research-calls-with-users-fd220eb3706b">Guide: The Process I Follow to Arrange Research Calls With Users</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Time I Tried Product Marketing for a Year — and Exited Quickly]]></title>
            <link>https://medium.com/@kylejacobsen/the-time-i-tried-product-marketing-for-a-year-and-exited-quickly-66582914131e?source=rss-fb8c27eef70f------2</link>
            <guid isPermaLink="false">https://medium.com/p/66582914131e</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[product-marketing]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[C. Kyle Jacobsen]]></dc:creator>
            <pubDate>Thu, 05 Nov 2015 16:08:16 GMT</pubDate>
            <atom:updated>2017-01-21T13:20:28.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VsnOvoi1WKo66zS6gCSSNQ.png" /></figure><p>I love to tell stories and believe me, I think I am good at it. So when I had a chance to transition from product management into product marketing I figured it would be a great fit. I was wrong.</p><p>I had been a product manager for 10 years but I never had the opportunity to work with a product marketer. What is a product marketer? Well, at the time I really didn’t know but in 2012 I took a chance to join a fast growing company. I lasted one year and here are three things I learned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*aJI6Uq4J11oeI3LkkgKCtA.png" /><figcaption><strong>“Since we have time on our hands, let me tell you a story.”</strong></figcaption></figure><h3><strong><em>1. Telling a story isn’t easy and telling someone else’s story is nearly impossible.</em></strong></h3><p>When I am building the product myself, telling the value of a product story is never easy. But now I was telling someone else’s product story and that was incredibly difficult. As a product manager I had the luxury of understanding the pains I was solving because I was speaking to users; but now I didn’t have exposure to users. So I had no context and relied on the product managers — this was hard. I desperately wanted to convey the passion of the product manager but I couldn’t because I lacked the basic empathy you gain from truly understanding the user and their problems.</p><p>As a result the content I cranked out was phony and didn’t do much to move the needle.</p><blockquote>Recommendation for product managers: You have convinced your organization to invest in product experience. Don’t fall short when it matters most; involve your product marketers in your product research. Or at the least, spend time with them explaining the pain you are trying to solve. A good product marketer is going to ask for this information anyway and if you don’t have a good story for them your investment is going to fall flat.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*DCDeU54T_Cbm6cjN4sh-Yw.png" /><figcaption><strong>First place the mask on yourself then tell others to get out of your way.</strong></figcaption></figure><h3><strong>2. Product Marketers spend a lot of time consensus building, in fact they spend too much time doing this.</strong></h3><p>Let’s be honest, people have opinions about word choice and many of those people should keep their opinions to themselves. Product marketers are the professionals who sculpt the message. They get paid for their vocabulary yet we never allow them to be creative. Instead we have others, and sales members seem to be the primary culprits, tear apart the content by nitpicking and arguing amongst themselves about proper word choice.</p><p>Look it makes sense, sales teams are pushing the collateral in front of the clients so they should share their opinion. But time and time again I ran into contention on the smallest details like, “well I find people like to talk about <strong>efficiency</strong>” versus “my clients are worried about <strong>productivity</strong>.” This meant I was constantly building consensus between team members and as a result, I found it difficult to actually care one way or the other. I just wanted the team to tell a unified story and stop worrying about the minor details.</p><p>(<em>Side note: I really wanted to sit in on sales calls but had little luck. I love sales people but they can be really territorial — and who can blame them when their clients are their livelihood</em>).</p><blockquote>Recommendation for sales leaders: If you want efficiency or productivity (take your pick) from product marketers, stay out of the way. Steer them gently but don’t pick apart their words. Give them access to clients and trust they can sculpt the perfect message. I promise, you are going to get a better story to tell.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*69_MGwyLmT15NluUQNu47A.png" /><figcaption><strong>This guy isn’t coming back.</strong></figcaption></figure><h3><strong>3. Companies do a terrible job of marketing to their existing clients.</strong></h3><p>Well, at least they do in my experience. All of the marketing budget went towards winning new clients yet nothing went towards marketing to existing clients or users. How could this be? I suppose as a product marketer it was my responsibility to keep the clients engaged but I had no tools. Instead, I was spending all my time enabling support teams and let’s face it, these teams aren’t communicating product value. Support teams were describing how to use the product, “Click here. OK now click there.”</p><p>As a product marketer I wanted to communicate value to the clients and help drive renewals but nobody in the traditional marketing team seemed to care. They were more concerned about new deals.</p><blockquote>Recommendation for marketing: throw some love over to the product marketer. They have built-in audiences who are dying for information. Don’t think your product marketer is going to be successful by emailing stupid newsletters. Nobody reads email anymore and newsletters suck.</blockquote><blockquote>Plus, we all know the cost of acquiring new customers is significantly more than retaining existing clients. Invest in user groups or user conferences. Anything!</blockquote><p>I actually learned a lot more but these were the highlights. I wasn’t good at this job but it gave me great perspective. And to all those product marketers out there… much love. You guys rock and keep fighting the fight.</p><h4>If you enjoyed this I recommend checking out my podcast episode about product marketing:</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F299204202%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fweneedanothermeeting%2Fproduct-marketing-for-product-managers&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000199738114-20jwzg-t500x500.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/07658dd27c7e93c07800d445c1acf1bc/href">https://medium.com/media/07658dd27c7e93c07800d445c1acf1bc/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66582914131e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Design Testing and Validation]]></title>
            <link>https://medium.com/@kylejacobsen/if-you-aren-t-testing-your-designs-you-should-be-fired-468454524ffa?source=rss-fb8c27eef70f------2</link>
            <guid isPermaLink="false">https://medium.com/p/468454524ffa</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[C. Kyle Jacobsen]]></dc:creator>
            <pubDate>Sun, 19 Jul 2015 02:40:55 GMT</pubDate>
            <atom:updated>2016-12-06T15:56:57.760Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3XDjLiD_p0U4QC7woRdy0g.jpeg" /></figure><p>Allow me to set the stage. I’ve been building product for a long time. I’ve built product in waterfall, Agile, Lean, you-name-it methodology and the result was always the same. At some point I would synthesize customer feedback, mostly gut feel, dump it into the laps of the development teams and the mistakes continued to grow. About six months ago I started a new job with yet another methodology (insert sarcastic smile), little did I know the effect it would have.</p><p>We had talked to a few customers and understood the problem — getting people into the application was not easy. In fact, it was bad. Here we were… a software company offering group plans and getting people into the application was impossible. So, we talked to clients. We analyzed market offerings. We checked out competitors. Then we wireframed some ideas and started to test.</p><p><em>The following describes my experience with </em><a href="http://kenjibankhead.com/"><em>Kenji Bankhead</em></a><em>, the best designer I’ve ever worked with, testing our wireframes from start to finish.</em></p><blockquote><strong>Round One: Wireframes and Wasted Time</strong></blockquote><p>So somehow we thought the most logical place to start was by asking the user to describe their organization structure. This seems logical, right? They are buying licenses for their people and have teams all across the world. So let them describe how their organization is structured and they can build teams and people at once. Within minutes of the first call we knew there was a problem — our design was wrong. Really, really wrong.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*g1K1xIcdpdOePK-_hKM3ig.png" /><figcaption>Our first tested wireframe. We tested with seven clients and immediately knew it was wrong.</figcaption></figure><p>Going into this I was confident that we had created a great design. In fact, so confident that I had scheduled seven (yep, that’s 7) design tests for the day. Wow, what a mistake. By the end of the day… we were smoked. Worse, we were frustrated because we had to listen to seven different people tell us our design was stupid and broken. Result — sadness.</p><p>The next iteration was very different. We killed the whole, “tell us about your organization structure” concept and went directly to creating a single team. At this point you may be asking yourself, “but wait, isn’t the problem about getting people into the application and not just creating a team?” well, yeah. We made another mistake here — don’t worry, we will make many more. Clearly, we needed more Voice of the Customer calls before we started to design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pKuiBMB0s5TC0c4i_iqZ1g.png" /><figcaption>Version 2: adding users at this point but still not focused on solving the pain.</figcaption></figure><p>Next we added some purchasing to the mix. We needed to give our users some context so from this point forward we tested purchasing and inviting at the same time. We also started to issue objectives to our testing partners so they knew what to do. This really improved the discussion because asking someone to click around on a screen and provide feedback without objectives is like asking someone to kick field goals in the dark — frustrating. <em>(Note: the experience we designed included ~12 screens which the user had to click through)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BElBqeP16LKBsnR-7XRE-A.png" /><figcaption>Version 3: We added purchasing for contextual purposes. People were going to buy before they added new people and we needed to set the stage for our users.</figcaption></figure><p>So, there we were, Round 1 of testing in the bag. Our designs were making progress but not without major mistakes and wasted time. We learned that providing context improved feedback. We learned to space the product testing sessions out over time. We learned that we needed more Voice of the Customer calls before we started to design. And having objectives make the testing users comfortable.</p><blockquote><strong>Round Two: Door Number 1 or Door Number 2?</strong></blockquote><p>At this point we were ready to move into hi-fidelity mocks and decided to make a major shift in the UI. Following our first round of testing we settled on two solutions to test:</p><blockquote>Door Number 1: Users can invite people by adding emails and let Pluralsight invite the user, OR</blockquote><blockquote>Door Number 2: Users can invite people by sharing a URL which let anyone (on their domain) create an account</blockquote><p>These solutions were both fast and easy for the users. What we didn’t know was how to present these options. So we started by presenting both options on the same page and immediately learned it was a mistake.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hFwQF9bklYTOo-lJYEgjPw.jpeg" /><figcaption>Version 4: We offered both options and it failed miserably.</figcaption></figure><p>Having both options in the same screen really confused our users. In test after test our users thought the two options were connected (they were trying to add emails of their teammates and then tried to get the link to share with them) — apparently they didn’t see the “OR” part of the screen.</p><p>Kenji and I were frustrated. But they were right. Our design was flawed. Too many CTAs (Call to Action) on a single screen. So… we broke out the options and let users toggle between the two.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ffarNGJz5M8ehMybztGmRQ.jpeg" /><figcaption>Version 5 / Option 1: Users can simply paste emails into the screen and we will send the invites out.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XiqBd-UXuxkgm0BFw1Rl3Q.jpeg" /><figcaption>Version 5 / Option 2: Users can copy a link and send it to anyone.</figcaption></figure><p>Success! Breaking the options out made it easy for users to understand what they had to do. However, now we were seeing users struggling with Door Number 2 (more on that later). So our next was question… which option should be presented first?</p><p>Turns out it was 50/50. After testing ~12 times there was no clear winner. We hoped the users would select the default option but no dice. So, we weighed the options and selected for them. Door Number 2 was chosen because of two reasons.</p><blockquote>First, this is a much easier path for the user to get people in the application.</blockquote><blockquote>Second, we believe this option will drive higher product usage (this is just an assumption but we plan to test this assumption in production).</blockquote><p>Round 2 lessons learned… too many options is a bad idea. People get confused and can mix them up. Also, testing doesn’t always reveal the correct design — sometimes you have to pick a path and test it after you roll to production.</p><p>Another note worth mentioning… we really struggled in this phase because I was speaking too much in our testing sessions. I wasn’t teaching them how to complete the tasks but my questions were leading them to the solution which was a terrible mistake. Luckily, this was pointed this out so I was able to shift my approach and as a result we immediately got honest responses.</p><blockquote><strong>Round Three: They just don’t get it?</strong></blockquote><p>It seemed so simple. So. Very. Simple. But explaining the “invite people by sharing a URL” option (Door Number 2) wasn’t easy. On the surface, this solution is simple but not for our users. They are accustomed to more traditional methods so how did we make it clear for everyone? We started by creating several versions and asking for people to explain each.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NozdqaiE8mNvttNxgqE2ZA.jpeg" /><figcaption>Here we tried to put the CTA first and let them add domains. Domains control who can get an account.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0xJqcrElS3XsPikya0Gr9A.jpeg" /><figcaption>When people showed concern over sharing a link, we flipped the design to make sure they understood they had control.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jEHJpQj1vI9Ur4-RKXCTaA.jpeg" /><figcaption>We then stripped out adding / editing domains.</figcaption></figure><p>We exhausted just about every possible scenario. We let them edit their domains (which is the gateway to users signing up). We changed the order by swapping the link and the domain. We stripped everything down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ssISlzaWRtgi7HhEHdoPA.jpeg" /><figcaption>The final version. Well, not really we pulled out the Twitter reference.</figcaption></figure><p>After testing this extensively Kenji and I decided to provide loose directions and this seemed to do the trick. People understood it.</p><p>Done! We got it. The users love it. Getting people into the application will be so easy now. Which path will they take to invite people? Will usage go up for those that have to go and get a license versus those that require little action? The design is about to hit the store shelves and I can’t wait to see what happens.</p><p><strong>Lessons learned:</strong></p><ol><li>Providing context to the user improved feedback.</li><li>Spacing testing sessions out made it easier to digest the information people were sharing.</li><li>We needed more Voice of the Customer calls before we started designing.</li><li>Testing objectives make the testing user comfortable.</li><li>One page equals one Call to Action.</li><li>Finally, not all testing reveals the correct design — sometimes you have to pick a path and test it after you roll to production.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=468454524ffa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>