<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">
    <title>Product Management Blog</title>
    
    
    <link rel="alternate" type="text/html" href="http://www.alwaysbeshipping.com/" />
    <id>tag:typepad.com,2003:weblog-83446947185399564</id>
    <updated>2012-02-23T12:09:11-08:00</updated>
    <subtitle>Tom Leung's blog about about why software product leadership is a wonderful pain in the ass.</subtitle>
    <generator uri="http://www.typepad.com/">TypePad</generator>
    <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/AlwaysBeShipping" /><feedburner:info uri="alwaysbeshipping" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://hubbub.api.typepad.com/" /><entry>
        <title>Dear Groupon and Amazon Offers</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AlwaysBeShipping/~3/uEQ-UGe9X1c/dear-groupon-and-amazon-offers.html" />
        <link rel="replies" type="text/html" href="http://www.alwaysbeshipping.com/2012/02/dear-groupon-and-amazon-offers.html" thr:count="4" thr:updated="2012-02-23T13:32:43-08:00" />
        <id>tag:typepad.com,2003:post-6a00d83451af5f69e2016762dc3470970b</id>
        <published>2012-02-23T12:09:11-08:00</published>
        <updated>2012-02-23T12:09:11-08:00</updated>
        <summary>Incoming ICBM from Zuck's death star?</summary>
        <author>
            <name>Tom Leung</name>
        </author>
        
        
<content type="xhtml" xml:lang="en-us" xml:base="http://www.alwaysbeshipping.com/"><div xmlns="http://www.w3.org/1999/xhtml"><p>Incoming ICBM from Zuck's death star? </p>
<p> </p>
<p><a href="http://leung.typepad.com/.a/6a00d83451af5f69e2016301e75ae9970d-pi" style="display: inline;"><img alt="2-23-2012 12-05-31 PM" border="0" class="asset  asset-image at-xid-6a00d83451af5f69e2016301e75ae9970d" src="http://leung.typepad.com/.a/6a00d83451af5f69e2016301e75ae9970d-800wi" title="2-23-2012 12-05-31 PM" /></a><br /><br /></p><xhtml:img xmlns:xhtml="http://www.w3.org/1999/xhtml" src="http://feeds.feedburner.com/~r/AlwaysBeShipping/~4/uEQ-UGe9X1c" height="1" width="1" /></div></content>



    <feedburner:origLink>http://www.alwaysbeshipping.com/2012/02/dear-groupon-and-amazon-offers.html</feedburner:origLink></entry>
    <entry>
        <title>Zuckerberg's Hacker Way: Code Wins Arguments</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AlwaysBeShipping/~3/x4Kxodzssis/zuckerbergs-hacker-way-code-wins-arguments.html" />
        <link rel="replies" type="text/html" href="http://www.alwaysbeshipping.com/2012/02/zuckerbergs-hacker-way-code-wins-arguments.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d83451af5f69e20163008de09b970d</id>
        <published>2012-02-01T17:03:11-08:00</published>
        <updated>2012-02-01T17:04:47-08:00</updated>
        <summary>Was just reading the Facebook S-1 and found this description pretty cool. I love the mantra "code wins arguments." The Hacker Way As part of building a strong company, we work hard at making Facebook the best place for great people to have a big impact on the world and learn from other great people. We have cultivated a unique culture and management approach that we call the Hacker Way. The word “hacker” has an unfairly negative connotation from being portrayed in the media as people who break into computers. In reality, hacking just means building something quickly or testing...</summary>
        <author>
            <name>Tom Leung</name>
        </author>
        
        
