<?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[Building Fast and Slow - Medium]]></title>
        <description><![CDATA[Build products people love - Medium]]></description>
        <link>https://medium.com/building-fast-and-slow?source=rss----7bf279314138---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Building Fast and Slow - Medium</title>
            <link>https://medium.com/building-fast-and-slow?source=rss----7bf279314138---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:30:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/building-fast-and-slow" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The leftovers: what if all the Product Managers disappeared?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">The other day a good friend was pushing me to give The Leftovers a chance, a 2014 TV show where 2% of the population suddenly vanishes.</p><p class="medium-feed-link"><a href="https://medium.com/building-fast-and-slow/the-leftovers-what-if-all-the-product-managers-disappeared-9a282c773e2?source=rss----7bf279314138---4">Continue reading on Building Fast and Slow »</a></p></div>]]></description>
            <link>https://medium.com/building-fast-and-slow/the-leftovers-what-if-all-the-product-managers-disappeared-9a282c773e2?source=rss----7bf279314138---4</link>
            <guid isPermaLink="false">https://medium.com/p/9a282c773e2</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Carlos Oliveira]]></dc:creator>
            <pubDate>Mon, 22 Aug 2022 18:30:47 GMT</pubDate>
            <atom:updated>2022-08-18T19:48:45.616Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Good Managers Vs. Great Managers]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/building-fast-and-slow/good-managers-vs-great-managers-33db30b74a51?source=rss----7bf279314138---4"><img src="https://cdn-images-1.medium.com/max/2504/1*wMmmo7DxNN9vza0oY4o5uw.jpeg" width="2504"></a></p><p class="medium-feed-snippet">One of the most important aspects of building great product organisations is to design a system where builders thrive. A small group of&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/building-fast-and-slow/good-managers-vs-great-managers-33db30b74a51?source=rss----7bf279314138---4">Continue reading on Building Fast and Slow »</a></p></div>]]></description>
            <link>https://medium.com/building-fast-and-slow/good-managers-vs-great-managers-33db30b74a51?source=rss----7bf279314138---4</link>
            <guid isPermaLink="false">https://medium.com/p/33db30b74a51</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Carlos Oliveira]]></dc:creator>
            <pubDate>Tue, 02 Jun 2020 10:13:39 GMT</pubDate>
            <atom:updated>2020-06-02T10:13:39.287Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Product Strategy: Visualized — Part II /]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/building-fast-and-slow/product-strategy-visualized-part-ii-91d5112ef19f?source=rss----7bf279314138---4"><img src="https://cdn-images-1.medium.com/max/640/1*hTCgy_BFZ1dke3-vXOMJzA.png" width="640"></a></p><p class="medium-feed-snippet">In the last post we looked at what strategy is and the false contradiction between planning for strategy  and letting your product emerge&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/building-fast-and-slow/product-strategy-visualized-part-ii-91d5112ef19f?source=rss----7bf279314138---4">Continue reading on Building Fast and Slow »</a></p></div>]]></description>
            <link>https://medium.com/building-fast-and-slow/product-strategy-visualized-part-ii-91d5112ef19f?source=rss----7bf279314138---4</link>
            <guid isPermaLink="false">https://medium.com/p/91d5112ef19f</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[product-strategy]]></category>
            <dc:creator><![CDATA[Carlos Oliveira]]></dc:creator>
            <pubDate>Wed, 06 May 2020 13:09:12 GMT</pubDate>
            <atom:updated>2020-05-06T13:12:18.972Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[7 Powers — Product Strategy: Visualized — Part I]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/building-fast-and-slow/7-powers-product-strategy-visualized-part-i-1ee0b88e6f39?source=rss----7bf279314138---4"><img src="https://cdn-images-1.medium.com/max/640/1*_9GbKrZ0hEXc0T-8wRVgnA.png" width="640"></a></p><p class="medium-feed-snippet">There is a recurrent thread going on in tech circles that contrasts 1) the philosophical approach of companies that have adopted the lean&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/building-fast-and-slow/7-powers-product-strategy-visualized-part-i-1ee0b88e6f39?source=rss----7bf279314138---4">Continue reading on Building Fast and Slow »</a></p></div>]]></description>
            <link>https://medium.com/building-fast-and-slow/7-powers-product-strategy-visualized-part-i-1ee0b88e6f39?source=rss----7bf279314138---4</link>
            <guid isPermaLink="false">https://medium.com/p/1ee0b88e6f39</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[experimentation]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Carlos Oliveira]]></dc:creator>
            <pubDate>Wed, 06 May 2020 13:07:48 GMT</pubDate>
            <atom:updated>2020-05-06T13:07:27.792Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Fast & slow metrics: Conversion Rate]]></title>
            <link>https://medium.com/building-fast-and-slow/fast-slow-metrics-conversion-rate-e5aff3b40433?source=rss----7bf279314138---4</link>
            <guid isPermaLink="false">https://medium.com/p/e5aff3b40433</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[conversion-optimization]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[metrics]]></category>
            <dc:creator><![CDATA[Carlos Oliveira]]></dc:creator>
            <pubDate>Thu, 16 Apr 2020 10:52:23 GMT</pubDate>
            <atom:updated>2020-04-16T10:58:30.934Z</atom:updated>
            <content:encoded><![CDATA[<p>This is part II of a series from <a href="https://medium.com/u/f6ec8c23f9b4">Carlos Oliveira</a> at <a href="https://medium.com/building-fast-and-slow">Building Fast and Slow</a> around how to think about your key metrics when building consumer products. In this second post, we look at one of the primary indicators companies use to increase their Average Revenue Per User, build audiences, increase orders and which has a whole field of optimization dedicated to it: Conversion Rate (CR).</p><h3>Talking about Conversion Rate</h3><p>The basic formula is dead simple:</p><blockquote>Conversion Rate = Completions / Users</blockquote><p>So if you run a commerce operation and your ultimate completion is an order, say you had 1000 users and those users made 10 orders, your conversion rate is 1%. Easy, right?</p><p>I agree. It’s easy to monitor, easy to compare, but over time, and as you grow, looking at <strong>all your users</strong> and <strong>comparing them to all your orders</strong>, becomes unhelpful when it comes to making product decisions.</p><h4>Breaking it down</h4><p>The most common and useful way to break Conversion Rate down is to use time. Say you’re looking at users who convert within the first day we’ve seen. them on the website. We’re now analyzing something like:</p><blockquote>Conversion Rate (1d) = Completions (1d) / Users (1d)</blockquote><h4>But… sessions</h4><p>If you’ve ever used Google Analytics(GA), for example, you’re now wondering how this is comparable to their definition. In GA, conversion rate is calculated using completions and sessions.</p><blockquote>Conversion Rate (GA) = Completions / Sessions</blockquote><p>A<strong> session</strong> in GA <strong>is a variable time interval</strong>, that begins when <strong>the user first arrives at the site and expires 30mins after their last interaction</strong>. One obvious consequence is that one user can have multiple sessions.</p><p>The point of the session definition is to try to capture one of your user’s visits to a website until they’ve left. If within 1000 sessions, there have been 10 orders, your conversion rate is 1%.</p><p>For the standard definition, GA doesn’t actually care if those sessions came from 1 or 1000 users. If your whole 10-member family is rooting for you and visiting your website 10 times a day for 10 days, that actually can account for your 1000 sessions. If your mom bought one article a day to boost morale, that could account for your 10 orders. Google only cares whether those visits (or sessions) turned into a purchase or not.</p><p><em>It </em><strong><em>does</em></strong><em> tell you how many users were behind your session count and allows you to change your definition, so it’s worth keeping an eye on both.</em></p><p>That definition, however, as you probably captured by now, changes everything. If you look at your 10-day conversion rate, it would vary between:</p><blockquote>CR = 100% (10 orders / 10 users)</blockquote><blockquote>CR = 1% (10 orders / 1000 sessions)</blockquote><p>Which, if you’re wanting to make actionable decisions, might actually change everything.</p><p>Wait, there’s more. The question you were probably trying to ask by looking at your 10-day conversion rate before you started drilling down, was “how many users have ordered something from me?”</p><p>That’s really 10%, right? All the orders came from our mom, and only 10 family members can actually account for all the visits!</p><blockquote>CR = SUM(Unique Orders / User)</blockquote><p>And that’s before we start worrying about double-counting users (if they’ve visited on different devices, for example, and we can’t figure out that that’s actually the same person).</p><h4>So what SHOULD we care about?</h4><p>What you want out of whatever way to measure CR you choose is that it is actionable, that it gives you a way to measure progress through time and make useful comparisons between groups.</p><p>So let’s look at how differences in looking at the metric can affect the decisions you make with it.</p><p>Imagine applying different timeframes will make your conversion graph plot something like the below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6aNye3RMcGVb7A1X03Lk6Q@2x.jpeg" /><figcaption>CR over longer and longer timespans for the same user groups</figcaption></figure><p>With a chart like the above, it may be relatively easy for you to identify a website/app change that affects your 30-min CR (a 10% improvement in session CR would take you from 5% to 5.5%).</p><p>That might barely if at all register on your 7-day or 30-day CR, since these improvements might be <strong>either negatively offset over that period, or just be small enough as to not even show on that long enough timescale and user base</strong>.</p><p>Sometimes, you might even see the opposite effect, with that specific change decelerating the CR progression curve and causing it to stall sooner since there was an unforeseen (negative) effect downstream.</p><p>Here are a couple of examples.</p><p>Example 1:</p><p><strong>Session-1 (30min) CR increases by 10%</strong></p><ul><li>This happened because you’re offering a 30% coupon for users who buy on their first visit, which led to</li></ul><p><strong>a decrease in Session-2+ purchases</strong></p><ul><li>Which happened because word got around about the campaign and new users flooded your site with instinct purchases, which then led to</li></ul><p><strong>30-day CR going down</strong></p><ul><li>Which in turn was because many of those customers who didn’t end up buying in their first session actually returned less than your typical new customer to the website. To add to that, your returning customers actually felt disappointed they were excluded from the promotional cohort and ended up purchasing less.</li><li>In this scenario, to measure the net success of the campaign, you’d need to compare and contrast behavior across both cohorts (new vs returning) and understand whether the end result was a net positive.</li></ul><p>Example 2:</p><p><strong>7d CR up</strong></p><p>You’ve launched an aggressive basket abandonment campaign that targets users 3 days after they’ve left the website with something in their basket. This leads to some of those customers coming back and purchasing on their 3rd day, increasing conversion rates on the 7-day timespan, but led to</p><p><strong>fewer returning visitors in weeks 2–4</strong></p><p>What you’ve noticed is that there is now a reduction in visitors coming into the website on weeks 2–4. A lot of people were annoyed by your insistent email and have either unsubscribed or just not visited the website at all, let alone your basket page. This led to</p><p><strong>30d CR going down</strong></p><p>As the conversion rate improvement through your email clickthrough cohort was completely offset by those who visited less and unsubscribed from your communications.</p><p>There are multiple causal reasons for phenomena such as the one described here (and others) to occur, so it’s important to not take the numbers at face value and dig deeper into users’ behavior to understand what behaviors we have introduced through this change, as well as what we were trying to incentivize.</p><p>It is also important to have an evaluation criterion that reflects not just what could happen through a positive result, but also what types of scenarios could occur if the experiment went wrong (and choosing monitoring metrics that account for that).</p><h4>Heuristics for decision-making</h4><p>Your brain will be primed to start thinking about this as you develop a sense for the types of results experiments may produce, but there are a few questions/heuristics that might come in handy as precautionary measures when trying to move the needle on CR, though:</p><ol><li>Is CR the ultimate metric we want to affect? (i.e. is this a funnel efficiency problem)</li><li>What secondary metrics can we measure that would let us assess the trade-offs of our decision? (7-day retention, % order returns/complaints per order, visit frequency, % users with a 2nd order)</li><li>What is our typical purchase window and how do we capture the behavior we’re looking to effect? (e.g. do our target users shop once a week or more, do they browse a lot before purchasing and only purchase a couple of times a year, is there a bimodal distribution where some purchase on a whim and others take a long time to decide? — this might change our key metric time window as well as our secondaries/monitoring)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aeh2WviQJWxjf7R-athADg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YUFskPQSFGjmwmkL1-4w-w.png" /><figcaption>Two distinct conversion behaviors. One where customers typically complete their task within the first three days of initiating their shopping, with a long tail of longer-horizon purchases (7 and 30d), and a second where purchases either happen on a whim (within their first session or their first day of shopping) or wait a long time to make their purchase decisions (7d). Selecting different conversion indicators as your key metric could yield significantly different results for your optimization efforts.</figcaption></figure><h4>Almost done: Don’t forget to define what a user is</h4><p>Finally, this may look like a no-brainer, non-issue, but more often than not, it is not. How are you tracking your user count?</p><p>If it’s a web app, do you keep an ID that’s set on the user’s cookies on their first visit? Are you double counting mobile web and desktop users?</p><p>If you do, when do they expire? How and when are they set?</p><p>Do you use that ID to allocate them to your experiments?</p><p>When the user logs in and you can identify them, do you reconcile and backfill your data or is there a chance you’re double-counting in places?</p><p>This may sound basic but there are loads of confusion around what a user is, how to handle corner cases, and how that affects test samples and experimental groups. Knowing and understanding how it affects your comparisons and your analysis is key to making good decisions and optimizing your conversion rate.</p><p>That’s it! If you want to know more about key product metrics, Part I is <a href="https://medium.com/building-fast-and-slow/fast-slow-metrics-ltv-loyalty-1008e07ca47d">here</a> and you can read more about product management techniques on my <a href="https://medium.com/@colivetree">profile</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5aff3b40433" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-fast-and-slow/fast-slow-metrics-conversion-rate-e5aff3b40433">Fast &amp; slow metrics: Conversion Rate</a> was originally published in <a href="https://medium.com/building-fast-and-slow">Building Fast and Slow</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fast & slow metrics: LTV & Loyalty]]></title>
            <link>https://medium.com/building-fast-and-slow/fast-slow-metrics-ltv-loyalty-1008e07ca47d?source=rss----7bf279314138---4</link>
            <guid isPermaLink="false">https://medium.com/p/1008e07ca47d</guid>
            <category><![CDATA[lifetime-value]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[retention]]></category>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[loyalty]]></category>
            <dc:creator><![CDATA[Carlos Oliveira]]></dc:creator>
            <pubDate>Mon, 13 Apr 2020 10:26:48 GMT</pubDate>
            <atom:updated>2020-04-13T10:26:48.229Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the first post of a series from <a href="https://medium.com/u/f6ec8c23f9b4">Carlos Oliveira</a> at <a href="https://medium.com/building-fast-and-slow">Building Fast and Slow</a> around how to think about your key metrics when building consumer products. In this first post, we look at one of the cornerstones of the economics of internet businesses. Customer lifetime value, or LTV, and its interplay with loyalty programs.</p><h3>How to move the LTV needle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Faro5cY8XKvYL0AiQcq6ww.jpeg" /></figure><p>In general, any loyalty scheme is built around two key factors that brands use to incentivize customers in order to drive their Lifetime Value (LTV): one that’s financial, another that’s emotional.</p><p>On both accounts, what we’re doing is creating an incentive for our user that generates a net positive effect on Average Revenue Per User (ARPU), within a reasonable payback period given the SAC/CAC we incurred in (Subscriber Acquisition Cost/Customer Acquisition Cost), our Running Costs (and runway) and our Cost of Capital (WACC).</p><p>Usually, that is done by offering the customer a discounted offer on their current or proximal purchase / spend (with said discount in the form of price, promotion, convenience — such as shipping costs or upgrade options), <strong>which actually negatively impacts someone’s ARPU within a short time frame, while lowering the cost of their preference on a subsequent purchase (reacquisition costs, lowered price sensitivity), thus ending up positively impacting SAC/CAC and ARPU within what is called the payback period</strong>, through volume in incremental purchases.</p><p><strong>If done effectively, it significantly raises barriers to exit, by virtue of a positive feedback loop that promotes an on-going relationship with the brand,</strong> where it becomes first to mind.</p><p>If not, the pitfalls of LTV kick-in and companies run out of runway before they make their CAC/LTV equation pay off — uber is a recent famous example where Venture Capital was used to drive growth with a clearly unsustainable CAC/LTV formula, to drive out competitors and establish a dominant market share in key geographies. One key thing to understand about LTV is that it is, by definition, very lagging. Because we’re waiting for a long enough time to come to completion in order to compare different cohorts of customers, we need many micro-moments of interaction with our brand touchpoints to occur, before decisions are made.</p><p>In order to measure their effectiveness, we want to look at incrementality. Typically those that are more sensitive to the effects of loyalty programs are already those more intent on purchasing frequently, typically leading to a self-selection effect emerging through the data, particularly when cohorts aren’t too big, making it hard for companies to understand the individual impact of their benefits and incentives.</p><p>For larger cohorts, companies can create holdout groups to control for these effects. The operating trade-off here is that you usually want to ensure your most loyal customers are immediately included in the program, getting full access to its benefits, and feeling that they’re valued, which makes things harder for those measuring it, as it may lead to an unreliable comparison with the holdout, which contains none of your most engaged customers. However, hard to measure isn’t impossible, and there is very strong reason to run cohort analysis, split testing whenever possible and even controlled experiments in order to successfully optimize loyalty programs.</p><h3>Loyalty driving LTV</h3><p>Let’s now look at a few well-known examples of brand loyalty incentives, aimed at increasing LTV through incremental ARPU. These include:</p><p><strong>/Paid Bundled offerings</strong></p><p>An interesting but hard to nail value proposition is a paid-for membership. Customers are required to pay for a subscription themselves (driving ARPU), which they will make up for in accrued value over time (potentially increasing Costs). The most famous is Amazon Prime, where customers pay a flat monthly/yearly fee to get free next-day delivery (which could cost up to $10+ per delivery). Additionally, Amazon has added a series of value-add services to the subscription (such as Video and Music), which incentivizes customers to continue using it for their commodity purchases, as well as to keep paying for continued access to their ancillary products.</p><ul><li>Amazon Prime</li><li>B&amp;N</li></ul><p><strong>/Spend-level offerings</strong></p><p><strong>//Tier-based</strong></p><p>Tier-based programs are normally based on customers’ spend with the brand to gamify their relationship, using the promise of further rewards as a way to incentivize their continued relationship with the brand (+ARPU). The more customers have spent, the better (and more expensive for the brand, +Costs) the incentives would be, playing on both the economic function of the rewards, as well as the social status associated with them.</p><ul><li>Sephora (+ community)</li><li>Farfetch</li></ul><p><strong>//Point-based</strong></p><p>Points-based programs tend to use the same spend-based mechanism to reward customers, but they accrue points towards a flexible system within which a monetary function exists, to collect rewards towards their next purchase. This incentivizes customers to spend again within the points’ lifetime. Airlines are famous for rewarding frequent travelers with points, promoting them to not only stay loyal on their frequent business routes, but to also use them for personal travel. The high barrier to entry with points systems, also means that once customers are engaged and understand the point system fully, they become their biggest distribution channels.</p><ul><li>Nordstrom</li><li>Airline Miles</li><li>Nectar points</li></ul><p><strong>/Coupons &amp; cash rewards based</strong></p><p>Another type of loyalty scheme consists of rewarding customers directly with either cash back or coupons towards their next purchase. Whereas cashback ensures a customer uses a given card network or affiliate site (which pays customers out of the commission they get for driving the purchase), coupon-based loyalty schemes typically offer coupons towards a customers’ next purchase based on their own / their peers’ buying habits, diversifying customers’ basket of purchases and driving habitual purchasing behavior.</p><ul><li>Cashback schemes</li><li>Branded credit cards</li><li>Retailer loyalty cards</li></ul><p>Customers make upfront investments in a brand in order to recoup them, over time, multiplied. Brands lower their margins for these segments in exchange for incrementality, ultimately driving lifetime value. By engaging with the program, there is also the expectation on the part of customers that they will come back, which is not always true — see projection bias — and that there’s a positive trade-off in choosing the seller over a competitor in a subsequent purchase. Rational or not, this guarantees that a larger share of wallet will be spent with the brand than would otherwise be the case.</p><p>Demand, once bought in, also tends to be less price elastic and more prone to making emotional decisions, thus more sensitive to coupon marketing, abandoned basket messaging, exclusive campaigns for commoditized / brand goods, sales seasons (particularly when combined with the possibility of creating exclusivity for loyal members).</p><p>Having programs such as these allows brands to create influence networks that treat power users as stars, growing their own<a href="http://tomtunguz.com/controlling-your-destiny/"> proprietary distribution channels</a>: If they become aspirational references for the masses, those who retain the greatest value out of these programs (the points addicts, the platinum card customers, the early adopters), then become a company’s greatest advocates, each bringing in many new customers and inspiring tens to thousands of less-than-committed followers. Not all of these will become power users themselves, but by virtue of believing that that is true, they’ll still prefer buying with the brand and chasing ever-fleeting rewards, which lowering acquisition and re-acquisition costs.</p><p>Finally, another lens through which to look at driving LTV through increased ARPU is the softer version of loyalty. Companies drive retention and loyalty through excellent levels of <a href="https://www.amazon.com/Nordstrom-Way-Customer-Service-Excellence/dp/1118076672">Customer Service</a>, frictionless purchase experience (1-tap checkout), emotional attachment, or sunk data costs (such as your friends’ graph, a fully organized photo album or all your phone’s data fully backed up). The issue again is measuring the effectiveness of these practices beyond a principled approach to product and customer service, beyond the elusive but instinctive common sense.</p><p>As Jeff Bezos insists, however, “Your margin is my opportunity”, and driving excellent standards of customer experience has never been known to hurt a brand.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1008e07ca47d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-fast-and-slow/fast-slow-metrics-ltv-loyalty-1008e07ca47d">Fast &amp; slow metrics: LTV &amp; Loyalty</a> was originally published in <a href="https://medium.com/building-fast-and-slow">Building Fast and Slow</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Budgeting as a Product Team]]></title>
            <link>https://medium.com/building-fast-and-slow/budgeting-as-a-product-team-2abc98000f98?source=rss----7bf279314138---4</link>
            <guid isPermaLink="false">https://medium.com/p/2abc98000f98</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Carlos Oliveira]]></dc:creator>
            <pubDate>Mon, 04 Nov 2019 15:25:39 GMT</pubDate>
            <atom:updated>2020-05-13T13:47:05.251Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product Teams: Stop Estimating, Start Budgeting</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/481/1*l0bc2HiMXVqdp2hyxgRc_A.png" /><figcaption>Forecast like you mean it — <a href="https://xkcd.com/1606/">https://xkcd.com/1606/</a></figcaption></figure><p>Why do we so often ask teams to estimate in detail how much effort is required to build a product, and to that upfront? There’s evidence that this lead us to output-oriented thinking, premature optimization, bloat and generally a commitment to suboptimal solutions that are designed with too many assumptions and a lack of clarity on the problem space.</p><p>Yet the main reason, I’d argue, is that estimation is an entirely rational risk mitigation strategy. Some of the reasons might be that:</p><ul><li>1) we’re promising to build a product for price X, when it’s going to cost us more than X-M, where M is our minimum acceptable profit margin. Maybe we don’t want to build this thing.</li><li>2) there are explicit and irreversible costs to not meeting a deadline and we want to minimize the risk of not doing so, so that we can organize and dedicate appropriate resources to it.</li><li>3) we are uncertain of the returns it will yield, so we want to be sure that we’re not overinvesting vs what we have in the bank.</li></ul><p>That’s all fine, but I argue that diminishing returns to estimation happen pretty early in the effort scale, and discount your ability to respond to future ambiguity. Teams should focus on simple, transparent budgeting, asking themselves a few key questions:</p><ul><li>how much runway do we have to build this? E.g. a start-up may need to get a particular feature out the door in about a month to test market appetite. A scale-up might need to deliver a big product stream within a year to capture the returns of that investment in the next financial exercise.</li><li>how much of that runway do we want or need to bet on this particular problem? Is it a bet the company move? Are we hedging our bets with 3/4 major plays? Are we just seeking initial validation?</li><li>Do we believe we need to acquire additional resources in order to fund these goals? Why? Is there anything we could drop instead? Do we know enough to make the decision?</li></ul><h4><strong>Clarifying Runway</strong></h4><p>Teams should be formed and funded to solve a specific problem or need, not given a fully shaped answer already. Understanding and negotiating the right runway to answer a given question upfront is an important part of the process.</p><ul><li><strong>Do we know the problem we’re solving well enough? </strong>Follow-up: How much funding do we need to figure it out? Can we meet in a few weeks to talk about what we’ve learned?</li><li><strong>Does this look too big for our team? </strong>F: How do we break this down? What’s our first goal and how much budget do we want to allocate to it?</li><li><strong>Have we discovered a major hurdle or roadblock? </strong>F: Are we likely to run out of runway to tackle it or can we solve with the current constraints?</li></ul><p>The right level of constraint fosters creativity, productivity, and agility, so managing your burn rate towards your expected outcomes<strong> as a team</strong> should be a fundamental part of your day to day discussions. When questions such as the ones above arise, when you can’t solve them within the budget you have, there’s a frank conversation to be had with your investors (either internal or external), to get a portfolio take on it and use your voice in a forum where you can advocate for the right resource structure given your current level of knowledge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ACTwcl5yM7RT9UK4qHQE_Q.png" /><figcaption>If you’re estimating you need to have converged on solution and sized it to a very narrow shape. Budgeting allows you to choose what to invest in and leave room for teams to figure it out.</figcaption></figure><h4><strong>Betting</strong></h4><p>Now when you’ve worked out your current runway (give us 3 months to work on this), it’s up to you as a team to decide how best to use it. People should share a stake in outcomes, so that they’re accountable and responsible for their achievements.</p><p>For simplicity’s sake let’s take money out of the picture. You have 5 highly qualified team members and 12 weeks of runway. Each team member gets 12 coins, which they can spend as they please. They can use it for experimentation. They can use it to solve technical debt. They can use it for foundational work with a longer payback period. They can manage their ROI horizon so long as there is team buy-in. As a team, your communication becomes about whether you’re using your runway the right way given the problem you have to solve, how much do we believe in our solution, how much evidence we have to back it up, and how to we maximize our personal time investment.</p><p>A great product manager, I’d say, maximizes this ROI function for their team. They devise the right investment strategy proposal, offer their teams the right level of information so they make informed decisions and good trade-offs, and continuously evaluate and communicate said strategy in the presence of new information — did we get results back from users? Are we becoming more confident about the value this represents?</p><p>They also let others take the lead and own solutions, emergent problem exploration or resource allocation plays, devoting their time to synthesising the outcomes into a good map of where we’ve been, what we know, and where we’re headed. Are we getting bang for our buck?</p><h4><strong>Funding</strong></h4><p>Finally, acknowledging that you need funding as early as possible in the process, whether it’s in the shape of time, money or both, is important. “Gotcha!”, you’d rightly say right about now. In order to know whether you need funding, you’d have needed to estimate whether your runway is sufficient to meet your goals. I don’t disagree. I argue though, that accuracy gains in product development estimates are quickly offset by the time and cost of those gains, particularly for complex problems where you have too many unknowns and need to make up assumptions to move forward. You should be making a continued assessment based on risk and reversibility while reducing unknowns and assumptions using a diverse set of viewpoints and tactics. Set your ego aside and ask honest questions, be open to change, be confident enough to bet.</p><h4><strong>Reviewing and Restructuring</strong></h4><p>Once you start budgeting and funding, as you become better at breaking problems down, identifying key assumptions, incorporating new information, assessing risks, potential returns, modeling your predictions and even improving your productivity, deep and detailed estimation will become much less important, while systematic flow will grow in relevance. We’re able to define bite-sized chunks of our larger meal, and use what we’ve learned to move forward in the right direction, gaining momentum.</p><p>Keeping a healthy bets portfolio and shipping consistently against it becomes ever more important and reviewing your investment strategy often, understanding the shape of each of your investment’s returns, is a fundamental exercise.</p><p>At a portfolio level, organizing teams in relation to the structure of your needs, your runway, and your risk level becomes the better lens through which to look at the world and gives individuals the authority to go out and discover the best solutions to your current problems, especially with healthy and regular feedback mechanisms in place.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2abc98000f98" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-fast-and-slow/budgeting-as-a-product-team-2abc98000f98">Budgeting as a Product Team</a> was originally published in <a href="https://medium.com/building-fast-and-slow">Building Fast and Slow</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should you use OKRs? A look at Framework-Organisation-Fit]]></title>
            <link>https://medium.com/building-fast-and-slow/should-you-use-okrs-a-look-at-framework-organisation-fit-39f8961f0679?source=rss----7bf279314138---4</link>
            <guid isPermaLink="false">https://medium.com/p/39f8961f0679</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[okr]]></category>
            <dc:creator><![CDATA[Carlos Oliveira]]></dc:creator>
            <pubDate>Mon, 22 Jan 2018 20:16:59 GMT</pubDate>
            <atom:updated>2018-01-22T21:08:55.516Z</atom:updated>
            <content:encoded><![CDATA[<p>When we talk about organisational models and systems of incentives as applied to companies, the conversation often (as with other topics) falls into dualism - implementation are wrongly pictured as just black or just white, nuance is removed from the conversation and the pitfalls of applying an incentive structure and goal-setting framework to an organisation are a second class citizen.</p><p>By system of incentive, I generally mean an organisational framework that allows departments and teams to define and pursue a given strategy, set goals, monitor their progress and celebrate their achievements. These frameworks end up defining which behaviours get rewarded, who progresses in their careers, which teams and individuals are considered high-performers, what metrics are in the company’s dashboards and what colours they’re displayed in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ms8KHNZ5zjPxKw2A56R_hw.png" /><figcaption>Geckoboard’s Mixpanel example integration with key web metrics</figcaption></figure><p>It is clear that these shouldn’t be taken lightly. Every rational individual within a given company will steer their behaviours towards what is rewarded, so these frameworks end up playing a fundamental role in defining the emergent and fractal set of behaviours we call culture. When executives try to create cultural shifts by architecting these incentive systems, they need to simplify the mental model of their organisation to a set of characteristics that need to be optimised. For example, one might be trying to increase throughput and decrease bureaucratic overhead, noble goals, so they deploy a system or framework to incentivise teams and employees to do so.</p><p>This post looks at how culture plays such a big role in the effectiveness of the models and framework of choice, and how when heavily optimising for some easily legible traits, you might fail to introduce checks and balances to counterweigh their negative consequences and other n-th order effects.</p><h3>Let’s talk about OKRs</h3><p>OKRs are an evolution of <a href="https://en.wikipedia.org/wiki/Management_by_objectives">Management By Objectives</a> and were initially used at Intel during Andy Grove’s tenure and have since skyrocketed in popularity after Google popularised them. They are one of the most commonly used goal-setting and tracking frameworks. On the surface, OKRs seem fairly agnostic: You have an organisational goal, so you write an objective that reflects it. Then you link it to a series of Key Results (you think would mean you were successful in attaining your objective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/292/1*n8UNScqhYli8a2_b5XDgBQ.jpeg" /></figure><p>OKRs allow departments and teams in large organisations to align their local objectives to the executive and strategic goals , they provide a means for teams to feed back into what their Tribe / Cluster / Department’s goals should be, and they’re supposed to be stretch targets — i.e. achieving 60–70% of your goal should be considered a success.</p><p>So it looks like a pretty good deal — and very often, it is. It provides a framework for alignment at scale, they rally people behind a measurable key result rather then the Product Manager or Department Head’s pet project, they give you clarity and focus and they are ambitiously set to force teams to go the extra mile in achieving their goals.</p><p>Now, Google themselves have recognised some of the pitfalls of deploying this approach at scale. There are some <a href="https://rework.withgoogle.com/guides/set-goals-with-okrs/steps/avoid-OKR-writing-mistakes/">easy traps</a> Google found are easy fall into and orgs should do their best to avoid them. For example:</p><ol><li><strong>Miscommunicating stretch goal OKRs</strong> — misunderstanding and misalignment between teams about how ambitious their OKRs are. If dependencies exist between teams, they’ll often be committing internally to a different threshold of success. Say for example Team A expects Team B to deliver Impact X on Metric Y. Only if Team B delivers on Metric Y, would Team A’s KR that looks at moving Metric Z be accomplished. This can lead to frustration and lots of fingers pointed at other teams.</li><li><strong>Business-as-usual OKRs — </strong>Team-centric OKRs (as opposed to customer-centric) are also a fan favourite. They are chosen by the team to guarantee they keep working on their favourite project and they don’t necessarily move the needle on the company’s strategy. A common counter-tactic is to stack rank all OKRs and guarantee people are always allocated to higher impact OKRs.</li><li><strong>Sandbagging</strong> — is, again, to guarantee team’s goals look like stretch targets but aren’t necessarily so. The team knows they’ll get there if they stay course and they might even have time and energy left for that one great project they wanted to do anyway.</li><li><strong>Low-value objectives</strong> — the name says it. They might be hard to get to, they might keep you busy, but they’re not really worth the effort and they won’t produce impact at the company level. Again, stack ranking might help keep people focused and incentivised to do right by their customers.</li><li><strong>Insufficient key results for objectives</strong> — Google’s final piece of advice is to ensure objectives are appropriately funded by their associated key results. It is easy to set stretch objectives but then only commit to hyperrealistic results (i.e. Business As Usual KRs). Achieving your KRs needs to mean your objective has been fulfilled.</li></ol><p>Apart from team-level pitfalls with OKRs, there are a few organisational ones that are easy to stumble on and are worth noting:</p><p>6. <strong>OKR blindness —</strong> Now uou’ve set your goals, have a measurable way of tracking their achievement and you’re on your way. Depending on how your company is structured, though, this can easily degenerate into a culture of self-interest and lack of peripheral vision. It doesn’t suddenly make good people turn bad. It can, however, provide the wrong incentive, causing people to forget about the complexity of the business, its changing needs, and oversimplify complex market needs to assume that the team’s <strong>only job </strong>is to deliver on theirs. Say, in this case, Marketing team A needs your team’s assistance to unblock a major promotional campaign that is likely to increase sales by 20%. Team A doesn’t have any engineering resource, and it would take a developer-day away from your sprint. If none of your OKRs matches that need and you’re tight on time, your incentive structure could mean they get rejected, even if you are the right team for what was, in the grand scheme of things, the right job. In medium/large organisations, which are always subjected to a form of unit/functional/matrix slicing, dependencies are very natural (even between technical teams) and solving them requires empathy, cooperation and a world-class prioritisation toolkit.</p><p>7. <strong>Incrementalism — </strong>Another trap to look out for with OKRs is a strong bias towards small iteration and incrementalism. Because the initial target is quite arbitrary, there is a tendency for continued motion, path dependency and continuity. If a team has set a stretch goal and has spent 3 months toiling away to achieve it, it’s very unnatural to then diverge in their next OKR planning session (which often happens a mere 1.5 months after their current cycle has begun) and set a completely new goal because of a new piece of information. The easiest thing to do is to keep trying to solve the problems you’re good at, iterating and incrementing your product, with little regard to how it fits the company’s current state and its market.</p><p>8. <strong>Local optima — </strong>Inflection points are hard to detect, more so with a framework that is poised to be ambitious, sets SMART goals and offers a clear and legible explanation of the company’s strategy. It is extremely difficult to detect that you might be stuck in local optima while in the midst of the struggle, deep in the build trap. The ability to learn at scale is one of the most important characteristics of fast-paced, high-growth organisations. Creating a structure that allows companies to reinvent themselves is hard and how Apple and Amazon chose to do so is extraordinarily different (Depth vs Breadth). It’s important to give teams the skills to learn as fast as they can, and the freedom to expand and move away from their OKRs if they discover they’re solving the wrong problem, otherwise your perfectly crafted Key Results can be the fastest route to a permanent state of Innovator’s Dilemma.</p><p>9. <strong>Fragmentation, </strong>which is extremely hard to counter as companies grow, is the results of the natural tendency for hyper-specialisation and the entropy and friction that arises from multiple teams trying to solve problems that are too specific. OKRs can make this worse if left unchecked. Teams will disregard others’ goals, build their own solutions to already solved problems, all to reach their quarterly targets. It can lead you down a dangerous road of divergence without alignment, creating force vectors that prevent the business moving forward, rather than propelling it with greater strength in the direction of focus.</p><p>10. <strong>Premature convergence</strong> — Because people are often painfully aware of the pitfalls outlined thus far, OKR exercises can be hard, take away large chunks of every middle manager’s time and end up compromising on least common denominator goals due to time pressures, dependency bottlenecks, budget constraints, legacy tech, top-down directives or lack of team buy-in. These and other factors can aggravate the fact that OKRs objectivity and focus can actually be detrimental if you’re solving the wrong problem. We need to stop and consider they might actually be<strong> too specific (hint: if they map one-to-one with a task, they are) </strong>and it would be empowering to teams in many organisations to receive high-level direction with a framework for accountability, without implicitly prescribing the tactics to success via proxy metrics.</p><p>Teams in regular 3-month cycles may soon discover they’re not able to have the impact they were supposed to, but not have the contingency to change plans as that would mean diverting from a largely arbitrary target. They also often fall into the sunk cost fallacy, and remain convinced that they’re solving the right problem because that’s what they committed to 3 months ago.</p><h3>What these problems say about OKRs (and other incentive frameworks)</h3><p>Some obvious patterns emerge when looking at what these pitfalls signal about large scale organisations. One is companies are complex, living organisms and applying a blanket system of incentives (whatever it may be) will oversimplify the network of interactions and behaviours across teams building product. Any framework we choose needs to have strong guardrails and counterweights to account for possible traps, as well as have contingency plans built into them that incentivise teams to stay smart, keep optimising, stay focused, share widely and collaborate to discover what the right problem to solve is.</p><p>In the case of OKRs, organisations soon discover that:</p><ol><li>it is unnatural for people to set unachievable goals</li><li>that dependencies are often poorly reflected in them</li><li>that teams can take advantage of the model to signal success</li><li>that a disconnection between biz goals and KRs, as well as between KRs and objectives often emerge</li><li>that highly-specific short-term goals can hinder creative behaviour and long-term thinking</li><li>that solving for incremental optimisation at a local level doesn’t always equate to global growth</li><li>that fragmented, team-level (or functional) goals can dissolve how much value customers end up receiving.</li></ol><h3>What will your organisation amplify</h3><p>This post focuses on OKRs because that’s what most companies have chosen to use over the last 10 years after Google popularised them. The principles of framework-organisation-fit, though, apply to every model in every organisation. Organisations should plot their models, their cultural traits and their ambitions, against the benefits and the pitfalls of their goal-setting framework.</p><p>They should also be aware of the fact that while they may be looking at both the model and their org in a mostly unidimensional manner (pros and cons, good and bad), the end result is a complex matrix. Think of it like multiplying an Nx1 matrix by a 1xM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*XoGXBgvHilNBOIIADicdTg.png" /><figcaption>The resulting matrix is a lot more complicated than its originators.</figcaption></figure><p>The end result is an NxM matrix, a complex reflection of how each individual trait of your model influenced every single aspect of your company’s genotype. You should be aware that, unlike on paper, what this matrix ends up looking like is very often extremely unpredictable as there are dependent variables all over the place and hidden layers your model of reality won’t be able to reflect. Likely there will be nth-order effects that will need to be managed. This is fine. Test &amp; Learn, iterate quickly, do your OODA loop as fast as you can once you acquire a better understanding of what the end result actually should be.</p><p>Remember that the end result may or may not be net positive for your organisation, so hard leadership decisions will have to be made — has this change provoked the positive effects we expected? Have we managed to contain and turn any negatives into strengths? Are you now better prepared to respond to the challenges you started with?</p><h3>How to predict the future</h3><p>So far we’ve looked in detail at how you can create positive change by modifying the incentive structure in your organisation. How OKRs can be that driver but need orgs to either already have or be ready to develop a set of cultural traits that make them succeed. How a seemingly linear multiplication can result in a complex behavioural matrix that can be net-positive or negative depending on your goals, your culture and the maturity of your organisation.</p><p>A few tips from the battlefield on how to predict the future and make sure that you maximise your chances of success with OKRs or another strategic objective framework.</p><h4>1. Don’t push large-scale changes from a single functional lens</h4><p>Get buy-in. At the exec level. Use it to get buy-in across the whole org. This will not work if Product people set OKRs that no-one cares about. It will also not work if Engineering set OKRs to work on large projects with no view of the impact to the customer. It will not work if you “forget” to tie it to your strategic goals.</p><p>Everyone involved needs a deep understanding of why you’re changing the game and they need to be completely involved from the start.</p><p>Say you choose a similar structure to <a href="https://blog.crisp.se/wp-content/uploads/2016/06/Spotify-Rhythm-Agila-Sverige.pdf">Spotify’s Rhythm and the DIBBs framework</a>. It won’t accrue to much if <strong>Data</strong> used isn’t available, reference-able and prioritizable, visibly linked to the company’s needs and directly connected to its most important goals, if the <strong>Insights</strong> you’re extracting aren’t understandable and can’t be challenged by teams on the ground, if resulting <strong>Beliefs</strong> aren’t widely shared, culturally and contextually relevant, and if teams don’t clearly understand the <strong>Bets </strong>they’re going to make and why.</p><blockquote>They need to know the problem they’re solving, how they know it’s a real problem and how they will know if they’re making progress towards achieving it.</blockquote><h4>2. Map your organisation and reintegrate it to deliver on goals</h4><p>If you’re organisation is structured in tightly knit, sometimes competing units and they are given mismatched objectives, they will more likely than not aggravate the natural friction — there is natural tension between a unit focused on increasing the Average Order Value through cross-sell, and a Conversion Rate Optimisation unit, who are both given aggressive growth targets.</p><p>Your organisation needs tools to solve these problems autonomously, instead of falling back on analysis paralysis, constant escalation and turf wars. So whatever incentive framework you lay out, ensure that:</p><ol><li>people that need to work together are highly aligned, that they clearly understand the goals and the focus</li><li>relative priorities are clear (stack rank if you must)</li><li>small enough groups of people are empowered to autonomously deliver relevant outcomes without having to untie a web of dependencies</li><li>operating principles allow teams to invalidate assumptions and quickly change tactics</li><li>that multidisciplinary voices are participating actively in your delivery pipeline</li><li>ownership of the end product is not so diluted that no one person really feels they’ve accomplished something.</li></ol><h4><strong>3. Build guardrails and safeguards</strong></h4><p>With any structure, there will be need to be a clear problem description, a clear rationale to support it, and a sound way of monitoring progress: quantitively, qualitatively or, ideally, both.</p><p>If you’re deploying OKRs, take another look at the section on pitfalls and what your organisation will amplify. If there are obvious traps, design your initial plan so that they’re covered. Don’t dismiss them, deploying a new structure is hard so, <a href="http://codevoyagers.com/2016/03/16/design-like-youre-right-test-like-youre-wrong/">design like you’re right and test like you’re wrong</a>. Over-communicate. Don’t fail because of the <a href="https://d2h1nbmw1jjnl.cloudfront.net/ckeditor/pictures/data/000/000/157/content/slide2.png">known knowns</a>.</p><h4>4. Treat it as an experiment</h4><p><a href="https://en.wikipedia.org/wiki/OODA_loop">John Boyd’s OODA Loops</a>, assimilated into the industry as <a href="http://theleanstartup.com/principles">build-measure-learn</a> cycles, are categorised as <em>asymmetric fast transients</em>, the ability to change states extremely fast based on new information that invalidates previous beliefs. Whatever the model is, be sure to test small, scale it fast and iterate incrementally.</p><p>Feedback loops will be more valuable if they’re bottom-up, people need ways to provide structured feedback that allow you to action new experiment iterations at scale. Change never happens overnight, your new framework will need time to succeed, but it is no less important to keep an eye out for the unintended consequences, the impact it is having on your system, and any tribal behaviour or identity politics that have emerged as a consequence of a new found incentive structure.</p><p>If culture eats strategy for breakfast, as Peter Drucker famously said, be sure to give yours the breakfast of champions.</p><p><a href="https://www.linkedin.com/in/colivetree/">Carlos Oliveira</a> (<a href="https://twitter.com/colivetree">@colivetree</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39f8961f0679" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-fast-and-slow/should-you-use-okrs-a-look-at-framework-organisation-fit-39f8961f0679">Should you use OKRs? A look at Framework-Organisation-Fit</a> was originally published in <a href="https://medium.com/building-fast-and-slow">Building Fast and Slow</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fearless Products]]></title>
            <link>https://medium.com/building-fast-and-slow/fearless-products-a905c9ad9c52?source=rss----7bf279314138---4</link>
            <guid isPermaLink="false">https://medium.com/p/a905c9ad9c52</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Carlos Oliveira]]></dc:creator>
            <pubDate>Sat, 25 Nov 2017 09:46:00 GMT</pubDate>
            <atom:updated>2017-11-25T09:45:49.618Z</atom:updated>
            <content:encoded><![CDATA[<p>That some things are more important than others seems obvious. However, product creators often forget that any solution will invariably expose their points of view.</p><p>Being afraid to see your opinions and insights voiced will invariably result in bland, grey, soulless experiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*vEFHGbLvy4by4_BYA3cDRw.gif" /><figcaption>“Here’s everything everyone has ever cared about because we couldn’t decide what we were about”.</figcaption></figure><p>Not only will the result be boring, it’ll be unnecessarily confusing.</p><h4>“The Authentic Italian” — The imaginary story of a failed pasta place</h4><p>You look around your neighborhood. There are 10 different hamburger restaurants, 7 of them call themselves “gourmet”. There are also 2 pizza places. They serve pasta too, but they’re franchises… Nothing wrong with that, but they’re really not the kind you’ve tasted on your Summer trip to Italy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*uLi0mjqA8-ljfu7agUA0rA.jpeg" /><figcaption>Picture from urbany.net</figcaption></figure><p>The fresh ingredients, the sauces, the smells — the simplicity!</p><blockquote>It hits you: Great pasta doesn’t have to be expensive. It just has to be authentic.</blockquote><p>You find a perfect central location and decide to just buy it. You have your savings, you can bootstrap yourself to success!</p><p>You take care of the logistics, find amazing local suppliers who can bring you freshly picked tomatoes, herbs, top quality meat and this incredible meat. Two of the most talented university colleagues you know join as your co-founders and you’re off. It’s almost unbelievable how well it’s going. People have started talking about you and you’ve got your opening night fully booked.</p><p>You thought of two mains:</p><ol><li>The <em>rapido</em> lunch, with just 2 dishes to choose from (one meat pasta and one veggie pasta)</li><li>The <em>signorile</em> dinners, where your prime bottles of Italian wine will perfectly complement the authentic pasta experience — there will be 4 dishes for dinner every night: 2 perfectly cooked meat or fish dishes, and 2 veggie dishes.</li></ol><blockquote>You’re now one week away from opening “L’Autentico”.</blockquote><p>You start to second guess yourself. 2 dishes for lunch? What was I thinking?! Only 4 for dinner? No no no… All those customers booked for your first night and you only have 4 dishes to choose from? This is going to be a disaster.</p><p>People like variety. Even the burger place next door has 20 different burgers. They’ve even introduced a tofu burger recently!</p><p>OK, let’s redesign the menu. Beef and Cod only?! No, people love some healthy chicken. A nice tender chicken is great. Your suppliers can get you some great chicken.</p><p>Oh, man, what about seafood? You hadn’t thought about seafood and now that you think about it, you had that amazing seafood pasta in Italy at that <em>Osteria</em>. It won’t be easy to source, but there’s a really good fishmonger two blocks away. You will just add this one.</p><p>And what about the people that don’t like tomato sauce? I mean, sure, it’s Italian cuisine, but there’s always someone who would hate to come in and only have pasta with tomato sauce available. You build a <em>tomato-less</em> dish.</p><p>Seriously, what’s the point of only having two categories: meat/fish or veggies. It’s all in your mind. Your customers will like variety. Let’s just kill it and have the whole range available. They could even make their own pasta dishes.</p><blockquote>I know, we’ll have pasta buffet for lunch!</blockquote><p>Your opening night quickly turns into a disaster. When talking to people about what they didn’t enjoy, <strong>they don’t tell you it’s too much choice</strong>. In fact they can’t quite put their finger on it.</p><p>Their feedback is all over the place. It’s the ingredients, or the ambiance, or the choice of wine, or that the seafood wasn’t the best. It wasn’t bad at all, it was a good night out, but you know they’re not jumping at the chance to come back for more.</p><p>You’re forced to close, 3 months later. You’ll never know that <em>L’Autentico</em> had started off well. You remembered what’s unique about your value proposition and what the Italian cuisine experience offered — that’s why your opening night was fully booked. You had successfully laid out the basic principles of what you were going to try.</p><p>But then you let fear take over. You lost track of the Job you were going to be hired for, the singular experience you would provide, the first principles of the implementation. You became the 3rd pizza restaurant in your neighbourhood.</p><h3><strong>So what defines a fearless product?</strong></h3><ol><li>A fearless product knows and is clear about what it is and what it isn’t. Its differences and uniqueness are its moat. It goes back to first principles.</li><li>A fearless product knows the specific problem it’s trying to solve, and all the problems it’s not. Focus on the job-to-be-done and solve it extraordinarily well.</li><li>It knows that not all information is equal. Dumping everything you know on a 5-inch screen (or a menu) does not help more people. De-prioritizing, hiding or even completely removing functionality and information is critical to create good understanding.</li><li>It cares about progress more than fanciness. It solves problems before it worries about putting on a show.</li><li><strong>It always puts users first</strong>. If there’s product-market fit, business follows creation of value for people.</li><li>It understands users aren’t always rational. Decisions aren’t linear, they aren’t statistically or economically sound. A great product is human, friendly, empathetic, clear and cooperative.</li><li>It isn’t afraid to take chances. Every single startup was born from a leap of faith. Trade-offs aren’t optional. They’re the everyday job of any Product creator.</li></ol><h3>What *isn’t* a fearless product?</h3><p>A fearless product isn’t data blind, arrogant or a dismissive of the importance of business models. Data is infinitely valuable, delivering incremental value is often necessary and translating your friction-removal into economic utility is critical to building valuable businesses. A deep understanding of why you’re doing what you’re doing is the foundation to every other decision you’ll need to make.</p><p>However, great products don’t try to be everything to everyone.</p><p>Don’t settle for the wrong things just to avoid trouble or to satisfy that one person who once wasn’t in the mood for pasta. Don’t be afraid to take a stance. If you find yourself constantly using edge cases to justify product decisions, you’re well on your way to a terrible product.</p><p>And what if you’re wrong? Well, you’ll find even being wrong can be fun if you do it often enough.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a905c9ad9c52" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-fast-and-slow/fearless-products-a905c9ad9c52">Fearless Products</a> was originally published in <a href="https://medium.com/building-fast-and-slow">Building Fast and Slow</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>