<?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 Jen Granito on Medium]]></title>
        <description><![CDATA[Stories by Jen Granito on Medium]]></description>
        <link>https://medium.com/@jengranito?source=rss-70420259569a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*eYZAOCReQHXAftaj.jpg</url>
            <title>Stories by Jen Granito on Medium</title>
            <link>https://medium.com/@jengranito?source=rss-70420259569a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:37:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jengranito/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[Are We Product Managers or Problem Managers?]]></title>
            <link>https://medium.com/@jengranito/are-we-product-managers-or-problem-managers-a53f4fc91858?source=rss-70420259569a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a53f4fc91858</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jen Granito]]></dc:creator>
            <pubDate>Wed, 27 Jan 2016 09:24:06 GMT</pubDate>
            <atom:updated>2017-03-21T07:17:17.234Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/379/1*GIdgvg4XPOVSQ8Et3uvxRw.jpeg" /></figure><h4>Problems should be the foundation of product development</h4><p>We’ve all been to those planning meetings where the conversation starts to go on a tangent and the team starts suggesting ideas that don’t actually solve the problem that you started talked about. I like to call them headless ideas. And as the person leading the meeting, you have to go into damage control. It starts with a delicate dance of slowing the current momentum &amp; corralling the conversation back to the problem.</p><p>Why and how does this happen? <strong>So much of product management glorifies coming up with great ideas and giving feedback</strong>. Also the wider you go in the organization combined with the closer you get to the pixels; the more feedback you’re going to get.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*5uXIMGw8WYWfX7vg34zSCg.jpeg" /></figure><p>The best arsenal you can have is to be armed with a clear problem. Problems are at the core of product development. You need to know what you’re solving and <em>who</em> you’re solving it for. <strong>Problems should be scrutinized over even more than the features or solutions that would solve them.</strong> If you don’t get the problem definition right, you’re putting the cart before the horse and everything that comes next is probably wrong.</p><p>You want your problems to beget effective solutions. Then be lean about executing solutions aimed at solving the problem. Otherwise you’re just shipping ideas or solutions to problems that your customer might not care about.</p><blockquote>Otherwise you’re just shipping ideas or solutions to problems that your customer might not care about.</blockquote><h4>Some problem statements</h4><p>Problem statements should be from the user’s point of view. Often times we get trapped by stating a problem that the business has; which can lead to a lack of market. Let’s look at a few examples where I take a guess at the problem statements related to features:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/120/1*lR0nTCTjFhVE6tbfn9wgwA.jpeg" /></figure><p>Facebook newsfeed — “I don’t have an easy way to see what all of my friends are doing without going to each of their profiles separately which is inefficient”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/175/1*N4t3AQNo7uC02zaQhC_H7w.png" /></figure><p>Nest smoke detectors — “I hate the annoying chirp my smoke detector makes when the batteries are dying.” or “I wish Nest adjusted the temperature for the rooms that I’m in and worried less about ones I’m not in” Since your thermostat is usually only in one room of the house, the smoke detector aims to solve that problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/144/1*yOI0fFbQl-jRdZCfHwRAEw.png" /></figure><p>Asana — Let’s be clear. I ❤ Asana. When they redesigned their service to be “<a href="https://blog.asana.com/2015/10/teamwork-is-beautiful-introducing-asanas-new-look/">beautiful</a>” I imagine they took a page from Slack and stated the problem as “Project management isn’t fun.” I’m not sure how user centric the problem statement could have been, which is why I’m not sure it was worth the investment. I’m truly curious what kind of incremental gains they are seeing.</p><p>I’ve noticed more people talking about this approach recently; <a href="https://medium.com/u/1b5561d847">Nils Davis</a> at Innotas wrote about <a href="https://medium.com/all-the-responsibility-none-of-the-authority/love-the-problem-not-the-product-21d7ab6152a0#.qxjqvbe06">loving the problem, not the product</a>. <a href="https://medium.com/u/d3b1190c0b5d">Marc Anthony Rosa</a>, product creator at <a href="https://medium.com/u/245d5483fb27">Buffer</a>, mentions that <a href="https://blog.bufferapp.com/product-creation-a-bufferchat-recap">every great product solves a painful problem</a>. <a href="https://medium.com/u/ff8cbec9c449">Sean Shadmand</a> talks about <a href="https://t.co/IDIQATwRUc">tough vs. hard problems</a>. Probably because there are lots of things that go into curating a good problem: how your company handles product development planning, how you structure your company, how you handle incoming feedback, how you talk to users about that feedback. In this piece, I’d like to start a conversation about at least two.</p><h3>How to structure your company</h3><p>In my experience as a product manager at companies like LinkedIn, AOL Instant Messenger, and currently at <a href="https://medium.com/u/5f8bd3117f0b">Kifi</a>; you’re required to wear a handful of hats under the product manager title. They include but are not limited to: product mgr, project mgr, QA tester, marketer, business development manager, front end engineer, analyst, &amp; customer service representative. Teams generally consist of 8 engineers, 1 PM, and then half a designer, a quarter of a QA, and a tenth of a customer service representative.</p><p>A few months ago I had a fantastic conversation with <a href="https://medium.com/u/cbea485fd64d">Jackie Bavaro</a>, PM at Asana and Co-Author of “<a href="http://www.amazon.com/dp/0984782818">Cracking the PM Interview</a>” about how product and design roles are managed at <a href="https://medium.com/u/4fecc4c082c">Asana</a> ….. and it was unlike any company I had ever worked at.</p><p>Jackie mentioned that the company has 4 product managers and around 12 designers. WHAT?! A 1:3 Product Manager (PM) to Designer ratio?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/303/1*Dx9t9vl8BhyZYNChAh9PIA.jpeg" /><figcaption>Whoa Whoa — it takes me a while to do math. Is that a 1:3 PM to designer ratio?</figcaption></figure><p>With only 4 product managers in a 200 person company, all of them are generalists. But still …. 4 PM’s at that large of a company? How was their product development process different from other companies? How do they manage to stay ahead of engineers? Jackie explained that <strong>product managers are responsible for thoughtfully &amp; strategically curating the problems that need to be solved</strong>. Then <a href="https://pmblog.quora.com/How-to-Work-with-Designers">bring the problems to your designers</a>; not solutions, not wireframes or feature ideas - hand them a clear, thoughtful problem. Designers,then, focus on ideas or features that serve as solutions to those problems. PM’s are stakeholders in selecting which solutions becomes features, but ultimately the majority of the details of feature development are directly in the hands of design and engineering.</p><blockquote>Bring your designer problems; not solutions, wireframes or feature ideas.</blockquote><p>When I first heard this, I thought that it was a little unnecessary to have that much focus on prioritizing problems. Can every new product innovation be defined by a problem? Who’s problem do you solve; a user’s or the companies? Can you really fill up a day thinking about problems? How can you let go of the “fun” part of product management which is coming up with great ideas? But the more I started thinking about it, the more it made <em>a lot</em> of sense. I think it can be broadened a bit to say <strong>bring your “team” problems. Make sure all major players, including yourself, are a part of the solution brainstorming and selection.</strong> But this set up gives everyone more autonomy and in theory gets higher quality gets creativity around your biggest problems and goals.</p><h3>How to make problems central to your product development process</h3><p>Not every company is at the size Asana is so you can’t afford to have product managers solely dedicated to problem identification. Here are a few areas of product development and daily life as a PM where focussing on the problem can help:</p><h4><strong>Getting to the MVP</strong></h4><p>We were building a feature within <a href="http://kifi.com/">Kifi</a> in which users <a href="http://blog.kifi.com/introducing-kifi-teams/">create a team</a>. Of course we struggle with when to release it vs adding in just a couple more features. One of the areas that was a hot topic of debate was around making it easier for people to get their coworkers to join the team.</p><p>Lots of companies have team like infrastructure on their site like Trello, Github, <a href="https://medium.com/u/98dc6895fb5e">Quip</a>, <a href="https://medium.com/u/2d2c8f4cb281">Dropbox</a> and Asana. So every single team member had opinions on how Kifi should do it. We should create a URL with an auth token that people can paste it in their company chat [Dropbox]. Build email domain mapping so that when people join Kifi using their company mail, they are automatically put on their company team [Quip]. We should redesign the invite email to be simpler [Asana].</p><blockquote>All of these are great ideas, but they solve COMPLETELY different problems.</blockquote><p>I took a step back and realized that all of these are great ideas that would certainly help improve team density, but they solve COMPLETELY different problems if a user was describing the problem(s) to us. <strong>When you’re nearing the finish line &amp; dealing with scope creep, it’s helpful to have a clear problem that you can revisit whenever something gets thrown your way.</strong></p><p>What was the user’s problem? “I don’t know how or why to invite my teammates” (% team owners inviting). “It’s too much work to send invitations to my entire team of 25+ people” (invites / inviter). “My coworker never got the email” (invite CTR). “Someone told me to join Kifi over lunch and now I can’t find my team” (# of users joining a team on Day 2+). Each of these problems would lead to different features and save wasted feature development cycles.</p><p>Fortunately I work with a great team of engineers at Kifi that I can often hand the problems too and they return with great solutions.</p><h4>All brainstorms should start with discussion about the problem</h4><p>Whenever you go into a brainstorm, there are rules like: <em>Don’t critique other’s ideas. It’s about quantity not quality. Don’t edit other ideas, build on them.</em> But that can be difficult and unproductive when you feel like the ideas aren’t solving a problem that your company has or that user’s will even care about.</p><p>Brainstorms should start with a clear problem that you’re trying to solve. Use the problem as a litmus test for the ideas coming out and refer to it when you think it will help get more actionable ideas to be discussed.</p><h4>1-off ideas in the hallway</h4><p>If you still don’t think you’re a problem manager, think about all the times you’ve had random ideas are thrown at you from summer interns to the CEO. It’ll happen when a competitor releases a new feature, when the CEO comes back from holiday break &amp; when customer support forwards on some awesome user feedback. Anytime someone comes to you with an idea, try responding with “What problem is this solving?” Getting other people into this frame of mind means that they next time they come back to you, they’ll already have this answered.</p><p>When you start evangelizing and advocating for <em>problems</em> you enable more autonomy throughout more roles in your team. From every angle you’ll get higher quality ideas from allowing a wider variety of roles within the company (customer service, engineering etc.) to <strong>successfully join in on those “fun parts” of product development like idea generation</strong>.</p><p>So much of our job gets described as coming up with ideas &amp; building features. The irony is that we’re the gatekeepers that need to say “no” more often than we’d like. We should talk more about how important identification of problems is to every aspect of our job and those of the people that we work alongside.</p><p><em>Many thanks to </em><a href="https://medium.com/u/c3903b20f918"><em>Vaibhav</em></a><em>, </em><a href="https://medium.com/u/bb0d522e7e9c"><em>Léo Grimaldi</em></a><em>, </em><a href="https://medium.com/u/9531da00d4f1"><em>Benjamin Lederer</em></a><em>, and </em><a href="https://medium.com/u/7c786946ce5a"><em>Scott Ruffner</em></a><em> for fantastic feedback on this post.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a53f4fc91858" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What We Learned Launching on the New Slack Platform]]></title>
            <link>https://medium.com/on-the-same-page-with-kifi/what-we-learned-launching-on-the-new-slack-platform-b87fec100d62?source=rss-70420259569a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b87fec100d62</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Jen Granito]]></dc:creator>
            <pubDate>Wed, 20 Jan 2016 19:34:14 GMT</pubDate>
            <atom:updated>2016-01-22T02:38:39.470Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PJHbO6UfE9Fsi00LaqLzcw.jpeg" /></figure><p>Have you ever felt the pain of scrolling through hundreds of chat messages, looking for a link that someone posted a couple days earlier? Or turned around and asked your colleague to resend it?</p><blockquote>“Where was that link Mike sent via Slack 3 days ago about our competitor’s new feature?”</blockquote><p><a href="https://medium.com/u/26d90a99f605">Slack</a>’s recent launch of the <a href="https://slack.com/apps">app directory</a> enabled us to make this pain point go away for thousands of our users and Slack’s. The directory allows companies like Kifi to build apps with additional functionality on top of Slack. Slack and Kifi users get even more out of both services.</p><p><strong>Perfect Pair</strong></p><p>Kifi captures links shared within Slack channels &amp; automatically saves or “Keeps” them in dedicated Kifi libraries. We create a full-text index of every page shared, making it easier to search and find those links within Slack or even within Google search, using our browser extension.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*53jdl934rkMsi_m0dDWsjw.png" /></figure><p>Your Google search results will bring you right back to the part of the conversation in your Slack channel where your teammates were talking about the link. We focused on the <a href="https://medium.com/on-the-same-page-with-kifi/a-roadmap-to-the-apps-that-will-make-you-more-productive-at-work-1c80df16dc72#.netw4wrzt">ease of its integration</a> and paid attention to the details. One of our users, Scott Williams of Greensboro, N.C.. marketing agency <a href="http://www.emisare.com/">Emisare</a>, which is known for its guerilla marketing techniques and its smart approach to building an application portfolio, told us that he noticed the integration when slack hashtags started appearing in his libraries. Then he realized libraries were corresponding with Slack channels. “The thing that I really like that other Slack integrations don’t offer is the granular level of customization. Bi-channel and bi-directional options are really, really cool (useful).”</p><blockquote>“Bi-channel and bi-directional options are really, really cool (useful).”</blockquote><p>Dennis Lysenko, <a href="http://riff.us/">Riff Digital Inc.</a> “As a developer, the Kifi slack integration lets me easily find that one stackoverflow link in a sea of hundreds that I sent to another developer. I don’t even have to break my googling habit, because it integrates seamlessly into google search results too.”</p><blockquote>“I don’t even have to break my googling habit, because it [Kifi] integrates seamlessly into google.”</blockquote><p>On the heels of a successful launch on Product Hunt, the <a href="https://medium.com/u/272cd95a3742">Slack API</a> team <a href="https://medium.com/slack-developer-blog/the-slack-app-directory-checklist-e3f3ba0ca7c5#.i5dt2xr9e">featured us</a> as one of their top integrations. We found out how much power Slack’s new platform has when we saw close to a 5x increase in the number of Kifi teams being created. Some of our new community members came from Betaworks, Cloudera, Comscore, even some from non-company communities on Slack like <a href="http://www.productmanagerhq.com/">Product Manager HQ</a>. You can imagine that on average hundreds of links would be imported from your # slack channels on Day 1; in some cases thousands. A handful more continue to come in each #channel per day. Multiply this by a year and it’s not hard to see that you can easily get up to 10,000 links within your Slack team, mixed in with order(s) of magnitude more chat messages. Sound like a lot? This is where Kifi comes in to manage that for you :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*CnnhOqbLWp7ff5H9.png" /></figure><p>We’re starting to see Slack as an operating system for your organization’s communication. Now, we’re doubling down on our investment in the Slack platform. In the coming weeks you’ll see features that make the integration between Kifi and Slack easier for our team admins and members can bring conversations about pages directly on the page with “same page chat”.</p><p>As always, your feedback is much appreciated!</p><p><em>Originally published at </em><a href="http://blog.kifi.com/slack-featured-kifi-top-integration-learned-lot/"><em>blog.kifi.com</em></a><em> on January 20, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b87fec100d62" width="1" height="1" alt=""><hr><p><a href="https://medium.com/on-the-same-page-with-kifi/what-we-learned-launching-on-the-new-slack-platform-b87fec100d62">What We Learned Launching on the New Slack Platform</a> was originally published in <a href="https://medium.com/on-the-same-page-with-kifi">On the Same Page with Kifi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Where The F*&* Did I Put That Link? Answers To A Modern Dilemma]]></title>
            <link>https://medium.com/on-the-same-page-with-kifi/a-roadmap-to-the-apps-that-will-make-you-more-productive-at-work-1c80df16dc72?source=rss-70420259569a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c80df16dc72</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Jen Granito]]></dc:creator>
            <pubDate>Mon, 18 Jan 2016 18:42:41 GMT</pubDate>
            <atom:updated>2016-01-18T19:37:23.413Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been thinking about the problem of knowledge management in the workplace for half a decade. In 2007, I launched the initial beta for the news product at LinkedIn, alongside <a href="https://medium.com/u/82d78646a743">Eishay Smith</a> and Allen Blue. LinkedIn was trying to help companies stay better informed about web content or news related to the company itself, their competitors &amp; industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*N0lcPLLCfOUIhbT4." /></figure><p>To make it work for companies, we needed to make it work for employees. We created a space for users to interact with their coworkers on LinkedIn. We used a bit of data to target the news. We enabled users to comment on articles, thinking they’d value the space we’d created to discuss relevant news among coworkers. Learning, really acquiring knowledge from the mass that is out there, requires interacting with it.</p><p>But we found people weren’t coming to LinkedIn frequently enough to develop meaningful conversation and insights around news. News articles have a shelf life of about 36 hours, and that wasn’t enough time for us to get good feedback &amp; data on the stories we served. I became aware then of how fast knowledge sinks in the ocean of the Web.</p><blockquote><em>I became aware then of how fast knowledge sinks in the ocean of the Web.</em></blockquote><p>Fast forward five years. Eishay and I are back together at Kifi. I’m still working on the same problem, but I learned a lot in the five years between LinkedIn and now. One of the most important lessons: <strong>When it comes to disseminating knowledge within an organization, the biggest idea is context.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/0*bZdAs4wmeHtNJTha." /></figure><p>Reid Hoffman always said that people will only visit 3–5 sites self-directed every day. Consider that email, Facebook and Google are in most people’s top three, then you have two chances to crack the top five …. and there are millions of fantastic services vying for those two spots. Therefore, you either have to convince the user to create a new habit or you have to bring context to where the user is when they need you. On the web, that means being integrated into the tools that people already use and developing a hyper-intuitive user interface.</p><p><strong>Knowledge Management is Evolving</strong></p><p>The knowledge management space has evolved a lot, too, in recent years; it’s become a lot broader. On one hand the problem has gotten much worse, because the volume of information is much larger. The total number of websites recently passed 1 billion…. with a “b”.</p><h3>Tim Berners-Lee on Twitter</h3><p>http://t.co/D9pwMXuZOa recently passed a billion websites by their count....</p><p>Every minute on the web, Facebook users <a href="http://blog.capitalogix.com/public/2015/06/this-happens-in-an-internet-minute-the-astounding-growth-of-web-content.html">share 2.46M pieces of content</a>. Here are a few more stats:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/1*Nu1ehZbTi_MMH5Br0ZliwQ.jpeg" /></figure><p><strong>On the other hand, there are more people working on it. </strong>Companies like <a href="https://medium.com/u/26d90a99f605">Slack</a>, <a href="https://medium.com/u/cc5554e706bb">Evernote</a> and <a href="https://medium.com/u/b5a5b138d42f">Yammer</a> have entered the space, and companies like LinkedIn and GitHub do it as an extension of their main functions.</p><blockquote><em>…the problem has gotten much worse, because the volume of information is much larger… but more people are working on it</em></blockquote><p>I find people looking for knowledge management tools in four broad areas. They want products to help them manage:</p><ol><li><strong>Files</strong> Lots of internal knowledge is maintained and shared via files such as documents, spreadsheets, presentations &amp; wikis.</li><li><strong>Messages</strong> Including chat and email, messages are a usually more informal and real-time means of disseminating information via chat or email. <strong>The kind of knowledge that lives in messages has so far resisted easy management</strong>.</li><li><strong>Role specific tools</strong> More structured records of a company containing knowledge used primarily by a particular division such as a CRM for sales or support, or budgeting &amp; tracking software for accountants</li><li><strong>Web content</strong> Research and articles that sometimes include metaknowledge, which means someone has highlighted, summarized, organized/tagged, and shared the knowledge within the organization.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xbYiNhn2-qBmnf93VF7vug.png" /></figure><p>Most companies are primarily focussed in the first three buckets, probably because the majority of knowledge captured and shared within companies, has traditionally been employee-generated content.</p><p>Web content has even has been blocked by larger companies; but that has been changing as organizations are more comfortable letting content in &amp; and using SaaS services. And companies in our space are responding. Slack, for instance, started out with a focus on messaging; chat directly with coworkers or in topic specific rooms. With regard to web content, when a link is messaged Slack unwraps it &amp; displays it beautifully. However as evidenced by the <a href="https://slack.com/apps">release of the app platform directory</a> and <a href="http://techcrunch.com/2015/12/15/trophy-emoji/">$80M in funding</a> for their app developers; Slack has opened the door to other areas of knowledge management, including web content, and I’m proud to say Kifi is a top integration on the Slack platform.</p><p>Web content, that great, free-form, unruly mass of information that’s the playing field where I think — and I know I’m not alone — is where best, fresh ideas come from. We try lots of things at Kifi to help people manage knowledge on the Web.</p><p>One of the most successful building blocks of our service, and the one that people talk about a lot, is our integration with Google, now coupled with our <a href="https://www.kifi.com/integrations/slack">Slack integration</a>.</p><blockquote>Simply by searching on Google, I saw that our engineers had been talking about it on Slack in a channel.</blockquote><p>A couple weeks ago I was researching some API documentation as I spec’d out <a href="https://slack.com/apps/A0F0XEP2A-kifi">Kifi’s new Slack integration</a>. Simply by searching on Google, I saw that our engineers had been talking about it on Slack in a channel I don’t pay heavy attention to. I was able to click right from Google Search and was brought to the part of the conversation they had been chatting. This saved my time by validating that this was the page I was looking for &amp; and my engineer’s time because I didn’t interrupt them to get their thoughts on the subject now that I could read the slack archives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sIoSZPIUind1o0Zz2llqWQ.png" /><figcaption>Get right back to <em>where</em> people were talking about a link from Google Search Results</figcaption></figure><p>That’s the difference between having to remember to visit a site with an ever growing stream of facts … <strong>and unveiling nuggets of real knowledge in a helpful and meaningful context</strong>, such as when you land on a page your coworker kept as you browse the web.</p><p>So this time we’re trying to solve the knowledge management problem on the Web. We’re creating a service that is easily and intuitively available to you whenever you need it, integrated in your work flows, contextual, meaning it helps capture many levels of knowledge and information, and interactive, so that you can add whatever you need to.</p><blockquote>The same reason managing knowledge within web content is hard — the sheer volume of information on the Web — is the same reason it’s important.</blockquote><p>I fell into knowledge management for the Web when I was at LinkedIn. Now, I think of it as one of the most important problems online today. The same reason it’s hard — the sheer volume of information on the Web — is the same reason it’s important. It’s tempting to close the door on all that knowledge sometimes, declare bankruptcy or retreat into smaller spaces, like the social media networks you like or your company’s intranet. But the wide world of the Web is where most of the best knowledge lies. We just need to be able to manage it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c80df16dc72" width="1" height="1" alt=""><hr><p><a href="https://medium.com/on-the-same-page-with-kifi/a-roadmap-to-the-apps-that-will-make-you-more-productive-at-work-1c80df16dc72">Where The F*&amp;* Did I Put That Link? Answers To A Modern Dilemma</a> was originally published in <a href="https://medium.com/on-the-same-page-with-kifi">On the Same Page with Kifi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Learnings & Stats from Kifi’s Launch on Product Hunt]]></title>
            <link>https://medium.com/on-the-same-page-with-kifi/6-learnings-stats-from-kifi-s-launch-on-product-hunt-8e1d07217caf?source=rss-70420259569a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e1d07217caf</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Jen Granito]]></dc:creator>
            <pubDate>Tue, 01 Dec 2015 19:12:43 GMT</pubDate>
            <atom:updated>2015-12-03T22:36:48.923Z</atom:updated>
            <content:encoded><![CDATA[<h4>LAUNCH DILEMMAS</h4><p>When you launch a product, you have to decide how to tell the world about it. With every investment of time and energy to publicize your launch, there is an unknown ROI. It’s even harder to guess what the ROI might be at a startup, where there isn’t a long track record to look at. The last thing any PM wants is to spend a bunch of effort and not see any returns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*XHf992U3oNw9Af8sbA6r8g.gif" /></figure><p>I hope sharing the lessons I learned from our latest launch campaign helps other PMs. Our latest launch, for <a href="http://kifi.com/teams/new">Kifi for Teams</a>, was a success. We brought in hundreds of new users. In true PM fashion, I had several hypotheses I was testing.</p><p>We were launching Kifi for Teams the week before Thanksgiving. It was one of a few dozen medium+ sized product launches I’ve been responsible for, after stints at LinkedIn, Myspace, and Zynga. Kifi has limited resources, like just about every Silicon Valley startup I know. So we were thinking it over: how to get the most for the least amount of team resources spent?</p><p>We had reached out to a few people in the media by that time. But, let me put it this way: I’m a product manager. I like things I can control. You can’t control whether the media writes about you or not, let alone what kind of story you’re going to get. I decided to focus more efforts on things I could control.</p><p>We had always planned to put Kifi on Product Hunt. But about two weeks before launch, we decided to focus our efforts on Product Hunt. <strong>We had always been nervous about whether or not our product was ready for the Product Hunt community, but I remembered </strong><a href="https://medium.com/u/974d6573e9dc"><strong>Reid Hoffman</strong></a><strong> saying in to a group of LinkedIn PMs:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*EXybXIXTmT_IbjYlFzCoeg.jpeg" /></figure><p><strong>He is quite a wise man. It was time to rip off the Band Aid and get first-hand feedback.</strong></p><h4>CHOOSING PRODUCT HUNT</h4><p>We chose to <a href="https://www.producthunt.com/tech/kifi-for-teams">launch with Product Hunt</a> and put the bulk of our resources into it because the community is a great fit. Many people who love Kifi are developers and techies in the broadest sense. They play with software in their spare time, and Product Hunt is one of their daily destinations .</p><p>We also wanted to get feedback from users on Product Hunt. Every piece of feedback we get is golden, because it helps us understand more and get better. Engineers who have been working on Kifi for years could hear from real people using Kifi’s newest iteration. We also knew that existing Kifi users also like Product Hunt from our internal data so we were hoping they would be excited to see us on there as well.</p><p>After we decided to focus on Product Hunt, I read a few great articles like the ones found in <a href="http://makersuccess.com/">Maker’s Success</a> and <a href="https://medium.com/@benhoffman/that-time-when-ashton-kutcher-hunted-neighborly-to-product-hunt-185b2789307d#.lfd6h32ja">Benjamin Hoffman’s post</a>. I created a checklist of the things I could control with this launch and that would have an impact. Here’s how the items on my checklist paid off. Our goal, of course, was to get new users on the platform, creating knowledge repositories for their teams. We weren’t shy.</p><h4>MY CHECKLIST</h4><p>There are lots of <a href="https://www.quora.com/What-does-it-take-to-be-featured-on-Product-Hunt">great checklists and posts with advice</a> out there. Below are a few new or noteworthy items worth sharing:</p><ol><li>Custom landing page banner featuring a $150 credit that people who came through Product Hunt could put toward a premium team. (KIfi for Teams is free but there’s a paid premium product). <strong>WORTHWHILE? ABSOLUTELY: </strong>The landing page converted 61% better. It’s hard to tell how much to attribute directly to the credit vs the banner vs the traffic source. Product Hunt has a great community of quality users — we might have gotten that many new users anyway. But my gut is that the banner helped a lot. Who can refuse an <a href="https://www.producthunt.com/tech/product-hunt-kitty-tee">adorable kitten</a> wearing Google glasses?</li><li>Finding a Kifi user with a lot of followers on PH to ask them to post for us. When someone with a lot of followers posts, all of their followers are automatically updated. <strong>WORTHWHILE? Helpful. </strong>Thanks to <a href="https://medium.com/u/454d729d5955">Ouriel Ohayon</a>’s help, this tactic got us higher placement earlier in the day. About 7% of our upvotes were followers of the poster. Taking a look at <a href="https://medium.com/@benhoffman/that-time-when-ashton-kutcher-hunted-neighborly-to-product-hunt-185b2789307d#.lfd6h32ja">Ben’s</a> findings; there are clearly diminishing returns. With 25k followers, Ashton posted Neighborly. A similar upvote rate would have generated 1,750 from Ashton alone. Given Neighborly ended with an overall total of 580 upvotes the day of their post, it’s clear they didn’t get 7% directly from Ashton, but I’m sure his influence didn’t hurt :) In the end, it supports what <a href="https://medium.com/u/c2146664c8e4">Ryan Hoover</a> says, which is that a good product will do well on PH … regardless of who posts.</li><li><strong>Prepping the media assets</strong>, including the video. <strong>WORTHWHILE? NOT SO MUCH </strong>We only saw a little over 100 views on it during the week of launch. If you have a video already, post it, but don’t spend a ton of time or money to make one.</li><li><strong>Make it exclusive. </strong>Product Hunt asks you to fill out <a href="https://rrhoover.typeform.com/to/ysDOD2">this</a> form in order to have an <a href="https://www.evernote.com/l/AUnYrr8tPEVKH79MzSqPQWtwBnoXzbLWKEY">exclusive launch on PH</a> that includes an extra special offer for Product Hunters. <strong>WORTHWHILE? YES, BUT: </strong>We applied about four business days before &amp; didn’t get the exclusive. On the day of launch, we <a href="https://www.evernote.com/l/AUkxX-JqcaFFhrohl5Y-rTpW6rR87wKO_V8">saw that a startup in a similar space</a> had an exclusive. We’re guessing our competitor on the platform might have something to do with the fact we didn’t get the exclusive.</li><li><strong>Get your teammates listed as “makers.” </strong>Makers have the ability to comment on the product’s hunt and you’ll want people from different disciplines within the company chiming in on the conversation. <strong>WORTHWHILE? YES </strong>I must have applied to be a maker of a previous Kifi hunt 5 times over the last 3 months but hadn’t heard anything. We ended up Tweeting at Ryan the day of launch, and <a href="https://twitter.com/rrhoover/status/666643464818266112">he responded</a> immediately to help us get sorted. I was busier than expected that day so it was helpful to have extra eyes that were able to stay on top of the Product Hunt comments.</li><li><strong>Find friends/users with comment capabilities.</strong> I poked around <a href="https://www.evernote.com/l/AUkhHkE7LypJ6ZMjFD1vwSa8q_lj7MDeIS4">PH profiles</a> to see to see which of my friends had submitted before. I assumed they would have capability to comment and get the conversation started. We found a handful of friends who got the conversation started by sharing their personal thoughts about Kifi. <strong>WORTHWHILE? YES. </strong>We’re unclear what this drove, but it certainly made me and the team happy, as we saw all the love.</li></ol><h4>OVERALL RESULTS</h4><p><strong>Product Hunt Stats:</strong> We received 280 upvotes and <a href="https://www.producthunt.com/tech/kifi-for-teams">30 comments</a> on day one, with lots of great feedback, in particular this comment from <a href="https://www.producthunt.com/tech/kifi-for-teams#comment-182359">PietroBlu Giandonato</a>.</p><blockquote>Amazing! Kifi is Delicious on steroids! It works like a charm, I really love the way it’s smoothly integrated in web search and navigation, as well as its powerful sharing features.</blockquote><blockquote>Moreover, as a teacher I imagine some awesome ways to integrate Kifi in classroom work with my students, to improve their collaboration in groups and to share knowledge with them.</blockquote><blockquote>Kifi is really powerful, definitely recommend it.</blockquote><p><strong>Teams Created:</strong> We also brought in hundreds of users over the next few days, who created hundreds of teams. Welcome to: <a href="http://www.wysiwyg.net/">Wsywig</a>, <a href="http://appdirect.design/">AppDirect</a>, <a href="http://www.redfrogseo.com/">Red Frog</a> <a href="http://www.infor.com/solutions/rhythm">Rhythm</a>, &amp; <a href="https://moneylover.me/">ZooStudio</a> just to name a few</p><p><strong>Retention:</strong> While you might expect that users coming in from a soft external source would bring down your average new user retention, in our case new user retention stayed constant.</p><p><strong>Virality:</strong> We brought in some viral and influential users. We saw a substantial percentage of the users coming in from Product Hunt and a substantial percentage of people inviting their coworkers to the service, mostly on the second day. Perhaps Product Hunters are early adopters that take the time to investigate before inviting others. They wanted to play around with the service for a bit / set up their team and then decided to invite.</p><h4>ABOUT ME AND KIFI</h4><p>I joined <a href="https://www.kifi.com/">Kifi</a> to hep lead their product efforts a little over 2 years ago. I love working on the problem we’re focussing on because I get frustrated that nearly every knowledge management tool recognizes the importance of web content enough to handle it gracefully, but no one is focussing on making it an organized and central part of a company’s knowledge base.</p><p><a href="https://www.kifi.com/">Kifi</a> connects people with knowledge. With Kifi for Teams, we are taking on the challenge of organizing web content and resources in ways that make it accessible for people at work every day. We also give web content its proper due: With our tools, you can integrate it into your knowledge management and client services. We just launched Kifi for Teams service into public beta.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e1d07217caf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/on-the-same-page-with-kifi/6-learnings-stats-from-kifi-s-launch-on-product-hunt-8e1d07217caf">6 Learnings &amp; Stats from Kifi’s Launch on Product Hunt</a> was originally published in <a href="https://medium.com/on-the-same-page-with-kifi">On the Same Page with Kifi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>