<content type="xhtml" xml:lang="en-us" xml:base="http://www.alwaysbeshipping.com/"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="http://leung.typepad.com/.a/6a00d83451af5f69e20168e684ff4f970c-pi" style="float: left;"><img alt="Images" class="asset  asset-image at-xid-6a00d83451af5f69e20168e684ff4f970c" src="http://leung.typepad.com/.a/6a00d83451af5f69e20168e684ff4f970c-120wi" style="margin: 0px 5px 5px 0px;" title="Images" /></a>Was just reading the <a href="http://www.sec.gov/Archives/edgar/data/1326801/000119312512034517/d287954ds1.htm" target="_self">Facebook S-1</a> and found this description pretty cool.  I love the mantra "code wins arguments."</p>
<p> </p>
<p><span style="font-size: 10pt;"><em><strong>The Hacker Way</strong></em></span></p>
<p><span style="font-size: 10pt;"><em> </em></span></p>
<p><span style="font-size: 10pt;"><em>As part of building a strong company, we work hard at making Facebook the best place for great people to have a big impact on the world and learn from other great people. We have cultivated a unique culture and management approach that we call the Hacker Way.</em></span></p>
<p><span style="font-size: 10pt;"><em> </em></span></p>
<p><span style="font-size: 10pt;"><em>The word “hacker” has an unfairly negative connotation from being portrayed in the media as people who break into computers. In reality, hacking just means building something quickly or testing the boundaries of what can be done. Like most things, it can be used for good or bad, but the vast majority of hackers I’ve met tend to be idealistic people who want to have a positive impact on the world.</em></span></p>
<p><span style="font-size: 10pt;"><em> </em></span></p>
<p><span style="font-size: 10pt;"><em>The Hacker Way is an approach to building that involves continuous improvement and iteration. Hackers believe that something can always be better, and that nothing is ever complete. They just have to go fix it — often in the face of people who say it’s impossible or are content with the status quo.</em></span></p>
<p><span style="font-size: 10pt;"><em> </em></span></p>
<p><span style="font-size: 10pt;"><em>Hackers try to build the best services over the long term by quickly releasing and learning from smaller iterations rather than trying to get everything right all at once. To support this, we have built a testing framework that at any given time can try out thousands of versions of Facebook. We have the words “Done is better than perfect” painted on our walls to remind ourselves to always keep shipping.</em></span></p>
<p><span style="font-size: 10pt;"><em> </em></span></p>
<p><span style="font-size: 10pt;"><em>Hacking is also an inherently hands-on and active discipline. Instead of debating for days whether a new idea is possible or what the best way to build something is, hackers would rather just prototype something and see what works. There’s a hacker mantra that you’ll hear a lot around Facebook offices: “Code wins arguments.”</em></span></p>
<p><span style="font-size: 10pt;"><em> </em></span></p>
<p><span style="font-size: 10pt;"><em>Hacker culture is also extremely open and meritocratic. Hackers believe that the best idea and implementation should always win — not the person who is best at lobbying for an idea or the person who manages the most people.</em></span></p>
<p><span style="font-size: 10pt;"><em> </em></span></p>
<p><span style="font-size: 10pt;"><em>To encourage this approach, every few months we have a hackathon, where everyone builds prototypes for new ideas they have. At the end, the whole team gets together and looks at everything that has been built. Many of our most successful products came out of hackathons, including Timeline, chat, video, our mobile development framework and some of our most important infrastructure like the HipHop compiler.</em></span></p>
<p><span style="font-size: 10pt;"><em> </em></span></p>
<p><span style="font-size: 10pt;"><em>To make sure all our engineers share this approach, we require all new engineers — even managers whose primary job will not be to write code — to go through a program called Bootcamp where they learn our codebase, our tools and our approach. There are a lot of folks in the industry who manage engineers and don’t want to code themselves, but the type of hands-on people we’re looking for are willing and able to go through Bootcamp.</em></span></p>
<p> </p><xhtml:img xmlns:xhtml="http://www.w3.org/1999/xhtml" src="http://feeds.feedburner.com/~r/AlwaysBeShipping/~4/x4Kxodzssis" height="1" width="1" /></div></content>



    <feedburner:origLink>http://www.alwaysbeshipping.com/2012/02/zuckerbergs-hacker-way-code-wins-arguments.html</feedburner:origLink></entry>
    <entry>
        <title>Dear Marketers: This is One of the Hidden Costs of Groupon</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AlwaysBeShipping/~3/2MwRxIgoYaE/dear-marketers-this-is-one-of-the-hidden-costs-of-groupon.html" />
        <link rel="replies" type="text/html" href="http://www.alwaysbeshipping.com/2012/01/dear-marketers-this-is-one-of-the-hidden-costs-of-groupon.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d83451af5f69e20168e63ed01d970c</id>
        <published>2012-01-28T11:45:23-08:00</published>
        <updated>2012-01-29T11:05:39-08:00</updated>
        <summary>Please wait while we find a Pack Member to assist you... You have been connected to Mindy L.. Mindy L.: Hello Tom! Welcome to the Great Wolf Lodge! How may I help you today? Mindy L.: Good afternoon! Tom Leung: Hi there Mindy Mindy L.: Hello! Tom Leung: I'm hoping you can help me, I'm kind of miffed at the moment. Mindy L.: Sure, what can I help you with? Tom Leung: I have reservations at your Grand Mound location for today. Mindy L.: Great! Tom Leung: And my colleague at work is going today as well but apparently he...</summary>
        <author>
            <name>Wendy Leung</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Product Critiques" />
        
        
