<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daniel Filson on Medium]]></title>
        <description><![CDATA[Stories by Daniel Filson on Medium]]></description>
        <link>https://medium.com/@danfilson?source=rss-1a45f0b1f872------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*CIwZ-ARSqY8h_FCv.jpg</url>
            <title>Stories by Daniel Filson on Medium</title>
            <link>https://medium.com/@danfilson?source=rss-1a45f0b1f872------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:56:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@danfilson/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[OKR You Ready to Gallop into the World of Risk Management?]]></title>
            <link>https://medium.com/@danfilson/okr-you-ready-to-gallop-into-the-world-of-risk-management-ef1020aa3bfd?source=rss-1a45f0b1f872------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef1020aa3bfd</guid>
            <category><![CDATA[okr-in-business]]></category>
            <category><![CDATA[product-operation]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Daniel Filson]]></dc:creator>
            <pubDate>Fri, 31 Mar 2023 15:41:29 GMT</pubDate>
            <atom:updated>2023-03-31T15:42:46.888Z</atom:updated>
            <content:encoded><![CDATA[<h3>OKR You Ready to Gallop into the World of Risk Management? Or Are You PROJECTing Assumptions as Truth?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m5oQpxGlkHLjrWy90RHcYA.png" /></figure><p>Welcome to the enchanted land where Workhorses roam with party hats and fairy wings, pretending to be Unicorns! Today, we’ll unravel the mystical differences between the mighty Workhorse (Project) and the majestic Unicorn (OKR) and explain why both these creatures need to embrace their true identities.</p><p>Let’s trot past the puns and quirky zoomorphism and get down to the nitty-gritty. Throughout my career, I’ve witnessed countless organizations struggle to distinguish between OKRs and Projects. Unfortunately, this confusion often leads to dressing up a Project (Workhorse) as an OKR (Unicorn) or trying to iterate from Project to OKR, only to remain stuck in the Project realm.</p><p>By the end of this article, I hope to clarify these two paradigms, bust some myths, and explain why organizations need both — but separately.</p><p>TLDR Version:</p><ul><li>Projects and OKRs serve different purposes: Projects are planned work with defined scopes and objectives (Output Centric), while OKRs help teams set and track measurable goals (Outcome Centric).</li><li>Confusing Projects and OKRs is easily done but is detrimental: Mixing up these two approaches can prevent organizations from effectively managing risk and achieving desired outcomes.</li><li>Projects and OKRs have distinct risk management strategies: Projects focus on minimizing risk through planning and fixed outputs. OKRs embrace uncertainty and adaptability for better efficiency (less waste) in reaching outcomes.</li><li>Organizations need both: Recognizing and utilizing projects and OKRs in their appropriate contexts is essential for optimizing risk reduction and achieving success.</li></ul><p>First, let’s clarify our definitions:</p><ul><li>Projects are planned work with defined scopes, objectives, and end dates for completing the scope (output).</li><li>OKRs (Objectives and Key Results) are goal-setting methodologies that help teams and individuals set and track measurable goals.</li></ul><p>Though these definitions seem distinct, confusion arises due to their similarities. Both have purposes, metrics, team execution, time constraints, accountability, governance, and output. It’s like trying to drink soup with a fork rather than a spoon — both are utensils to eat food with but are designed for two different purposes. Project and OKR are fundamentally different models that can’t be merged. One relies on specific, planned activities based on an assumption, while the other explores various activities to achieve the objective.</p><p>Does it really matter if you confuse the two approaches? Unfortunately, yes. This distinction matters because organizations want to manage risk, and Project and OKR are different ways to optimize risk reduction.</p><p>Let’s explore an analogy to illustrate how the Project and OKR approaches manage risk.</p><p>Imagine you’re planning a day trip to a new city to have fun, get enriched, and become reinvigorated. You have two options: take a pre-planned, 6-hour guided tour or embark on a spontaneous adventure.</p><p>Project (Guided Tour): This option represents the Workhorse. You book the guided tour a week in advance, taking advantage of a 50% early bird discount and securing your spot. The tour ensures you visit the city’s most iconic sites, sticking to a set itinerary, schedule, and cost.</p><p><strong>Risk Management:</strong> By opting for the guided tour, you minimize the risk of missing out on the city’s greatest hits or getting lost. You have a clear plan, meaning you’ll see specific sites, and the cost is predetermined. However, the downside is that you might miss out on unique discoveries or experiences tailored to your interests. In addition, the tour’s fixed nature can limit your opportunity to explore the city’s hidden gems, missing out on maximizing your fun and enrichment. You may also find that it is raining down, so you cannot get off the bus and see the sites up close, ultimately minimizing your enjoyment.</p><p>OKR (Impromptu Adventure): This option represents the Unicorn. You arrive in the city with no definitive plans, choosing to explore by wandering around and creating your own adventure. This approach opens the door to endless possibilities, allowing you to discover off-the-beaten-path attractions and experiences tailored to your preferences.</p><p><strong>Risk Management:</strong> With spontaneous adventure, you embrace uncertainty and a willingness to adapt. The risk here is that you may only visit some of the city’s top attractions and get lost. However, by venturing off the beaten path, you increase your chances of finding unique experiences that align with your goals of having fun and getting enriched. This approach is more outcome-centric, focusing on maximizing the enjoyment and enrichment of the trip rather than simply ticking off a list of predetermined sites.</p><p>This analogy demonstrates that both Project (guided tour) and OKR (spontaneous adventure) approaches have unique risk management methods. The guided tour minimizes the risk of missing out on iconic sites and controls costs. At the same time, the spontaneous adventure allows for more exploration and a greater chance of finding experiences that align with your desired outcomes. As with organizations, understanding which approach to take depends on how certain you are that the Project (guided tour) will deliver the desired outcome (enjoyment and enrichment). If the answer to the question, “Will the delivery of output for this Project be considered a success?” is yes, then stick with it being a Project, as it’s the better tool for output. If the answer is no, then you should ask what will. If the answer is some behavior change, you should craft an OKR around that goal.</p><p>To understand when to use one or the other, consider the following:</p><p>Projects are best for:</p><ul><li>“Cost of doing business” tasks (e.g., legal, security, regulatory compliance)</li><li>Business enablement tasks (e.g., infrastructure optimization, critical sales requests)</li><li>Hardening or scaling a capability (e.g., new product builds post successful product/market fit exploration)</li><li>Integration tasks (e.g., integrating a new capability)</li></ul><p>OKRs are best for:</p><ul><li>Improving effectiveness, impact, or experience of an organization, product, service, or process</li><li>Enhancing adoption or stickiness of a product, service, or process</li><li>Increasing customer or user base for a product or service</li><li>Boosting operational efficiency for an organization, product, service, or process</li></ul><p>In conclusion, don’t confuse either approach and don’t try and create a hybrid, as it won’t work. You can disguise a Workhorse (Project) with fairy wings and a party hat to resemble a Unicorn (OKR), but it isn’t one. It’s still a Workhorse. Both magnificent creatures are necessary for different reasons. Organizations should be outcome-oriented and, therefore, minimize Projects, utilizing them only when necessary as an exception, the rule being OKR. However, I hope I have demonstrated why we need both Workhorses (Projects) to power through tasks and Unicorns (OKRs) to inspire and motivate us to reach our goals and perform better. You can watch your organization soar by embracing both in their true forms!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef1020aa3bfd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>