<?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[DoubleLoop - Medium]]></title>
        <description><![CDATA[DoubleLoop is a tool that product leaders use to communicate business impact. To learn more, check us out at doubleloop.app. - Medium]]></description>
        <link>https://medium.com/doubleloop?source=rss----71d4f0b267fc---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>DoubleLoop - Medium</title>
            <link>https://medium.com/doubleloop?source=rss----71d4f0b267fc---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:58:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/doubleloop" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[OKRs ≠ Strategy]]></title>
            <link>https://medium.com/doubleloop/okrs-strategy-30f9f9dd5624?source=rss----71d4f0b267fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/30f9f9dd5624</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[okr]]></category>
            <dc:creator><![CDATA[Daniel Schmidt]]></dc:creator>
            <pubDate>Tue, 25 Jan 2022 00:07:06 GMT</pubDate>
            <atom:updated>2022-01-25T00:06:44.147Z</atom:updated>
            <content:encoded><![CDATA[<h4>OKRs are great, but there’s a problem with how most companies use them.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ayEjsNjymBVsNneim8EL5w.png" /></figure><p>OKRs (objectives and key results) are a critical tool. I helped bring them to my last company. Using OKRs successfully made us more objective and quantitative in how we built products.</p><p>My favorite part of OKRs is the KRs (key results).</p><p>It’s easy to be sloppy in our thinking when conceiving product initiatives. We often prioritize doing things that we “know” must be done. But our intuition is riddled with biases. Assumptions about focus and scope are nested in each initiative.</p><p>Asking ourselves, “What is the key result for this initiative?” forces us to think about what matters to achieve the critical business outcomes. KRs are slicing mechanisms. Through the OKR process, we often discover short paths to outcomes that we previously assumed would require much more work. Sometimes, through contemplating KRs, we realize that projects we were <em>convinced</em> must be done actually don’t fit with company priorities and therefore shouldn’t be done after all.</p><p>One of the basic principles of OKRs is that they should not be task lists. If your key result is “We launched project X,” it means that you lack an objective measure of why project X is important.</p><p>While we’re taught that OKRs should orient around outcomes and not outputs, I’ve never been part of an OKR process where we don’t at some point give up and say, “Ok fine, let’s allow <em>some</em> of our OKRs to be our project list.”</p><p>It often unfolds like this:</p><p>We sit down to write OKRs only to realize that we don’t have the metrics we need to objectively measure our work. So then, we make a key result to instrument metrics. By the time our quarterly OKR cycle is over, we haven’t done the actual work. Or, if things go super fast, we made the metric and shipped the work, but we run out of time in the OKR cycle to see if our work achieved the result or not — it might take 180 days to know for sure. Then, in the next OKR cycle, we shift priorities and embark down a totally different road without closing the loop on the previous cycle of work.</p><p>Making your KRs a laundry list of projects to ship gets more tempting with each hour of OKR planning, even for those who start the process with pure intentions.</p><p>The root problem with how most companies do OKRs is that they enter the process with <em>strategy debt</em>.</p><p>John Culter describes it brilliantly in his article, <a href="https://cutlefish.substack.com/p/tbm-2553-persistent-models-vs-point"><em>Persistent Models vs. Point-In-Time Goals</em></a>:</p><blockquote>There is a big difference between persistent models and work (or goal) related models. OKRs, for example, are a work related model. Work related models involve a specific time-span (e.g. a quarter). The team attempts to achieve The Goal by end-of-quarter.</blockquote><blockquote>Meanwhile, a north star metric and related inputs persist for as long as the strategy holds (often 1–3 years ). The constellation of metrics serves as a belief map, driver diagram, or causal relationship diagram. It explains our mental model for how value is created and/or preserved in our product/system.</blockquote><p>The <a href="https://amplitude.com/north-star">North Star Playbook</a> that John refers to is an example of how “strategy” can be expressed. For metrics-driven companies, a strategy is a model for (1) how types of events and work influence measurable outcomes, and (2) how leading indicators influence lagging indicators. It’s a map like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9XUZxaDYQfXzMLqG" /></figure><p>My last post, <a href="https://blog.doubleloop.app/metrics-driven-product-development-is-hard/"><em>Metrics-driven product development is hard</em></a>, explains the diagram in detail.</p><p>If you already have a strategy, that is, a persistent model of how your business functions, the OKR process is radically more effective and efficient.</p><p>Imagine starting an OKR process where everyone <em>already knows</em> the important metrics for the business and how previous work has influenced it. So instead of asking “what is a measurable key result for this initiative that we want to do?” you ask “what can we do to move this metric that is critical to the business?”</p><p>When a company lacks a persistent model of their strategy, people feel the gap and try to model their strategy in the form of OKRs. <em>But using OKRs as the sole articulation of your strategy is toxic overkill.</em> Not every metric that is important to your business should have a time-based goal tied to it at every moment. It’s OK to declare that a metric is meaningful without actively doing anything to move it. OKRs don’t have a concept of that. They’re blunt instruments.</p><p>At <a href="https://doubleloop.app/">DoubleLoop</a>, we believe you should build a persistent model of your company strategy, in the style of the Northstar Playbook, before you do OKRs.</p><p>Here’s what a strategy visualization in DoubleLoop looks like (or <a href="https://www.loom.com/share/1d17b1eff11942129ad5e541f75d65d9">watch the demo video</a>):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J6-QMV-5jCsQCb0D" /></figure><p>By modeling a strategy that’s independent of time-based goals, you get a lot of the same benefits as OKRs. You clearly articulate the “why?” behind your work. With DoubleLoop, your strategy visualization is populated with live metric data so you can quickly see what’s working and not working in your strategy.</p><p>From there, you can selectively <em>deploy your strategy with key results as needed</em>. The majority of your metrics may not have key results at all. It’s fine to try to move a metric up or down without a clear target. It takes cycles of tinkering before you have a sufficient <em>feel for the metric</em> to design a key result for it.</p><p>In DoubleLoop, you can <em>optionally</em> add key results to metrics, as much or as little as you choose to. And you can update your OKRs whenever the time is right, which is probably not quarterly.</p><p>Branches of your product strategy will likely stay fixed for long periods of time, even years. You shouldn’t feel like you <em>have</em> to revise the whole thing every quarter. Some branches of your strategy might change every week, others might never change.</p><p>Focusing <em>first</em> on the persistent model of your strategy is your ticket off the quarterly OKR hamster wheel.</p><p><em>Thanks to John Cutler and Sumit Gupta for reviewing a draft of this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30f9f9dd5624" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doubleloop/okrs-strategy-30f9f9dd5624">OKRs ≠ Strategy</a> was originally published in <a href="https://medium.com/doubleloop">DoubleLoop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Metrics-driven product development is hard.]]></title>
            <link>https://medium.com/doubleloop/metrics-driven-product-development-is-hard-2cf3f1c71e57?source=rss----71d4f0b267fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/2cf3f1c71e57</guid>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Daniel Schmidt]]></dc:creator>
            <pubDate>Mon, 13 Dec 2021 16:21:19 GMT</pubDate>
            <atom:updated>2021-12-13T18:24:29.669Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xe6f69Bej9kneVoLn58GQw.jpeg" /></figure><h4>The way great companies do it follows the same structure.</h4><p>The way that the FAANG companies use metrics to build products is vital to their success. They invest an army of people and homegrown tools to pull it off. My last article, <a href="https://blog.doubleloop.app/balancing-short-term-and-long-term-product-bets/"><em>Balancing short-term and long-term product bets</em></a>, describes Google’s process.</p><p>While the very top companies are great at using metrics, after talking to the hundreds of PMs who signed up for DoubleLoop, I’ve learned that almost everyone else is struggling.</p><p>Myself included. In my 15 years of product management experience, working for companies from big to small, effectively using metrics was painfully hard every time.</p><p>There are <em>many</em> ways for a metrics-driven process to go astray.</p><p>For a lot of teams, getting visibility into the metrics that matter is elusive by itself. Instrumenting new metrics takes work that tends to slip in priority.</p><p>But even teams who successfully create a library of valuable metrics are not out of the woods. They are left with the question: what do we <em>do </em>with all the data at our fingertips?</p><p>The answer, presumably, is that you can use the data to do better work and build better products. This is easier said than done. Teams risk two primary pathologies that I’ve personally suffered from multiple times:</p><ul><li><strong>Nearsightedness</strong><em>. </em>The team is skilled at moving sensitive metrics, but their optimizations don’t translate to long-term business success. Or worse, while they optimize one set of metrics, other important metrics go in the wrong direction.</li><li><strong>Farsightedness</strong><em>. </em>The team monitors metrics tied to their company’s long-term business success, but they’re unable to see how their work can move the metrics that matter. Consequently, they place product bets without a precise thesis for creating measurable impact.</li></ul><p>“Good vision,” in the product development sense, is the capacity to make short-term bets that compound to create long-term business value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qov41REDWWar4ouZ.png" /></figure><p>It might seem paradoxically hard to be simultaneously short-term and long-term oriented, but this is exactly what the world’s top companies do. The way they do it follows the same pattern.</p><p><em>There’s a shared structure to how product teams at the top companies get business results. </em>It looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CFqhWY2iHSOdcoeW" /></figure><p>While each company has its own vocabulary, I’ve found that Amplitude’s <a href="https://amplitude.com/north-star">North Star Playbook</a> by John Cutler and Jason Scherschligt provides an excellent synthesis. I get reliable head nodding when I’ve shared the above visual with PMs at companies like Google, Facebook, Netflix, Square, and Uber.</p><p>A key element of the visual model is that the metrics are arranged on a spectrum from “leading” to “lagging.” Leading indicators are sensitive. You can make a change and quickly see leading indicators go up or down. Lagging indicators, in contrast, are slow to move. They’re subject to things outside of your control like macroeconomic forces, seasonality, or pandemics. You <em>can</em> influence lagging indicators, but it takes time and patience.</p><p>There are two sides to the brutal reality of metrics-driven product development:</p><ol><li><strong>Lagging indicators</strong> are the KPIs that actually matter for your business; things like revenue and customer retention. Because they are lagging and subject to external forces, product teams often feel helpless in impacting them.</li><li><strong>Leading indicators</strong> <em>can</em> be influenced by work, like the percent of users that perform a certain action during a session. By themselves, they don’t equate business success. Impacting them feels more like local optimizations than game-changing breakthroughs. And they’re subject to being “gamed” or manipulated if they’re poorly conceived or handled.</li></ol><p>Your North Star metric is the antidote. It’s the bridge between your leading and lagging indicators. A good North Star metric will align your team around creating differentiated customer and business value. It expresses your product strategy.</p><p>For example, <a href="https://amplitude.com/north-star/amplitudes-north-star-metric-and-inputs">Amplitude’s own North Star metric</a> is <em>Weekly Learning Users (WLUs)</em>, “the count of active Amplitude users who have shared a learning that is consumed by at least two other people in the previous seven days.” They explain:</p><blockquote>This North Star represents Amplitude’s most valuable user persona, the Advocate, who shares context to drive decisions and take action in an organization. Amplitude’s product strategy is to be learning-driven, providing insights to cross-functional teams. WLUs represent this strategy.</blockquote><p>Another educational example is <a href="https://amplitude.com/north-star/netflix-and-the-north-star">how Netflix applied the North Star framework</a> to increase customer retention when they were a DVD business. Since customer retention is a lagging indicator that is difficult to swiftly impact with product work, they created a more sensitive North Star metric. Gibson Biddle, the former VP of Product for Netflix, is quoted in the North Star Playbook:</p><blockquote>“At Netflix, we knew that improving retention was the critical metric to improve — it would improve both customer and shareholder value. But retention is very hard to move and A/B tests for retention require lots of time to see a meaningful difference,” said Gibson. “So we developed more sensitive proxy metrics. Our ‘Percentage of new members who add at least three titles to their queue during their very first session with the service’ is a good example.”</blockquote><p>Seeing the above visual model of the North Star Playbook is both anxiety-relieving and anxiety-inducing at the same time. When I first saw it, it felt cathartic to see a clear picture of how metrics-driven product development works. But it also illustrates the complexity of executing it.</p><p><em>To tie work to business results, you must create a graph of relationships between work and metrics</em>.</p><p>E.g., “If we optimize X in the product, then metric Y will go up. If metric Y goes up, then that improves our North Star metric. And if we increase our North Star metric, the business will make more money.”</p><p>Here’s how we use the new strategy diagramming tool in <a href="https://doubleloop.app/">DoubleLoop</a> to build our own graph of work and metrics:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*89MwdZwX9vrsuYkd1VcVIA.png" /></figure><p>Each link in the graph is an assumption that could be wrong or go wrong. You can form <em>hypotheses</em> for how work will move input metrics and for how leading indicators influence lagging indicators. But your hypotheses, of course, can prove false. And a correlation that exists at one point in time might break in the future.</p><p>Thus, your map of relationships between work and metrics must be dynamic, not static. When an initiative succeeds or fails, your strategy must be adjusted. When the market changes it must be adjusted. When your North Star metric fails to correlate with your business KPIs, it must be adjusted.</p><p>Adjustments can range from big to small. In some cases, a nuanced recalculation of a metric suffices. In other cases, the premise of a metric or initiative must completely change, or the graph of relationships must be reorganized.</p><p>Each change has rippling effects. If you tweak your North Star metric, all upstream indicators and initiatives might need to shift as well. One branch of your strategy might stay fixed for quarters while another branch needs constant attention.</p><p>Metrics-driven product development is hard and will always be hard. But there’s a lot to be done to make it easier.</p><p>We’re building DoubleLoop to be your system-of-record of the <em>relationships </em>between your work and metrics. DoubleLoop enables you to map how all the pieces come together, align your team around it, keep it in sync with reality, and iterate.</p><p>We don’t claim to have all the answers. We’re working with product leaders to figure out, together, how to build a system for metrics-driven product development that can be utilized by companies who don’t have the resources of Amazon, Google, Netflix, and Facebook.</p><p><em>To get started with DoubleLoop, sign up on </em><a href="https://doubleloop.app/"><em>our homepage</em></a><em>. We’ll work with you to form a process for metrics-driven product development that’s right for your company.</em></p><p><em>Thanks to Jeremy Toeman, Sumit Gupta, and John Cutler for providing feedback on previous drafts of this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cf3f1c71e57" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doubleloop/metrics-driven-product-development-is-hard-2cf3f1c71e57">Metrics-driven product development is hard.</a> was originally published in <a href="https://medium.com/doubleloop">DoubleLoop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Balancing short-term and long-term product bets]]></title>
            <link>https://medium.com/doubleloop/balancing-short-term-and-long-term-product-bets-dde35266150d?source=rss----71d4f0b267fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/dde35266150d</guid>
            <dc:creator><![CDATA[Daniel Schmidt]]></dc:creator>
            <pubDate>Wed, 06 Oct 2021 15:49:43 GMT</pubDate>
            <atom:updated>2021-10-06T15:49:42.905Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*DnA8Od0SfEagtKztlrPl6A.jpeg" /></figure><h4>What I’ve learned from Dan Rubinstein</h4><p><a href="https://www.linkedin.com/in/ydanrubinstein/">Dan Rubinstein</a> has a unique vantage point on the evolution of the product management craft. He joined Google as a PM in 2005. His initial role was to put in place processes and systems to help other product managers understand the efficacy of what they were building.</p><p>In 2005, Google Analytics didn’t exist yet. Running A/B tests was laborious and manual. <em>Dan’s team had to shape product analytics virtually from scratch.</em></p><p>After (1) in-depth conversations with Dan about his experience as a product leader for Google, Facebook, and Palantir, and (2) countless chats with PMs through the course of building DoubleLoop, I’ve strengthened my view that an important puzzle exists:</p><p>While many of the analytics capabilities that Google built back in the 2000s are now available to all product developers, there are vital elements of <em>how Google (and other top companies) use these tools</em> that most of today’s companies still don’t apply. Consequently, even with a deep well of analytics at their disposal, most companies struggle to build valuable products.</p><p>Google had two key insights that are still poorly applied today:</p><p><em>Principle 1. The value of product changes can be quantified and tied to revenue</em>.</p><p>I’m shocked by how many product folks insist that the impact of product development cannot be measured. Strong-willed founders or executives tend to push through their UX intuitions without interest in data-based evidence. Google realized that it was indeed possible to quantify the impact of product changes — both in terms of revenue contribution and in terms of the product experience and user engagement.</p><p><em>Principle 2. Short-term versus long-term trade-offs must be examined relentlessly</em>.</p><p>If Google optimized just for short-term revenue, they would have added blinking ads across their home page like an over-monetized news site. Rubinstein admired how the founding team at Google was passionate about user experience. They prioritized having a high-quality user experience for the long term over lucrative, but inevitably ephemeral, product changes.</p><p>Today, many companies sleepwalk through trade-off decisions, unaware or uncaring of tensions between short-term optimizations and long-term strategic bets. Product teams get lost in a number of ways:</p><ul><li>They neglect data feedback loops altogether. The team builds purely based on a strong product vision or intuition of a good UX. They miss opportunities to test their assumptions or monetize the value they created.</li><li>They A/B test themselves into the corner of a local maximum. Based on business pressures or lack of imagination, the team over-invests in product changes that correlate directly to short-term gains. They lose sight of the impact on the long-term business trajectory.</li><li>The team religiously tracks KPIs or lagging indicators pertaining to revenue and UX goals, but they don’t correlate metrics changes with product changes. Consequently, the team struggles to understand the impact of what they built.</li></ul><p>Very few teams, from what Dan and I have observed, <em>synthesize quantitative and qualitative measures</em> to intentionally balance short-term optimization with long-term strategic bets. (Note: for an interesting analysis of “nested bets,” see John Cutler’s <a href="https://medium.com/hackernoon/beyond-outcomes-over-outputs-6b2677044214"><em>Beyond “Outcomes Over Outputs”</em></a>.)</p><p>Believing in Google’s principles of product development is easy. Executing them during the chaos of company building is hard.</p><p>While Google broke new ground with analytics infrastructure, their <em>process</em> of examining product changes was equally vital to their success. The key to this process, Rubinstein explained, is <em>executive attention</em>. Google had regular meetings to review the full impact of product changes. Everyone looked forward to these meetings because <em>decisions were made</em>. It was exciting.</p><p>To provide a simple example, imagine a product change that increases clicks on ads but decreases clicks on organic search results. Should this change be shipped?</p><p>The short-term revenue implications are clear, but the long-term UX implications are not. To understand trade-offs, a variety of quantitative and qualitative indicators must be considered. It requires input from all the people who work on the product across a diverse set of functions spanning UX, product, engineering, sales, marketing, and finance.</p><p>Rubinstein’s team recognized that A/B testing, while a vital method, is not by itself sufficient for building a valuable product. There are a few reasons why:</p><ul><li>Product changes do not happen in isolation.</li><li>A/B tests cannibalize and overlap each other.</li><li>Metrics can be impacted outside of the scope of the A/B test.</li></ul><p>Consequently, <em>people</em> must make judgment calls regarding trade-offs. They must constantly be on the watch for blind spots in their business awareness. If you neglect to incorporate a key UX consideration into your analysis, you could alienate users and run your company into the ground before you even realize it. As Rubinstein puts it, “if it were purely metrics, then you just let the robot run the company.”</p><p>It’s been over ten years since Dan Rubinstein helped build Google’s product analytics capability from the ground up. Dan and I discussed the state of product management tools today. While the analytics that are available to product managers have exploded since Rubinstein worked at Google, he described still a surprising tools gap:</p><p>I haven’t seen tools that … integrate the analytics with the underlying root causes that are exogenous to the analytics. So not just what happened, but why did it happen and what can we do about it? … It would be a huge enabler for companies to do the right things, to build the right products.</p><p>Without tools like what Dan envisions, product teams are limited in their ability to apply Google’s product development process. He sees several problems:</p><ul><li><em>It’s hard to see the impact of product initiatives on long-term strategic bets.</em> A/B testing helps you make short-term optimizations, but it doesn’t provide visibility into how your short-term bets compound to impact lagging UX and business KPIs.</li><li><em>It takes a long time for product managers to learn how to build valuable products</em>. When they join a new company, PMs need to accumulate a lot of domain knowledge about how to assess the efficacy of their product initiatives. If the key metrics and drivers were readily available, it would be an “equalizer of talent.”</li><li><em>A/B tests can be confounded by product changes that happen externally to the test</em>. For example, maybe there was a change that sped up the app or a bug that altered system behavior. Without an easy-to-access record of product changes and potential drivers, it’s hard to solve the mysteries of why metrics are moving one way or the other.</li><li><em>Companies lack institutional memory of what moves the needle and what doesn’t</em>. Product teams are unable to easily see the results of previous product bets to decide what types of future product bets to place.</li></ul><p>Dan doesn’t foresee a world where product management tools tell you what product changes to ship or not ship. But he sees a ripe opportunity to improve how product builders make decisions that are right for their business.</p><p><em>Given his extensive experience as a product leader and unique role at Google, we were thrilled when Dan Rubinstein made the decision to invest in </em><a href="https://doubleloop.app/"><em>DoubleLoop</em></a><em>. Rubinstein invested because DoubleLoop, he concluded, productizes the process for understanding the revenue impact of product changes.</em></p><p><em>We have a ways to go to realize the potential Dan Rubinstein sees in DoubleLoop. To help us get there, we’d love to thought-partner with like-minded product teams who share the vision.</em></p><p><em>Thank you to </em><a href="https://twitter.com/johncutlefish"><em>John Cutler</em></a><em> and </em><a href="https://twitter.com/jtoeman"><em>Jeremy Toeman</em></a><em> for providing feedback on previous drafts of this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dde35266150d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doubleloop/balancing-short-term-and-long-term-product-bets-dde35266150d">Balancing short-term and long-term product bets</a> was originally published in <a href="https://medium.com/doubleloop">DoubleLoop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Brain’s Guide to Product Development]]></title>
            <link>https://medium.com/doubleloop/the-brain-s-guide-to-product-development-76d2f9751932?source=rss----71d4f0b267fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/76d2f9751932</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[brain]]></category>
            <dc:creator><![CDATA[Daniel Schmidt]]></dc:creator>
            <pubDate>Wed, 08 Sep 2021 23:37:13 GMT</pubDate>
            <atom:updated>2015-07-08T17:38:20.963Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n6GkD5iLPQPyMo5-fFqbTg.gif" /></figure><blockquote>The concepts that govern our thought are not just matters of the intellect. They also govern our everyday functioning, down to the most mundane details. Our concepts structure what we perceive, how we get around in the world, and how relate to other people. Our conceptual system thus plays a central role in defining our everyday realities. If we are right in suggesting that our conceptual system is largely metaphorical, then the way we think, what we experience, and we do every day is very much a matter of metaphor.</blockquote><blockquote>– George Lakoff, Mark Johnson from <a href="http://www.amazon.com/Metaphors-We-Live-George-Lakoff/dp/0226468011"><em>Metaphors we Live By</em></a></blockquote><p>I discovered Gareth Morgan’s book, <a href="http://www.amazon.com/Images-Organization-Gareth-Morgan/dp/1412939798"><em>Images of Organization</em></a>, on Venkat Rao’s <a href="http://www.ribbonfarm.com/now-reading/">reading list</a>. In the text, Morgan thoroughly explores many possible metaphors through which to understand the workings of a company. For example, companies can be thought of as machines, organisms, brains, or cultures. As a product developer, I’m always searching for frameworks to provide meaning and direction for my work. In this regard, each metaphor Morgan discusses is a goldmine capable of inspiring product vision, mission statements, and roadmaps.</p><p>It is often the circumstances around a company that dictate the applicability of one metaphoric lens over another. For example, when the environment around an organization is static, the machine-like elements of a company pop to the foreground. When interactions with the outside world are predictable, corporations can create formulaic routines for optimizing their internal behavior. For example, from Morgan’s book, the below performance checklist applied to workers at a fast food restaurant demonstrates how even human interactions can be assessed in a binary machine-like manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/0*TGlFfFYuSqNc7qPD.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/0*eD5qUzS1FQYLKa6n.png" /></figure><p>Within a mechanical operation, each employee is thought of like an interchangeable part. You might need some spare parts floating around, but for the most part, when someone leaves, a new worker can be be plugged in with minimal interruption to the system as a whole. While there can be harmful effects on the humans involved, in the right circumstances companies can achieve business success through emulating machines.</p><p>The machine metaphor, however, breaks down when considering digital companies operating in the age of the internet. Unlike the relatively static environments of many industrial-age companies, the environment surrounding many of today’s organizations is fraught with compounding uncertainty that I break down into a few categories:</p><ul><li><em>The uncertainty inherent in how people interact with software</em>. When you are designing a piece of software, whether it is a consumer web site, app or an enterprise platform, you don’t know in advance which design directions will fail or succeed. Instead, it takes a core group of people close to users to “discover” a working product. You don’t really know what works until you see real people using it.</li><li><em>The uncertainty inherent in how internal changes propagate through networks</em>. When you do create a piece of software that clicks with its users, business success is dependent on the ability for the user base to scale to a sufficient number of paying customers. Successful growth tactics are difficult to predict in advance. When developing marketing avenues or viral mechanics, extensive tinkering is necessary to discover messages that stick and spread. As explored in Malcolm Gladwell’s <a href="http://www.amazon.com/The-Tipping-Point-Little-Difference/dp/0316346624"><em>The Tipping Point</em></a>, seemingly trivial changes can be the difference between virality and insignificance.</li><li><em>The uncertainty inherent in external changes</em>. After discovering a product that resonates and scales, maintaining product-market fit requires constant adaptation. The networked system of the internet is ripe for rapid change. Phenomena can emerge and swiftly capture the attention of a large portion of the network. Competitors can quickly appear, yanking away mind share. A search engine algorithm change can destroy a crucial user acquisition channel.</li></ul><p>Organizations aspiring to operate like machines involve centralized management creating fixed recipes to dictate the behavior of front-line employees. Due to the environment of uncertainty inherent in the internet, such an approach has become futile. A centralized management team, removed from the front lines, does not know what will make a sustainably successful web site, app, or marketing approach. Instead, the contributors in the trenches must be valued, not as interchangeable parts, but as indispensable sources of knowledge and ideas.</p><p>Consequently, we’re seeing today’s organizations emphasize learning as a critical element of their operations. When looking for a model for how companies should aspire to learn, the richest place to turn is the workings of the human brain itself. The brain, of course, is the original learning system. When comparing how companies learn to how brains operate, we can see why many of today’s product development practices are effective. Yet, we also see that companies have only begun to learn how to learn. Using Gareth Morgan’s chapter, <em>Learning and Self-Organization: Organizations as Brains</em>, as my jumping off point, I’m going to explore how patterns of the brain are becoming prevalent in product development practices. Specifically, I’m going to focus on three phenomena:</p><ol><li>Rapid adjustments based on external feedback;</li><li>Redundancy; and</li><li>Double loop learning.</li></ol><p><em>(1) Rapid adjustments based on external feedback</em></p><p>In <em>Images of Organization</em>, Gareth Morgan draws upon <a href="https://en.wikipedia.org/wiki/Cybernetics">cybernetics</a> to explain that “the brain relies on patterns of increasing refinement and not (as man-made machines do) on chains of cause and effect.” The brain relies on negative feedback loops with the external world to optimize actions. For example, “if we shift a boat off course by taking the rudder too far in one direction, we can get back on course again only moving in the opposite direction.” Even something as basic as picking up an object, Morgan argues, relies on negative feedback loops. He writes:</p><blockquote>… when we pick up an object from a table we typically assume that our hands, guided by our eyes, move directly toward the object. Cybernetics suggests not. This action occurs through a process a process of error elimination, whereby deviations between hand and object are <em>reduced at every stage of the process</em>, so that in the end no error remains. We pick up the object by avoiding not picking it up.</blockquote><p>Here’s Morgan’s illustration:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/0*j5VVpRlAFz_ODjgf.png" /></figure><p>Many of today’s product development techniques mirror the brain’s pattern of repeated adjustment based on feedback from the external world. In agile software development, projects are broken down into small iterations such that the course can be readily adjusted as new information is uncovered. With lean startup methodology, teams create “hypotheses” for how to effectively reach their objectives and run experiments to cheaply validate or invalidate their hypotheses before excessive time and resources are invested. Modern teams strive to rapidly move through build-measure-learn loops.</p><p><em>(2) Redundancy</em></p><p>Morgan emphasizes the importance of redundancy in self-regulating systems like the brain. He writes:</p><blockquote>Any system with an ability to self-organize must have a degree of “redundancy,” a kind of excess capacity that can create room for innovation and development to occur. Without redundancy, systems are fixed and completely static.</blockquote><blockquote>In the human brain we find this redundancy in the vast networks of connectivity through which each neuron, or nerve cell, is connected with thousands upon thousands of others. This enormous capacity generates considerable evolutionary potential. It allows vast amounts of information process from which thousands of potential patterns of development can emerge, contributing to the brain’s constantly evolving structure, refinement, and intelligence.</blockquote><p>A clear example is <a href="http://en.wikipedia.org/wiki/Pair_programming">pair programming</a>, that is, having two engineers simultaneously work on the same task. On the surface, spending two resources on a task instead of one might seem economically wasteful. It’s unclear whether it makes task completion take shorter or longer. But teams have found that pairs, compared to individuals, produce cleaner, more maintainable code with less defects. Furthermore, pair programming prevents critical knowledge from getting isolated within one person’s mind. When only one team member has deep knowledge of an area of the code base, the team becomes vulnerable when the business requires more changes in that area. The one person with specialized knowledge may be absent or stretched thin between other responsibilities. Pairing is a key ingredient in keeping knowledge flowing through an engineering team. Flexibility, quality, creativity, and efficiency are maximized when all engineers are capable of working in all areas of the code base. Hence, the <a href="https://www.google.com/trends/explore#q=full%20stack%20developer&amp;cmpt=q&amp;tz=Etc%2FGMT%2B7">popularity</a> of the job title “<a href="http://codeup.com/what-is-a-full-stack-developer/">Full Stack Developer</a>” where engineering expertise, instead of being divided according to layers of the software (e.g., front-end versus back-end), are duplicated across many developers. In my article, <a href="http://productlogic.org/2014/08/21/three-types-of-product-builders-vertex-builders-edge-builders-and-full-triangle-builders/">The Three Types of Product Builders</a>, I take things one step further by arguing for the importance of individuals who are proficient in all of the primary areas of building a company; technology, design, and business strategy. When more of a company’s contributors are able to understand the full picture across all traditional job functions, the company has increased their ability to quickly adapt to changing circumstances.</p><p>Pair programming is an example of how product development teams create redundancy in their internal process. Split testing (or <a href="http://en.wikipedia.org/wiki/A/B_testing">A/B testing</a>), in contrast, is an example of how teams learn through creating redundancy in their external outputs. With split testing, teams produce redundant versions of the same page and distribute web traffic such that some portion goes to each version. While the redundant versions of the page serve the same overall purpose, each site instance contains variance along the lines of content or design. This allows the team to discover which page elements perform the best according to company objectives. For examples, product development teams can use A/B testing to determine which home page layout leads to the highest click through rate or which labeling of the buy button (e.g., “buy now” vs “check price”) leads to the highest conversion rate.</p><p>Both pair programming and split testing mirror patterns of parallel processing prevalent in the brain. Morgan writes:</p><blockquote>A lot of the brain’s activity seems to be completely random and characterized by a massive amount of distributed and parallel information processing. At any one time many parts of the brain may be involved with the same activity or information. This redundancy allows initiatives to be generated from many locations at once, reducing dependence on the activities of any single location. The process generates the multiple, competing “drafts” of intelligence from which an evolving pattern eventually emerges. The redundancy reflected in this system of parallel process is vital in generating a range of potential outcomes, in coping with error, and in contributing to the brain’s flexibility, creativity, and adaptiveness.</blockquote><p>Teams that employ redundancy understand the value of learning and strive to avoid the predicament of trapping knowledge in the minds of few. Furthermore, they recognize that their assumptions about how to reach objectives are only hypotheses that need to be examined and tested. Creating redundancy is a key technique in discovering and spreading surprising, counter-intuitive knowledge about what works and what doesn’t.</p><p><em>(3) Double loop learning</em></p><p>It is critical for today’s organizations to learn how to more effectively reach their objectives. However, it is often the case that the objectives themselves are flawed from the outset or due to external change. When an organization’s operating norms become misaligned with its environment, as Morgan explains, “the intelligence of the system breaks down, because the process of negative feedback ends up trying to maintain an inappropriate pattern of behavior. Morgan continues:</p><blockquote>… More complex cybernetic systems, such as the human brain or advanced computers, have the capacity … to detect and correct errors in operating norms, thereby influencing the standards that guide their detailed operations.</blockquote><blockquote>It is this self-questioning ability that underpins the activities of systems that are able to learn to learn and self-organize. The essential difference between these two types of learning is identified in terms of a distinction between “single-loop” and “double-loop” learning.</blockquote><p>Morgan’s illustration:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/0*tA5nh3ZtXQbZDT3L.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/0*5mZrX9alWwrmBy0L.png" /></figure><p>We see some of today’s product development teams embracing double-loop learning. In agile software development, teams routinely question their own operating norms in the form of project “retrospectives.” In retrospectives, teams ask themselves the question, “What’s going well or not well in our current process? How should our process change next time?” Retrospectives allow organizations to identify and correct pathologies in their alignment.</p><p>Perhaps the most iconic embodiment of double-loop learning is “the pivot.” Lean startup teams iteratively formulate and test hypotheses for how to achieve company objectives. After a hypotheses fails, sophisticated teams don’t blindly move on to the next tactic. Instead, they question whether their overall objective is tenable. When a larger strategic direction is deemed a failure, companies pivot to a new direction. Many of <a href="http://www.forbes.com/sites/jasonnazar/2013/10/08/14-famous-business-pivots/">today’s most successful companies pivoted</a> before landing on a winning proposition. Without double-loop learning, they would no longer be in business.</p><p>While we’re seeing an increasing number of the brain’s patterns emerge in product development practices, there are still areas where learning capacities are severely limited as if there is a legion in the collective brain of an organization. A primary example is the phenomenon of <a href="https://en.wikipedia.org/wiki/Corporate_amnesia">corporate amnesia</a>. As investments in learning continue to rise, the <a href="https://en.wikipedia.org/wiki/Corporate_amnesia#Cost">cost</a> of lost or poorly leveraged knowledge rises. The forms of organizational memory loss mirror the types of amnesia occurring in the brain. According to <a href="https://en.wikipedia.org/wiki/Amnesia">Wikipedia</a>,</p><blockquote>There are two main types of amnesia: retrograde amnesia and anterograde amnesia. Retrograde amnesia is the inability to retrieve information that was acquired before a particular date, usually the date of an accident or operation. In some cases the memory loss can extend back decades, while in others the person may lose only a few months of memory. Anterograde amnesia is the inability to transfer new information from the short-term store into the long-term store. People with this type of amnesia cannot remember things for long periods of time.</blockquote><p><a href="https://en.wikipedia.org/wiki/Retrograde_amnesia">Retrograde amnesia</a> occurs in organizations when previous employees do not pass on their knowledge when they depart. In software development, it can take years of experience crafting a product to develop a sufficiently nuanced understanding of what works and what doesn’t. When the people with direct experience of previous launches leave, the new people that take over have to start from almost zero in building their understanding of the product. The problem is only exacerbated with increases to <a href="https://en.wikipedia.org/wiki/Labour_market_flexibility">labor market flexibility</a>. In tech we’re seeing trends in people holding a position for less than a couple years before moving to the next opportunity. While this practice may benefit the individuals, organizations can struggle when accumulated knowledge repeatedly walks out he door.</p><p>While individuals working on a product over a period time acquire valuable knowledge, the new information they discover is commonly not transferred to long-term memory that is actionable to the whole organization. If you compare an organization to a brain, this form of failed memory transfer is akin to <a href="https://en.wikipedia.org/wiki/Anterograde_amnesia">anterograde amnesia</a>. Consequently we see teams failing to apply lessons learned by other teams, we see managers failing to adjust strategy when new information comes in from the front lines, and we see individual contributors fail to change their tactics when company leadership uncovers a change to the overall business landscape.</p><p>While companies try to combat amnesia through <a href="https://en.wikipedia.org/wiki/Knowledge_management#KM_Technologies">knowledge management</a>solutions like intranets and wikis, these solutions are too manual to comprehensively keep up and are subject to future misinterpretations. I liken today’s organizations to the amnesiac main character in the film<a href="http://www.imdb.com/title/tt0209144/"><em>Memento</em></a>. To solve the murder of his wife, he tries compensate for his amnesia by tattooing clues for his future self all over his body. These “clues” lead him to pursue the wrong suspect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*Sfmv1Gan4Z9_lxFZ.jpg" /></figure><p>Healthy brains are organized such that functioning is distributed. Morgan characterizes this phenomenon as the holographic quality of the brain. He writes:</p><blockquote>Holography uses lensless cameras to record information in a way that stores the whole in all of the parts. One of the interesting features is that, if the holographic plate recording the information is broken, any single piece can be used to reconstruct the entire image. Everything is enfolded in everything else, just as if we were able to throw a pebble into a pond and see the whole pond and all the waves, ripples, and drops of water generated by the splash<em> in each and every one of the drops of water.</em></blockquote><blockquote>Holography demonstrates that it is possible to create processes where the whole can be encoded in all of the parts so that each and every part represents the whole. Neuroscientist Karl Pribram has suggested that the the brain functions in the accordance with holographic principles: that memory is distributed throughout the brain and therefore can be reconstituted from any of the parts. If he is correct, this may explain why the rats in Karl Lashley’s experiments were able to function reasonably well even when major portions of their brain had been removed.</blockquote><p>While functioning may be distributed across the brain, specific regions of the brain are still specialized. Morgan excitedly points out the paradox that “The brain, it seems, is <em>both</em> holographic <em>and </em>specialized!” He continues:</p><blockquote>This paradox is clearly illustrated in the results of “split brain” research, which shows how the brain’s right hemisphere plays a dominant role in creative, intuitive, emotional, acoustic, and pattern recognition functions and controls the left side of the body. The left hemisphere is more involved with rational, analytic, reductive, linguistic, visual, and verbal functions while controlling the right side of the body. The is undoubtedly a high degree of specialization on the part of each hemisphere, but both are always involved in any given activity. It is just that one hemisphere seems to be more active or dominant than the other as different functions are brought into play.</blockquote><p>Traditional organizations are attracted to the “specialized” side of the holographic/specialized paradox while neglecting the “holographic” side. We commonly see companies organized into groups according to their preconceived, narrow job responsibility; engineering, marketing, design, sales, etc.. As Venkat Rao explains in his essay <a href="http://www.ribbonfarm.com/2015/05/28/the-amazing-shrinking-org-chart/"><em>The Amazing, Shrinking Org Chart</em></a>, the classic org chart model is becoming deficient as preconceived structures fail to keep up with a dynamically changing environment. Rao argues that tools like <a href="https://slack.com/">Slack</a> demonstrate a new way for companies to organize around order that emerges naturally out of the actual work being done. By using Slack, a team increases their ability to achieve a balance between holographic and specialized functioning. Slack makes it easier for each of an organization’s employees to dip into the river of what others are working on.</p><p>While there are promising tools and new organizational design philosophies like <a href="http://www.businessinsider.com/tony-hsieh-zappos-holacracy-management-experiment-2015-5?op=1">holacracy</a>, most companies have not broken free from machine-like ways of operating. When comparing the operations of product development teams to the workings of the brain, we find areas where organizations are severely limited. However, each limitation we identify provides a clearly delineated opportunity for improvement. The brain serves as a model that the product development community can aspire to recreate if they want to maximize their learning potential.</p><p>Personally, I’ve found the brain to be an inspiring north star for product ideas. My project, <a href="http://productlogic.org/the-doubleloop-project/">DoubleLoop</a>, aspires to cure organizational amnesia through recording a history of a company’s past website launches, striving to dramatically shorten the time required for an organization to discover and capitalize on opportunities moving forward. As product developers, we’ve only begun to learn how to learn. I expect we’re going to continue to see a new era of tools, organizing principles, and product development methodologies that will bring our operations closer to that of the brain. If you’re looking for product vision, look inward.</p><p><em>This post was published originally on my blog, </em><a href="http://productlogic.org/"><em>Product Logic</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76d2f9751932" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doubleloop/the-brain-s-guide-to-product-development-76d2f9751932">The Brain’s Guide to Product Development</a> was originally published in <a href="https://medium.com/doubleloop">DoubleLoop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Fox-Hedgehog Collaboration Loop]]></title>
            <link>https://medium.com/doubleloop/the-fox-hedgehog-collaboration-loop-87e048ac502?source=rss----71d4f0b267fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/87e048ac502</guid>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[venture-capital]]></category>
            <dc:creator><![CDATA[Daniel Schmidt]]></dc:creator>
            <pubDate>Wed, 08 Sep 2021 23:36:58 GMT</pubDate>
            <atom:updated>2017-07-17T16:09:37.763Z</atom:updated>
            <content:encoded><![CDATA[<p>The dichotomy of the <a href="https://en.wikipedia.org/wiki/The_Hedgehog_and_the_Fox">fox and the hedgehog</a> is fascinating, in part, because it gets at a paradox we face in trying to achieve our goals. On the one hand, we need to be monomaniacal hedgehogs to relentlessly execute a vision. On the other hand, we need the fox’s open-mindedness and sound judgment to fit our plans with an uncertain environment.</p><p>Hedgehogs and foxes are often pitted against each other in competition. In this post, however, I’m going to propose a model for how the two mentalities can work together, intertwined in the creative process. The ability to strategically mix the hedgehog and fox cognitive styles, either on a team or within your skull, is critical for innovation.</p><p><strong>The Fox-Hedgehog Metaphor</strong></p><p>The fox-hedgehog philosophy started with the words of Archilochus, an ancient greek poet.</p><blockquote>“a fox knows many things, but a hedgehog one important thing”</blockquote><blockquote>– Archilochus</blockquote><p>In a fight, the cunning fox deploys a diversity of strategies while the hedgehog has one defense, curling up into a ball. Philosopher Isaiah Berlin unleashes the metaphoric power in his essay <a href="http://www.blogs.hss.ed.ac.uk/crag/files/2016/06/the_hedgehog_and_the_fox-berlin.pdf"><em>The Hedgehog and the Fox</em></a><em>.</em></p><p>Berlin describes how hedgehogs “… relate everything to a single central vision, one system, less or more coherent or articulate, in terms of which they understand, think and feel — a single, universal, organising principle in terms of which alone all that they are and say has significance…”</p><p>Foxes, in contrast, “… lead lives, perform acts and entertain ideas that are centrifugal rather than centripetal; their thought is scattered or diffused, moving on many levels, seizing upon the essence of a vast variety of experiences and objects for what they are in themselves, without, consciously or unconsciously, seeking to fit them into, or exclude them from, any one unchanging, all embracing, sometimes self-contradictory and incomplete, at times fanatical, unitary inner vision.”</p><p>Hedgehogs commit to a single framework for how the world works while foxes dance across many models.</p><p>It’s tempting to place thinkers in one profile or the other. Berlin says that Plato, Fyodor Dostoyevsky, and Friedrich Nietzsche are hedgehogs while Shakespeare, Aristotle, and James Joyce are foxes.</p><p>It’s also interesting to consider which cognitive profile is better for different purposes. Philip E. Tetlock’s research indicates that foxes are better than hedgehogs at predicting geopolitical events (see my <a href="https://productlogic.org/2017/02/08/the-superforecasting-playbook-for-product-development/">last post</a>). Jim Collins <a href="http://www.jimcollins.com/article_topics/articles/good-to-great.html">says</a> that hedgehogs are better leaders. “They know how to simplify a complex world into a single, organizing idea — the kind of basic principle that unifies, organizes, and guides all decisions.”</p><p><strong>A Collaboration Model</strong></p><p>While many us fit one profile better than the other, there’s the intriguing possibility that we, individually or in teams, could metamorphize between fox and hedgehog mentalities with strategic intent. The most successful innovators, it seems, can nimbly toggle between these two modes <em>within a single problem space</em>.</p><p>With this diagram, I’ve depicted what a fox-hedgehog collaboration process might look like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*aPmL_1g0mLtLzBHa." /></figure><p>Each segment of the loop corresponds to a component of the cognitive cycle described by American pragmatist philosopher <a href="https://plato.stanford.edu/entries/peirce/">Charles Sanders Peirce</a> as <a href="http://www.jfsowa.com/pubs/cogcycle.pdf">summarized</a> by computer scientist John F. Sowa. (Thanks to <a href="https://josephckelly.com/">Joseph Kelly</a> for the tip!) Let’s walk through the loop.</p><ol><li>We form a <em>theory </em>for how the world works.</li><li>We <em>deduce</em> how to apply the theory to a particular context.</li><li>We <em>predict</em> the results of a planned action.</li><li>We perform the <em>action</em>.</li><li>Through <em>induction</em>, we learn from the resulting data and experience.</li><li>We accumulate new <em>knowledge</em>.</li><li>Given our new understanding, we use <a href="https://en.wikipedia.org/wiki/Abductive_reasoning"><em>abduction</em></a> to make the leap to a new theory based on a hunch or a guess.</li></ol><p>In the Hedgehog-Fox Collaboration Loop, each animal owns half of the loop with two handoff points.</p><p>Theory, given its reductive and abstract nature, is clearly hedgehog territory. Theories rest upon Big Ideas that, in startup terms, exist in the form of visions or <a href="https://www.forbes.com/sites/gregsatell/2015/01/24/peter-thiel-says-that-we-should-hunt-for-secrets-thats-true-but-we-also-need-to-kill-unicorns/#225e8f5b49e8">Thielian secrets</a>. They roughly take the form, “By organizing around [insert Big Idea], we will [insert social mission].”</p><p>Many startup founders don’t think of their Big Ideas as “theories.” Their visions, to them, feel more like inevitabilities than hypotheses to be validated. However, reframing a hedgehog’s vision as a “theory” is a key step towards creating an environment where hedgehogs and foxes can collaborate. Theories are falsifiable. While leaders must be confident, they must have the humility to subject their brain children to testing.</p><p>Given a theory for how to enact world change, innovators must deduce the implications in a particular environment or market. Hedgehogs, masters of their theories, have a role to play in converting their ideas to actionable strategies. Foxes, however, are creatively advantaged in the planning process. By spotting cross-domain patterns, foxes can apply foreign techniques well-suited to the problem at hand. See <a href="https://www.youtube.com/watch?v=JTTWSE4Qhx0">this example</a> of how an algorithm for interpreting telescope images was applied to breast cancer identification.</p><p>In evolved hedgehog-fox relationships, prediction is a point in the cognitive cycle where the fox can say “no.” As I mentioned above, Tetlock’s research shows that Foxes are better forecasters than Hedgehogs. Foxes can predict that a proposed action is so unlikely to succeed that it should not even be attempted, like a general refusing to accept the king’s order to attack at the wrong time. Foxes should decide which endeavors are mostly likely to yield the greatest benefit at the lowest cost.</p><p>Assuming acceptance of the Hedgehog-defined mission, foxes are best equipped to cleverly implement the plans. When reality hits, optimal action requires situational awareness and agility. Foxes can adjust tactics based on relatively unfiltered, malleable views of their changing environments.</p><p>The value of each action we perform is multiplied if we can learn from the results. Hedgehogs have a tendency to over-filter empirical evidence. Data that doesn’t fit the hedgehog’s model is ignored. Thus, we need foxes to own the inductive reasoning process. Foxes will pluck out interesting insights regardless of how conveniently they fit within the active paradigm.</p><p>Induction provides the ingredients for, as Sowa puts it, the “knowledge soup” in the cognitive cycle. The multi-model-minded foxes craft a knowledge soup that is diverse in flavors and textures. When the hedgehog re-enters the picture at the knowledge segment of the loop, they will encounter unfamiliar elements. The fox keeps the hedgehog’s thinking fresh.</p><p>In his <a href="http://us1.campaign-archive2.com/?u=78cbbb7f2882629a5157fa593&amp;id=8404d38662">discussion</a> of hybridizing fox and hedgehog thinking, Venkatesh Rao writes that “The trick is to listen to everything, but also say no to almost everything… But once in a while, the fox half decides to pass something along to the hedgehog half, and the latter trusts the intel enough to change course.”</p><p>We saw earlier that foxes should say “no” to implementing some plans proposed by the hedgehog. Conversely, the hedgehog should say “no” to reacting to much of the new information supplied by the fox.</p><p>Yet, sometimes a foxy insight will penetrate the hedgehog’s stingy filter, exposing a flaw in the hedgehog’s model. In the collaboration loop, hedgehogs use abductive reasoning to form and revise their theories to accommodate the world illuminated by the fox, leaping to each new iteration based on a hunch or guess (see Joseph Kelly’s discussion of <a href="https://www.ribbonfarm.com/2016/09/07/startups-secrets-and-abductive-reasoning/">abductive reasoning and startups</a>). A hedgehog’s passion for its Big Idea is a driving force of abduction. A singular focus propels the hedgehog to make necessary adjustments without losing the gravitational weight of the original vision.</p><p><strong>Individuals and Teams</strong></p><p>The hedgehog-fox collaboration loop can be applied to your own thought process or to a team workflow.</p><p>Venkatesh Rao invented the term “<a href="http://us1.campaign-archive2.com/?u=78cbbb7f2882629a5157fa593&amp;id=8404d38662">foxhog</a>” to describe individuals who can combine fox and hedgehog thinking. A foxhog, Rao writes, is “A miraculous beast that turns uncertainty into certainty.”</p><p>One of my favorite examples of foxhog innovation is Gutenberg’s invention of the printing press, according to Arthur Koestler’s account in <a href="https://en.wikipedia.org/wiki/Arthur_Koestler"><em>The Act of Creation</em></a>. Gutenberg, in hedgehog fashion, fixated on a singular goal to print copies of the bible at scale. In fox fashion, he temporarily let go of his mission to enjoy the wine harvest where he stumbled upon the wine press. Gutenberg’s eureka moment occurred after his fox half told his hedgehog half about a mechanic of the winepress that could be applied to reliably print with movable type. I made a <a href="https://productlogic.org/2017/01/18/a-maze-of-innovation-video/">maze</a> to tell this story.</p><p>I consider myself to be a natural hedgehog who is learning to be foxier over time.</p><p>My default mode is to survey the world with an eye towards exploiting new information for my goals. As a product manager, the products I work on become organizing principles for much of my cognition. Rao <a href="https://www.ribbonfarm.com/2014/02/20/the-cactus-and-the-weasel/">says</a> that “hedgehogs have lots of books 5% read (judged by their cover), and a few 300% read (repeatedly and closely re-read).” This is me.</p><p>But I feel liberated to know that the best way to achieve my hedgehog dreams is, on occasion, to forget about them and enjoy the world as a fox, without an agenda. In doing so I can improve my judgment and eat yummier knowledge soup.</p><p>I also try to partner with foxes. Assuming we can’t all be perfect fox-hedgehog hybrids, we can at least aspire to apply both cognitive styles in aggregate on teams. To be productive, hedgehogs should recognize they need foxes and vice versa.</p><figure><a href="http://bit.ly/HackernoonFB"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hqOaABQ7XGPT-OYNgiUBg.png" /></a></figure><figure><a href="https://goo.gl/k7XYbx"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgw1jkA6hgnvwzTsfMlnpg.png" /></a></figure><figure><a href="https://goo.gl/4ofytp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBpq1ruUi0FVK2UM_I4tQ.png" /></a></figure><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a> family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35tCjoPcvq6LbB3I6Wegqw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87e048ac502" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doubleloop/the-fox-hedgehog-collaboration-loop-87e048ac502">The Fox-Hedgehog Collaboration Loop</a> was originally published in <a href="https://medium.com/doubleloop">DoubleLoop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Feedback loops, Orientation, & The Substance of Product]]></title>
            <link>https://medium.com/doubleloop/feedback-loops-orientation-the-substance-of-product-c15a7e5ecb23?source=rss----71d4f0b267fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/c15a7e5ecb23</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Daniel Schmidt]]></dc:creator>
            <pubDate>Wed, 08 Sep 2021 23:36:39 GMT</pubDate>
            <atom:updated>2017-07-13T20:45:59.231Z</atom:updated>
            <content:encoded><![CDATA[<h4>A loopy iteration of the product triangle.</h4><p>When I received the question on Quora, “What does ‘closing the feedback loop’ mean with regards to product management?”, I found immediate inspiration. It was the middle of a work day, so I chose to crank out <a href="https://www.quora.com/What-does-closing-the-feedback-loop-mean-with-regards-to-product-management/answer/Dan-Schmidt">an answer</a> and publish. But the question stuck with me. I had the intuition that feedback loops are core to product in a way that my cursory Quora response neglected. To follow the the thread, I set out to express feedback loops in the visual terms of <a href="https://productlogic.org/2014/06/22/the-product-management-triangle/">the product management triangle</a>. The result is a new, loopy iteration of the product triangle that expresses the substance of “product” in a way I haven’t done previously.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*5ZsB1ulQYbyNQ3mf." /></figure><p>While each term in the diagram is familiar, the visual structure may be hard to digest. So I’ll unpack it by going through its components separately. Let’s the start with the outer loop…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*5i1ZZRQgNnJdbL73." /></figure><p>The outer loop summarizes what we aspire to achieve through product. We’ll use our resources to build a technology. We’ll attract users to our technology by crafting a stellar user experience. People will love or need it so much they’ll pay to use it (or be valuable to advertisers). Then we’ll reinvest our revenue back into enhancing the technology. The loop will repeat, leading to more revenue and glory.</p><p>Unfortunately, it’s not so simple to move through these big loops. To do so, we need three intersecting feedback loops. Building and maintaining these feedback loops is where we get into the meat of product — it’s how companies stay oriented while reaching for their vision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*EPDkp2u-AIqrXJtd." /></figure><p>Let’s look at the feedback loop that connects technology and users. No matter how powerful our vision is, <a href="https://www.experiencedynamics.com/blog/2014/09/busting-myth-apple-doesnt-do-user-research">even if we’re Apple</a>, we can’t blindly sustain a great user experience. We need insight into the people who use or might use our product. This type of insight exists in qualitative forms like user testing and surveys; and quantitative forms like web analytics and A/B testing. When this feedback loop is broken, you can’t course adjust when the product doesn’t stick. When the loop is healthy<strong>,</strong> product usage provides strong signal informing product direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*9e8npOHYKMPrp5Er." /></figure><p>The terms of the loop connecting users and capital is how we traditionally describe the health of a business. No matter how viral your product is, to grow revenue, you’ll need to invest specifically in acquiring users, whether it’s through traditional or untraditional methods. Even Facebook advertises itself. Industry thinking about how to balance user acquisition and revenue is <a href="http://abovethecrowd.com/2016/04/21/on-the-road-to-recap/">evolving</a>. The feedback loop is broken when the product is not achieving the intended balance, whatever that may be. If you’re trying to be profitable, the loop is broken when acquired users are not converting to paying customers. If you’re trying to grow, the loop is broken when your<a href="http://tomtunguz.com/the-3-pricing-strategies/">pricing strategy</a> introduces too much friction. For an example of a thriving users-capital loop, see <a href="https://news.greylock.com/why-uber-won-5598a2a66561#.xvkvmnway">this piece</a> on how how Uber used “Capital as a Performance Enhancing Drug.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*mlJkWesOL-9XX7KF." /></figure><p>Finally, we have the feedback loop connecting capital and tech. Even the most talented engineers shouldn’t build, build, build all day. To ship the right product at minimal cost, teams need to periodically examine their process. Process improvements can be in the form of tweaking <a href="http://blog.gardeviance.org/2015/06/why-agile-lean-and-six-sigma-must-die.html">project management structure</a>, communication methods, or tools. When the capital-tech loop is broken, teams fail to deliver within business parameters; they ship a flawed product or run out of time/money. When the loop is functioning, the team continuously improves its velocity and the soundness of each release.</p><p>To conclude, the process of creating and writing about these diagrams has led me to believe that <em>orientation</em> is a core responsibility of product management. Companies have a vision for where they want to go, but the landscape around a product is filled with surprises, both good and bad. A company faced with a set back can overreact like a government in the wake of a terrorist attack. And new pathways to success can go unobserved. Feedback loops are how we stay oriented. If the product manager can maintain the healthy functioning of loops described above, the company as a whole will understand its own context and act accordingly.</p><figure><a href="http://bit.ly/HackernoonFB"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hqOaABQ7XGPT-OYNgiUBg.png" /></a></figure><figure><a href="https://goo.gl/k7XYbx"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgw1jkA6hgnvwzTsfMlnpg.png" /></a></figure><figure><a href="https://goo.gl/4ofytp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBpq1ruUi0FVK2UM_I4tQ.png" /></a></figure><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a> family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><figure><a href="https://goo.gl/Ahtev1"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35tCjoPcvq6LbB3I6Wegqw.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c15a7e5ecb23" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doubleloop/feedback-loops-orientation-the-substance-of-product-c15a7e5ecb23">Feedback loops, Orientation, &amp; The Substance of Product</a> was originally published in <a href="https://medium.com/doubleloop">DoubleLoop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Varieties of Product Management Tension]]></title>
            <link>https://medium.com/doubleloop/the-variety-of-product-management-tension-afe94ceafab4?source=rss----71d4f0b267fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/afe94ceafab4</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[tension]]></category>
            <category><![CDATA[pm]]></category>
            <dc:creator><![CDATA[Daniel Schmidt]]></dc:creator>
            <pubDate>Wed, 08 Sep 2021 23:36:23 GMT</pubDate>
            <atom:updated>2017-12-02T17:13:55.211Z</atom:updated>
            <content:encoded><![CDATA[<h4>Managing these six types of tension is a chief responsibility of PMs.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/403/1*_6JPfFbWPTWOjyHXAknJsw.jpeg" /></figure><p>Starting with <a href="https://productlogic.org/2014/06/22/the-product-management-triangle/"><em>The Product Management Triangle</em></a>, I’ve argued that a chief responsibility of product managers is to release the tension surrounding a product. In the PM triangle article, I focused on business model tensions and tensions between teams. But since then, I’ve explored an additional four types of product tension. This post takes a zoomed out view which also serves as a guide to much of my writing over the last three years.</p><p><em>1. Tensions inherent in the business model</em></p><p>Every product has some degree of tension arising from its business model. Since people would rather not pay for things, UX and monetization are fundamentally at odds. The tension is most inflamed in advertising-based business models where the company makes money by making the user experience worse in adding more ads to the page.</p><p>PMs live at the conflict line between UX and monetization and must find ways to manage the tension. For example, <a href="https://en.wikipedia.org/wiki/Native_advertising">native ads</a> mitigate biz model tension by meeting monetization goals while minimizing UX damage. An increasing number of SaaS enterprise companies, like Slack, are charging on a per active user basis. While customers would prefer “free,” this minimizes the tension by ensuring that customers only pay in proportion to the value they receive.</p><p>For more, see <a href="https://productlogic.org/2014/06/22/the-product-management-triangle/"><em>The Product Management Triangle</em></a><em>.</em></p><p><em>2. Tensions between a product and its environment</em></p><p>Launching a new product is like injecting a foreign object into a stable environment. Sometimes the intrusion is embraced while other times its rejected.</p><p>PMs must balance two ways of thinking. On the one hand, companies aspire to “change the world” or “dent the universe” with their product. On the other hand, they must adapt their product according to customer feedback and market signal.</p><p>The tension between bending the world versus bending to the world is one of my favorite product management dilemmas.</p><p>For more, see <a href="https://productlogic.org/2016/05/12/the-fundamental-tension-in-product/"><em>The Fundamental Tension in Product</em></a>.</p><p><em>3. Tensions between predictable and unpredictable game plans</em></p><p>Building a product requires navigating an unpredictable future. Yet the people who fund and resource products often want to see clearly defined development roadmaps and predictable budgets.</p><p>We’ve seen the software development world drift from waterfall to agile ways of operating. Waterfall methodology puts up a false facade of certainty regarding the path forward. Agile allows teams to iteratively adapt a product based on incremental learning and external response, but <a href="https://www.ribbonfarm.com/2010/07/26/a-big-little-idea-called-legibility/">legibility</a> is sacrificed. Stakeholders have trouble planning around a product with an unclear future shape and cost structure.</p><p>To manage this tension, PMs must give products the breathing room to evolve organically while providing stakeholders and clients sufficient stability in the future plan.</p><p>For more, see <a href="https://productlogic.org/2015/10/14/give-up-product-roadmaps/"><em>Let’s Rethink Product Roadmaps</em></a>.</p><p><em>4. Tensions between short-term and long-term goals</em></p><p>There are two popular edicts that are actually at odds with each other. On the one hand, startups are told to build MVPs that test core product assumptions as early as possible. On the other hand, startups are advised to build platforms that take on a life beyond any single application.</p><p>PMs must navigate when to ship a lightweight MVP app and when to invest in a platform. Either approach can go wrong. A failed MVP could discourage a team from following a lucrative direction. A platform can be expensively built to never find its killer app.</p><p>For more, see <a href="https://productlogic.org/2016/07/31/lean-fat-product-thinking/"><em>Lean &amp; Fat Product Thinking</em></a>.</p><p><em>5. Tensions between religious and scientific mentalities</em></p><p>Inherent in many of the above tensions is a conflict from two ways of thinking about products. Lean startup methodology rides a wave of scientific product thinking focused on falsifying hypotheses and split testing. Yet, prominent product visionaries like Steve Jobs operate more like religious leaders who stay true to a mission regardless of what the world throws at them.</p><p>Product managers strive to articulate a “north star” that inspires an almost religious following. But to reach that north star, they must cultivate a scientific mindset where beliefs are discarded when disproven.</p><p>For more, see <a href="https://productlogic.org/2016/07/17/risk-of-a-scientific-creative-process/"><em>The Risk of Scientific Creative Process</em></a>.</p><p><em>6. Tensions between employees</em></p><p>All of the above tensions can lead to clashes between team members. The sales team clashes with designers when both parties have different incentives under the business model. Or one team can be frustrated with another team who isn’t, in their eyes, sufficiently scientific in their approach. To manage these types of tensions, the PM must clearly articulate <em>how</em> the company is approaching all the above tension. This provides the rationale for how conflicts between team members should be handled.</p><p>However, the worse types of tension I’ve seen is between the identities of team members; when two people have different intuitions for how to solve a single problem. I’ve found that for teams to thrive, everyone needs their own swim lane so they aren’t competing with others over sacred turf. Yet swim lane differentiation can’t come at the price of collaboration. You need people from different swimlanes working together to accomplish singular objectives.</p><p>For more, see <a href="https://productlogic.org/2014/06/22/the-product-management-triangle/"><em>The Product Management Triangle</em></a>.</p><p><em>Thanks for reading this post! Check out my project, </em><a href="http://www.double-loop.co/"><em>Double-Loop</em></a><em>, that strives to improve the product development process by recording the story of your build-measure-learn loops.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afe94ceafab4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doubleloop/the-variety-of-product-management-tension-afe94ceafab4">The Varieties of Product Management Tension</a> was originally published in <a href="https://medium.com/doubleloop">DoubleLoop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Superforecasting Playbook for Product Development]]></title>
            <link>https://medium.com/doubleloop/the-superforecasting-playbook-for-product-development-a10f13dd412?source=rss----71d4f0b267fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/a10f13dd412</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[forecasting]]></category>
            <dc:creator><![CDATA[Daniel Schmidt]]></dc:creator>
            <pubDate>Wed, 08 Sep 2021 23:35:50 GMT</pubDate>
            <atom:updated>2017-07-16T19:56:12.570Z</atom:updated>
            <content:encoded><![CDATA[<p>When you inject new software into an environment, it’s difficult to forecast what will transpire.</p><p>Product teams continually try to predict what will work. We predict that a certain new feature will increase conversion, that a targeted ad spend will bring critical mass, or that market conditions will change in our favor. We expect many of our bets to fail.</p><p>We inoculate ourselves from bad predictions with methodologies like Agile and Lean Startup. Measuring market signal with each iteration helps us quickly change course. If the brilliant new feature decreases conversion, we can remove it before our revenue plummets.</p><p>Minimizing losses from bad bets give us more opportunities to try things. However, the experience of failed attempts does not reliably lead to better predictions in the future. Faced with new information, we can overreact, under-react, misunderstand, forget, or turn a blind eye. Emotions and cognitive biases can cloud our judgment.</p><p>Learning can go even more haywire at an organizational level. Add group-think, knowledge silos, and <a href="https://en.m.wikipedia.org/wiki/Corporate_amnesia">corporate amnesia</a> to the list of epistemological threats.</p><p>But imagine if we could systematically improve the accuracy of our company’s predictions. Then we could reliably increase our ability to make winning bets over time.</p><p>I was surprised to discover that a playbook for optimizing prediction accuracy already exists. It’s called Superforecasting. But it’s not being widely leveraged by product teams yet.</p><p><strong>Superforecasting</strong></p><p>The first step to improving something is measuring it. In the book <a href="https://www.amazon.com/Superforecasting-Science-Prediction-Philip-Tetlock/dp/0804136718"><em>Superforecasting</em></a>, Philip E. Tetlock and Dan Gardner describe a system for measuring the accuracy of predictions called the Brier score. In their words, “Brier scores measure the distance between what you forecast and what actually happened.”</p><p>To explain Brier scores, let’s consider weather forecasting.</p><p>Weather forecasting involves making probabilistic predictions like “There’s a 70% chance it will rain tomorrow.” If it doesn’t rain tomorrow, it doesn’t mean the forecast was wrong since it gave a 30% chance of no rain. This can be counter-intuitive since people have a false tendency to think that a forecast is wrong when a prediction that something is likely doesn’t end up happening.</p><p>In the terminology of the Brier score, a forecaster’s predictions are “well calibrated” if the things they say are X% likely to happen actually happen X% of the time. So if a meteorologist says “there’s 70% chance of rain tomorrow” one hundred times during the year, they would be perfectly calibrated if it rained 70 times and didn’t rain the other 30. If it had only rained 50 times, we would say the forecaster is over-confident. If it had rained 80 times, they’re under-confident. Over-confidence and under-confidence are the two forms of mis-calibration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/486/0*WrV0bi3ovSHkPZze." /><figcaption>Over-confidence</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/0*5qVxDG8fblMXezOb." /><figcaption>Under-confidence</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/0*A2hMjncbYiT-quXr." /><figcaption>Perfect calibration</figcaption></figure><p>The other dimension of the Brier score is resolution. Resolution measures the decisiveness of a forecaster’s predictions. If a meteorologist says the chance of rain is 100% when it does rain and 0% when it doesn’t, they would have perfect resolution.</p><p>Forecasters can be perfectly calibrated with poor resolution. Let’s say a forecaster predicts a 50% chance of rain every day. Even if it does rain exactly half of the days, their resolution will be dinged for not elevating the chances on the days it does rain and lowering them on the days when it doesn’t. Poor resolution implies overly cautious predictions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/0*7fDkNERra6C0-vt5." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/0*qAopDwnkydysA7Hy." /></figure><p>The Brier score combines calibration and resolution into a single accuracy metric. The lower the Brier score, the more accurate a forecaster’s predictions.</p><p>With a metric for prediction accuracy, we can scientifically investigate which factors lead individuals or teams to improve their foresight. Tetlock did exactly this to win a forecasting tournament administered by the United States Intelligence Community.</p><p>The forecasting tournament was created in the wake of the tragic false assessment that Iraq possessed WMDs. According to the <a href="https://www.iarpa.gov/index.php/research-programs/ace">IARPA website</a>, the goal of the government program is to</p><blockquote>… dramatically enhance the accuracy, precision, and timeliness of intelligence forecasts for a broad range of event types, through the development of advanced techniques that elicit, weight, and combine the judgments of many intelligence analysts.</blockquote><p>The tournament, held over four years, asked participants to forecast questions like “Will Russia officially annex additional Ukrainian territory in the next three months?” and “In the next year, will any country withdraw from the eurozone?”</p><p>As measured by the Brier score, the predictions made by Tetlock’s group of “superforecasters” were 30% more accurate than the average for intelligence community analysts who has access to classified information.</p><p>While the highest performing forecasters are smart, Tetlock concluded that making consistently accurate predictions has more to do with <em>how</em> they think. Tetlock’s discoveries constitute a set of proven principles of good judgment, summarized here:</p><blockquote>In philosophic outlook, [superforecasters] tend to be:</blockquote><blockquote>CAUTIOUS: Nothing is certain</blockquote><blockquote>HUMBLE: Reality is infinitely complex</blockquote><blockquote>NONDETERMINISTIC: What happens is not meant to be and does not have to happen</blockquote><blockquote>In their abilities and thinking styles, they tend to be:</blockquote><blockquote>ACTIVELY OPEN-MINDED: Beliefs are hypotheses to be tested, not treasures to be protected</blockquote><blockquote>INTELLIGENT AND KNOWLEDGEABLE, WITH A “NEED FOR COGNITION”: Intellectually curious, enjoy puzzles and mental challenges</blockquote><blockquote>REFLECTIVE: Introspective and self-critical</blockquote><blockquote>NUMERATE: Comfortable with numbers</blockquote><blockquote>In their methods of forecasting they tend to be:</blockquote><blockquote>PRAGMATIC: Not wedded to any idea or agenda</blockquote><blockquote>ANALYTICAL: Capable of stepping back from the tip-of-your-nose perspective and considering other views</blockquote><blockquote>DRAGONFLY-EYED: Value diverse views and synthesize them into their own</blockquote><blockquote>PROBABILISTIC: Judge using many grades of maybe</blockquote><blockquote>THOUGHTFUL UPDATERS: When facts change, they change their minds</blockquote><blockquote>GOOD INTUITIVE PSYCHOLOGISTS: Aware of the value of checking thinking for cognitive and emotional biases</blockquote><blockquote>In their work ethic, they tend to have:</blockquote><blockquote>A GROWTH MINDSET: Believe it’s possible to get better</blockquote><blockquote>GRIT: Determined to keep at it however long it takes</blockquote><p>I love how Tetlock’s research puts data to philosophically rich concepts, like the <a href="https://en.wikipedia.org/wiki/The_Hedgehog_and_the_Fox">hedgehog-fox dichotomy</a>. The Ancient Greek poet Archilochus famously said that “a fox knows many things, but a hedgehog one important thing.” Tetlock categorized his forecasters into each persona.</p><p>Hedgehogs are fixated on one Big Idea; a single world view. They see everything through that lens. Tetlock describes this group in his forecasters pool:</p><blockquote>Some were environmental doomsters (“ We’re running out of everything”); others were cornucopian boomsters (“ We can find cost-effective substitutes for everything”). Some were socialists (who favored state control of the commanding heights of the economy); others were free-market fundamentalists (who wanted to minimize regulation). As ideologically diverse as they were, they were united by the fact that their thinking was so ideological. They sought to squeeze complex problems into the preferred cause-effect templates and treated what did not fit as irrelevant distractions. Allergic to wishy-washy answers, they kept pushing their analyses to the limit (and then some), using terms like “furthermore” and “moreover” while piling up reasons why they were right and others wrong. As a result, they were unusually confident and likelier to declare things “impossible” or “certain.”</blockquote><p>Foxes, in contrast, are open to many perspectives. They synthesize inputs from multiple models. Tetlock writes:</p><blockquote>The [fox] group consisted of more pragmatic experts who drew on many analytical tools, with the choice of tool hinging on the particular problem they faced. These experts gathered as much information from as many sources as they could. When thinking, they often shifted mental gears, sprinkling their speech with transition markers such as “however,” “but,” “although,” and “on the other hand.” They talked about possibilities and probabilities, not certainties. And while no one likes to say “I was wrong,” these experts more readily admitted it and changed their minds.</blockquote><p>The hedgehog vs. fox battle has been officially settled: foxes win, at least as far as forecasting goes. Tetlock found that “Foxes beat hedgehogs on both calibration and resolution. Foxes had real foresight. Hedgehogs didn’t.” Imagine an economist who relentlessly preaches austerity in the face of clear evidence showing the failure of austerity measures.</p><p>Yet, Tetlock doesn’t close the door on the utility of the hedgehog mindset. He raises the possibility that, while Hedgehogs suck at forecasting, their commitment to a single frame of thinking might lead them to ask more illuminating questions. Tetlock speculates:</p><blockquote>The psychological recipe for the ideal superforecaster may prove to be quite different from that for the ideal superquestioner, as superb question generation often seems to accompany a hedgehog-like incisiveness and confidence that one has a Big Idea grasp of the deep drivers of an event. That’s quite a different mindset from the foxy eclecticism and sensitivity to uncertainty that characterizes superb forecasting.</blockquote><p>This is a compelling hypothesis for how foxes and hedgehogs can collaborate to achieve great things.</p><p><strong>Applying Superforecasting to Startups</strong></p><p>Now that we’ve taken a quick tour of superforecasting, let’s consider how the system could be applied to product development.</p><p>Imagine your team at an eCommerce startup is finishing a project to redesign the checkout page. Right before you launch an A/B test with the new page, you pose the question:</p><p>“Will the purchase conversion rate of the new checkout page beat the current page by 10% for the 30 days after launch?”</p><p>Everyone on your team provides probabilistic forecasts ranging from 10% to 80%. The average prediction gives a 30% chance that the new page will increase conversion by 10%.</p><p>If you had seen these forecasts <em>before</em> you committed to doing the project, would you have moved forward with it?</p><p>It depends. Given the scale of your company, maybe a 30% chance to increase revenue by 10% is a good bet to make. But maybe other endeavors are more likely to succeed, so you start forecasting all proposed projects before you prioritize them.</p><p>And your forecasts need not be limited to the impact of potential projects. You can predict other factors related to the inner workings of your company, the technological landscape, or the market. Some examples:</p><p>“Will the engineering team finish refactoring our accounting system within two months of the project start date?”</p><p>“If we added 5 employees to the sales team in March, will our customer base grow by 20% by the end of the year?”</p><p>“Will the augmented/virtual reality market exceed $100 billion in revenue by 2020?”</p><p>“Will the word recognition accuracy rate of Google Voice reach 99% by the end of 2019?”</p><p>“Will the average health insurance deductible increase by 5% by the end of 2018?”</p><p>With accurate forecasts to questions like these, we’ll be more aware of our capabilities and steps ahead of the market. We’d have the foresight necessary for exceptional strategy.</p><p>One might argue that companies are already making forecasts in the form of cost-benefit analysis or financial models. But these formats are too ambiguous to help us improve our predictions over time. Tetlock and Gardner write:</p><blockquote>The first step in learning what works in forecasting, and what doesn’t, is to judge forecasts, and to do that we can’t make assumptions about what the forecast means. We have to know. There can’t be any ambiguity about whether a forecast is accurate or not…</blockquote><p>In cost-benefit analysis, you might forecast the impact of a project to be high. But what exactly does “high” mean? And in what time frame must the benefit occur? There are too many shades of gray. And maybe we’re two months after launch with little impact from the project. Does that mean the prediction is wrong or do we give it more time?</p><p>With a financial model, the projections will surely not be <em>exactly</em> right. So how can we determine if the model was correct? How close do the numbers need to be?</p><p>Cost-benefit analysis and financial models serve a real purpose, but they must be converted into unambiguous forecasts if we’re serious about improving our predictions over time.</p><p>So let’s say our company starts making a high quantity of unambiguous predictions. If we calculated our collective Brier score, we’d probably see that it leaves much to be desired.</p><p>Besides the fact that accurate forecasting is hard, I suspect many startup people are especially poor forecasters. There’s a hedgehoggy aspect of working on a product. It requires an almost irrational devotion to the product direction; a narrow lens that misses relevant opposing perspectives. We may be prone to overconfidence in predicting the success of product launches or improvement of their environmental conditions. Exuberant optimism is conducive to good work but runs counter to accurate forecasting.</p><p>Perhaps company staff is too biased to proficiently forecast their own future. The solution could be to insert 3rd party superforecasters into a company’s operations. It appears that <a href="http://goodjudgment.com/index.html">Tetlock co-founded a commercial firm</a> based on this idea. I’m compelled to try this out. In the future, asking questions of superforecasters could become ubiquitous, like running user tests or customer surveys. I anticipate there’d be some challenges in transferring domain knowledge, at least as far as some key questions are concerned. But this can be overcome.</p><p>But even without enlisting external superforecasters, applying the model is useful. These practices will be beneficial no matter what:</p><ul><li>Creating unambiguous hypotheses for projects</li><li>Making predictions before you commit to resourcing</li><li>Looping back to old predictions to judge their accuracy</li></ul><p>Turning these practices into habits is the goal of my side-project, <a href="https://productlogic.org/2016/01/18/why-how-to-use-double-loop-1-0/">Double-Loop</a>.</p><p>A good way to summarize the potential of the superforecasting model for product teams is that it nudges us to become more like <a href="http://us1.campaign-archive2.com/?u=78cbbb7f2882629a5157fa593&amp;id=8404d38662">foxhogs</a>, a hybrid animal invented by Venkatesh Rao. He explains:</p><blockquote>The net effect of this personality profile is that the foxhog can live in a highly uncertain environment, and be responsively engaged within it, yet create a high-certainty execution context.</blockquote><blockquote>This ability to turn uncertainty into certainty is the key to … entrepreneurial effectiveness…</blockquote><p>Accurate predictions are not a sufficient for success. You need to ask the right questions. This requires leaving no stone unturned while you push forward on a singular mission to achieve your product vision.</p><figure><a href="http://bit.ly/HackernoonFB"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hqOaABQ7XGPT-OYNgiUBg.png" /></a></figure><figure><a href="https://goo.gl/k7XYbx"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgw1jkA6hgnvwzTsfMlnpg.png" /></a></figure><figure><a href="https://goo.gl/4ofytp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBpq1ruUi0FVK2UM_I4tQ.png" /></a></figure><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a> family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35tCjoPcvq6LbB3I6Wegqw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a10f13dd412" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doubleloop/the-superforecasting-playbook-for-product-development-a10f13dd412">The Superforecasting Playbook for Product Development</a> was originally published in <a href="https://medium.com/doubleloop">DoubleLoop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s rethink product roadmaps]]></title>
            <link>https://medium.com/doubleloop/let-s-rethink-product-roadmaps-d1c56574e4e6?source=rss----71d4f0b267fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/d1c56574e4e6</guid>
            <dc:creator><![CDATA[Daniel Schmidt]]></dc:creator>
            <pubDate>Wed, 08 Sep 2021 23:35:33 GMT</pubDate>
            <atom:updated>2015-10-20T05:11:49.624Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hGLd_K2bZ0ZEooSKz0-d4w.jpeg" /></figure><p>Hierarchical thinking makes our western minds feel comfortable. When looking at the messy, apparent randomness of the world, we find ourselves searching for core truths that, when understood, make everything seem clean and logical. We want principles that fork into sub-principals like tree roots. Sometimes this impulse pays off big. Science and medicine are rewards for breaking phenomena down into parts and sub-parts whose behavior can be explained and predicted. In the industrial age, companies thrived in the form of hierarchical structures in which the role of each low-level worker is explicitly defined by managers sitting at the top. In the industrial age, the boundary between human and machine became blurred.</p><p>While humans continue to extract deep value from hierarchical thought, our reductive tendencies can go overboard. Venkatesh Rao has explored this notion through the concept of “<a href="http://www.ribbonfarm.com/2010/07/26/a-big-little-idea-called-legibility/">legibility</a>.” To satisfy our deep desire for the world to be legible, we impose our own structures on behaviors we don’t understand. As discussed in James C. Scott’s book, <a href="http://www.amazon.com/gp/product/0300078153?ie=UTF8&amp;tag=ribbonfarmcom-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0300078153"><em>Seeing Like a State: How Certain Schemes to Improve the Human Condition Have Failed</em></a><em>, </em>this tendency has led to disastrous consequences in the realm of statecraft. The U.S. government’s attempt to create order in the middle east illustrates the point. Rao summarizes the recipe for legibility-based failure:</p><blockquote><em>- Look at a complex and confusing reality, such as the social dynamics of an old city</em></blockquote><blockquote><em>- Fail to understand all the subtleties of how the complex reality works</em></blockquote><blockquote><em>- Attribute that failure to the irrationality of what you are looking at, rather than your own limitations</em></blockquote><blockquote><em>-Come up with an idealized blank-slate vision of what that reality ought to look like</em></blockquote><blockquote><em>- Argue that the relative simplicity and platonic orderliness of the vision represents rationality</em></blockquote><blockquote><em>- Use authoritarian power to impose that vision, by demolishing the old reality if necessary</em></blockquote><blockquote><em>- Watch your rational Utopia fail horribly</em></blockquote><p>So when should we apply hierarchical thinking and when should we avoid it? This question is especially puzzling in the realm of software development. Rooted in computer science and analytical modes of thought, software has internal logic that <em>can</em> be well understood. You can solve big problems by breaking them down to smaller problems.</p><p>Yet we’ve seen the desire for legibility get software companies into trouble. A primary example is the <a href="https://en.wikipedia.org/wiki/Waterfall_model">waterfall model</a> of development. It’s a lot easier to run a business when the outcome, cost, and timeframe of each project is clear. With the waterfall model, companies try to achieve certainty through completely defining requirements upfront and estimating the corollary engineering work. While the outcome of running a line of code can be predicted, the industry has learned that the outcomes of complex software projects, even with heavy analysis, cannot be. Nobody can predict upfront the exact set of human or technical challenges. Waterfall projects lead companies to spend fortunes on failed software.</p><p>With the advent of <a href="https://en.wikipedia.org/wiki/Agile_software_development">Agile</a>, <em>we’ve seen companies trade in legibility for results. </em>Learning and course adjustments are baked iteratively into the agile process. In the agile model, companies are less certain about exactly what they are building upfront. This can be hard for some people to accept, but they can be more certain that value will come out the other end.</p><p>The venture capital model provides another example of choosing results over legibility. In venture capital, it’s understood that, to discover how software can transform an industry, the most successful approach is not to conceive and flesh out the one big idea. Instead, the winning approach is to make many bets and let time be the judge. We don’t need to know <em>why </em>company X will hit a home run while similar company Y will strike out. We just someone to hit the home run.</p><p>While agile and venture capital demonstrate that the software industry is learning how to manage uncertainty, companies still try to exert too much control over the future unfolding of their products. Product managers are commonly expected to create “product roadmaps.” The roadmap metaphor suggests that teams are driving down a defined road that will lead to certain projects, like passing by gas stations. There can be forks in the road, but since you have a roadmap, you know in advance what you’ll get in each direction.</p><p>It’s ironic that the same companies who embrace agile create product roadmaps offering static views of the future. In my experience as a product manager, roadmaps are bullshit. They are created to make the company at large feel comfortable with where the product is going. Roadmaps make the product evolution legible. But inevitably, the experience of each project completely changes the trajectory. Things you thought were important aren’t. Things you previously neglected are vital. Things that you thought would be technically easy were hard, and vice versa. The unfolding of new knowledge does not just dictate which road on the map to take, it renders the map meaningless. I concede that, in the case of mature software with a long backlog of clearly valuable feature development, roadmaps have value, especially in managing the expectations of external clients. But if you’re trying to build something truly new, whether you are a big company or startup, roadmaps create the illusion of certainty at the detriment of success. If the PM can tear up and regenerate their roadmap at each iteration, they are relatively innocuous. But if teams are actually held to their roadmaps, they’re toxic. Product builders must be given the freedom to be maximally adaptive.</p><p>So if we don’t do roadmaps, what do we do instead? I’m not entirely sure yet. In my current company, I just say what we’re doing next and keep a list of all the things we could be doing but aren’t. The collective imagination of a company should be captured, just not with flawed forecasts for dreams becoming real.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1c56574e4e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doubleloop/let-s-rethink-product-roadmaps-d1c56574e4e6">Let’s rethink product roadmaps</a> was originally published in <a href="https://medium.com/doubleloop">DoubleLoop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Object-Oriented Product Thinking]]></title>
            <link>https://medium.com/doubleloop/object-oriented-product-thinking-ea55146e2ec5?source=rss----71d4f0b267fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/ea55146e2ec5</guid>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Daniel Schmidt]]></dc:creator>
            <pubDate>Wed, 08 Sep 2021 23:35:19 GMT</pubDate>
            <atom:updated>2017-08-16T02:33:46.837Z</atom:updated>
            <content:encoded><![CDATA[<h4>Sidestepping the fundamental tension in product.</h4><p>Introspective product builders can find themselves trapped in a paradox between (A) the product-driven Steve Jobs mentality of <em>bending</em> the world to your vision, and (B) the customer-driven lean startup mindset of <em>adapting</em> our products to the environment and the marketplace.</p><p>This <a href="https://productlogic.org/2016/05/12/the-fundamental-tension-in-product/">fundamental tension in product</a> mirrors an ancient philosophy puzzle.</p><p>The product-driven mindset echoes an anti-realist branch of epistemology where the world is a construction of our minds. Anti-realists emphasize how reality is malleable, something that can be transformed by language and concepts.</p><p>The customer-driven approach, in contrast, echoes a realist philosophy. Epistemic realists believe that there is an absolute world that exists independently of us. It is the job of philosophers and scientists, they say, to conform our mental models to the external reality.</p><p>It’s easy to say that the product-driven / customer-driven paradox is a yin-yang that requires a balancing act as opposed to a resolution. However, as someone who perpetually yearns for maximum strategic clarity, I find “balance” to be an unsatisfying answer. I’d rather find a way around the ambiguity.</p><p>In <a href="http://openhumanitiespress.org/books/download/Bryant_2011_Democracy-of-Objects.pdf"><em>The Democracy of Objects</em></a>, philosopher Levi Bryant argues that the world views of both epistemological realists and anti-realists rest upon their bifurcation of subject and object. Bryant writes:</p><blockquote>… within the Modernist schema that drives both epistemological realism and epistemological anti-realism, the world is bifurcated into two distinct domains: culture and nature. The domain of the subject and culture is treated as the world of freedom, meaning, signs, representations, language, power, and so on. The domain of nature is treated as being composed of matter governed by mechanistic causality. Implicit within forms of theory and philosophy that work with this bifurcated model is the axiom that the two worlds are to be kept entirely separate, such that there is to be no inmixing of their distinct properties.</blockquote><p>Both realist and anti-realist mental models anthropomorphize nature such that objects can only be understood in human terms. Their debate is only about whether or not human representations correlate to an absolute reality. Anti-realists hold that there is no such thing beyond our constructions, while realists aspire to accurately map an independently real external environment. Bryant distills the contention as the X in the following diagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/0*WfZoVPI7XXJ7yh-s." /></figure><p>Bryant elaborates:</p><blockquote>… this mode of distinction leads us to ignore the role of the nonhuman and asignifying in the form of technologies, weather patterns, resources, diseases, animals, natural disasters, the presence or absence of roads, the availability of water, animals, microbes, the presence or absence of electricity and high speed internet connections, modes of transportation, and so on. All of these things and many more besides play a crucial role in bringing humans together in particular ways…</blockquote><p>Put in this light, both the realist and anti-realist philosophies seem ill-equipped to grapple with the realms of tech products where people and technologies are tangled together.</p><p>Alternatively, Bryant argues for an <a href="https://en.wikipedia.org/wiki/Object-oriented_ontology">object-oriented ontology</a> where human and non-human objects, first and foremost are <em>objects. </em>Wikipedia defines this philosophy as a “… school of thought that rejects the privileging of human existence over the existence of nonhuman objects” The door then opens to examining, not just how machines can mimic human systems, but how all forms of human and non-human objects interact with each other. Bryant writes:</p><blockquote>… where the anti-realists have obsessively focused on a single gap between humans and objects, endlessly revolving around the manner in which objects are inaccessible to representation, object-oriented philosophy allows us to pluralize this gap, treating it not as a unique or privileged peculiarity of humans, but as true of all relations between objects whether they involve humans or not. In short, the difference between humans and other objects is not a difference in kind, but a difference in degree. Put differently, all objects translate one another. Translation is not unique to how the mind relates to the world. And as a consequence of this, no object has direct access to any other object.</blockquote><p>While I’ve barely touched the surface, object-oriented ontology feels like a solid foundation for product thinking. The extreme forms of both the product-driven and customer-driven mindsets give primacy to the single problem of how a company integrates with its external environment. It’s liberating to let go of this bifurcation and delve into the <em>multiplicity</em> of systems that require integration. Product builders must integrate teams, technologies, customers, and business models who are all simultaneously interacting with society, culture, nature, and the economy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea55146e2ec5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doubleloop/object-oriented-product-thinking-ea55146e2ec5">Object-Oriented Product Thinking</a> was originally published in <a href="https://medium.com/doubleloop">DoubleLoop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>