<content type="html" xml:lang="en-us" xml:base="http://www.alwaysbeshipping.com/">
&lt;div xmlns="http://www.w3.org/1999/xhtml"&gt;
&lt;div&gt;&lt;a style="float: left;" href="http://leung.typepad.com/.a/6a00d83451af5f69e20167613d7b7f970b-pi"&gt;&lt;img class="asset  asset-image at-xid-6a00d83451af5f69e20167613d7b7f970b" style="margin: 0px 5px 5px 0px;" title="Groupon" src="http://leung.typepad.com/.a/6a00d83451af5f69e20167613d7b7f970b-120wi" alt="Groupon" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;em&gt;Please wait while we find a Pack Member to assist you...&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;You have been connected to Mindy L..&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; Hello Tom! Welcome to the Great Wolf Lodge! How may I help you today?&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; Good afternoon!&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; Hi there Mindy&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; Hello!&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; I'm hoping you can help me, I'm kind of miffed at the moment.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; Sure, what can I help you with?&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; I have reservations at your Grand Mound location for today.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; Great!&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; And my colleague at work is going today as well but apparently he paid 1/2 what I paid. I'm not asking for a refund but would like request a complimentary room upgrade.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; :-(&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; At this time we only have our standard suites available for today, so we would not be able to offer a free upgrade.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; Can u put us in a Grizzly&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; They are sold out for today.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; oh man. that's a bummer. I hate groupon.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; Is there anything else I may assist you with, Tom?&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; yes, i'd like to request a coupon for an upgrade next time i visit&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; You would have to request that at guest services when checking in.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; i feel like i'm paying $400 and my friend is paying $200&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; that's just wrong.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; Our rates change very quickly this time of year based on room availability. As you can see we are almost sold out for today, so that makes the rates much higher.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; so what can you do for me next time we visit?&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; and you're partly sold out because you gave the rooms away for 1/2 price to a bunch of people and folks paying full freight like me get hosed.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; Unfortunately, I am not able to honor any add on amenities or upgrades. You have to refer to guest services when you arrive at the lodge.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Tom Leung:&amp;nbsp; ok thx, please tell your supervisor i intend to blog about this and post to yelp as well. i'm not pleased.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; All of our chats are monitored by supervisors at all times.&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Mindy L.:&amp;nbsp; Thank you for visiting greatwolf.com Tom, have a Great Wolf day!&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Thank you for visiting greatwolf.com! We hope to see you at the lodge!&lt;/em&gt;&lt;/div&gt;
&lt;div&gt;&lt;em&gt;Your session has ended. You may now close this window.&lt;/em&gt;&lt;/div&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;div&gt;Update: An ABS reader from the ABS Facebook page rightly called out I was a bit condescending and unreasonably upset in talking to the customer service lady. &amp;nbsp;He's probably right in that this business didn't do anything wrong by charging people different prices and I could have scoured all the deals sites before booking directly from the business itself. &amp;nbsp;That said, here are some takeaways I'd suggest are worth considering:&lt;/div&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;div&gt;1. &amp;nbsp;If you do mega-discounts on the same inventory on 3rd party sites like Groupon while charging direct customers double at the same time, just be aware that it could make the direct customers upset. &amp;nbsp;Arguably, &amp;nbsp;those direct customers (the ones who went to your website) might be the highest value ones.&lt;/div&gt;
&lt;div&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
2. While it may still make sense to do things like Groupon while charging direct customers higher prices, you may want to consider offering those direct customers something more (e.g. more flexible booking, complimentary services, etc.) which don't need to make the difference but numb the pain a bit more for missing on the great deal.&lt;/div&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;div&gt;-Tom&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;img src="http://feeds.feedburner.com/~r/AlwaysBeShipping/~4/2MwRxIgoYaE" height="1" width="1"/&gt;</content>



    <feedburner:origLink>http://www.alwaysbeshipping.com/2012/01/dear-marketers-this-is-one-of-the-hidden-costs-of-groupon.html</feedburner:origLink></entry>
    <entry>
        <title>Help Test a Minimally Viable Product</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AlwaysBeShipping/~3/DFuMns2wzRY/help-test-a-minimally-viable-product.html" />
        <link rel="replies" type="text/html" href="http://www.alwaysbeshipping.com/2012/01/help-test-a-minimally-viable-product.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d83451af5f69e20168e63dc540970c</id>
        <published>2012-01-28T09:53:43-08:00</published>
        <updated>2012-01-28T10:59:05-08:00</updated>
        <summary>Hi Folks: Practicing what I preach, we've been iterating on a new concept which allows you to one-click call any telephone number from Firefox for free. Call any telephone number on any web page from browser, bridge to your mobile, or text the number for future reference. It only works in Firefox now and requires latest version of Firefox. Would love to get your feedback in the comments here or send it to me directly (tleung  marchex dot com). Check it out at www.LetsFirefly.com Thanks, Tom</summary>
        <author>
            <name>Wendy Leung</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Product Critiques" />
        
        
