<?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 David Kennan on Medium]]></title>
        <description><![CDATA[Stories by David Kennan on Medium]]></description>
        <link>https://medium.com/@davidkennan?source=rss-3e286213b20a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*vr8gXyABKbVzFKQa.jpg</url>
            <title>Stories by David Kennan on Medium</title>
            <link>https://medium.com/@davidkennan?source=rss-3e286213b20a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:53:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@davidkennan/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[YouTube vs Netflix: Helping YouTubers reach 1000 subscribers]]></title>
            <link>https://medium.com/@davidkennan/youtube-vs-netflix-helping-youtubers-reach-1000-subscribers-2072fb8a5b78?source=rss-3e286213b20a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2072fb8a5b78</guid>
            <category><![CDATA[youtube]]></category>
            <category><![CDATA[reaction]]></category>
            <category><![CDATA[online-video]]></category>
            <dc:creator><![CDATA[David Kennan]]></dc:creator>
            <pubDate>Wed, 27 Jan 2016 21:51:09 GMT</pubDate>
            <atom:updated>2016-01-27T21:55:56.111Z</atom:updated>
            <content:encoded><![CDATA[<p>Since taking over the helm of YouTube, Susan Wojcicki has placed a great deal of emphasis on <a href="https://www.youtube.com/watch?v=O6JPxCBlBh8&amp;feature=youtu.be&amp;t=478">the connection between creators and fans</a>. Initiatives like <a href="https://www.youtube.com/yt/space/"><strong>Creator Spaces</strong></a> and <a href="http://youtubecreator.blogspot.com/2013/09/connecting-with-your-top-fans.html"><strong>Top Fans</strong></a>, in Analytics, are geared to feed the star pipeline. Wojcicki’s ‘the best is yet to come’ prediction got me thinking: what else could YouTube do to enable talented, hard-working creators improve their fan connections? Here’s an idea: add qualitative insights to the already awesome quantitative analytics.</p><h4>Audience Retention: Quantitative View</h4><p>YouTube Analytics has a great feature called the Audience Retention graph. This per-video graph shows you how long people are sticking around. So, a smart YouTuber can study Audience Retention, replay sections of their video where they see drop-off, and infer why they are losing viewers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lo0AM62wFivU9PSq." /><figcaption>Example: Audience Retention with drop-off</figcaption></figure><p><strong>Example</strong>: Viewers are abandoning the video after 4 seconds. Why?</p><p><strong>Analysis</strong>: This is an uninteresting family video I posted in 2007. As a joke I titled it “Sponge Pop Roundpants”. The video popped up in tens-of-thousands of searches for <strong>Spongebob,</strong> and it only took viewers a few seconds to realize this wasn’t Spongebob.</p><p><strong><em>Conclusion</em></strong><em>: the Audience Retention graph can guide a creator where to look for problems in their video, but it can’t tell them what the problem is.</em></p><h4>Audience Retention: Qualitative View</h4><p>Serious YouTubers have hundreds of subscribers. It’s a lot of work. There’s an “impedance gap” between launching a video and interacting with a stream of comments. It strikes me that there’s a way to deepen the audience connection and get better insights with very little effort by the creators. I call it <strong>Front Row</strong>.</p><p>Front Row is a feature idea for YouTube, but it could work for any video service.</p><blockquote>With Front Row, creators can invite a limited number of their top fans to have their reactions video-recorded. The creator can then replay the fan reactions and use that qualitative information to figure out what’s working and what’s not.</blockquote><p>It’s like the Audience Retention graph but instead of a graph, the creator sees facial expressions. This qualitative information should be especially useful to budding creators — those who haven’t yet reached 1000 subscribers. And top fans would simply love it!</p><p>Here’s a video to explain it visually.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FUPuBjShSxiI%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DUPuBjShSxiI%26feature%3Dyoutu.be&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FUPuBjShSxiI%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d6f5d12a173543ec09159a4331b630f4/href">https://medium.com/media/d6f5d12a173543ec09159a4331b630f4/href</a></iframe><h4>Summary</h4><p>YouTube’s Audience Retention graph and Top Fans feature help the most successful creators extend their success. The next generation of creators are still figuring out how to connect with their audience. These up-and-coming YouTubers would benefit from the compelling qualitative view of <strong>Front Row</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2072fb8a5b78" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Estimates and Priorities: How to make it work with Engineering!]]></title>
            <link>https://medium.com/@davidkennan/estimates-and-priorities-how-to-make-it-work-with-engineering-4063ca43eb77?source=rss-3e286213b20a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4063ca43eb77</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[David Kennan]]></dc:creator>
            <pubDate>Thu, 05 Nov 2015 01:10:14 GMT</pubDate>
            <atom:updated>2015-11-09T17:42:11.617Z</atom:updated>
            <content:encoded><![CDATA[<p>As product managers, we often speak of <strong>influencing without authority</strong>, and the need for <strong>building</strong> <strong>relationships</strong> with engineering management. But what if basic conversations about estimation and prioritization are difficult? Here are tips from my experience resolving such problems as a first, and necessary, step to building productive relationships.</p><p>First and foremost: keep your product management hat on and create the product vision. Most of us have worked in other roles before, so it’s tempting to slip into other roles and perspectives. You need to clearly separate <strong>what’s in your control</strong> from what’s <strong>engineering responsibility</strong>.</p><h3>When estimates are “too big”</h3><p>Management is pushing back, or you are just surprised by the magnitude of the estimate.</p><ul><li><strong>Subdivide</strong>: Are you estimating too much at once? Reconsider whether the scope can be cut, whether the release can be broken into meaningful sub-releases? With Agile, we get better at estimating small chunks of work in 1–2 week sprints. Major release and big-project estimates are still highly unreliable.</li><li><strong>Corroborate</strong>: Work with engineering to explain the rationale of the estimate.</li><li><strong>Manage risk</strong>: Probe how engineering is padding due to uncertainties, work with them to reduce risks.</li><li><strong>Step aside</strong>: Let engineering take responsibility for its estimates. Engineers don’t like other people making commitments for them.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*eo_lYFRhSktaSskqFBsttQ.png" /><figcaption>Let engineering take responsibility for its estimates.</figcaption></figure><h3>When estimates are unreliable</h3><p>Too many deadlines are missed, or Engineering often finishes early and works on “technical debt” or other non-functional priorities. It’s time to work on your Agile process.</p><ul><li><strong>Clarify</strong>: Improve your requirements and break features (cards) down into smaller pieces.</li><li><strong>Ballpark</strong>: Focus on relative estimation using a point system, not an hour/day/week system. Ask for comparisons to other projects/features.</li><li><strong>Review</strong>: Use the Sprint Review meeting to explore how the last estimate differed from actual work, ask what is affecting “velocity”</li></ul><h3>Unresolved debates about priorities</h3><p>People are back-channeling and stirring up controversy about priorities you’re trying to set.</p><ul><li><strong>Align</strong>: Remove ego from the equation by tying prioritization to top-level company goals</li><li><strong>Orchestrate</strong>: define the time and place for debate, and signal when it’s time to move on.</li><li><strong>Show your work</strong>: Use a consistent and transparent process for setting priorities, with scoring/voting wherever possible. Hint: business value scoring often comes from elsewhere in the business, or from customer input.</li><li><strong>Be real</strong>: Recognize that a percentage of engineering activities deal with bugs and externally imposed events like platform upgrades.</li></ul><h3>Final thoughts</h3><p>Big changes in staff, business direction, or process will naturally disrupt estimations for a time. Experience teaches us to not over-react to foreseeable blips in estimate accuracy, and to continue reflecting and learning as a team.</p><p>Relationships with Engineering start with recognizing their work and their process. As is well said by Atlassian, “<a href="https://www.atlassian.com/agile/estimation/">estimation is a team sport</a>.” Never unilaterally make commitments on behalf of Engineering. Provide clear inputs and feedback. Do these things and you just may find yourself influencing without authority.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4063ca43eb77" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>