<?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 Ty Magnin on Medium]]></title>
        <description><![CDATA[Stories by Ty Magnin on Medium]]></description>
        <link>https://medium.com/@tymagnin?source=rss-173a4ca6df93------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4lGHDQjTXKarGZxjfwsdYA.jpeg</url>
            <title>Stories by Ty Magnin on Medium</title>
            <link>https://medium.com/@tymagnin?source=rss-173a4ca6df93------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 12:06:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tymagnin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why ‘Feature Blindness’ Is Killing Your App’s Retention and How You Can Fix It]]></title>
            <link>https://medium.com/appcues/why-feature-blindness-is-killing-your-app-s-retention-and-how-you-can-fix-it-edab44b81d00?source=rss-173a4ca6df93------2</link>
            <guid isPermaLink="false">https://medium.com/p/edab44b81d00</guid>
            <category><![CDATA[user-psychology]]></category>
            <category><![CDATA[consumer-behavior]]></category>
            <category><![CDATA[user-behavior]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[psychology-marketing]]></category>
            <dc:creator><![CDATA[Ty Magnin]]></dc:creator>
            <pubDate>Mon, 26 Jun 2017 13:36:43 GMT</pubDate>
            <atom:updated>2017-06-26T13:36:43.333Z</atom:updated>
            <content:encoded><![CDATA[<p>Digital advertising spend approached $60 billion dollars in the year 2015 — meanwhile, more than 80% of ads go ignored. Ironically, the more advertising we see, the less we pay attention to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*w6_wKAggr2XujpfS.jpg" /><figcaption><a href="https://www.nngroup.com/articles/banner-blindness-old-and-new-findings/">Source</a></figcaption></figure><p>The heatmaps above visualize eye tracking studies of three different web pages conducted by the <a href="https://www.nngroup.com/articles/banner-blindness-old-and-new-findings/">Nielsen Norman Group</a>. Areas users spent most of their time looking at are lit up in red, while yellow represents fewer views, and blue even fewer. As users quickly scan webpages, they completely ignore design elements that suggest advertising.</p><p>This phenomenon is known as ad blindness, and most product people understand it to be a marketer’s problem. What they fail to realize, however, is that the same mental process that makes us ad-blind renders us <em>feature-blind</em>, too. We juggle a constantly shifting assortment of applications every day, and in doing so, don’t even register features that we don’t use regularly.</p><p>At work, we change windows <a href="http://www.nytimes.com/2010/06/07/technology/07brain.html">nearly 37 times an hour</a>. You might have built a powerful product decked out with sparkling features, but if no one uses them, all the effort you put into development goes to waste. Users suffer from feature blindness — and only see features that they’re already accustomed to using.</p><p>The good news? By understanding how feature blindness operates within your product, you can launch countermeasures and ramp up user engagement — without building anything new.</p><h3>The Psychology Behind Feature Blindness</h3><p>Feature blindness is rooted in the human brain’s instinctual ability to filter out unnecessary information and stimuli.</p><p>Imagine that you’re at a noisy party. The sounds of people talking, laughter, and loud music all even out into a pleasant haze of white noise. Yet the moment someone mentions your name from across the room, your ears perk up, and your attention switches into high gear. You immediately drown out all other noise to hear what that person is saying about you.</p><p>Psychology tells us that this isn’t just because you’re a narcissist. <a href="https://en.wikipedia.org/wiki/Detection_theory">Signal Detection Theory</a> explains the manner in which the human brain filters out extraneous noise in order to focus on what it deems as immediately relevant — it’s how we navigate the world under constant, sensory assault. How we detect certain stimuli and ignore others is dependent on a variety of psychological factors: what we gain from detecting relevant signals, the cost of missing relevant signals, and the cost of mistaking noise as an important signal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*ax37MHVU1Usq4QNF.jpg" /><figcaption><a href="http://discovermagazine.com/2013/jan-feb/36-new-project-maps-the-wiring-of-the-mind">Source</a></figcaption></figure><p>Developments in brain imaging technology illustrate the neural pathways of the brain as bursts of color — strong connections and high activity are colored red. The majority of our brains, however, are more passive and painted in cold blues and greens. Feature blindness occurs when your app is in these green zones, you want them in the highly active red.</p><p>Users of your app are there to get things done. They build behavior patterns and workflows around the features they really need, and in doing so, start to forget about the others. As they sink into your app, they become feature blind. Our brains are <a href="http://www.wsj.com/articles/our-amazingly-plastic-brains-1423262095">“use it or lose it” organs</a> — like muscles, they atrophy by sitting still for too long. Your app becomes dormant and ordinary in the mind of the user — easily replaced the moment a shinier competitor comes to market.</p><p>As a product person, it’s tempting to let sleeping dogs lie. Don’t. By identifying feature blindness at every turn in the customer journey, you gain an incredible opportunity to rewire the way users engage with their apps — and possibly even their brains.</p><h3>1. Reactivate Neglected, Must-Have Features</h3><p>The core value of your product is already there, only it’s hidden in the miasma of feature blindness. Users will often try features out a couple times, before forgetting about them and limiting their use of your app to a narrow set of features. Even if they found other features valuable, they may never use them again as they enter into the user’s blind spot.</p><p>This is okay for seldom-used, complimentary features, but this spells total disaster when it comes to core features in your app. There’s a lot at stake here: fail to get the user engaged with must-have features and the user is certain to drop off eventually and become inactive. But get the core feature back in front of the user, and you’ll be able to incorporate it back into the user’s usage pattern.</p><p>What’s most important is to look for the intersection between must-have features that you already have, and forgotten features that users have tried but are now blind to. It’s the hot zone for feature reactivation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t0-SjM7s3JfPkqai.jpg" /></figure><p>To land in the hot zone of feature reactivation, do the following:</p><ol><li>Use an event tracking platform like <a href="https://amplitude.com/">Amplitude</a> to dig into the “must-have” features that users used a couple of times, and then forgot about. By conducting <a href="https://amplitude.com/blog/2015/12/15/how-to-increase-growth-through-retention-analysis/">behavioral cohort analysis</a>, you can identify the features that correlate with long-term retention. Those are the ones that you want to make sure to bring back to your user’s attention.</li><li>Run <a href="http://appcues.com/academy/user-testing/">user tests and conduct surveys</a> to reach out to users in-app to discover why people aren’t using these features. If the feature has a setting that you can toggle off, then find out why users toggled off a core feature. Find points of friction, and develop a reactivation strategy.</li><li>Segment out users unengaged with the feature, and reactivate it for them.</li></ol><p>It’s tricky knowing what specific features to reactivate, and how to do so. That’s why it’s so important that you build a systematic process to increase user engagement, and avoid the blind leading the blind.</p><p>At <a href="http://priceintelligently.com/">Price Intelligently’s</a> <a href="http://www.priceintelligently.com/saasfest-2015-speakers-presentations-slides">SaaSFest Conference</a>, Wolchonok described his <a href="http://appcues.com/blog/6-growth-experiments-sidekick-ran-to-improve-retention/">growth strategy to increase long-term retention for Sidekick</a>, HubSpot’s email tracking and scheduling product. For Sidekick, the key to boosting Week 1 retention was getting users to send their first tracked email as quickly as possible during user onboarding, to get to that glorious aha! moment.</p><p>Tracked emails showed the user when an email recipient actually received and opened an email — and that gave users the feeling of having x-ray vision as a superpower. A salesperson, for example, could see when prospects opened his emails, and schedule follow-ups accordingly.</p><p>Even though this lifted retention across the board, the growth team at HubSpot noticed something strange: over time, users would turn off tracking. Weirdly, users saw the core value, then for some reason, they would disable it, neutering the product of its core value. User engagement would drop-off, and they’d eventually churn out.</p><p><a href="http://appcues.com/blog/6-growth-experiments-sidekick-ran-to-improve-retention/">After surveying their users and conducting extensive user testing</a>, the HubSpot team learned the surprising reason why this happened. It turns out that users didn’t always want to receive notifications every time an email is opened. They’d uncheck the tracking box after sending a personal email, and completely forget its existence. Over time, they became blind to the little, but hugely important, checkbox — and it would stay unchecked forever.</p><p>One solution was to leave open-tracking always on — but this would have forced users to uncheck the box every time they wanted to send an untracked email, leading to even more friction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/588/0*m6q66rigyl0QtkPp.jpg" /></figure><p>Instead, Sidekick implemented an incredibly simple and effective strategy. After long periods of inactivity, they automatically turned tracking back on for users who hadn’t used it in some time, and reintroduced the feature with a little tool-tip. It allowed users to rediscover Sidekick’s core value, and it took the checkbox out of the user’s blind spot.</p><p>When it comes to re-engaging users, take a page out of HubSpot’s book. Minimize the cognitive effort it takes for users to get the most out of your app, and you’ll be on your way to inspiring long-term delight.</p><h3>Push notifications on Peach</h3><p>For mobile apps, push notifications are often the magic ingredient to user engagement — <a href="http://info.localytics.com/blog/push-messaging-drives-88-more-app-launches-for-users-who-opt-in">leading to increases of up to 278%</a>. And yet so many apps only ask you once, during onboarding, before you know whether you like the app, whether you want to enable push. Say no, and the app won’t ask again, making long-term engagement with the app far far less likely.</p><p><a href="http://peach.cool/">Peach</a>, the hot new social network and messaging app, takes the opposite approach. The app doesn’t immediately ask users to allow push notifications during onboarding — users create a login, pick a profile picture, and connect with friends. It’s only after they’re greeted by an empty activity feed for the first time that users are asked to turn them on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*kTsOD_1kCmmdip6j.jpg" /></figure><p>Because we’re already collectively swamped by notifications, we’re always reluctant to add more, especially early in the app experience. Instead of immediately emphasizing push notifications, Peach bides its time and it presents you with the request on the page for which it’s relevant.</p><p>But even if you say no to push notifications at that point, the app will present you a persistent banner in your notifications feed inviting you to turn on push. This banner only appears in your notifications feed, and not on any other screen, so you don’t grow blind to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aWQfv2B4jnurRik4.jpg" /></figure><p>The purple call-to-action at the top of the feed gently reminds users to enable notifications, and allows them to do so at any time. What’s brilliant is that as a user’s feed fills with activity with friends, they’re increasingly motivated to re-enable push, because they can clearly see its benefits. Turn push notifications on, and whenever Eli “boops” you, you’ll know instantaneously — and then you’ll really get addicted.</p><h3>2. Dust Off Never-Used Features</h3><p>Before developing a new version of Office, Microsoft surveyed users and asked what new features they’d like to see — <a href="https://blog.intercom.io/new-features-usually-flop/">over 90% asked for features that were already available</a>.</p><p>When you announce features, don’t just get them launched, get them used. Most of your users will never use certain features, and miss out on the full value they could be receiving from your product. We often think that once a feature goes live, our work is done. <em>We</em> know that it’s there, so we assume that our customers do too. The simple truth is that your users don’t care nearly as much about your features as you do. They’re focused on other things, like getting their own work done.</p><p>Even if a feature has been sitting around for a while, you can re-launch it as a new feature for users who never touched it.</p><p>However, you don’t want to indiscriminately push all of your existing features upon all of your customers. You’ll lose credibility and customers will stop listening. Remember, you’re trying to alleviate feature blindness, not increase it.</p><p>This is absolutely critical because different user personas will use your app differently. While your product will have an overlap of core feature usage — <a href="http://venturebeat.com/2016/01/05/evernotes-5-problem-offers-a-cautionary-lesson-to-tech-companies/">hopefully greater than Evernote’s 5%</a> — complimentary features will only make sense for certain personas and use cases.</p><p>The best way to go about this is to start by <a href="http://appcues.com/blog/diagnosing-your-user-engagement-problem/">segmenting your users by persona, and measure their success metrics against each other</a> — that way, you can highly target the group of users most likely to benefit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hqU79b5mW3qV1Cfc.jpg" /></figure><p>For maximum exposure, relaunch features across various touchpoints:</p><ul><li><strong>In-app messaging</strong>: try <a href="http://appcues.com/">Appcues for in-app alerts, tooltips, and hotspots</a> depending on how obtrusive you want the notification to be. This will depend on the significance of the feature to the user persona, but also on the urgency of breaking a user out of feature blindness with respect to a certain feature.</li><li><strong>Email announcements</strong>: use <a href="http://customer.io/">Customer.io</a>, using segmentation to break up your list and send tailored emails based on recency of activity or user persona. Emails are powerful ways to reactivate users who haven’t logged in to view your in-app new feature announcements.</li></ul><p>It links back to the cocktail party effect — relaunch features as if you’re calling out your users by name. Instead of pushing users toward what matters to you — your shiny features — eliminate noise so they can see what matters to them.</p><h3>The Non-Intrusive Feature Relaunch</h3><p>Let’s say that your product is a team communication platform, similar to Slack. A couple months ago, you launched calling capabilities for the app, and broadcast it in an email message and on a short blog post. You segment out the main user groups of your app that you want to target into engineers and customer success reps.</p><p>By analyzing usage data, you discover that some of your customer success reps have been making calls in your app — but the majority of engineers haven’t given it a second glance, or even a first. The moment they login to your app, they hop into the chat room, and never leave.</p><p>Don’t bother the engineers — they’re busy. Instead, focus on getting the rest of your customer success reps making calls, as they’re the ones who can best appreciate the feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AGD0On4baqwWGcaP.jpg" /></figure><p>Use hotspots and tooltips to reintroduce the feature to them, as if for their first time. That way, the next time they make their way to their eyes will get lit up by a bright red dot, triggering a small rush of dopamine to the brain. The hotspot breaks up feature blindness, preventing the eyes from just glossing over the call button in the action panel and compelling users to see and explore items they’ve previously overlooked. It directs users to take a specific action — configure calling integration, and get Tyrion on the phone!</p><h3>3. Re-Engage Users with New Feature Launches</h3><p>The introduction of a new feature is one of the most powerful ways to break existing usage-patterns within your app and helps create new habits and behaviors.</p><p>Getting users to build habits around your app is super important, but if they get stuck in the same behavior patterns, your product actually loses value in their minds. As the saying goes, familiarity breeds contempt. Without change, users will begin to approach your app mechanically, as if on auto-pilot, and it fades into the background.</p><p>That’s why you need to use new feature launches to actually break the user’s conception of your product. Do that, and the user will look at your product again with blindness stripped away and fresh eyes.</p><p>When you launch a new feature, don’t just launch the small feature itself — launch it within a broader use-case, and the larger context of your app.</p><p>When launching a new feature:</p><ul><li>Storyboard your onboarding flow before the feature launch. Map out how they’ll see and interact with it in a variety of scenarios, from giving a quick once-over, to a deep dive.</li><li>Clearly demonstrate to users how they can benefit from the new feature. Don’t just show off new features — use them to demonstrate larger use-cases of your product.</li><li>Launch the feature within context, instead of just tacking it on haphazardly. Not only will you boost adoption of the new feature, but increase user engagement across the board.</li></ul><p>We often think it’s all about the next massive feature that will overhaul your app, and fix retention for good. What’s more important, however, are the small, marginal changes you make. Over time, they add up to seismic changes in user behavior. Constantly get users to look at your product in new ways, and they’ll continually rediscover, and engage with your app.</p><h3>What’s New with Slack</h3><p>Every time Slack introduces a new feature, a little red dot lights up in the top right corner of its app, triggering a dopamine rush. Once clicked, a sidebar opens that Slack users can then scroll down for an overview of new features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qa0khChzwAPBYHEQ.jpg" /></figure><p>The most recent feature gives users the ability to allow team members to edit their posts, and directs them how to do so in plain, simple english. What’s great about this specific announcement is that it builds on existing capabilities of Slack that users don’t necessarily know about.</p><p>Browsing through the “What’s New” sidebar, users learn about all the new ways they can interact with Slack — as they actually go and see for themselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zpqQnlijSut6_Q7Q.jpg" /></figure><p>Allowing others to edit your posts, for example, isn’t a particularly game-changing addition to Slack’s arsenal, but the update also subtly reminds Slack users that they have the ability to edit their <em>own</em> posts. By driving users toward a specific action — clicking on the ellipsis menu — the update gets users to see a whole range of features and options they can take, from marking posts as unread, to adding a reaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1tuQSKnvdmPfcwJG.jpg" /></figure><p>What’s effective about this feature announcement is that it’s situated contextually within a larger use-case for Slack. It opens up a whole new range of actions and ways that users can engage with Slack — that they might previously have been blind to.</p><p>A good habit to get into is to make a new feature announcement every two weeks or month, no matter what. Don’t get caught in the trap of waiting until something is big enough or perfect enough to announce, so that you end up never announcing any new features.</p><p>Review what your product team accomplished over the period and turn it into a new feature announcement, even if it was just a simple bug fix. An app developer’s inability to recognize when an improvement is worthy of announcement is its own kind of feature blindness. Forcing yourself to do it will help you break the bad habit of procrastinating new feature announcements and it will motivate you to regularly produce customer-facing improvements.</p><p><a href="http://helpscout.net/">Help Scout</a>, a help desk for small businesses, consistently announces over 2 new features per month. But look closely, and notice how some of the “Latest Updates” aren’t what you’d conventionally think of new features at all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OPMvEnjqLl_x8ClT.jpg" /></figure><p>They’ve announced as a new feature that “Mailboxes are 40% Faster” — more an enhancement than a feature — and a majority of the updates are actually tips on how to use existing features better.</p><p>Rather than strictly define what’s worthy of announcement and miss out on communicating the product’s value, Help Scout’s consistent cadence conveys an exciting feeling of non-stop product progress and evolution. The user gets the message: the app is constantly changing and improving, and therefore, worthy of perpetual exploration and experimentation.</p><h3>Move Beyond WOW</h3><p>We love to talk about the WOW moment — the first time a user recognizes the core value of your app. It’s what gets users to actually use your product, and justify paying for it. But in order to truly unlock longterm growth, you have to constantly WOW your customers all the time, and continually enhance the user experience.</p><p>The human brain is alive, and constantly adapts to sensory information. As we think, learn and experience new things, connections between our brain cells rapidly shift and readjust. By paying close attention to user psychology and how your app is implemented, you can get users to experience your app in a completely new way — and get them to really engage with what’s hidden in plain sight.</p><p><em>Originally published at </em><a href="https://www.appcues.com/blog/why-feature-blindness-is-killing-your-apps-retention-and-how-you-can-fix-it/"><em>www.appcues.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edab44b81d00" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appcues/why-feature-blindness-is-killing-your-app-s-retention-and-how-you-can-fix-it-edab44b81d00">Why ‘Feature Blindness’ Is Killing Your App’s Retention and How You Can Fix It</a> was originally published in <a href="https://medium.com/appcues">Appcues</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LearnVest’s Head of Product Shares His Best Storytelling Tips for Product Managers]]></title>
            <link>https://medium.com/appcues/learnvests-head-of-product-shares-his-best-storytelling-tips-for-product-managers-91e1320ab559?source=rss-173a4ca6df93------2</link>
            <guid isPermaLink="false">https://medium.com/p/91e1320ab559</guid>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[digital-storytelling]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ty Magnin]]></dc:creator>
            <pubDate>Wed, 21 Jun 2017 14:07:23 GMT</pubDate>
            <atom:updated>2017-06-21T14:07:23.247Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*TLrrKJZLXbJaty6gdQNHgw.jpeg" /></figure><p>“What’s your story?”</p><p>That’s Vivek Bedi’s favorite question to ask product managers in interviews. If PMs can’t explain their own background and interests well, they probably won’t be able to build a strong case for your product.</p><p>Vivek is a product guy with over 15 years of experience and knows a thing or two about building and selling great products. As the Head of Product at <a href="https://www.learnvest.com/">LearnVest</a>, he manages financial planning products and client experience functions for Northwestern Mutual, which acquired LearnVest in 2015. He is also the founder of <a href="http://myswapp.com/">mySwapp</a>, a mobile app that allows people to trade unwanted goods. Before joining the startup world, Vivek was a product leader at Goldman Sachs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/0*xpXBCxM10F510QdE." /></figure><p>Vivek’s work has helped millions of people with their finances, and he attributes much of his success in product management to his love of storytelling:</p><p>“Telling great stories enables you to convince others to help you build a great product and convince people to buy that great product,” he says.</p><p>He has used storytelling to make his pitches more engaging, keep his team motivated, and even turn harsh criticism into inspiring goals. Here are some of Vivek’s best storytelling tips for product managers.</p><h3>Build excitement in the first few minutes</h3><p>Vivek has worked on enough first-time user experiences to know that people are impatient. If users can’t figure out how to use a product within minutes, they will leave. “It’s important when crafting your story to focus heavily on the first few minutes. That is when most in the crowd will decide to stick with you or you will lose them,” says Vivek.</p><p>Some audiences need more context than your day-to-day team. Speaking with external stakeholders gives you a chance to tell a broader story about your product and yourself. Vivek recounts a time when he was invited to discuss his products at an off-site conference and missed this valuable opportunity:</p><blockquote>“I jumped right into the product roadmap and our strategy, without setting the stage or even telling people who I was and why I was there. A minute into the meeting one of the senior folks on their side stopped me in my tracks and made a joke about how we should take a step back, as it would be nice to introduce ourselves. Some folks chuckled and I felt very embarrassed.”</blockquote><p>Vivek’s tactic to building excitement is to thank his audience right from the start. Here’s how he does it with different groups:</p><ul><li><strong>Clients and external audiences:</strong> Thank the audience for coming to hear you speak or inviting you to their office. “It makes it about them and not you. And that’s a great way to stroke the egos of the audience and set the tone of the story,” says Vivek.</li><li><strong>Your team:</strong> Don’t overlook the importance of thanking your own teammates. It’s their hard work that helped you build a better product. Vivek says,<em> “</em>Every time I meet with my team, I thank them for working hard and creating magic. It automatically fills the room with smiles.”</li></ul><p>A good first impression makes your audience more receptive to hearing what you have to say — whether that’s an <a href="https://www.appcues.com/blog/aha-moment-guide/">aha! moment in the product</a>, a presentation about your product roadmap, or just a weekly status report to your team.</p><h3>Use personal experiences to validate feedback</h3><p>When Vivek first joined LearnVest, his team was responsible for <a href="https://www.appcues.com/blog/proven-customer-retention-strategies/">increasing repeat usage</a> and <a href="https://www.appcues.com/blog/increase-user-engagement">engagement</a>. The charter was to create a product experience that was much stickier.</p><p>Vivek had first-hand experience with the product’s engagement issues. Vivek had purchased an insurance policy from Northwestern Mutual, but years had gone by since he really logged into his account and paid attention to it.</p><p>Instead of tiptoeing around his own user frustrations, Vivek was upfront about his experience:</p><blockquote>“As I shared my personal disinterest in using the existing website, I saw heads nodding. Everyone was on the same page — our product experience today needed an overhaul. After getting everyone to realize we have a similar viewpoint on the product today, I started sharing about other products I’ve used, like Mint, Personal Capital…especially pointing out the things they do better than our product does today.”</blockquote><p>Not only did people thank him for his honesty, but they also had more faith in his abilities to lead the team because of it:</p><blockquote>“One of the most experienced financial reps thanked me for criticizing the product. He recognized that everyone was thinking it, but not everyone had the guts to say something. It inspired them to trust me a bit more in leading the initiative to improve our own product.”</blockquote><p>Sharing criticism about your team’s work isn’t easy, especially when you’re the newest person in the room. Personal experiences can help soften the criticism and foster a more open and collaborative environment. Reframing areas of improvement as growth opportunities can also be a great tactic for inspiring your team.</p><h3>Put on a show, not a presentation</h3><p>Every quarter, Vivek and his team present a company-wide SOTU about the product roadmap and the team’s successes. After one of these sessions, Vivek received two compliments that changed his entire mindset about presentations. One colleague congratulated him on the “amazing show” his team put on, while another person said, “You were like Steve Jobs up there, I loved it!”</p><p>Vivek considers Steve Jobs to be the “product storytelling master,” so ever since that moment, Vivek has aspired to turn all his presentations into “shows.” The subtle shift in mindset reminds him of the importance of using product demos early and often:</p><blockquote><em>“Showing your product is much more of a compelling story then talking about it. And show it soon. Think back to Steve Jobs. He did a great job of getting to the demos soon into his presentations, sharing the product features and new Apple product releases, captivating his audience from the get go.”</em></blockquote><p>In addition to product demos, Vivek urges using visuals:</p><blockquote><em>“When you add visuals, product demos, or interactive experiences you are hitting on the second sense of sight as well. Sensory studies show if you take advantage of two or more senses when engaging you are automatically going to get more audience attention you would have otherwise gotten.”</em></blockquote><h3>Don’t be afraid to make fun of the product (or yourself)</h3><p>It’s second-nature to adopt a formal tone of voice when discussing your work. Afterall, building a product can take months’ or years’ of hard work. You want people to take it seriously and appreciate its value.</p><p>However, an overly serious tone can backfire and bore your audience. Vivek had to hone his pitches early on because his partners were traders, who “<em>by nature, have an attention span similar to my 4-year-old. Time is money in their minds,” </em>he says.</p><p>Vivek has since learned to infuse bits of humor and personal tidbits into his discussions:</p><blockquote>“For instance, I recently gave a talk discussing how I am going through a ‘product management identity crisis’ and needed to go find my product self, even after 15 years in the industry…I incorporate some jabs at myself and bring in jokes from my personal life — stories about my kids, my wife.”</blockquote><p>If you’re not comfortable sharing jokes from your own personal life, another easy way to do this is to poke fun at the product. “Showing that softer sider is a secret gem for storytelling that makes your audience feel more comfortable with you,” says Vivek.</p><p>Vivek suggests talking about what a horrible experience the first MVP of your product was, and even showing screenshots of how clunky and misguided early user experiences were:</p><blockquote>“This is really a great tactic in getting folks to know that you keep it real and you aren’t here just feeding them bullshit. It also sets a great tone that this wasn’t easy — we started from the bottom and now we worked hard to be where we are.”</blockquote><p>By making fun of the product, you can make your experiences more vulnerable and relatable, while also showing off progress.</p><h3>Storytelling ultimately helps PMs connect to others</h3><p>Product managers work at the intersection of so many teams with competing priorities and different skillsets. Storytelling skills are key to bridging departmental and individual differences, as Vivek explains:</p><blockquote>“As a product manager, you’re working with engineers, designers, and marketers to build a product. How are you going to convince them to help you and then communicate your vision for the product you want to build? You sure as heck better be good at telling a compelling story to get them onboard, motivated, and clear about the product you’re building.”</blockquote><p>For product managers, storytelling isn’t just about whipping up a fantastic tale or putting on a good show. It’s also about understanding your users and teammates and championing their needs.</p><p><em>Originally published at </em><a href="https://www.appcues.com/blog/storytelling-tips-for-product-managers/"><em>www.appcues.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91e1320ab559" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appcues/learnvests-head-of-product-shares-his-best-storytelling-tips-for-product-managers-91e1320ab559">LearnVest’s Head of Product Shares His Best Storytelling Tips for Product Managers</a> was originally published in <a href="https://medium.com/appcues">Appcues</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Growth Experiments HubSpot Ran to Improve Retention]]></title>
            <link>https://medium.com/appcues/6-growth-experiments-sidekick-ran-to-improve-retention-73e679d71cb2?source=rss-173a4ca6df93------2</link>
            <guid isPermaLink="false">https://medium.com/p/73e679d71cb2</guid>
            <category><![CDATA[hubspot]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[retention]]></category>
            <category><![CDATA[user-onboarding]]></category>
            <category><![CDATA[user-retention]]></category>
            <dc:creator><![CDATA[Ty Magnin]]></dc:creator>
            <pubDate>Wed, 14 Jun 2017 16:14:19 GMT</pubDate>
            <atom:updated>2017-06-21T14:15:26.135Z</atom:updated>
            <content:encoded><![CDATA[<p>Retention is a tricky beast. It can sneak up on you and sink your entire endeavor. Getting your new user retention experience right often takes iteration and patience, but it’s always, always, always worth the effort.</p><p>We’ve been working to improve retention at <a href="https://www.getsidekick.com/">Sidekick — a HubSpot product</a> — for the better part of a year now. And with the help of our excellent team, we’ve found some success after running numerous growth experiments to solve our retention challenge.</p><p><em>Note: the data in these — and the following — charts are all fake; but the lessons are 100% real.</em></p><h3>The Importance of Retention</h3><p>“If you have poor retention, nothing else matters.” This was said by my colleague, renowned growth marketer, <a href="https://twitter.com/bbalfour">Brian Balfour</a>, and it’s absolutely true.</p><p>With bad retention, monthly cohorts slowly slink into sadness. It makes all the effort you put into acquisition seem useless.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lNmMXvYe0zUvPVzt.jpg" /></figure><p>But <a href="https://www.appcues.com/blog/the-importance-of-customer-retention-by-the-numbers">good retention keeps a company energized</a>. It can give you more at bats to get your marketing or your product right, and it brings in more revenue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J5H-pIku7t2U36sy.jpg" /></figure><p>Do you know what’s even better than good retention? Negative churn. Negative churn is that holy-smokes-awesome phenomenon that reflects users that sign up for your product, and spend more money over time; offsetting revenue lost with churn with upgrade revenue.</p><p>This could be from upgrading to a paid or higher paying plan, or from adding team members in what we call <a href="http://www.anumhussain.com/presentations/b2c2b-content-strategy">a B2C2B strategy</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7zr58AYmgzrZZ8o5.jpg" /></figure><p>The benefits of better retention are vast:</p><ul><li>A higher LTV of your customers, which can be reinvested into a greater customer acquisition budget.</li><li>An increased virality as there’s more happy users to spread the word, which lowers your CAC significantly.</li><li>Shorter payback periods, especially with a free-to-paid business model like that of Sidekick.</li></ul><p>A user’s journey can be broken up into three stages of retention, each with its own challenges:</p><ol><li>Week 1 — can you get your users to use your product more than once?</li><li>Mid-term (Weeks 2–4) — can you establish any pattern of usage?</li><li>Long-term (Weeks 5 and on) — how does your product become an indispensable tool?</li></ol><p>At Sidekick, we had 2 main problems we wanted to fix. The first was that cohorts were getting worse month over month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pBR1Nx_-lRD5SJvB.jpg" /></figure><p>We tied this problem back to week 1 retention issues. We seemed to have a high volume of “drive by” users that only took one action and then bounced.</p><p>And the second problem was that retention never plateaued. New users were churning at a consistent clip and never found their way into routine usage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RtIk2boEaGc4xzUU.jpg" /></figure><h3>How We Improved Week 1 Retention at Sidekick</h3><h4>We sent out a survey</h4><p>Sometimes the easiest way to get the insight you are looking for is to go straight to the source. In this case, we sent out a survey asking churned users why they stopped using Sidekick. We then isolated the feedback from users that churned within week 1, and broke it down by reasons like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*525qpuQgZROvMb36.jpg" /></figure><p>This data gave us enough confidence to start experimenting. Each insight was — with the exception of competition — things we believed we could fix with the right user onboarding experience.</p><p>Because so many of these users never returned to app even once, we focused on the welcome screen to engage users when they first login.</p><h4>Experiment 1: Add Explanation to Empty State</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vd8OqwlW0uH85QZB.jpg" /></figure><p>We stripped out a ton of CTAs that we thought were confusing. There are still too many CTAs here, but, at the time, we thought it was an improvement. It turned out not to make a difference. Users didn’t know how to interpret what we implemented.</p><h4>Experiment 2: Adding Sample Data</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WsLbuFKECG12nAVq.jpg" /></figure><p>Adding sample data confused users. We got a lot of people thinking we were sending emails on their behalf already. This may be a common danger when using sample data.</p><h4>Experiment 3: Inserting an Explainer Video</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dZuFby9Pha3GBWI5.jpg" /></figure><p>Even though it looked like people watched a decent amount of the video, we didn’t know what their reaction was. They may not have listened to the sound, they may have thought “I still don’t get how I would use it” — the examples may not have been pertinent — , or they didn’t think it would be valuable for them.</p><h4>7 Failed Experiments Later…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ksCB-RadUdQuR2h-.jpg" /></figure><p>After 7 failed experiments, we went back to the drawing board and we asked ourselves, “is the empty activity stream providing any value to new users?” We decided it didn’t.</p><p>So we figured it was worth trying to get them to send more emails instead, and this modal text was the simplest way to test that. Ultimately, this message pointed users to a better place to start engaging with Sidekick, and lead to a significant increase in user retention.</p><h3>How We Improved Long-Term Retention</h3><h4>Long-Term Survey Results</h4><p>The survey feedback from users that churned after week 5 was also easy to sort by reason.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-0iA7suSmiyml3P7.jpg" /></figure><p>We focused on the actionable reasons and ignored the others, and ran experiments toward actually solving churn.</p><h4>Experiment 1: Cut Down Noise</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Po_KiRDgiL4Ke07C.jpg" /></figure><p>By consolidating Sidekick notifications, we reduced the cognitive load that we were impressing on our users. This fix helps avoid annoying them to the point where they turn off Sidekick entirely.</p><h4>Experiment 2: Resurrecting Users</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mEtyNj-8dL9-6dX4.jpg" /></figure><p>The checkbox shown above allows users to toggle the product on / off. Once it’s off, a user has to remember to toggle it back on.</p><p>It turns out a lot of people had forgotten they had turned their checkboxes off, and they didn’t remember to turn it back on. We found this through the qualitative feedback, many users said “Oh yeah! I was wondering what happened to Sidekick.”</p><p>Turning it back on was something that most users appreciated and was a genuine way to bring active users back instead of tricking them into turning it back on.</p><h4>Experiment 3: Investing in Outlook</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Uu_lTwfrprEBv8CV.jpg" /></figure><p>It’s hard to point to one bug fix, or one issue that we resolved for Outlook users that fixed our retention issues, but we were pleasantly surprised to see that after focusing on stability improvements our retention started to improve.</p><h3>Retention Takeaways</h3><p>Retention can be a tricky beast. But I hope you know how much there is to gain by improving your user retention if even by a few percent. As you implement your own retention experiments, here are some tips to keep in mind:</p><ul><li>Retention problems sneak up on you: your top level metrics may be going up, but if your users are not sticking around, you’re in trouble. Don’t be blind to this.</li><li>Ownership: it really helps to have a directly responsible individual (DRI) on new user onboarding. We set up a team that was specifically focused on week 1 retention.</li><li>Alignment of goals: make sure all teams are excited about optimizing for growth and are willing to make sacrifices and invest time in helping improving retention.</li><li>Soak time: weekly/monthly <a href="http://www.danwolch.com/2015/04/the-hard-secret-about-optimzing-week-1-retention/">cohorts take a while to mature</a>. Make sure to give them enough runway to understand their engagement habits — or lack thereof.</li><li>Cohort sizes: you really need a large cohort size to run and effectively measure many experiments.</li></ul><p><em>Originally published at </em><a href="https://www.appcues.com/blog/6-growth-experiments-sidekick-ran-to-improve-retention/"><em>www.appcues.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73e679d71cb2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appcues/6-growth-experiments-sidekick-ran-to-improve-retention-73e679d71cb2">6 Growth Experiments HubSpot Ran to Improve Retention</a> was originally published in <a href="https://medium.com/appcues">Appcues</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Casey Winters Reveals How Pinterest Perfected User Onboarding]]></title>
            <link>https://medium.com/appcues/casey-winters-reveals-how-pinterest-perfected-user-onboarding-639fcc7486d7?source=rss-173a4ca6df93------2</link>
            <guid isPermaLink="false">https://medium.com/p/639fcc7486d7</guid>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-onboarding]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Ty Magnin]]></dc:creator>
            <pubDate>Mon, 12 Jun 2017 19:18:08 GMT</pubDate>
            <atom:updated>2017-06-12T19:27:36.588Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever been in a bad relationship?</p><p>It seems like we all have. Where a partner didn’t return the love we were giving. Or perhaps — more honestly — where we’ve been the partner giving less.</p><p>A good relationship is all about balance. You’ve heard this before, <em>it’s about give and take. </em>Relationships between software products and their users are much the same.</p><p>Pinterest has focused its efforts on balancing give and take. They mastered their onboarding experience by experimenting with these dynamics.</p><p>Casey Winters was a member of the team behind Pinterest’s onboarding as the product experienced rapid growth. During Casey’s tenure, the team ran hundreds of experiments to improve their activation rate.</p><p>Casey recently shared his onboarding secrets on Greylock Partners’ podcast, <a href="https://soundcloud.com/greylock-partners/greymatter-scaling-users-products-and-growth-teams-with-casey-winters"><em>Greymatter</em></a>.</p><p>We here at Appcues have taken the time to break it down with screenshots to give you a better idea of how Pinterest perfected user onboarding by balancing give and take.</p><h3>Give Contextual Help to Demonstrate Your Value</h3><p>As soon as a user hits your product for the first time, it’s on. In Casey’s words, “you really need to accomplish showing the main value in the first session. Or else there’s no guarantee there will be a next session.”</p><p>Showing initial value is as difficult to execute as it is critical to your success. It takes a deep understanding of what a new user wants from your product.</p><p>You probably have an idea of what new users want, but the more you can zero in on this need, and focus on delivering value, the more leverage you’ll have in improving your activation rate.</p><p>Pinterest has a clear understanding of what new users want, which — Casey reported — “is [to see] cool topics that [they’re] interested in.” This value is reinforced through its initial onboarding screen:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QuRLjenzM6AfomC25_jrKg.jpeg" /></figure><p>Not only does the subheader suggest “cool interesting topics,” but the foreground and background imagery complements it.</p><p>Reinforcing your value with images and words is the easy part. Delivering on it is what’s hard.</p><p>Pinterest delivers on its value promise by giving new users contextual help that gets them to engage with the product in a meaningful way. <em>Here it is in action:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JQIvFrZpzremadpU7VhzYg.jpeg" /></figure><p>This blue banner tells readers exactly what to do. There is little room to get lost or confused.</p><p><em>Clicking a pin brings users here:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HU9jwqbLmwzLxcx5." /></figure><p>A pulsing <a href="https://www.appcues.com/ui-patterns/hotspots/">hotspot</a> hovers over the save button, again, making it clear what to do next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*djThsaLrTGoKqxgNPFeJFw.jpeg" /></figure><p>The <a href="https://www.appcues.com/ui-patterns/tooltip/">tooltip</a> message that appears upon clicking the hotspot contextualizes the button further.</p><p><em>From here, we’re given more context:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GJODaR4Z4oZEWxT60FtNbw.jpeg" /></figure><p>Contextual help in the banner below this modal is aimed to prompt action. The copy above — ”A board is a visual collection of Pins” — helps a user understand the product.</p><p><em>Upon clicking save, the blue banner turns green:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lqep88y3Rgpt4SHMJhB4mg.jpeg" /></figure><p>This confirmation message helps a user know they’re on the right track. By this time, first-time users navigating Pinterest have a pretty good idea of what it is and does.</p><p>Level one complete.</p><p>The next time a user clicks into a pin, they see another hotspot. This time on a different element of the product:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*935BuWgGyHrJpxQK." /></figure><p>Pinterest’s onboarding experience continues to progress from here, but at this point, the user has had one or two significant <a href="https://www.appcues.com/blog/aha-moment-guide/">Aha! moments</a>. They understand the value of the product, and are ready to explore more on their own.</p><h3>Get Data to Give a Personalized Experience</h3><p><a href="https://www.appcues.com/user-onboarding-academy">Effective user onboarding experiences</a> often require personalization. <a href="https://www.appcues.com/blog/personalizing-user-onboarding">Personalized onboarding</a> aims to more closely align with the value an individual user wants than a one-size-fits-all approach.</p><p>This approach requires you to either ask for data from your users or obtain it through a third-party data source such as a user’s browser. Pinterest does both.</p><h3>Personalization by asking for data</h3><p>When a user signs up, Pinterest quickly asks them to define their interests in order to customize their home feed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QuRLjenzM6AfomC25_jrKg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ighKHCGj5O6gI76XcEtxSg.jpeg" /></figure><p>Pinterest contextualizes its ask to “Follow 5 topics.” Immediately under is “Then we’ll build a custom home feed for you.”</p><p>As Casey shared,</p><blockquote><em>“you really need to make sure the user understands why you’re asking these questions. That it’s going to help them get value. And you need to strike the balance of how long you’re going to ask them questions before you try and deliver value. Because it is a funnel, right? And the more questions you ask the more there will be drop off.</em></blockquote><blockquote><em>And that’s something something that the Pinterest activation team has played with a lot between level of specificity and yet time to value.”</em></blockquote><p>Having asked a user what they want to see, Pinterest then reciprocates with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iDxFPNWkQuUb5AIxrOgxYA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JQIvFrZpzremadpU7VhzYg.jpeg" /></figure><p>It’s brilliant. Users are given a personalized home feed based on their gender, age, and interests. Not sure about you, but I’m falling in love already ❤️</p><h3>Personalization by browser data</h3><p>A few years ago, Pinterest users abroad saw the same onboarding experience as users in the U.S. And unfortunately, users in certain countries were bouncing at higher rates.</p><p>When Pinterest’s team sat down to draw up some onboarding experiments, they hypothesised that the interests of users abroad were different than those in the U.S., resulting in home feeds that didn’t resonate as deeply.</p><p>By identifying local interests, and pairing that with a user’s country — found within the browser data — Pinterest was able to turn a feed for German men that looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*ehIRjACjimMi5r16q71U1w.jpeg" /></figure><p>Into one for the same persona that looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*4mfXkPEv-HQsUWgxc9Q5vg.jpeg" /></figure><p>You can see the the topics suggested are vastly different after the optimization.</p><p>This experiment improved Pinterest’s activation rate abroad by 5–10% depending on the country and demographic. You can see exactly how Pinterest ran this experiment on <a href="https://medium.com/@Pinterest_Engineering/personalizing-pinterests-new-user-experience-abroad-60f8f55177ac">their engineering blog</a>.</p><h3>Hide Distractions to Hook Your Users</h3><p>Having a clear vision of what a user wants in their first session can inform what to save for future sessions.</p><p>Putting this idea into action, Casey “had the activation team at Pinterest really invest in removing a lot of the complexity of the product over time, so we got people to the core value of the product as soon as possible.”</p><p>Did you catch that?! Pinterest hides elements of their user interface for first-time users. Mind blowing, I know.</p><p>As Casey explains,</p><blockquote><em>“Everything about where the Pins come from, how to add your own Pin, that you can share boards with other people…all of that is removed from the early product until we can make sure that you understand the really important parts of getting value…and then we can slowly start reintroducing those features later on.”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Md_a0Z3REwHI__y4ms3Gxw.jpeg" /><figcaption>Pinterest’s home feed for new users</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yGdjoAXnfTn5igEyX_l-RQ.jpeg" /><figcaption>Pinterest’s home feed for returning users</figcaption></figure><p>Notice what we’ve highlighted in the home feed for returning users is hidden for new? Information about the source for a pin is secondary in value to being able to search and save them. Pinterest reduces friction during onboarding by hiding these elements.</p><p>After Pinterest has their users hooked, it can now ask them for more. See the ‘Enable desktop notifications’ banner for returning users?</p><p>It’s smart for Pinterest to ask for things like this once a user is already engaged in order to try and <a href="https://www.appcues.com/blog/increase-user-engagement">drive further engagement</a>.</p><p>Josh Elman, the host of the <em>Greymatter</em> podcast from which many of these lessons were first shared, refers to this approach as ‘<a href="https://medium.com/@joshelman/building-your-growth-model-and-ladder-of-engagement-3b3a18f2d1a8">the ladder of engagement</a>.’</p><p><em>Originally published at </em><a href="https://www.appcues.com/blog/casey-winters-pinterest-user-onboarding/"><em>www.appcues.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=639fcc7486d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appcues/casey-winters-reveals-how-pinterest-perfected-user-onboarding-639fcc7486d7">Casey Winters Reveals How Pinterest Perfected User Onboarding</a> was originally published in <a href="https://medium.com/appcues">Appcues</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts On Hiring a Writer for Appcues]]></title>
            <link>https://medium.com/@tymagnin/thoughts-on-hiring-a-writer-for-appcues-46e44b167923?source=rss-173a4ca6df93------2</link>
            <guid isPermaLink="false">https://medium.com/p/46e44b167923</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[content-marketing]]></category>
            <dc:creator><![CDATA[Ty Magnin]]></dc:creator>
            <pubDate>Wed, 07 Sep 2016 15:08:56 GMT</pubDate>
            <atom:updated>2016-09-07T15:08:56.600Z</atom:updated>
            <content:encoded><![CDATA[<p>Jackson Noel, Co-founder, brought me on to Appcues as our first focused marketer in July 2015. He had already brought our blog from 0 to about 4k monthly unique visitors. He did this by creating the <a href="http://www.appcues.com/user-onboarding-academy">User Onboarding Academy</a> and hustling the Appcues story around the web. Jackson hired a content marketer to pass the torch on a channel he was convinced would help Appcues gain momentum, so he could focus on other initiatives.</p><p>When I took over, my main objective was to grow our top of the funnel. over the next 6 months, I lead the charge to 20k monthly unique visitors, and built a process in place for creating solid content and growing our blog audience. We’re at the point now where we want to bring in help to continue to grow this audience. We want them to take it over from me. I’ll spend my time experimenting with other channels for acquisition and working further down our marketing funnel.</p><p>So the next person we want to come onboard should be interested in growing us from 20k uniques to 200k and beyond. That’s the mission.</p><h3>Avoiding burnout; an opportunity</h3><p>We’ve heard from many marketers that we’ve talked to about this role, that there’s risk of burnout when you hire someone to focus on writing. I’ve definitely experienced the threat of burnout myself. However, The best way I think to handle this is by thinking of this role as writer =&gt; editor for the right person. Yeah you’re going to write a lot in your first 3 months. But more and more I get people interested in contributing to the Appcues blog. I hope we can be like KISSmetrics of ConversionXL in few years from now. So good that other writers want to contribute with frequency for free.</p><p>And further, by appropriately aligning our company mission of helping people make products users love, we can broaden the scope of our content over time to include our other thoughts and stories to appeal to our ever growing audience over time. It may not make sense to speak in those terms today, however, as we do better to be focused on more specific topics. But look at <a href="http://t.umblr.com/redirect?z=http%3A%2F%2Fwww.helpscout.net%2Fblog%2F&amp;t=NzExYjY3NWM1NmMwZDljZjUwYzgzNDk3NTIxZDY0ZjUwMTIxNTg4Niw2UFNFV1JxMA%3D%3D">Help Scout’s blog</a>. We will get there.</p><p>Another way I think writers can avoid burnout is by involving a lot of networking into their process. This happens naturally as a content marketer developing stories, and I’ve found it helps improves a writer’s craft, enriches their content and increases their influence/distribution. A nice side-effect of networking is an increase in worth to one’s personal brand, which our team members will take with them when they graduate from Appcues.</p><h3>Describing our ideal candidate</h3><p>As Jackson and I chatted more about the opportunity, we laid out what the necessary strengths for our ideal candidate might be, and we also listed out what weaknesses we might tolerate. We then tested these ideas against other sources. I spoke with multiple writers on these subjects, I got a ton of feedback on <a href="http://t.umblr.com/redirect?z=https%3A%2F%2Finbound.org%2Fdiscuss%2Fwhat-are-some-lessons-you-ve-learned-from-hiring-full-time-writers&amp;t=NDg2MDczMzIyYTkxZWJhNjRiMGNlOTI2ZmExOTJhOGVlMDcwZTdkNiw2UFNFV1JxMA%3D%3D">this inbound thread I started</a>, and I pulled from <a href="http://t.umblr.com/redirect?z=http%3A%2F%2Fwww.gregoryciotti.com%2Fnew-content-hires%2F&amp;t=ZmNhNzIzYTViMjczNGIzMTQ3YzU3YTJlZDRjMGVhMDVkZmU0NzVhYiw2UFNFV1JxMA%3D%3D">Greg Ciotti</a> and <a href="http://t.umblr.com/redirect?z=https%3A%2F%2Finbound.org%2Fblog%2Fhow-to-hire-great-content-marketers&amp;t=ODg3Yjc4NWI1NzhkYjJhZWUxODRlYWZmMDMzMzc1OTcxNjExM2Y4OCw2UFNFV1JxMA%3D%3D">Walter Chen</a>. Many thanks to everyone who lent us a hand!</p><p>Here’s what we ended up with:</p><p><strong>Strengths</strong></p><ul><li>Has clear idea of their writing process</li><li>Knows that good writing is grounded in facts and examples</li><li>Journalistic in their approach</li><li>A storyteller with a high creative output</li><li>Doesn’t compromise on quality</li><li>Hungry with the initiative to drive endless rapid growth</li></ul><p><strong>Tolerable weaknesses</strong></p><ul><li>Lack of domain expertise; but should be excited about software and products</li><li>Lack of distribution process or channels — we do this well today</li><li>Can be a writing specialist; doesn’t need design or video — we have those chops in-house already</li><li>Doesn’t need a network, but has to be open to hustling and have networking skills</li></ul><h3>Getting people interested in the position</h3><p>I’m all for engaging people organically as possible as we build a process. We believe in our networks and our audience, and we believe we can likely surface the right talent from there. At this stage in our growth, we’ve found that job boards are often a waste of time at this stage in our growth. So we’re taking referrals from the team, friends and customers as we chat casually about the company or specifically about hiring processes.</p><p>We’re driving interest as we research for the right candidates. A secondary motive to starting <a href="http://t.umblr.com/redirect?z=https%3A%2F%2Finbound.org%2Fdiscuss%2Fwhat-are-some-lessons-you-ve-learned-from-hiring-full-time-writers&amp;t=NDg2MDczMzIyYTkxZWJhNjRiMGNlOTI2ZmExOTJhOGVlMDcwZTdkNiw2UFNFV1JxMA%3D%3D">the Inbound thread</a> was to try and get some interest. As is this blog post here.</p><p>Soon — if we have to — we’ll start diving deeper into our networks and ask for introductions to Boston companies that have people succeeding in similar roles. Ahem, I’m looking at you Wordstream…and HubSpot…and InsightSquared.</p><p>My hope is that anyone who knows someone will refer them to the company. And they will figure out an easy way to get in touch with me. *Cough* <a href="http://twitter.com/tymagnin">Here’s a link</a> *Cough*</p><p><em>Originally published at </em><a href="http://tymagnin.com/post/139800958926/thoughts-on-hiring-a-writer-at-appcues"><em>tymagnin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46e44b167923" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Opening Our Books on the Recent Website Redesign]]></title>
            <link>https://medium.com/@tymagnin/opening-our-books-on-the-recent-website-redesign-4ffe84a2da24?source=rss-173a4ca6df93------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ffe84a2da24</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[redesign]]></category>
            <dc:creator><![CDATA[Ty Magnin]]></dc:creator>
            <pubDate>Thu, 21 Apr 2016 15:16:24 GMT</pubDate>
            <atom:updated>2016-04-21T15:16:24.555Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s never obvious when the right time is to roll out a new website redesign. But it’s true that design trends change and companies evolve and their marketing website should reflect that.</p><p>We just rolled out a redesign at <a href="http://t.umblr.com/redirect?z=http%3A%2F%2Fwww.appcues.com&amp;t=ZGYwOGU3ZjA4ZDczZTMzYjE3NzI1ZjE3MTQ4ZDg5MzllZDVjYzhkYixNR1pMT2ttcQ%3D%3D">Appcues</a>, and I thought I’d lay out some of our reasons why.</p><h3>TIMING</h3><p>We always knew our website could use a revamp, but we weren’t sure when the ideal time would be. Soon after we hired our first designer, <a href="http://t.umblr.com/redirect?z=https%3A%2F%2Fdribbble.com%2Fdonnywilson&amp;t=YTczMGVhMWU5MGQ4YzJjMDc5Yzk5NTAyZDI0OGMxODlhYzQ0YjUwOCxNR1pMT2ttcQ%3D%3D">Donny Wilson</a>, in November last year, it became obvious that the time was now.</p><p>A few weeks in, Donny had rolled up his sleeves and redesigning many of our brand assets, he’d made our content look a hell of a lot better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*U7x1e0gLOVEKQh6C.gif" /></figure><p>Donny has a strong marketing background. He worked for the last 3 years at <a href="http://t.umblr.com/redirect?z=https%3A%2F%2Fwww.impactbnd.com%2F&amp;t=NGVmZTUxY2ZmYjA4ZDU4OTEzNGQwODc5NWIyNjkwZThmYTY2MzFiNyxNR1pMT2ttcQ%3D%3D">Impact</a>, a marketing design firm that we ended up contracting for the coding part of the project…so, naturally, he was interested in the project. Trusting in his experience with the website redesign process, we went ahead and broke ground by laying out a project plan in early December.</p><h3>BRAND</h3><p>In our eyes, our brand outgrown its website. We received well over 20k unique visitors in December and our homepage — from top to bottom — looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*bdRkxi0LvAj-0uyj.jpg" /></figure><p>Our biggest qualms with our homepage was that it didn’t capture enough of who we are or what we do, and we felt like — for better or for worse — people were just signing up to figure out what the hell our product was all about.</p><p>Our new homepage design hopefully does a significantly better job at telling our story, while still providing a strong CTA to test our product out. Instead of showing you here, I encourage you to check it out: <a href="http://t.umblr.com/redirect?z=http%3A%2F%2Fwww.appcues.com&amp;t=ZGYwOGU3ZjA4ZDczZTMzYjE3NzI1ZjE3MTQ4ZDg5MzllZDVjYzhkYixNR1pMT2ttcQ%3D%3D">www.appcues.com</a>.</p><p>…gone are the days of our blatantly scrappy selves. *Sigh*</p><h3>SEO</h3><p>We’ve been focusing more and more on keywords and search opportunity as we’ve gained domain authority — from 30–40 — over the last 6–8 months. It was obvious to me that we weren’t doing enough around keywords other than “user onboarding” which only encompassed a part of what we do.</p><p>We decided to organize our subpages around these use cases rather than features as most software companies do it. This was not only to gain the SEO opportunity from keywords such as “customer engagement” and “feature adoption,” but also because we believe our prospects prefer the experience of browsing by how they can apply the product — think <a href="http://t.umblr.com/redirect?z=https%3A%2F%2Fstrategyn.com%2Fjobs-to-be-done%2F&amp;t=Mzg2N2JhM2NlZDhhY2U4YTQ1YzEyNTVmOWRkMmMxZjNmYTM1NmZiMSxNR1pMT2ttcQ%3D%3D">jobs to be done</a> — rather than by the features that may or may not help them get there.</p><p>Because Customer Engagement is first and foremost more encompassing of the use cases Appcues can be applied to, we decided this was a better way to go. Additional reason involved the far greater search opportunity around the term “Customer Engagement” in comparison to “User Onboarding.”</p><h3>JEKYLL VS HUBSPOT</h3><p>Although I am a marketer with coding chops, some of the things I was doing to simply get a blog post live might not scale well. Our previous marketing website and blog was built with Jekyll and requires a form of Liquid and Markdown for all kinds of content. Each update and edit required a deploy via Github. Here’s what the top of a given post might look like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*uQtBzw55oheHYQzT.jpg" /></figure><p>Coding and deploying a blog post from google doc to production often took me over an hour, and it would be even more difficult for a non-technical person to do it. This time adds up.</p><p>Now we can simply copy and paste whole blog posts into HubSpot and set them to publish at a certain time. How nice is that?!</p><h3>WHERE WE CAN STILL IMPROVE</h3><p>Although we’re happy with our new marketing site, there are a few pieces we didn’t get published with v1 of the site. On our use cases page for example, instead of images to illustrate each sub use-case, we want to implement an interactive demo via when a user clicks ‘See it in action’ … right now the button pulls the user down to the sign up CTA.</p><p>We’d also like to reduce our signup CTA form fields from three to either two or zero fields. That’s something we plan to experiment with as we redesign our user onboarding process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*gnijt5vZc1jp1CZm.jpg" /></figure><p>In order to get a v1 out in time, we reduced our scope by eliminating our feature pages. We still have to get those out there to help further illustrate what you can do with Appcues. Here’s a sneak peak:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*BqZgMA0RXqNu4hQE.jpg" /></figure><p>Surely there are many other ways to enhance our website’s language and conversion rates by gaining feedback and running tests. We hope to collect that data and iterate over time. If you want to contribute your two cents, please do below.</p><p><em>Originally published at </em><a href="http://tymagnin.com/post/139507246086/opening-our-books-on-the-recent-website-redesign"><em>tymagnin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ffe84a2da24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crowdsourced Copyediting]]></title>
            <link>https://medium.com/@tymagnin/crowdsourced-copyediting-952241ddcb13?source=rss-173a4ca6df93------2</link>
            <guid isPermaLink="false">https://medium.com/p/952241ddcb13</guid>
            <dc:creator><![CDATA[Ty Magnin]]></dc:creator>
            <pubDate>Wed, 20 Nov 2013 15:39:15 GMT</pubDate>
            <atom:updated>2013-11-20T16:08:40.435Z</atom:updated>
            <content:encoded><![CDATA[<h4>Never Sweat Pressing Publish Again</h4><p>You know that moment of uncertainty when you click “send” on an important email that you haven’t proofread? Or worse, you publish a blog post without that “left it all on the field” level of confidence? Maybe it happens at the end of a long day. Or when you think you are multitasking, but you are really just doubled up on coffee and fumbling between distractions.</p><p>I know. I’ve been there—as has probably every one who regularly creates content. But guess what? There’s a method for overcoming that bout of doubt the second after you click publish—consider crowdsourced copyediting.</p><p>This practice furthers traditional peer edits by leveraging your networks of trusted peers, engaged readers and your broader audience. It has saved me time and helped me create better content through the years. I never publish anything without discussing it with several interested parties first. This process saves me <a href="http://www.bakadesuyo.com/2013/06/increase-willpower/">decision time</a>, and it helps me build on relationships of all types. Here’s how it works:</p><p><strong>First publication: trusted peers</strong></p><p>Your most trusted audience is most likely your colleagues, peers and mentors. Share your content with them first.</p><p>You can expect your most trusted copyeditor to read your content at a high level for form, tone and purpose. From experience, I’ve learned that those closest with you read your content with a wider lens, meaning they are more interested in how it fits into your story or your company’s story than how much sense it makes or how powerful it is.</p><p>I’m not condoning handing your trusted peers a <a href="http://shitroughdrafts.com/">sloppy first draft</a>, but getting them involved in the earlier stages of writing is generally a good idea. There’s nothing worse than working hard on something only to trash it later because it didn’t serve the right purpose or uphold your brand’s image.</p><p><strong>Second publication: interested clients</strong></p><p>Leverage your closest clients/early adopters. They are already deeply engaged and will have conversations around the subject matter of your content. Why not crowdsource feedback further and push your next content to them before everyone else?</p><p>Content often comes from customer interactions. Wouldn’t that same customer be flattered that they inspired a blog post? I’m sure they would have something more to say on the topic, and you may have more to learn!</p><p>Read between the lines when receiving feedback about a publication. It’s not always what your audience says about your writing, it’s often what they don’t say.</p><p><strong>Third publication: general public</strong></p><p>Your general audience will be able to appreciate your content for what it’s worth. They will digest your brand, purpose, and subject matter. If you do it right, your audience will feel engaged in all of the conversations you had around your content.</p><p>Additionally, your widest audience will review your content for effective SEO (did they find it effectively), for strong call to actions (did they end up where you wanted) and help you write more effective copy next time.</p><p>There you have it—the three steps to crowdsouce you copyediting. I am sure that this art can become increasingly granular in its steps over time, so as we content markets engage this practice further, let’s share our findings for best practices.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=952241ddcb13" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>