<content type="xhtml" xml:lang="en-us" xml:base="http://www.alwaysbeshipping.com/"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="http://www.letsfirefly.com" style="float: left;" target="_blank"><img alt="Firefly" class="asset  asset-image at-xid-6a00d83451af5f69e201630046fc9f970d" src="http://leung.typepad.com/.a/6a00d83451af5f69e201630046fc9f970d-320wi" style="margin: 0px 5px 5px 0px;" title="Firefly" /></a>Hi Folks:</p>
<p>Practicing what I preach, we've been iterating on a new concept which allows you to one-click call any telephone number from Firefox for free.  Call any telephone number on any web page from browser, bridge to your mobile, or text the number for future reference.  It only works in Firefox now and requires latest version of Firefox.  Would love to get your feedback in the comments here or send it to me directly (tleung &lt;AT&gt; marchex dot com).</p>
<p>Check it out at <a href="http://www.letsfirefly.com" target="_blank">www.LetsFirefly.com</a></p>
<p>Thanks,</p>
<p>Tom </p><xhtml:img xmlns:xhtml="http://www.w3.org/1999/xhtml" src="http://feeds.feedburner.com/~r/AlwaysBeShipping/~4/DFuMns2wzRY" height="1" width="1" /></div></content>



    <feedburner:origLink>http://www.alwaysbeshipping.com/2012/01/help-test-a-minimally-viable-product.html</feedburner:origLink></entry>
    <entry>
        <title>It's 2012, But I Still Like PRD's</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AlwaysBeShipping/~3/fqFz8fCfzIM/its-2012-but-i-still-like-prds.html" />
        <link rel="replies" type="text/html" href="http://www.alwaysbeshipping.com/2012/01/its-2012-but-i-still-like-prds.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d83451af5f69e20162ff602acd970d</id>
        <published>2012-01-10T22:41:10-08:00</published>
        <updated>2012-01-11T14:29:23-08:00</updated>
        <summary>I know in the age of agile, things like product requirements docs are a bit out of favor but I still like them -- at least to help solidify the PM's thinking and facillitate some tough discussions. It's often easier to flesh out non-obvious misalignment when you walk folks through a good PRD and some nice mocks than agreeing on the strategy in abstract. So here are some things I like to see in a PRD. You don't have to write it as a long doc, heck you can even use it as a check list but if you can't...</summary>
        <author>
            <name>Tom Leung</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="The Theory of Product Management" />
        
        
<content type="xhtml" xml:lang="en-us" xml:base="http://www.alwaysbeshipping.com/"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="http://leung.typepad.com/.a/6a00d83451af5f69e20168e55f0e42970c-pi" style="float: left;"><img alt="Gps-navigator1" class="asset  asset-image at-xid-6a00d83451af5f69e20168e55f0e42970c" src="http://leung.typepad.com/.a/6a00d83451af5f69e20168e55f0e42970c-120wi" style="margin: 0px 5px 5px 0px;" title="Gps-navigator1" /></a>I know in the age of agile, things like product requirements docs are a bit out of favor but I still like them -- at least to help solidify the PM's thinking and facillitate some tough discussions.  It's often easier to flesh out non-obvious misalignment when you walk folks through a good PRD and some nice mocks than agreeing on the strategy in abstract.</p>
<p>So here are some things I like to see in a PRD.  You don't have to write it as a long doc, heck you can even use it as a check list but if you can't answer these questions quickly, you probably haven't thought through what you're building as much as you need to.</p>
<ul>
<li>Who's the customer?  What do they say, do, think, and feel?</li>
<li>What problem are we trying to solve?  Why is it a problem?</li>
<li>What does success look like (this is often best written as a "press release")?</li>
<li>How does it work (best written as a few paragraph user narrative like "jane decides she wants to grow her business...")</li>
<li>What are the key use cases?  What use cases are out of scope for now?</li>
<li>What are the key capabilities and features we'd need to build to support that (stack ranked P0-P3)?</li>
<li>What are the biggest open issues (and include stake in the ground for answers)?</li>
<li>What does the experience look like (low-resolution sharpie sketches).</li>
<li>What are the milestones?  How are we gonna avoid this becoming a never ending project?</li>
<li>What are the key metrics to measure and goal against?  What do we think success will look like from a metrics point of view? </li>
</ul>
<p>Happy shipping :-)</p>
<p>-Tom</p><xhtml:img xmlns:xhtml="http://www.w3.org/1999/xhtml" src="http://feeds.feedburner.com/~r/AlwaysBeShipping/~4/fqFz8fCfzIM" height="1" width="1" /></div></content>



    <feedburner:origLink>http://www.alwaysbeshipping.com/2012/01/its-2012-but-i-still-like-prds.html</feedburner:origLink></entry>
    <entry>
        <title>Rebecca Henderson from HBS on Innovation</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AlwaysBeShipping/~3/fjiTMaZsB4s/rebecca-henderson-from-hbs-on-innovation.html" />
        <link rel="replies" type="text/html" href="http://www.alwaysbeshipping.com/2011/09/rebecca-henderson-from-hbs-on-innovation.html" thr:count="1" thr:updated="2011-11-01T16:50:08-07:00" />
        <id>tag:typepad.com,2003:post-6a00d83451af5f69e2015435bc1e32970c</id>
        <published>2011-09-27T11:49:56-07:00</published>
        <updated>2011-09-27T11:49:56-07:00</updated>
        <summary>I attended a conference call this morning hosted by HBS featuring Professor Rebecca Henderson talking about her research around innovation. Thought I'd share some takeaways. Here's a link to some of her other publications around innovation strategy. Why is it so hard for large companies to innovate? 1. Most new ideas have a low probability of success so it's easy to poke holes in any idea and shoot it down. Furthermore, it takes investing in some level in 10-20 ideas to get one that really takes off. 2. Most new ideas seem most interesting to peripheral customers. Core customers like...</summary>
        <author>
            <name>Tom Leung</name>
        </author>
        
        
<content type="xhtml" xml:lang="en-us" xml:base="http://www.alwaysbeshipping.com/"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="http://leung.typepad.com/.a/6a00d83451af5f69e2015435bc1ddf970c-pi" style="float: left;"><img alt="Ent12345[1]" border="0" class="asset  asset-image at-xid-6a00d83451af5f69e2015435bc1ddf970c" src="http://leung.typepad.com/.a/6a00d83451af5f69e2015435bc1ddf970c-800wi" style="margin: 0px 5px 5px 0px;" title="Ent12345[1]" /></a>I attended a conference call this morning hosted by HBS featuring Professor Rebecca Henderson talking about her research around innovation.  Thought I'd share some takeaways.  Here's a link to some of her other <a href="http://drfd.hbs.edu/fit/public/facultyInfo.do?facInfo=pub&amp;facId=12345" target="_blank">publications around innovation strategy</a>.</p>
<p><strong>Why is it so hard for large companies to innovate?</strong></p>
<p>1. Most new ideas have a <strong>low probability of success</strong> so it's easy to poke holes in any idea and shoot it down.  Furthermore, it takes investing in some level in 10-20 ideas to get one that really takes off.</p>
<p>2. Most new ideas seem most interesting to <strong>peripheral customers</strong>.  Core customers like you for what you do today.  Parodoxically, customer-centric organizations often miss the most disruptive innovations precisely because their current customer set finds the innovation to be a bit on the margins.  This is one of the core arguments to Clay Christensen's Innovator's Dilemna concept.</p>
<p>3. Most new ideas have <strong>lower margins</strong> than the core.  This is because they may meet a different need, an embryonic market that's not yet fully developed, and/or the current company's cost structure and internal infrastructure is set up for the current core business.  If you take a innovative idea and manage it to "the numbers" and then underinvest in it, it will almost certainly fail.</p>

4. <strong>Organization challenges</strong>.  The people, culture, processes of today are set up to maximize success for the core business and sometimes individual actors in the enterprise will not benefit from a new innovation (in fact, they may feel like they look bad, have to risk their own division's growth prospects, etc.).  Furthermore, it's often really hard to integrate an external group's innovations into the core because of the organizational chasms.  It's also harder to develop great innovation completely seperated from the core since a seperate innovation division may not have the on-the-ground market understanding that the core businesses have.  
<p>Her ideal is to have a heavyweight team that is connected to the core but not completely tied down by it.  She also mentioned this depends partly on how "stuck" the enterprise is.  I.e., if it's really stuck in its current ways, you may need to carve out a labs like environment but understand that has it's own challenges around market savvy and future integration.</p>
<p>5. <strong>Overload</strong>.  This was probably one of the most compelling arguments in my opinion which is most enterprises can't say no.  They evaluate every project independently and don't take a holistic view across the enteprise and say how many projects can we really nail.  She quote Kim Clark (her thesis advisor) as once saying you don't send a teenager to the mall with $5 to watch a $7.50 movie.  She also shared a story about a Fortune 200 senior leadership offsite where every divisional leader had a great idea that everyone agreed made a ton of sense until 8 hours later, they had a list of 20+ new initiatives which would likely have some initial fanfare and then die a slow death 6 months later because of insufficient focus and investment.</p>
<p>Lastly, I was struck by her assessment of the Steve Jobs effect where she argued that the "great leader" approach had a very high variance of success.  If you have someone (or are someone) who can see the future, you're very lucky but most companies that rely on the single visionary often ride themselves off cliffs.  Her argument is for a combination of great leadership on top of a highly capable culture and organization with as much bottoms up innovation as there is top down.</p>
<p>Thanks to HBS and Professor Henderson for sharing this morning.  Good stuff.</p>
<p> </p>
<p> </p><xhtml:img xmlns:xhtml="http://www.w3.org/1999/xhtml" src="http://feeds.feedburner.com/~r/AlwaysBeShipping/~4/fjiTMaZsB4s" height="1" width="1" /></div></content>



    <feedburner:origLink>http://www.alwaysbeshipping.com/2011/09/rebecca-henderson-from-hbs-on-innovation.html</feedburner:origLink></entry>
    <entry>
        <title>Lean Startup: How Intuit Innovates</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AlwaysBeShipping/~3/FvwvImcdN38/lean-startup-how-intuit-innovates.html" />
        <link rel="replies" type="text/html" href="http://www.alwaysbeshipping.com/2011/09/lean-startup-how-intuit-innovates.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d83451af5f69e201543566b9f5970c</id>
        <published>2011-09-13T14:18:45-07:00</published>
        <updated>2011-09-13T14:18:45-07:00</updated>
        <summary>Video streaming by Ustream</summary>
        <author>
            <name>Tom Leung</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Product Org Leadership" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Product Strategy" />
        
        
<content type="xhtml" xml:lang="en-us" xml:base="http://www.alwaysbeshipping.com/"><div xmlns="http://www.w3.org/1999/xhtml"><p>
<object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" height="296" width="480">
<param name="flashvars" value="vid=17251068&amp;autoplay=false" />
<param name="allowfullscreen" value="true" />
<param name="allowscriptaccess" value="always" />
<param name="src" value="http://www.ustream.tv/flash/viewer.swf" /> <embed allowfullscreen="true" allowscriptaccess="always" flashvars="vid=17251068&amp;autoplay=false" height="296" src="http://www.ustream.tv/flash/viewer.swf" type="application/x-shockwave-flash" width="480" />
</object>
<br /><a href="http://www.ustream.tv/" style="padding: 2px 0px 4px; width: 400px; background: #ffffff; display: block; color: #000000; font-weight: normal; font-size: 10px; text-decoration: underline; text-align: center;" target="_blank">Video streaming by Ustream</a></p><xhtml:img xmlns:xhtml="http://www.w3.org/1999/xhtml" src="http://feeds.feedburner.com/~r/AlwaysBeShipping/~4/FvwvImcdN38" height="1" width="1" /></div></content>



    <feedburner:origLink>http://www.alwaysbeshipping.com/2011/09/lean-startup-how-intuit-innovates.html</feedburner:origLink></entry>
    <entry>
        <title>Why Leading a Product Org is Hard...</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AlwaysBeShipping/~3/lBuwDQXB_Kk/product-management-leadership.html" />
        <link rel="replies" type="text/html" href="http://www.alwaysbeshipping.com/2011/09/product-management-leadership.html" thr:count="2" thr:updated="2011-09-06T07:37:35-07:00" />
        <id>tag:typepad.com,2003:post-6a00d83451af5f69e2015434aa09fa970c</id>
        <published>2011-09-03T21:14:23-07:00</published>
        <updated>2011-09-03T21:14:01-07:00</updated>
        <summary>After doing in product management over the last 20,000+ office hours, I still find there are some things that are extremely difficult to do consistently well as a software product management leader. So this post is for all of you hot shot PM's a few years out of b-school who wonder what things might slow down your career progression once you've nailed the fundementals. (Many of these might be applicable for leaders outside of product management as well.) Below are five tough challenges and some color on why I think they're hard. In the future, I'll probably do some posts...</summary>
        <author>
            <name>Tom Leung</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Career Development" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Product Org Leadership" />
        
        
<content type="xhtml" xml:lang="en-us" xml:base="http://www.alwaysbeshipping.com/"><div xmlns="http://www.w3.org/1999/xhtml"><p><br /><a href="http://leung.typepad.com/.a/6a00d83451af5f69e2014e8b3d9e75970d-pi" style="float: left;"><img alt="Mountain climbers" class="asset  asset-image at-xid-6a00d83451af5f69e2014e8b3d9e75970d" src="http://leung.typepad.com/.a/6a00d83451af5f69e2014e8b3d9e75970d-320wi" style="margin: 0px 5px 5px 0px;" title="Mountain climbers" /></a> After doing in product management over the last 20,000+ office hours, I still find there are some things that are extremely difficult to do consistently well as a software product management leader.  </p>
<p>So this post is for all of you hot shot PM's a few years out of b-school who wonder what things might slow down your career progression once you've nailed the fundementals.  (Many of these might be applicable for leaders outside of product management as well.)  </p>
<p>Below are five tough challenges and some color on why I think they're hard.  In the future, I'll probably do some posts on lessons I've learned and potential approaches worth considering for each of these areas.  Feel free to share thoughts and advice in the comments.  I need all the help I can get ;-)</p>
<p><strong>1. Hiring</strong><br /><br />Everyone knows the most important thing in any business is hiring great people.  Pulling that off is at least 1/2 of my job.  Here are some reasons building out a world-class team is a pain in the butt.</p>
<p>A lot of good people you want to hire to work for you would love to have your job (which is a good thing).  They're usually kicking butt wherever they are, have a long track record, and solid credentials -- which is why you're recruiting them in the first place.  Unfortunately, many of those same A candidates find anything less (working for you versus being you) beneath them even if their current job is less challenging than the one you're offering.  That's not a dig on them, it just makes it hard since you ideally want someone who's ambitious but also fired up to do the job for which you're hiring today.</p>
<p>Unless you're recruiting for the company du jour, the candidates you want may not know about your firm or at least the opportunity you're trying to fill so you may not be interviewing the right people.  Let's face it, there's only a few hot companies in tech each year.  A few years ago it might have been Myspace, Plaxo, and Yahoo.  Then it might have been Google, Facebook, and Zynga. Next year, it will be a whole new crop.  If you're like 99.9% of hiring managers, you're not from one of the two or three "it" companies of the year (of course we all believe we're the next one) so you have to hunt versus gather.</p>
<p>Most people are not a good fit and to make matters worse, the interviewing process is like weather prediction.  It's better than guessing but wrong enough that it can feel like that.  Case interviews, behavioral interviews, reference checks, etc. are most good at evaluating a candidates interviewing and personal marketing skills.  Trying to figure out how someone will actually grow long term in your Company versus talk about performing may be akin to picking stocks -- shades of improvement over random.  To be fair, it's a bit more achievable to pick people who can do the job you're hiring for today, it's the growth ceiling that's harder to forecast. </p>
<p><strong> </strong></p>

<strong>2. Alignment</strong>
<p>You can be awesome at strategy, insights, requirements, and tradeoffs and still be collosal failure if you can't get the entire organization aligned culturally, philosophically, and personally.</p>
<p>By virtue of their chosen profession and the values of their own teams, most functional groups are not naturally aligned.  Some groups feel passionately about process and comraderie, others are most passionate about financial performance, and others are passionate about customer satisfaction.  In theory, those are not mutually exclusive but invariably, choices about prioritization, resource allocation, and success metrics show the gaps between these overlapping world views.</p>
<p>Not only are functional folks often wired different and colored by their personal experience, they are often compensated and promoted based on non-aligned goals (if only everyone were paid completely in equity).  Some are bonused on sales, some on media mentions, some on hires, some on customer satisfaction, some on absolute usage, etc.  This isn't necessarily because their employer is neurotic but often because it often makes sense to compensate people based on the levers they have most control over and equity values are hard to move quarter to quarter (some would say year to year) no matter how good an individual really is.</p>
<p>Everyone isn't at work for the same reasons.  Some are looking to prove something.  Some are passionate about the customer problem.  Some are looking to pay their kids' college tuition.  Then there are some who are not the right fit but you don't know it.  At any rate, people's personal situations and arc of life make it such that unless we're all being invaded by the British, we're a motley crew with divergent priorities and motivations in life that impacts how we are at the office.</p>
<p><strong>3. Personal Scale</strong></p>
<p>You may have kicked butt as an IC or manager or group manager but getting more enterprise impact can be increasingly challenging as you attempt to get closer to running the whole show.</p>
<p>One challenge is you have less and less direct control over decisions, work product, conversations etc.  At one extreme, if you've got the juice, you can be a great IC.  If you can find people with the juice, you can be a solid manager.  Getting beyond that introduces increasing degrees of challenge such as cross-group cultural issues (see #2 above), increasing levels of high beta decisions (all the easy ones get made before they reach you), and further dillution of your individual activities from the trenches (i.e. layers of people between you and the people who do stuff).</p>
<p>This is where work-life balance also takes a hit since Type A people tend to compensate for this by working harder, "rolling up our sleaves" more, and looking for blind spots in every direction, color, and shape.  This is usually a good thing (that's why your boss likes you) but at some point, it's a bit like driving a sports car at high speeds constantly where your mind, body, and soul get taxed to a point where the enterprise will take as much as you can give it and always want more.  Unlike your earlier IC jobs, you will never be in full control.  You need to accept that and try to get your 8 hours of sleep and be present for your family if you want to be a player for the long haul.</p>
<p><strong>4. Winning Products</strong></p>
<p>Picking winning product ideas is even harder than hiring.  Predicting what customers will want, need, pay for, use, recommend, generate growing revenue, retain competitive advantage, and stick with is no walk in the park.  And let's not forget making sure you can build such a thing better than your competitors is kind of hard as well.   Most of us can come up with ideas that meet some of those criteria but it's hard to nail all of them.</p>
<p>If picking, designing, building, launching, evolving, and scaling winning products was easy, Microsoft would have had a kick ass phone back in 2005, Google would have figured out social, and Amazon would have figured out mobile advertising.  I'm sure all of those places have been trying to do that kind of thing for many years now but somehow others who had similar talent, money, and time nailed it (at least social and mobile). </p>
<p>To make matters more challenging, unless you have a monopoly or close to one, you usually don't have enough resources to place as many bets as you'd like to place.  We've all seen the academic articles about innovation pipelines and there's hundreds of dots on the left hand side of the pipeline and a few emerge as winning products.  In reality, most of us work at places where we can only flare so much beyond brainstorming and soon after we need to figure out which few prototypes to build and even fewer alphas to ship.  So as much as we'd like to load up with buck shot in the morning sun, most of us are dealing with bolt-action rifles in the moonlight.</p>
<p><strong>5. Team bar raising</strong></p>
<p>Hiring a great team is hard enough (as per #2) but growing it's capabilities beyond just adding more people is a different ball game.  If you're doing your job, your company is probably growing and going after increasingly competitive, demanding, and/or growing markets. By definition, for you to be as successful as you were last year, your team needs to improve at at least the same rate that your company's goals are scaling.  I.e., last year's A team can't just rinse and repeat next year if the Company has big growth ambitions. Your team needs to be better, smarter, and faster. </p>
<p>Surely, adding more varsity players is critical to raising the team's capacity and mojo.  However, raising the game of every existing team player (yourself included) is the fastest way to sustainably increase output, especially as the team gets big.  Figuring out how to unlock unrealized potential in people and helping them get there is a huge challenge for varsity teams since everyone should already be performing at a high level.  Inevitably, you may determine that some people are capable of a lot more than you thought (awesome outcome) but you may also find some people are peaking.  In that latter case, knowing for sure when you've reached that point, making sure you've been fair and transparent and supportive to disprove this assumption, and making a call on if that's an ok long-term proposition can really seperate leaders from managers.</p>
<p><strong>Summary</strong></p>
<p><strong> </strong>If you're in a PM role and wondering if you'll be as challenged in a few years as you were a few years ago, I think the answer is yes.  </p>
<p>-Tom </p>
<p> </p><xhtml:img xmlns:xhtml="http://www.w3.org/1999/xhtml" src="http://feeds.feedburner.com/~r/AlwaysBeShipping/~4/lBuwDQXB_Kk" height="1" width="1" /></div></content>



    <feedburner:origLink>http://www.alwaysbeshipping.com/2011/09/product-management-leadership.html</feedburner:origLink></entry>
    <entry>
        <title>Design Thinking...the video</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AlwaysBeShipping/~3/dLhU1Asmyd8/design-thinkingthe-video.html" />
        <link rel="replies" type="text/html" href="http://www.alwaysbeshipping.com/2011/05/design-thinkingthe-video.html" thr:count="2" thr:updated="2011-07-28T23:44:40-07:00" />
        <id>tag:typepad.com,2003:post-6a00d83451af5f69e20154324041d6970c</id>
        <published>2011-05-11T22:02:27-07:00</published>
        <updated>2011-05-11T22:02:27-07:00</updated>
        <summary>Just stumbled across this... Apparently Tim Brown gave this presentation at the MIT Sloan School (not sure why he didn't do this at HBS).</summary>
        <author>
            <name>Wendy Leung</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Non Software Design" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Product Strategy" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="UX" />
        
        
<content type="xhtml" xml:lang="en-us" xml:base="http://www.alwaysbeshipping.com/"><div xmlns="http://www.w3.org/1999/xhtml"><p>Just stumbled across this...  Apparently Tim Brown gave this presentation at the MIT Sloan School (not sure why he didn't do this at HBS).</p>
<p> </p>
<p>
<object align="middle" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=9,0,0,0" height="361" id="Main" width="481">
<param name="allowScriptAccess" value="always" />
<param name="movie" value="http://mitworld.mit.edu/flash/player/Main.swf?host=cp58255.edgefcs.net&amp;flv=mitw-00389-sloan-dils-brown-ideo-16mar2006&amp;preview=http://mitworld.mit.edu//uploads/mitwstill-00389-sloan-dils-brown-ideo-16mar2006.jpg" />
<param name="quality" value="high" />
<param name="bgcolor" value="#000000" /><embed align="middle" allowscriptaccess="always" bgcolor="#000000" height="361" name="Main" pluginspage="http://www.macromedia.com/go/getflashplayer" quality="high" src="http://mitworld.mit.edu/flash/player/Main.swf?host=cp58255.edgefcs.net&amp;flv=mitw-00389-sloan-dils-brown-ideo-16mar2006&amp;preview=http://mitworld.mit.edu//uploads/mitwstill-00389-sloan-dils-brown-ideo-16mar2006.jpg" type="application/x-shockwave-flash" width="481" />
</object>
</p><xhtml:img xmlns:xhtml="http://www.w3.org/1999/xhtml" src="http://feeds.feedburner.com/~r/AlwaysBeShipping/~4/dLhU1Asmyd8" height="1" width="1" /></div></content>



    <feedburner:origLink>http://www.alwaysbeshipping.com/2011/05/design-thinkingthe-video.html</feedburner:origLink></entry>
    <entry>
        <title>Recruiting Product People</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AlwaysBeShipping/~3/7cN6jvtuIU4/recruiting-product-people.html" />
        <link rel="replies" type="text/html" href="http://www.alwaysbeshipping.com/2011/05/recruiting-product-people.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d83451af5f69e2014e885b5a70970d</id>
        <published>2011-05-10T20:23:51-07:00</published>
        <updated>2011-05-10T20:23:51-07:00</updated>
        <summary>Hiring top talent is hard. Check out this video to see the lengths people will go to attract the interest of great product managers.</summary>
        <author>
            <name>Tom Leung</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Career Development" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Product Org Leadership" />
        
        
<content type="xhtml" xml:lang="en-us" xml:base="http://www.alwaysbeshipping.com/"><div xmlns="http://www.w3.org/1999/xhtml"><p>Hiring top talent is hard.  Check out this video to see the lengths people will go to attract the interest of great product managers.</p>
<p> </p>
<p><iframe frameborder="0" height="349" src="http://www.youtube.com/embed/vgvTPGpTI4c" width="560" /></p><xhtml:img xmlns:xhtml="http://www.w3.org/1999/xhtml" src="http://feeds.feedburner.com/~r/AlwaysBeShipping/~4/7cN6jvtuIU4" height="1" width="1" /></div></content>



    <feedburner:origLink>http://www.alwaysbeshipping.com/2011/05/recruiting-product-people.html</feedburner:origLink></entry>
 
</feed><!-- ph=1 -->

