<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet href="https://rss.buzzsprout.com/styles.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:podcast="https://podcastindex.org/namespace/1.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:psc="http://podlove.org/simple-chapters" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <atom:link href="https://feeds.buzzsprout.com/2322157.rss" rel="self" type="application/rss+xml" />
  <atom:link href="https://pubsubhubbub.appspot.com/" rel="hub" xmlns="http://www.w3.org/2005/Atom" />
  <title>Good intentions, bad outcomes</title>

  <lastBuildDate>Wed, 04 Mar 2026 20:47:28 -0500</lastBuildDate>
  <link>https://goodintentionsbadoutcomes.buzzsprout.com</link>
  <language>en-us</language>
  <copyright>© 2026 Good intentions, bad outcomes</copyright>
  <podcast:locked>yes</podcast:locked>
    <podcast:guid>19ee3683-cf84-5e92-87b2-0b23847fa34e</podcast:guid>
  <podcast:txt purpose="verify">feedback@goodintentionsbadoutcomes.org</podcast:txt>
<podcast:podroll>
    <podcast:remoteItem feedGuid="77d600b2-c09a-5ba3-87bb-c761285bc085" feedUrl="https://feeds.buzzsprout.com/1643821.rss" />
    <podcast:remoteItem feedGuid="5dd1cf80-b1f5-5efa-9208-fa907c818f48" feedUrl="https://feeds.buzzsprout.com/883858.rss" />
  </podcast:podroll>
  <itunes:author>Xodiac</itunes:author>
  <itunes:type>episodic</itunes:type>
  <itunes:explicit>false</itunes:explicit>
  <description><![CDATA[<p>A podcast about challenges and practices you might encounter in the workplace... things that were intended well, but have outcomes that aren't so great. In most cases, the organizations aren't even aware of how bad the outcomes are.<br><br>Every episode we discuss a situation that has something wrong with it: the what, the why and what can be done to address it.</p>]]></description>
  <generator>Buzzsprout (https://www.buzzsprout.com)</generator>
  <itunes:keywords>project management, smells, failures, risks, recovery</itunes:keywords>
  <itunes:owner>
    <itunes:name>Xodiac</itunes:name>
    <itunes:email>feedback@goodintentionsbadoutcomes.org</itunes:email>
  </itunes:owner>
  <image>
     <url>https://storage.buzzsprout.com/4p5seo30nscazriwh97auidtkbck?.jpg</url>
     <title>Good intentions, bad outcomes</title>
     <link></link>
  </image>
  <itunes:image href="https://storage.buzzsprout.com/4p5seo30nscazriwh97auidtkbck?.jpg" />
  <itunes:category text="Business" />
  <podcast:person role="host" href="https://www.linkedin.com/in/ginomarckx/" img="https://storage.buzzsprout.com/6kgj4y9g29uolf9sjjbnywxazvgs">Gino Marckx</podcast:person>
  <podcast:person role="host" href="https://www.linkedin.com/in/wayne-hetherington/" img="https://storage.buzzsprout.com/f4wb2tjo3uzj18nxipffva4qfxed">Wayne Hetherington</podcast:person>
  <item>
    <itunes:title>Local Optimization: Why Your Team&#39;s Success Might Be Slowing Down the Whole Company</itunes:title>
    <title>Local Optimization: Why Your Team&#39;s Success Might Be Slowing Down the Whole Company</title>
    <itunes:summary><![CDATA[Are your teams working harder and faster but nothing is getting to production quicker?  You might be falling into the local optimization trap. In this episode of Good Intentions and Outcomes, we explore how optimizing one part of your system can accidentally slow down the entire organization. Wayne shares real-world examples from software delivery teams, IT departments, and QA processes where good intentions led to unexpected bottlenecks.  🎯 What You'll Learn:  - What local opt...]]></itunes:summary>
    <description><![CDATA[<p>Are your teams working harder and faster but nothing is getting to production quicker? </p><p>You might be falling into the local optimization trap. In this episode of Good Intentions and Outcomes, we explore how optimizing one part of your system can accidentally slow down the entire organization. Wayne shares real-world examples from software delivery teams, IT departments, and QA processes where good intentions led to unexpected bottlenecks. </p><p>🎯 What You&apos;ll Learn: </p><p>- What local optimization is and why it happens </p><p>- Real examples of teams improving metrics while overall delivery slows </p><p>- The disconnect between deployment and release </p><p>- Why focusing on what&apos;s in front of you can blind you to bigger problems </p><p>- Practical techniques to see the whole system (value stream mapping, theory of constraints) </p><p>💡 Key Takeaway: </p><p>Sometimes you need to &quot;de-optimize&quot; one part to optimize the whole system.</p><p> Perfect for: Engineering managers, product owners, Agile coaches, DevOps teams, and anyone interested in systems thinking and organizational efficiency. </p><p>🔗 Have a workplace situation you&apos;d like us to discuss? Let us know in the comments!</p><p> #LocalOptimization #SystemsThinking #AgileTransformation #DevOps #SoftwareDelivery</p><p> ---</p><p> Good Intentions and Outcomes Podcast - Exploring workplace challenges where good intentions lead to unintended consequences.</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>Are your teams working harder and faster but nothing is getting to production quicker? </p><p>You might be falling into the local optimization trap. In this episode of Good Intentions and Outcomes, we explore how optimizing one part of your system can accidentally slow down the entire organization. Wayne shares real-world examples from software delivery teams, IT departments, and QA processes where good intentions led to unexpected bottlenecks. </p><p>🎯 What You&apos;ll Learn: </p><p>- What local optimization is and why it happens </p><p>- Real examples of teams improving metrics while overall delivery slows </p><p>- The disconnect between deployment and release </p><p>- Why focusing on what&apos;s in front of you can blind you to bigger problems </p><p>- Practical techniques to see the whole system (value stream mapping, theory of constraints) </p><p>💡 Key Takeaway: </p><p>Sometimes you need to &quot;de-optimize&quot; one part to optimize the whole system.</p><p> Perfect for: Engineering managers, product owners, Agile coaches, DevOps teams, and anyone interested in systems thinking and organizational efficiency. </p><p>🔗 Have a workplace situation you&apos;d like us to discuss? Let us know in the comments!</p><p> #LocalOptimization #SystemsThinking #AgileTransformation #DevOps #SoftwareDelivery</p><p> ---</p><p> Good Intentions and Outcomes Podcast - Exploring workplace challenges where good intentions lead to unintended consequences.</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/18243445-local-optimization-why-your-team-s-success-might-be-slowing-down-the-whole-company.mp3" length="11500774" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-18243445</guid>
    <pubDate>Tue, 25 Nov 2025 08:00:00 -0500</pubDate>
    <itunes:duration>954</itunes:duration>
    <itunes:keywords>local optimization, systems thinking, agile methodology, devops, software delivery, bottleneck analysis, theory of constraints, value stream mapping, organizational efficiency, lean software development, continuous delivery, deployment vs release, workpla</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>18</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>How Do We Actually Show Support as a Leader?</itunes:title>
    <title>How Do We Actually Show Support as a Leader?</title>
    <itunes:summary><![CDATA[Ever wondered if your well-intentioned presence as a leader might be undermining your team's autonomy? In this episode, Gino Marckx and Wayne Hetherington tackle one of the most common leadership challenges: how to show support without accidentally taking away your team's decision-making power.  🎯 KEY TOPICS: • Why leaders showing up to team meetings can backfire • The power differential effect and how it silences teams • How authority figures unintentionally anchor decisions • The hidden cos...]]></itunes:summary>
    <description><![CDATA[<p>Ever wondered if your well-intentioned presence as a leader might be undermining your team&apos;s autonomy? In this episode, Gino Marckx and Wayne Hetherington tackle one of the most common leadership challenges: how to show support without accidentally taking away your team&apos;s decision-making power.<br/><br/>🎯 KEY TOPICS:<br/>• Why leaders showing up to team meetings can backfire<br/>• The power differential effect and how it silences teams<br/>• How authority figures unintentionally anchor decisions<br/>• The hidden cost of &quot;just observing&quot;<br/>• Practical strategies for supporting without hovering<br/><br/>💡 MAIN TAKEAWAYS:<br/>✅ Stick to feedback-focused events (like sprint reviews)<br/>✅ Ask permission before attending planning sessions<br/>✅ Limit your presence - less is often more<br/>✅ Ask &quot;How can I help?&quot; instead of jumping in with answers<br/>✅ Use &quot;What would you do?&quot; to empower team decisions<br/>✅ Know when to give feedback and when to stay silent<br/><br/>⏱️ TIMESTAMPS:<br/>0:00 Introduction<br/>0:43 The Challenge: Well-Intentioned Leader Presence<br/>2:17 Why Leaders Want to Be Involved<br/>4:03 What Actually Happens When Leaders Show Up<br/>6:24 The Power Differential Effect<br/>7:26 How Autonomy Breaks Down<br/>9:02 Real Example: The Story Point Incident<br/>10:22 Having Difficult Conversations with Leaders<br/>11:53 Solutions: How to Support Without Overbearing<br/>13:14 Ask Permission, Don&apos;t Just Show Up<br/>14:50 The Power of &quot;How Can I Help?&quot;<br/>15:28 Resist the Urge to Fill the Silence<br/>16:12 Quick Summary<br/><br/>🎙️ ABOUT THIS PODCAST:<br/>Good Intentions and Outcomes explores workplace challenges where good intentions lead to unintended consequences. Hosts Gino Marckx and Wayne Hetherington discuss real situations, analyze what goes wrong, and provide practical alternatives on the spot.<br/><br/>#Leadership #TeamAutonomy #AgileLeadership #ScrumMaster #Management #WorkplaceCulture #TeamDynamics #LeadershipDevelopment #GoodIntentions #PodcastEpisode<br/><br/><br/></p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>Ever wondered if your well-intentioned presence as a leader might be undermining your team&apos;s autonomy? In this episode, Gino Marckx and Wayne Hetherington tackle one of the most common leadership challenges: how to show support without accidentally taking away your team&apos;s decision-making power.<br/><br/>🎯 KEY TOPICS:<br/>• Why leaders showing up to team meetings can backfire<br/>• The power differential effect and how it silences teams<br/>• How authority figures unintentionally anchor decisions<br/>• The hidden cost of &quot;just observing&quot;<br/>• Practical strategies for supporting without hovering<br/><br/>💡 MAIN TAKEAWAYS:<br/>✅ Stick to feedback-focused events (like sprint reviews)<br/>✅ Ask permission before attending planning sessions<br/>✅ Limit your presence - less is often more<br/>✅ Ask &quot;How can I help?&quot; instead of jumping in with answers<br/>✅ Use &quot;What would you do?&quot; to empower team decisions<br/>✅ Know when to give feedback and when to stay silent<br/><br/>⏱️ TIMESTAMPS:<br/>0:00 Introduction<br/>0:43 The Challenge: Well-Intentioned Leader Presence<br/>2:17 Why Leaders Want to Be Involved<br/>4:03 What Actually Happens When Leaders Show Up<br/>6:24 The Power Differential Effect<br/>7:26 How Autonomy Breaks Down<br/>9:02 Real Example: The Story Point Incident<br/>10:22 Having Difficult Conversations with Leaders<br/>11:53 Solutions: How to Support Without Overbearing<br/>13:14 Ask Permission, Don&apos;t Just Show Up<br/>14:50 The Power of &quot;How Can I Help?&quot;<br/>15:28 Resist the Urge to Fill the Silence<br/>16:12 Quick Summary<br/><br/>🎙️ ABOUT THIS PODCAST:<br/>Good Intentions and Outcomes explores workplace challenges where good intentions lead to unintended consequences. Hosts Gino Marckx and Wayne Hetherington discuss real situations, analyze what goes wrong, and provide practical alternatives on the spot.<br/><br/>#Leadership #TeamAutonomy #AgileLeadership #ScrumMaster #Management #WorkplaceCulture #TeamDynamics #LeadershipDevelopment #GoodIntentions #PodcastEpisode<br/><br/><br/></p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/18186331-how-do-we-actually-show-support-as-a-leader.mp3" length="12368693" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-18186331</guid>
    <pubDate>Thu, 13 Nov 2025 14:00:00 -0500</pubDate>
    <itunes:duration>1027</itunes:duration>
    <itunes:keywords>leadership, management, team dynamics, workplace culture, agile, coaching, team autonomy, organizational psychology, scrum, leadership development, servant leadership, team empowerment, power dynamics, micromanagement, agile coaching</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>17</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>The AWS Outage That Broke Half the Internet: Your Cloud Isn&#39;t as Safe as You Think</itunes:title>
    <title>The AWS Outage That Broke Half the Internet: Your Cloud Isn&#39;t as Safe as You Think</title>
    <itunes:summary><![CDATA[Ever moved to the cloud thinking you'd finally eliminate those dreaded outages? In this episode, Gino Marckx and Wayne Hetherington break down what happened when AWS went down and took half the world's services with it. The intent behind cloud migration is solid. Move off your own hardware, get better reliability, scale as needed, and never worry about infrastructure again. The cloud provider handles redundancy, right? Except when AWS goes down, so does everything running on it. You've just t...]]></itunes:summary>
    <description><![CDATA[<p>Ever moved to the cloud thinking you&apos;d finally eliminate those dreaded outages? In this episode, Gino Marckx and Wayne Hetherington break down what happened when AWS went down and took half the world&apos;s services with it.</p><p>The intent behind cloud migration is solid. Move off your own hardware, get better reliability, scale as needed, and never worry about infrastructure again. The cloud provider handles redundancy, right? Except when AWS goes down, so does everything running on it. You&apos;ve just traded one single point of failure for another.</p><p>We walk through why this keeps happening. Most organizations assume the cloud provider has built-in redundancy across regions and availability zones. And they do - within their own system. But if you&apos;re only on AWS, or only on Azure, or only on Google Cloud, you&apos;re still vulnerable when that one provider has issues.</p><p>The solution? Multi-cloud architecture. Spread your critical services across different providers. Yes, it costs more. Yes, it adds complexity. But if uptime actually matters for your business, it&apos;s the only real answer.</p><p>We also talk about when it&apos;s okay to accept the risk. A pet grooming appointment booking site can probably survive a few hours down per year. Medical services or air traffic control? That&apos;s a different calculation. It comes down to understanding how many nines of uptime you actually need and what you&apos;re willing to pay for it.</p><p><b>Timestamps:</b> </p><p>0:00 - Introduction </p><p>0:33 - AWS outage hits half the world </p><p>1:16 - Why organizations move to cloud in the first place </p><p>2:50 - The promise of always-available infrastructure </p><p>4:39 - So why did everything go down? </p><p>5:28 - You still have a single point of failure </p><p>6:25 - The assumption of built-in redundancy </p><p>7:21 - Building real backup plans across providers</p><p> 8:40 - How unlikely is a multi-cloud failure? </p><p>9:41 - The challenge of keeping environments consistent </p><p>10:58 - Cost vs. redundancy: the eternal tradeoff </p><p>11:34 - How many nines do you actually need? </p><p>12:39 - Making the right choice for your situation </p><p>13:24 - Wrap-up</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>Ever moved to the cloud thinking you&apos;d finally eliminate those dreaded outages? In this episode, Gino Marckx and Wayne Hetherington break down what happened when AWS went down and took half the world&apos;s services with it.</p><p>The intent behind cloud migration is solid. Move off your own hardware, get better reliability, scale as needed, and never worry about infrastructure again. The cloud provider handles redundancy, right? Except when AWS goes down, so does everything running on it. You&apos;ve just traded one single point of failure for another.</p><p>We walk through why this keeps happening. Most organizations assume the cloud provider has built-in redundancy across regions and availability zones. And they do - within their own system. But if you&apos;re only on AWS, or only on Azure, or only on Google Cloud, you&apos;re still vulnerable when that one provider has issues.</p><p>The solution? Multi-cloud architecture. Spread your critical services across different providers. Yes, it costs more. Yes, it adds complexity. But if uptime actually matters for your business, it&apos;s the only real answer.</p><p>We also talk about when it&apos;s okay to accept the risk. A pet grooming appointment booking site can probably survive a few hours down per year. Medical services or air traffic control? That&apos;s a different calculation. It comes down to understanding how many nines of uptime you actually need and what you&apos;re willing to pay for it.</p><p><b>Timestamps:</b> </p><p>0:00 - Introduction </p><p>0:33 - AWS outage hits half the world </p><p>1:16 - Why organizations move to cloud in the first place </p><p>2:50 - The promise of always-available infrastructure </p><p>4:39 - So why did everything go down? </p><p>5:28 - You still have a single point of failure </p><p>6:25 - The assumption of built-in redundancy </p><p>7:21 - Building real backup plans across providers</p><p> 8:40 - How unlikely is a multi-cloud failure? </p><p>9:41 - The challenge of keeping environments consistent </p><p>10:58 - Cost vs. redundancy: the eternal tradeoff </p><p>11:34 - How many nines do you actually need? </p><p>12:39 - Making the right choice for your situation </p><p>13:24 - Wrap-up</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/18045256-the-aws-outage-that-broke-half-the-internet-your-cloud-isn-t-as-safe-as-you-think.mp3" length="10264449" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-18045256</guid>
    <pubDate>Tue, 21 Oct 2025 07:00:00 -0400</pubDate>
    <itunes:duration>851</itunes:duration>
    <itunes:keywords>cloud migration, AWS outage, cloud infrastructure, DevOps, disaster recovery, multi-cloud strategy, IT management, system resilience, cloud architecture, service availability, digital transformation, workplace challenges, tech leadership</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>16</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>OKRs vs KPIs: Why Confusing Them Kills Your Goals</itunes:title>
    <title>OKRs vs KPIs: Why Confusing Them Kills Your Goals</title>
    <itunes:summary><![CDATA[Are KPIs Sabotaging Your OKRs? This Episode Will Change How You Measure Success Gino Marckx and Wayne Hetherington tackle the most common question from their OKR courses: "What's the difference between OKRs and KPIs?" The answer reveals why mixing them up is deflating your goals and confusing your teams. The Problem: Teams with good intentions want to measure progress, so they put KPIs into their OKRs. Everything's on one dashboard—efficient, right? Wrong. The Unintended Consequence: Using ma...]]></itunes:summary>
    <description><![CDATA[<p><b>Are KPIs Sabotaging Your OKRs? This Episode Will Change How You Measure Success</b></p><p>Gino Marckx and Wayne Hetherington tackle the most common question from their OKR courses: &quot;What&apos;s the difference between OKRs and KPIs?&quot; The answer reveals why mixing them up is deflating your goals and confusing your teams.</p><p><b>The Problem:</b> Teams with good intentions want to measure progress, so they put KPIs into their OKRs. Everything&apos;s on one dashboard—efficient, right? Wrong.</p><p><b>The Unintended Consequence:</b> Using maintenance metrics (KPIs) to track transformational goals (OKRs) turns ambitious objectives into ordinary tasks. Your GPS becomes a dashboard, and your team loses sight of where they&apos;re going.</p><p><b>Key Insights:</b></p><ul><li>OKRs are temporary and directional—they end when you reach your goal</li><li>KPIs are permanent system health monitors—they never stop</li><li>The same number can mean different things depending on why you&apos;re measuring it</li><li>KPIs don&apos;t enable autonomous decision-making toward future goals</li><li>Exception: Transform an unhealthy KPI into a temporary OKR when you need to fix it</li></ul><p>Wayne&apos;s car metaphor makes it click: Your GPS tells you where to turn (OKRs), your dashboard tells you to change the oil (KPIs). Both essential, completely different purposes.</p><p>Perfect for leaders struggling with goal-setting, team alignment, and making measurements that actually matter.</p><p><b>Got a workplace challenge where good intentions led to bad outcomes? Share it for a future episode!</b></p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p><b>Are KPIs Sabotaging Your OKRs? This Episode Will Change How You Measure Success</b></p><p>Gino Marckx and Wayne Hetherington tackle the most common question from their OKR courses: &quot;What&apos;s the difference between OKRs and KPIs?&quot; The answer reveals why mixing them up is deflating your goals and confusing your teams.</p><p><b>The Problem:</b> Teams with good intentions want to measure progress, so they put KPIs into their OKRs. Everything&apos;s on one dashboard—efficient, right? Wrong.</p><p><b>The Unintended Consequence:</b> Using maintenance metrics (KPIs) to track transformational goals (OKRs) turns ambitious objectives into ordinary tasks. Your GPS becomes a dashboard, and your team loses sight of where they&apos;re going.</p><p><b>Key Insights:</b></p><ul><li>OKRs are temporary and directional—they end when you reach your goal</li><li>KPIs are permanent system health monitors—they never stop</li><li>The same number can mean different things depending on why you&apos;re measuring it</li><li>KPIs don&apos;t enable autonomous decision-making toward future goals</li><li>Exception: Transform an unhealthy KPI into a temporary OKR when you need to fix it</li></ul><p>Wayne&apos;s car metaphor makes it click: Your GPS tells you where to turn (OKRs), your dashboard tells you to change the oil (KPIs). Both essential, completely different purposes.</p><p>Perfect for leaders struggling with goal-setting, team alignment, and making measurements that actually matter.</p><p><b>Got a workplace challenge where good intentions led to bad outcomes? Share it for a future episode!</b></p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/17886071-okrs-vs-kpis-why-confusing-them-kills-your-goals.mp3" length="10834897" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-17886071</guid>
    <pubDate>Tue, 07 Oct 2025 06:00:00 -0400</pubDate>
    <itunes:duration>899</itunes:duration>
    <itunes:keywords>OKRs vs KPIs, objectives and key results, key performance indicators, OKR framework, goal setting, business metrics, team alignment, performance management, agile metrics, organizational goals, KPI dashboard, OKR best practices, measurement strategy, busi</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>15</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>When CI/CD Pipelines Enable Bad Decisions</itunes:title>
    <title>When CI/CD Pipelines Enable Bad Decisions</title>
    <itunes:summary><![CDATA[What happens when your deployment pipeline consistently shows failing tests, but your team needs to keep shipping? In this episode, Gino and Wayne share a real-world example of how one organization created an "amber state" - where code compiles but tests fail, and treated it as "good enough" for deployment. Wayne and Gino explore the dangerous psychology behind this common workplace pattern: when feedback becomes untrustworthy, teams stop listening to it entirely. The result? Quality silently...]]></itunes:summary>
    <description><![CDATA[<p>What happens when your deployment pipeline consistently shows failing tests, but your team needs to keep shipping? In this episode, Gino and Wayne share a real-world example of how one organization created an &quot;amber state&quot; - where code compiles but tests fail, and treated it as &quot;good enough&quot; for deployment.</p><p>Wayne and Gino explore the dangerous psychology behind this common workplace pattern: when feedback becomes untrustworthy, teams stop listening to it entirely. The result? Quality silently erodes while everyone pretends the system is working.</p><p><br/><b>In this episode, we discuss:</b></p><ul><li>How the amber light anti-pattern destroys test discipline</li><li>Why &quot;defects vs bugs&quot; classifications create similar problems</li><li>The connection between failing CI/CD and &quot;almost done&quot; Kanban columns</li><li>When radical solutions (like deleting your entire test suite) make sense</li><li>How good intentions around &quot;unblocking&quot; teams lead to quality debt</li></ul><p>Timestamps:<br/>0:00 - The Amber Light Anti-Pattern Exposed </p><p>1:45 - Why 90% Failed Tests Became &quot;Good Enough&quot; </p><p>4:00 - The Hidden Psychology of Ignoring Quality </p><p>5:14 - Defects vs Bugs: Another Dangerous Distinction </p><p>6:41 - &quot;Almost Done&quot; Columns: The Kanban Version </p><p>8:21 - The Nuclear Option: Delete Your Tests</p><p><b>Key insight:</b> If you don&apos;t trust your feedback system enough to act on it, remove it entirely rather than work around it.</p><p>This is a shorter episode focusing on one powerful anti-pattern that many development teams will recognize. Whether you&apos;re dealing with flaky tests, unreliable builds, or teams that have learned to ignore quality signals, this conversation offers both diagnosis and cure.</p><p><br/><b>Got a workplace situation where good intentions led to bad outcomes?</b> We&apos;d love to hear about it for a future episode.</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>What happens when your deployment pipeline consistently shows failing tests, but your team needs to keep shipping? In this episode, Gino and Wayne share a real-world example of how one organization created an &quot;amber state&quot; - where code compiles but tests fail, and treated it as &quot;good enough&quot; for deployment.</p><p>Wayne and Gino explore the dangerous psychology behind this common workplace pattern: when feedback becomes untrustworthy, teams stop listening to it entirely. The result? Quality silently erodes while everyone pretends the system is working.</p><p><br/><b>In this episode, we discuss:</b></p><ul><li>How the amber light anti-pattern destroys test discipline</li><li>Why &quot;defects vs bugs&quot; classifications create similar problems</li><li>The connection between failing CI/CD and &quot;almost done&quot; Kanban columns</li><li>When radical solutions (like deleting your entire test suite) make sense</li><li>How good intentions around &quot;unblocking&quot; teams lead to quality debt</li></ul><p>Timestamps:<br/>0:00 - The Amber Light Anti-Pattern Exposed </p><p>1:45 - Why 90% Failed Tests Became &quot;Good Enough&quot; </p><p>4:00 - The Hidden Psychology of Ignoring Quality </p><p>5:14 - Defects vs Bugs: Another Dangerous Distinction </p><p>6:41 - &quot;Almost Done&quot; Columns: The Kanban Version </p><p>8:21 - The Nuclear Option: Delete Your Tests</p><p><b>Key insight:</b> If you don&apos;t trust your feedback system enough to act on it, remove it entirely rather than work around it.</p><p>This is a shorter episode focusing on one powerful anti-pattern that many development teams will recognize. Whether you&apos;re dealing with flaky tests, unreliable builds, or teams that have learned to ignore quality signals, this conversation offers both diagnosis and cure.</p><p><br/><b>Got a workplace situation where good intentions led to bad outcomes?</b> We&apos;d love to hear about it for a future episode.</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/17886067-when-ci-cd-pipelines-enable-bad-decisions.mp3" length="7538437" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-17886067</guid>
    <pubDate>Tue, 23 Sep 2025 07:00:00 -0400</pubDate>
    <podcast:transcript url="https://www.buzzsprout.com/2322157/17886067/transcript" type="text/html" />
    <itunes:duration>624</itunes:duration>
    <itunes:keywords>SoftwareDevelopment, CICD, DevOps, SoftwareQuality, TestingStrategy, AgileDevelopment, TechnicalDebt, SoftwareEngineering, QualityAssurance, BuildPipeline, AutomatedTesting, DeploymentPipeline, ScrumAntiPatterns, KanbanBoard, WorkplaceChallenges</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>16</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>Why &quot;Protecting&quot; Your Team Actually Hurts Delivery (The Isolation Trap)</itunes:title>
    <title>Why &quot;Protecting&quot; Your Team Actually Hurts Delivery (The Isolation Trap)</title>
    <itunes:summary><![CDATA[Think shielding your team from distractions helps them focus? You might be creating a bigger problem.  In this episode, Gino and Wayne tackle one of the most common workplace traps: the well-meaning manager who "protects" their team by cutting them off from external input. What starts as good intentions - giving teams space to focus - often ends with teams building the wrong thing entirely.  They share real examples of teams that became so isolated they lost context, missed critical dependenc...]]></itunes:summary>
    <description><![CDATA[<p>Think shielding your team from distractions helps them focus? You might be creating a bigger problem.<br/><br/>In this episode, Gino and Wayne tackle one of the most common workplace traps: the well-meaning manager who &quot;protects&quot; their team by cutting them off from external input. What starts as good intentions - giving teams space to focus - often ends with teams building the wrong thing entirely.<br/><br/>They share real examples of teams that became so isolated they lost context, missed critical dependencies, and delivered work that other teams couldn&apos;t actually use. The result? Longer delivery timelines and frustrated stakeholders - exactly what the protection was supposed to prevent.<br/><br/>The Real Problem:<br/>When teams get isolated, they stop being part of the bigger picture. They lose the feedback loops that keep them aligned with what actually needs to be built.<br/>What Works Instead:<br/><br/>Set up controlled feedback sessions instead of complete isolation<br/>Use Scrum ceremonies strategically for stakeholder input<br/>Create &quot;office hours&quot; for team availability<br/>Implement communication boards for non-urgent questions<br/>Remember that focus doesn&apos;t mean disconnection<br/><br/>Bottom Line: Teams need focus, not isolation. The goal is managing distractions, not eliminating all outside contact.<br/><br/>Timestamps:<br/>0:00 - Introduction<br/>0:35 - The &quot;Team Protection&quot; Problem<br/>1:17 - Why Managers Try to Shield Teams<br/>2:13 - When Good Intentions Go Wrong<br/>3:33 - Better Ways to Handle Distractions<br/>5:00 - Using Scrum for Controlled Feedback<br/>6:32 - Office Hours and Communication Systems<br/>8:05 - Keeping Teams Connected to the Big Picture<br/>10:18 - Avoiding the &quot;Special Project&quot; Mentality<br/>11:05 - Managing Emergency Work Without Chaos<br/><br/>About Good Intentions, Bad Outcomes:<br/>A podcast about workplace challenges where good intentions create unintended consequences. Hosted by Gino Marckx and Wayne Hetherington.</p><p><br/>#TeamManagement #Agile #ScrumMaster #Leadership #ProjectManagement #WorkplaceCollaboration</p><p><br/>Subscribe for more insights on avoiding common workplace traps.</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>Think shielding your team from distractions helps them focus? You might be creating a bigger problem.<br/><br/>In this episode, Gino and Wayne tackle one of the most common workplace traps: the well-meaning manager who &quot;protects&quot; their team by cutting them off from external input. What starts as good intentions - giving teams space to focus - often ends with teams building the wrong thing entirely.<br/><br/>They share real examples of teams that became so isolated they lost context, missed critical dependencies, and delivered work that other teams couldn&apos;t actually use. The result? Longer delivery timelines and frustrated stakeholders - exactly what the protection was supposed to prevent.<br/><br/>The Real Problem:<br/>When teams get isolated, they stop being part of the bigger picture. They lose the feedback loops that keep them aligned with what actually needs to be built.<br/>What Works Instead:<br/><br/>Set up controlled feedback sessions instead of complete isolation<br/>Use Scrum ceremonies strategically for stakeholder input<br/>Create &quot;office hours&quot; for team availability<br/>Implement communication boards for non-urgent questions<br/>Remember that focus doesn&apos;t mean disconnection<br/><br/>Bottom Line: Teams need focus, not isolation. The goal is managing distractions, not eliminating all outside contact.<br/><br/>Timestamps:<br/>0:00 - Introduction<br/>0:35 - The &quot;Team Protection&quot; Problem<br/>1:17 - Why Managers Try to Shield Teams<br/>2:13 - When Good Intentions Go Wrong<br/>3:33 - Better Ways to Handle Distractions<br/>5:00 - Using Scrum for Controlled Feedback<br/>6:32 - Office Hours and Communication Systems<br/>8:05 - Keeping Teams Connected to the Big Picture<br/>10:18 - Avoiding the &quot;Special Project&quot; Mentality<br/>11:05 - Managing Emergency Work Without Chaos<br/><br/>About Good Intentions, Bad Outcomes:<br/>A podcast about workplace challenges where good intentions create unintended consequences. Hosted by Gino Marckx and Wayne Hetherington.</p><p><br/>#TeamManagement #Agile #ScrumMaster #Leadership #ProjectManagement #WorkplaceCollaboration</p><p><br/>Subscribe for more insights on avoiding common workplace traps.</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/17736618-why-protecting-your-team-actually-hurts-delivery-the-isolation-trap.mp3" length="8984218" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-17736618</guid>
    <pubDate>Tue, 09 Sep 2025 06:00:00 -0400</pubDate>
    <itunes:duration>744</itunes:duration>
    <itunes:keywords></itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>15</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>Why Handing Teams OKRs Kills Motivation (And What to Do Instead)</itunes:title>
    <title>Why Handing Teams OKRs Kills Motivation (And What to Do Instead)</title>
    <itunes:summary><![CDATA[Ever wondered why your team isn't hitting those carefully crafted OKRs? You might be making the same mistake most leaders make - turning a powerful alignment tool into a top-down directive.  In this episode of Good Intentions, Bad Outcomes, Gino and Wayne break down why handing pre-made objectives to teams backfires, even when your intentions are good. They compare it to giving someone else's estimate and expecting accountability - spoiler alert: it doesn't work. What You'll Learn:  Why teams...]]></itunes:summary>
    <description><![CDATA[<p>Ever wondered why your team isn&apos;t hitting those carefully crafted OKRs? You might be making the same mistake most leaders make - turning a powerful alignment tool into a top-down directive.<br/><br/>In this episode of Good Intentions, Bad Outcomes, Gino and Wayne break down why handing pre-made objectives to teams backfires, even when your intentions are good. They compare it to giving someone else&apos;s estimate and expecting accountability - spoiler alert: it doesn&apos;t work.<br/>What You&apos;ll Learn:<br/><br/>Why teams lose ownership when goals are handed to them<br/>The difference between goal-setting and alignment tools<br/>How to turn OKRs into powerful negotiations instead of mandates<br/>Why the person setting the goal matters more than the goal itself<br/><br/>Key Takeaway: OKRs work best when teams help create them, not when they&apos;re told to follow them. It&apos;s the difference between &quot;your goal&quot; and &quot;my goal that you need to hit.&quot;<br/><br/>Timestamps:<br/>0:00 - Introduction<br/>0:38 - The Problem: Handing Teams Pre-Made OKRs<br/>2:00 - Why This Approach Fails<br/>4:32 - How OKRs Should Actually Work<br/>5:37 - OKRs as Alignment Tools, Not Just Goal Setting<br/>7:16 - The Power of Negotiation in Goal Setting<br/>8:28 - Ownership vs. Accountability<br/>9:33 - Real-World Example: Sports Team Management<br/>10:15 - Wrap-up<br/><br/>Got a workplace situation where good intentions led to bad outcomes? We&apos;d love to hear about it for a future episode!<br/><br/>About Good Intentions, Bad Outcomes:<br/>A podcast exploring workplace challenges where well-meaning practices create unintended consequences. Hosted by Gino Marckx and Wayne Hetherington.<br/><br/>#OKRs #Leadership #TeamManagement #GoalSetting #WorkplaceCulture #Management #BusinessStrategy<br/><br/>Like this content? Subscribe for more insights on turning good intentions into great outcomes.</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>Ever wondered why your team isn&apos;t hitting those carefully crafted OKRs? You might be making the same mistake most leaders make - turning a powerful alignment tool into a top-down directive.<br/><br/>In this episode of Good Intentions, Bad Outcomes, Gino and Wayne break down why handing pre-made objectives to teams backfires, even when your intentions are good. They compare it to giving someone else&apos;s estimate and expecting accountability - spoiler alert: it doesn&apos;t work.<br/>What You&apos;ll Learn:<br/><br/>Why teams lose ownership when goals are handed to them<br/>The difference between goal-setting and alignment tools<br/>How to turn OKRs into powerful negotiations instead of mandates<br/>Why the person setting the goal matters more than the goal itself<br/><br/>Key Takeaway: OKRs work best when teams help create them, not when they&apos;re told to follow them. It&apos;s the difference between &quot;your goal&quot; and &quot;my goal that you need to hit.&quot;<br/><br/>Timestamps:<br/>0:00 - Introduction<br/>0:38 - The Problem: Handing Teams Pre-Made OKRs<br/>2:00 - Why This Approach Fails<br/>4:32 - How OKRs Should Actually Work<br/>5:37 - OKRs as Alignment Tools, Not Just Goal Setting<br/>7:16 - The Power of Negotiation in Goal Setting<br/>8:28 - Ownership vs. Accountability<br/>9:33 - Real-World Example: Sports Team Management<br/>10:15 - Wrap-up<br/><br/>Got a workplace situation where good intentions led to bad outcomes? We&apos;d love to hear about it for a future episode!<br/><br/>About Good Intentions, Bad Outcomes:<br/>A podcast exploring workplace challenges where well-meaning practices create unintended consequences. Hosted by Gino Marckx and Wayne Hetherington.<br/><br/>#OKRs #Leadership #TeamManagement #GoalSetting #WorkplaceCulture #Management #BusinessStrategy<br/><br/>Like this content? Subscribe for more insights on turning good intentions into great outcomes.</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/17736558-why-handing-teams-okrs-kills-motivation-and-what-to-do-instead.mp3" length="7879224" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-17736558</guid>
    <pubDate>Wed, 27 Aug 2025 07:00:00 -0400</pubDate>
    <itunes:duration>652</itunes:duration>
    <itunes:keywords>OKRs, Leadership, Team Management, Goal Setting, Team Motivation, Objectives and Key Results, Workplace Culture, Management Tips, Team Ownership, Business Strategy, Employee Engagement, How to use OKRs correctly, OKR implementation, Team accountability</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>14</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>When Good Metrics Go Bad: The Hidden Dangers of Performance Targets</itunes:title>
    <title>When Good Metrics Go Bad: The Hidden Dangers of Performance Targets</title>
    <itunes:summary><![CDATA[HR departments everywhere are implementing performance targets with the best intentions: helping employees grow and driving company success. But what happens when these well-meaning metrics actually backfire? In this episode, Gino and Wayne unpack a common workplace scenario where measuring "projects completed" leads to reduced collaboration, short-term thinking, and gaming the system. They explore the psychology behind Goodhart's Law ("when a measure becomes a target, it ceases to be a good ...]]></itunes:summary>
    <description><![CDATA[<p>HR departments everywhere are implementing performance targets with the best intentions: helping employees grow and driving company success. But what happens when these well-meaning metrics actually backfire?</p><p>In this episode, Gino and Wayne unpack a common workplace scenario where measuring &quot;projects completed&quot; leads to reduced collaboration, short-term thinking, and gaming the system. They explore the psychology behind Goodhart&apos;s Law (&quot;when a measure becomes a target, it ceases to be a good measure&quot;) and share real-world examples of metrics gone wrong.</p><p><b>You&apos;ll discover:</b></p><ul><li>Why traditional project completion metrics can harm team dynamics</li><li>How performance targets psychologically change employee behavior</li><li>Two striking examples of well-intentioned metrics creating perverse incentives</li><li>Alternative approaches focusing on employee engagement and organizational alignment</li><li>The role of OKRs in setting direction without micromanaging actions</li><li>Why annual performance reviews might be counterproductive</li></ul><p><b>Key Insights:</b></p><ul><li>The difference between measuring for information vs. measuring for targets</li><li>How financial incentives tied to metrics amplify problematic behaviors</li><li>Why HR should focus on creating healthy workplaces rather than counting projects</li><li>The importance of aligning individual growth with organizational outcomes</li></ul><p>Whether you&apos;re in HR, management, or simply interested in workplace dynamics, this episode offers practical wisdom for creating performance systems that actually work.</p><p>H<em>ave a workplace situation with unintended consequences? Share it with us and we might feature it in a future episode!</em></p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>HR departments everywhere are implementing performance targets with the best intentions: helping employees grow and driving company success. But what happens when these well-meaning metrics actually backfire?</p><p>In this episode, Gino and Wayne unpack a common workplace scenario where measuring &quot;projects completed&quot; leads to reduced collaboration, short-term thinking, and gaming the system. They explore the psychology behind Goodhart&apos;s Law (&quot;when a measure becomes a target, it ceases to be a good measure&quot;) and share real-world examples of metrics gone wrong.</p><p><b>You&apos;ll discover:</b></p><ul><li>Why traditional project completion metrics can harm team dynamics</li><li>How performance targets psychologically change employee behavior</li><li>Two striking examples of well-intentioned metrics creating perverse incentives</li><li>Alternative approaches focusing on employee engagement and organizational alignment</li><li>The role of OKRs in setting direction without micromanaging actions</li><li>Why annual performance reviews might be counterproductive</li></ul><p><b>Key Insights:</b></p><ul><li>The difference between measuring for information vs. measuring for targets</li><li>How financial incentives tied to metrics amplify problematic behaviors</li><li>Why HR should focus on creating healthy workplaces rather than counting projects</li><li>The importance of aligning individual growth with organizational outcomes</li></ul><p>Whether you&apos;re in HR, management, or simply interested in workplace dynamics, this episode offers practical wisdom for creating performance systems that actually work.</p><p>H<em>ave a workplace situation with unintended consequences? Share it with us and we might feature it in a future episode!</em></p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/17588668-when-good-metrics-go-bad-the-hidden-dangers-of-performance-targets.mp3" length="11217052" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-17588668</guid>
    <pubDate>Tue, 05 Aug 2025 10:00:00 -0400</pubDate>
    <itunes:duration>931</itunes:duration>
    <itunes:keywords>HR, performance management, workplace culture, employee engagement, metrics, targets, Goodhart&#39;s Law, OKRs, leadership, management, workplace psychology, performance reviews, employee development, organizational behavior, business strategy, team collabora</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>13</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>Why &quot;Perfect&quot; Products Take Forever to Ship</itunes:title>
    <title>Why &quot;Perfect&quot; Products Take Forever to Ship</title>
    <itunes:summary><![CDATA[In this episode, Gino and Wayne explore one of the most common traps in product development: the pursuit of perfection that actually prevents you from delivering great products. We discuss why waiting for the "perfect" product can take 2-3 years and still fail in production, share a real case study of a project that took 2 years to build but needed 6 more months to actually work, and explore how different companies handle the perfection vs. speed dilemma. Key topics include: The perfectionism...]]></itunes:summary>
    <description><![CDATA[<p>In this episode, Gino and Wayne explore one of the most common traps in product development: the pursuit of perfection that actually prevents you from delivering great products.</p><p>We discuss why waiting for the &quot;perfect&quot; product can take 2-3 years and still fail in production, share a real case study of a project that took 2 years to build but needed 6 more months to actually work, and explore how different companies handle the perfection vs. speed dilemma.</p><p>Key topics include:</p><ul><li>The perfectionism trap and elongated delivery times</li><li>Apple vs. startup approaches to product perfection</li><li>Customer segmentation strategies for faster releases</li><li>Feature toggles and controlled rollouts</li><li>Why production validation trumps test environment success</li><li>Multidimensional planning: dirt road vs. highway implementations</li><li>A fascinating airport dropdown case study that reveals unexpected user behavior</li></ul><p>The counterintuitive insight: If you want to make a perfect product, go to your client with an imperfect product first.</p><p>Ideal for product managers, developers, startup founders, and anyone involved in product development who wants to ship faster without sacrificing quality.</p><p>Have a workplace situation with unintended bad outcomes? Share it with us for a future episode!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>In this episode, Gino and Wayne explore one of the most common traps in product development: the pursuit of perfection that actually prevents you from delivering great products.</p><p>We discuss why waiting for the &quot;perfect&quot; product can take 2-3 years and still fail in production, share a real case study of a project that took 2 years to build but needed 6 more months to actually work, and explore how different companies handle the perfection vs. speed dilemma.</p><p>Key topics include:</p><ul><li>The perfectionism trap and elongated delivery times</li><li>Apple vs. startup approaches to product perfection</li><li>Customer segmentation strategies for faster releases</li><li>Feature toggles and controlled rollouts</li><li>Why production validation trumps test environment success</li><li>Multidimensional planning: dirt road vs. highway implementations</li><li>A fascinating airport dropdown case study that reveals unexpected user behavior</li></ul><p>The counterintuitive insight: If you want to make a perfect product, go to your client with an imperfect product first.</p><p>Ideal for product managers, developers, startup founders, and anyone involved in product development who wants to ship faster without sacrificing quality.</p><p>Have a workplace situation with unintended bad outcomes? Share it with us for a future episode!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/17516782-why-perfect-products-take-forever-to-ship.mp3" length="13400319" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-17516782</guid>
    <pubDate>Tue, 22 Jul 2025 10:00:00 -0400</pubDate>
    <podcast:transcript url="https://www.buzzsprout.com/2322157/17516782/transcript" type="text/html" />
    <itunes:duration>1112</itunes:duration>
    <itunes:keywords>product development, perfectionism, MVP, minimum viable product, product management, startups, software development, agile development, customer feedback, product launch, feature development, workplace challenges, business strategy, product strategy, inno</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>12</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>Too Many Daily Stand-ups? Here&#39;s How to Fix Meeting Overload</itunes:title>
    <title>Too Many Daily Stand-ups? Here&#39;s How to Fix Meeting Overload</title>
    <itunes:summary><![CDATA[In this episode of Good Intentions and Bad Outcomes, Gino and Wayne explore how the well-meaning practice of daily stand-ups can become overwhelming when individuals are expected to attend multiple stand-ups across different teams.  TIMESTAMPS:  0:00 Introduction  0:33 Today's problem: attending too many daily stand-ups  1:06 When expert contributors spread themselves too thin  1:23 The good intentions behind wanting to stay involved  2:15 Why too many meetings can dr...]]></itunes:summary>
    <description><![CDATA[<p>In this episode of Good Intentions and Bad Outcomes, Gino and Wayne explore how the well-meaning practice of daily stand-ups can become overwhelming when individuals are expected to attend multiple stand-ups across different teams.<br/><br/>TIMESTAMPS:<br/> 0:00 Introduction<br/> 0:33 Today&apos;s problem: attending too many daily stand-ups<br/> 1:06 When expert contributors spread themselves too thin<br/> 1:23 The good intentions behind wanting to stay involved<br/> 2:15 Why too many meetings can drain productivity<br/> 2:39 A different lens on a recurring issue<br/> 2:58 Balancing collaboration with individual capacity<br/> 3:28 Refocusing on the intention: communication<br/> 4:14 Solution 1: Back-to-back scheduling to preserve deep work<br/> 4:49 Solution 2: Supplier-team model for shared work<br/> 5:31 Solution 3: Scrum of scrums or cross-team sync<br/> 6:05 Solution 4: Joint planning and reviews for cross-team clarity<br/> 6:44 Solution 5: Rotating representatives between teams<br/> 7:10 Solution 6: Weekly cross-team progress alignments<br/> 8:13 Making information sharing efficient and intentional<br/> 8:52 Closing thoughts on time-conscious communication<br/> 9:28 Don&apos;t follow the playbook—do what makes sense<br/> 9:45 Wrap-up and invitation for listener stories<br/><br/>Gino and Wayne tackle a challenge common in many agile environments: when people contribute to multiple teams and end up drowning in stand-up meetings. What starts as a simple communication tool turns into a calendar nightmare where no time is left for actual work.<br/><br/>In this episode, they explore alternatives that preserve the value of daily coordination while respecting people’s time, such as:<br/>Organizing back-to-back meetings to protect blocks of focus time<br/>Shifting to a supplier relationship for shared work<br/>Implementing scrum-of-scrums or other cross-team alignment practices<br/>Holding joint sprint planning and reviews to reduce duplicate discussions<br/>Rotating team representatives to maintain connection without overload<br/>Setting up weekly cross-team check-ins to keep things aligned<br/><br/>If your calendar ever made you think &quot;When am I supposed to actually do the work?&quot; you’ll relate to this one.<br/><br/>Got your own workplace story where a good idea had unintended consequences? Drop us a line and it might be featured in a future episode!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>In this episode of Good Intentions and Bad Outcomes, Gino and Wayne explore how the well-meaning practice of daily stand-ups can become overwhelming when individuals are expected to attend multiple stand-ups across different teams.<br/><br/>TIMESTAMPS:<br/> 0:00 Introduction<br/> 0:33 Today&apos;s problem: attending too many daily stand-ups<br/> 1:06 When expert contributors spread themselves too thin<br/> 1:23 The good intentions behind wanting to stay involved<br/> 2:15 Why too many meetings can drain productivity<br/> 2:39 A different lens on a recurring issue<br/> 2:58 Balancing collaboration with individual capacity<br/> 3:28 Refocusing on the intention: communication<br/> 4:14 Solution 1: Back-to-back scheduling to preserve deep work<br/> 4:49 Solution 2: Supplier-team model for shared work<br/> 5:31 Solution 3: Scrum of scrums or cross-team sync<br/> 6:05 Solution 4: Joint planning and reviews for cross-team clarity<br/> 6:44 Solution 5: Rotating representatives between teams<br/> 7:10 Solution 6: Weekly cross-team progress alignments<br/> 8:13 Making information sharing efficient and intentional<br/> 8:52 Closing thoughts on time-conscious communication<br/> 9:28 Don&apos;t follow the playbook—do what makes sense<br/> 9:45 Wrap-up and invitation for listener stories<br/><br/>Gino and Wayne tackle a challenge common in many agile environments: when people contribute to multiple teams and end up drowning in stand-up meetings. What starts as a simple communication tool turns into a calendar nightmare where no time is left for actual work.<br/><br/>In this episode, they explore alternatives that preserve the value of daily coordination while respecting people’s time, such as:<br/>Organizing back-to-back meetings to protect blocks of focus time<br/>Shifting to a supplier relationship for shared work<br/>Implementing scrum-of-scrums or other cross-team alignment practices<br/>Holding joint sprint planning and reviews to reduce duplicate discussions<br/>Rotating team representatives to maintain connection without overload<br/>Setting up weekly cross-team check-ins to keep things aligned<br/><br/>If your calendar ever made you think &quot;When am I supposed to actually do the work?&quot; you’ll relate to this one.<br/><br/>Got your own workplace story where a good idea had unintended consequences? Drop us a line and it might be featured in a future episode!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/17445478-too-many-daily-stand-ups-here-s-how-to-fix-meeting-overload.mp3" length="9464431" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-17445478</guid>
    <pubDate>Tue, 08 Jul 2025 08:00:00 -0400</pubDate>
    <itunes:duration>785</itunes:duration>
    <itunes:keywords>daily standup,scrum meetings,meeting overload,agile methodology,productivity tips,time management,workplace efficiency,team communication,scrum master,agile coaching,cross-team collaboration,meeting fatigue,calendar management,remote work,distributed team</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>11</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>Why Your Retrospectives Keep Failing</itunes:title>
    <title>Why Your Retrospectives Keep Failing</title>
    <itunes:summary><![CDATA[In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how retrospectives and other well-meaning workplace meetings can lose their effectiveness when teams fail to follow through on their commitments.  TIMESTAMPS: 0:00 – Introduction 0:41 – The recurring problem: repeated retrospective action items 1:17 – Why retrospectives should work 1:56 – The danger of unresolved improvements 2:11 – When meetings turn into time-wasters 2:48 – External feedback loops that go nowh...]]></itunes:summary>
    <description><![CDATA[<p>In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how retrospectives and other well-meaning workplace meetings can lose their effectiveness when teams fail to follow through on their commitments.<br/><br/>TIMESTAMPS:<br/>0:00 – Introduction<br/>0:41 – The recurring problem: repeated retrospective action items<br/>1:17 – Why retrospectives should work<br/>1:56 – The danger of unresolved improvements<br/>2:11 – When meetings turn into time-wasters<br/>2:48 – External feedback loops that go nowhere<br/>3:26 – Gino’s first solution: Commit to just one action<br/>4:38 – Wayne’s addition: Don’t bite off more than you can chew<br/>5:47 – Define “done”: Set clear acceptance criteria<br/>6:46 – Agreeing on outcomes before the meeting ends<br/>7:13 – Example from product backlog planning with clients<br/>8:14 – Stakeholder feedback without clear results<br/>8:55 – How to make feedback loops visible<br/>9:23 – Respecting participants’ time and contributions<br/>10:02 – Similar breakdowns in stand-ups and planning meetings<br/>10:49 – Summary: Clarity, accountability, and closing the loop<br/>11:27 – Netflix quote: 2 essential questions to ask after every meeting<br/>12:15 – Closing thoughts + invite for listener stories<br/><br/>Gino and Wayne dive into a common agile trap: teams holding retrospectives and other recurring meetings with good intentions, but making the same commitments week after week without real change. They discuss how this pattern can frustrate teams, disengage stakeholders, and eventually lead to cancelled meetings or worse: teams that stop believing in improvement.<br/><br/>Drawing from real-world examples, they offer practical strategies including:<br/>Committing to just one improvement at a time<br/>Breaking big problems into smaller, doable chunks<br/>Defining “done” with clear acceptance criteria<br/>Making progress visible to internal teams and external stakeholders<br/>Asking two powerful questions after every meeting<br/><br/>If you’ve ever sat in a meeting thinking &quot;Haven’t we talked about this before?&quot; this episode is for you.<br/><br/>Got your own story of good intentions that led to bad outcomes? Share it in the comments or reach out to be featured in an upcoming episode!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how retrospectives and other well-meaning workplace meetings can lose their effectiveness when teams fail to follow through on their commitments.<br/><br/>TIMESTAMPS:<br/>0:00 – Introduction<br/>0:41 – The recurring problem: repeated retrospective action items<br/>1:17 – Why retrospectives should work<br/>1:56 – The danger of unresolved improvements<br/>2:11 – When meetings turn into time-wasters<br/>2:48 – External feedback loops that go nowhere<br/>3:26 – Gino’s first solution: Commit to just one action<br/>4:38 – Wayne’s addition: Don’t bite off more than you can chew<br/>5:47 – Define “done”: Set clear acceptance criteria<br/>6:46 – Agreeing on outcomes before the meeting ends<br/>7:13 – Example from product backlog planning with clients<br/>8:14 – Stakeholder feedback without clear results<br/>8:55 – How to make feedback loops visible<br/>9:23 – Respecting participants’ time and contributions<br/>10:02 – Similar breakdowns in stand-ups and planning meetings<br/>10:49 – Summary: Clarity, accountability, and closing the loop<br/>11:27 – Netflix quote: 2 essential questions to ask after every meeting<br/>12:15 – Closing thoughts + invite for listener stories<br/><br/>Gino and Wayne dive into a common agile trap: teams holding retrospectives and other recurring meetings with good intentions, but making the same commitments week after week without real change. They discuss how this pattern can frustrate teams, disengage stakeholders, and eventually lead to cancelled meetings or worse: teams that stop believing in improvement.<br/><br/>Drawing from real-world examples, they offer practical strategies including:<br/>Committing to just one improvement at a time<br/>Breaking big problems into smaller, doable chunks<br/>Defining “done” with clear acceptance criteria<br/>Making progress visible to internal teams and external stakeholders<br/>Asking two powerful questions after every meeting<br/><br/>If you’ve ever sat in a meeting thinking &quot;Haven’t we talked about this before?&quot; this episode is for you.<br/><br/>Got your own story of good intentions that led to bad outcomes? Share it in the comments or reach out to be featured in an upcoming episode!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/17445472-why-your-retrospectives-keep-failing.mp3" length="7520246" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-17445472</guid>
    <pubDate>Thu, 03 Jul 2025 14:00:00 -0400</pubDate>
    <itunes:duration>622</itunes:duration>
    <itunes:keywords>agile,retrospectives,scrum,team meetings,workplace productivity,project management,software development,agile coaching,team improvement,meeting effectiveness,agile methodology,sprint retrospective,team dysfunction,workplace culture,continuous improvement,</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>10</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>Progress Report Perils: When Updates Become Obstacles</itunes:title>
    <title>Progress Report Perils: When Updates Become Obstacles</title>
    <itunes:summary><![CDATA[In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how weekly progress reports, while intended to create transparency and visibility, can sometimes become counterproductive time sinks that actually impede progress.  TIMESTAMPS: 0:00 - Introduction 0:37 - Gino introduces the topic of weekly progress reports 0:57 - The good intentions behind progress reports 1:41 - Wayne's winter frustrations (and progress report frustrations) 2:16 - The perceived benefits of prog...]]></itunes:summary>
    <description><![CDATA[<p>In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how weekly progress reports, while intended to create transparency and visibility, can sometimes become counterproductive time sinks that actually impede progress.<br/><br/>TIMESTAMPS:<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0'>0:00</a> - Introduction<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=37s'>0:37</a> - Gino introduces the topic of weekly progress reports<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=57s'>0:57</a> - The good intentions behind progress reports<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=101s'>1:41</a> - Wayne&apos;s winter frustrations (and progress report frustrations)<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=136s'>2:16</a> - The perceived benefits of progress reporting<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=185s'>3:05</a> - When progress reports go wrong: excessive time consumption<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=254s'>4:14</a> - Real-life example: Creating multiple reports for different managers<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=344s'>5:44</a> - The false sense of control from color-coded status reports<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=423s'>7:03</a> - The &quot;illusion of control&quot; problem<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=460s'>7:40</a> - When progress reports aren&apos;t even read by management<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=562s'>9:22</a> - Solution 1: Keep progress tracking but make it efficient<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=631s'>10:31</a> - Solution 2: Create meaningful feedback loops<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=674s'>11:14</a> - Solution 3: Set strict time limits for report creation<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=695s'>11:35</a> - Solution 4: Write the planned progress at the beginning of the week<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=734s'>12:14</a> - Solution 5: Use a publish-subscribe model for reporting<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=782s'>13:02</a> - Solution 6: Leverage existing tools like Jira for real-time visibility<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=857s'>14:17</a> - Focus on communicating what really matters<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=932s'>15:32</a> - Conclusion and invitation for listener stories<br/><br/>Gino and Wayne discuss how weekly progress reports, while intended to provide visibility into team progress and challenges, often become elaborate time-consuming processes that actually hinder productivity. They share real experiences of spending up to 50% of work time creating redundant reports for different managers, dealing with reports that aren&apos;t actually read, and seeing how color-coded status indicators can create a false sense of control.<br/><br/>The hosts offer practical alternatives including:</p><ul><li>Setting strict time limits on report creation (max 10 minutes)</li><li>Creating the progress report structure at the beginning of the week</li><li>Implementing a publish-subscribe model where teams publish once and managers subscribe</li><li>Using existing tools like Jira to create real-time progress dashboards</li><li>Focusing on communicating blockers and help needed, not just completed tasks</li><li>Creating short, fast, easy, and actually useful reporting mechanisms<br/><br/></li></ul><p>If you&apos;ve experienced situations where well-intended workplace processes have backfired, share your story for a chance to be featured in an upcoming episode!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how weekly progress reports, while intended to create transparency and visibility, can sometimes become counterproductive time sinks that actually impede progress.<br/><br/>TIMESTAMPS:<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0'>0:00</a> - Introduction<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=37s'>0:37</a> - Gino introduces the topic of weekly progress reports<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=57s'>0:57</a> - The good intentions behind progress reports<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=101s'>1:41</a> - Wayne&apos;s winter frustrations (and progress report frustrations)<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=136s'>2:16</a> - The perceived benefits of progress reporting<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=185s'>3:05</a> - When progress reports go wrong: excessive time consumption<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=254s'>4:14</a> - Real-life example: Creating multiple reports for different managers<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=344s'>5:44</a> - The false sense of control from color-coded status reports<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=423s'>7:03</a> - The &quot;illusion of control&quot; problem<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=460s'>7:40</a> - When progress reports aren&apos;t even read by management<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=562s'>9:22</a> - Solution 1: Keep progress tracking but make it efficient<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=631s'>10:31</a> - Solution 2: Create meaningful feedback loops<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=674s'>11:14</a> - Solution 3: Set strict time limits for report creation<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=695s'>11:35</a> - Solution 4: Write the planned progress at the beginning of the week<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=734s'>12:14</a> - Solution 5: Use a publish-subscribe model for reporting<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=782s'>13:02</a> - Solution 6: Leverage existing tools like Jira for real-time visibility<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=857s'>14:17</a> - Focus on communicating what really matters<br/><a href='https://www.youtube.com/watch?v=NkqeRfZghw0&amp;t=932s'>15:32</a> - Conclusion and invitation for listener stories<br/><br/>Gino and Wayne discuss how weekly progress reports, while intended to provide visibility into team progress and challenges, often become elaborate time-consuming processes that actually hinder productivity. They share real experiences of spending up to 50% of work time creating redundant reports for different managers, dealing with reports that aren&apos;t actually read, and seeing how color-coded status indicators can create a false sense of control.<br/><br/>The hosts offer practical alternatives including:</p><ul><li>Setting strict time limits on report creation (max 10 minutes)</li><li>Creating the progress report structure at the beginning of the week</li><li>Implementing a publish-subscribe model where teams publish once and managers subscribe</li><li>Using existing tools like Jira to create real-time progress dashboards</li><li>Focusing on communicating blockers and help needed, not just completed tasks</li><li>Creating short, fast, easy, and actually useful reporting mechanisms<br/><br/></li></ul><p>If you&apos;ve experienced situations where well-intended workplace processes have backfired, share your story for a chance to be featured in an upcoming episode!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/17275355-progress-report-perils-when-updates-become-obstacles.mp3" length="11771552" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-17275355</guid>
    <pubDate>Tue, 10 Jun 2025 13:00:00 -0400</pubDate>
    <itunes:duration>977</itunes:duration>
    <itunes:keywords>Good Intentions Bad Outcomes, Progress Reports, Project Management, Status Reporting, Agile Development, Workplace Efficiency, Team Productivity, Management Visibility, Feedback Loops, Jira, Transparency, Agile Practices, Status Updates, Project Reporting</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>9</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>Demo Disasters: When Product Showcases Go Wrong</itunes:title>
    <title>Demo Disasters: When Product Showcases Go Wrong</title>
    <itunes:summary><![CDATA[In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how product demos and sprint reviews, while well-intentioned, can sometimes lead to counterproductive outcomes in agile teams.  TIMESTAMPS: 0:00 - Introduction 0:43 - Wayne introduces the topic of product demos and sprint reviews 1:32 - The good intentions behind product demos 2:16 - When demos become counterproductive 3:43 - Teams turning demos into elaborate productions 5:17 - The "no code check-ins before dem...]]></itunes:summary>
    <description><![CDATA[<p>In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how product demos and sprint reviews, while well-intentioned, can sometimes lead to counterproductive outcomes in agile teams.<br/><br/>TIMESTAMPS:<br/>0:00 - Introduction<br/>0:43 - Wayne introduces the topic of product demos and sprint reviews<br/>1:32 - The good intentions behind product demos<br/>2:16 - When demos become counterproductive<br/>3:43 - Teams turning demos into elaborate productions<br/>5:17 - The &quot;no code check-ins before demo&quot; problem<br/>7:16 - The &quot;fake demo&quot; with screenshots instead of working software<br/>9:21 - Solution 1: Clarify the true purpose of demos<br/>11:03 - Solution 2: Show what you&apos;ve done without extra preparation<br/>11:44 - Solution 3: Drop PowerPoint and use your existing tools<br/>13:00 - A success story: How a technical demo led to project simplification<br/>15:01 - Solution 4: Don&apos;t wait for perfect software to demo<br/>16:17 - Conclusion and invitation for listener stories<br/><br/>Wayne and Gino discuss how sprint reviews and product demos, while intended to showcase progress and gather feedback, can sometimes become elaborate productions that waste development time or turn into competitive performances between teams. They share real examples of teams spending days preparing for demos, creating presentation decks instead of showing actual software, and prohibiting code check-ins before demos to avoid potential issues.<br/><br/>The hosts offer practical alternatives including:<br/>- Reminding everyone that demos are primarily for feedback, not performances<br/>- Showing actual working software rather than presentations or screenshots<br/>- Eliminating extra preparation by simply demonstrating what&apos;s been completed<br/>- Building confidence to demo work-in-progress features for earlier feedback<br/>- Using existing tools (Jira, wikis) instead of creating separate presentations<br/><br/>If you&apos;ve experienced situations where well-intended workplace processes have backfired, share your story for a chance to be featured in an upcoming episode!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how product demos and sprint reviews, while well-intentioned, can sometimes lead to counterproductive outcomes in agile teams.<br/><br/>TIMESTAMPS:<br/>0:00 - Introduction<br/>0:43 - Wayne introduces the topic of product demos and sprint reviews<br/>1:32 - The good intentions behind product demos<br/>2:16 - When demos become counterproductive<br/>3:43 - Teams turning demos into elaborate productions<br/>5:17 - The &quot;no code check-ins before demo&quot; problem<br/>7:16 - The &quot;fake demo&quot; with screenshots instead of working software<br/>9:21 - Solution 1: Clarify the true purpose of demos<br/>11:03 - Solution 2: Show what you&apos;ve done without extra preparation<br/>11:44 - Solution 3: Drop PowerPoint and use your existing tools<br/>13:00 - A success story: How a technical demo led to project simplification<br/>15:01 - Solution 4: Don&apos;t wait for perfect software to demo<br/>16:17 - Conclusion and invitation for listener stories<br/><br/>Wayne and Gino discuss how sprint reviews and product demos, while intended to showcase progress and gather feedback, can sometimes become elaborate productions that waste development time or turn into competitive performances between teams. They share real examples of teams spending days preparing for demos, creating presentation decks instead of showing actual software, and prohibiting code check-ins before demos to avoid potential issues.<br/><br/>The hosts offer practical alternatives including:<br/>- Reminding everyone that demos are primarily for feedback, not performances<br/>- Showing actual working software rather than presentations or screenshots<br/>- Eliminating extra preparation by simply demonstrating what&apos;s been completed<br/>- Building confidence to demo work-in-progress features for earlier feedback<br/>- Using existing tools (Jira, wikis) instead of creating separate presentations<br/><br/>If you&apos;ve experienced situations where well-intended workplace processes have backfired, share your story for a chance to be featured in an upcoming episode!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/17228775-demo-disasters-when-product-showcases-go-wrong.mp3" length="12079349" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-17228775</guid>
    <pubDate>Mon, 26 May 2025 16:00:00 -0400</pubDate>
    <podcast:transcript url="https://www.buzzsprout.com/2322157/17228775/transcript" type="text/html" />
    <podcast:chapters url="https://www.buzzsprout.com/2322157/17228775/chapters.json" type="application/json" />
    <psc:chapters>
  <psc:chapter start="0:00" title="Introduction" />
  <psc:chapter start="0:49" title="Wayne introduces the topic of product demos and sprint reviews" />
  <psc:chapter start="1:38" title="The good intentions behind product demos" />
  <psc:chapter start="2:22" title="When demos become counterproductive" />
  <psc:chapter start="3:49" title="Teams turning demos into elaborate productions" />
  <psc:chapter start="5:23" title="The &quot;no code check-ins before demo&quot; problem" />
  <psc:chapter start="7:22" title="The &quot;fake demo&quot; with screenshots instead of working software" />
  <psc:chapter start="9:27" title="Solution 1: Clarify the true purpose of demos" />
  <psc:chapter start="11:09" title="Solution 2: Show what you&#39;ve done without extra preparation" />
  <psc:chapter start="11:50" title="Solution 3: Drop PowerPoint and use your existing tools" />
  <psc:chapter start="13:06" title="A success story: How a technical demo led to project simplification" />
  <psc:chapter start="15:07" title=" Solution 4: Don&#39;t wait for perfect software to demo" />
  <psc:chapter start="16:23" title="Conclusion and invitation for listener stories" />
</psc:chapters>
    <itunes:duration>1002</itunes:duration>
    <itunes:keywords></itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>8</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>When Business Cases Go Wrong: The Danger of Manufactured Numbers</itunes:title>
    <title>When Business Cases Go Wrong: The Danger of Manufactured Numbers</title>
    <itunes:summary><![CDATA[In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how organizations' well-intentioned financial approval processes can lead to unexpected negative consequences. Wayne shares a real-world example of a project where financial justification documents were created with manufactured numbers to satisfy process requirements rather than reflect reality. They discuss how this common practice can lead to poor resource allocation, wasted time creating meaningless document...]]></itunes:summary>
    <description><![CDATA[<p>In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how organizations&apos; well-intentioned financial approval processes can lead to unexpected negative consequences.</p><p>Wayne shares a real-world example of a project where financial justification documents were created with manufactured numbers to satisfy process requirements rather than reflect reality. They discuss how this common practice can lead to poor resource allocation, wasted time creating meaningless documentation, and potentially harmful business decisions.</p><p>The hosts offer practical alternatives including:</p><ul><li>Implementing shorter funding cycles with regular benefit verification</li><li>Expanding the definition of &quot;value&quot; beyond just monetary returns</li><li>Using throughput accounting instead of traditional cost accounting</li><li>Creating metrics that don&apos;t solely focus on headcount reduction</li></ul><p>SUBSCRIBE for more episodes that reveal how good intentions can lead to unexpected outcomes in the workplace!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how organizations&apos; well-intentioned financial approval processes can lead to unexpected negative consequences.</p><p>Wayne shares a real-world example of a project where financial justification documents were created with manufactured numbers to satisfy process requirements rather than reflect reality. They discuss how this common practice can lead to poor resource allocation, wasted time creating meaningless documentation, and potentially harmful business decisions.</p><p>The hosts offer practical alternatives including:</p><ul><li>Implementing shorter funding cycles with regular benefit verification</li><li>Expanding the definition of &quot;value&quot; beyond just monetary returns</li><li>Using throughput accounting instead of traditional cost accounting</li><li>Creating metrics that don&apos;t solely focus on headcount reduction</li></ul><p>SUBSCRIBE for more episodes that reveal how good intentions can lead to unexpected outcomes in the workplace!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/17169255-when-business-cases-go-wrong-the-danger-of-manufactured-numbers.mp3" length="11029905" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-17169255</guid>
    <pubDate>Mon, 12 May 2025 07:00:00 -0400</pubDate>
    <podcast:transcript url="https://www.buzzsprout.com/2322157/17169255/transcript" type="text/html" />
    <itunes:duration>915</itunes:duration>
    <itunes:keywords>BusinessCase, FinancialJustification, ProjectApproval, ManufacturedNumbers, ROIAnalysis, CorporateProcesses, ProjectFunding, ThroughputAccounting, ValueMetrics, HeadcountReduction, ResourceAllocation, FinancialPlanning, BusinessDecisions, ProjectManagemen</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>7</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>Why Constant Switching Destroys Team Productivity</itunes:title>
    <title>Why Constant Switching Destroys Team Productivity</title>
    <itunes:summary><![CDATA[In this episode of "Good Intentions, Bad Outcomes," Gino Marckx and Wayne Hetherington expose the hidden costs of constantly shifting priorities before completing work. Discover why this well-intentioned practice secretly destroys team productivity and morale, and learn practical strategies to break the cycle of never finishing work.  Learn why two-thirds of work often sits permanently "in progress," how constant switching creates codebase complexity, and the devastating impact on team motiva...]]></itunes:summary>
    <description><![CDATA[<p>In this episode of &quot;Good Intentions, Bad Outcomes,&quot; Gino Marckx and Wayne Hetherington expose the hidden costs of constantly shifting priorities before completing work. Discover why this well-intentioned practice secretly destroys team productivity and morale, and learn practical strategies to break the cycle of never finishing work.</p><p><b><br/></b>Learn why two-thirds of work often sits permanently &quot;in progress,&quot; how constant switching creates codebase complexity, and the devastating impact on team motivation. Perfect for product managers, team leads, executives, and anyone struggling with the &quot;shiny new feature&quot; syndrome that prevents teams from delivering real value.</p><p>SUBSCRIBE for new episodes that reveal the workplace practices secretly sabotaging your success!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>In this episode of &quot;Good Intentions, Bad Outcomes,&quot; Gino Marckx and Wayne Hetherington expose the hidden costs of constantly shifting priorities before completing work. Discover why this well-intentioned practice secretly destroys team productivity and morale, and learn practical strategies to break the cycle of never finishing work.</p><p><b><br/></b>Learn why two-thirds of work often sits permanently &quot;in progress,&quot; how constant switching creates codebase complexity, and the devastating impact on team motivation. Perfect for product managers, team leads, executives, and anyone struggling with the &quot;shiny new feature&quot; syndrome that prevents teams from delivering real value.</p><p>SUBSCRIBE for new episodes that reveal the workplace practices secretly sabotaging your success!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/17168689-why-constant-switching-destroys-team-productivity.mp3" length="9975279" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-17168689</guid>
    <pubDate>Mon, 28 Apr 2025 08:00:00 -0400</pubDate>
    <podcast:transcript url="https://www.buzzsprout.com/2322157/17168689/transcript" type="text/html" />
    <podcast:chapters url="https://www.buzzsprout.com/2322157/17168689/chapters.json" type="application/json" />
    <psc:chapters>
  <psc:chapter start="0:00" title="Introduction" />
  <psc:chapter start="0:36" title="The changing focus problem" />
  <psc:chapter start="1:06" title="Why organizations constantly shift priorities" />
  <psc:chapter start="2:15" title="Consequences of stopping work in progress" />
  <psc:chapter start="3:00" title="The growing backlog challenge" />
  <psc:chapter start="3:40" title="Code complexity consequences" />
  <psc:chapter start="4:24" title="Psychological impact on teams and management" />
  <psc:chapter start="5:19" title="Impact on client relationships" />
  <psc:chapter start="6:23" title="Strategies to solve the changing focus problem" />
  <psc:chapter start="6:37" title="Setting and respecting WIP limits" />
  <psc:chapter start="7:59" title="Replacing items instead of adding them" />
  <psc:chapter start="9:25" title="Salvaging partial value from in-progress work" />
  <psc:chapter start="11:06" title=" Reducing work item size" />
  <psc:chapter start="12:22" title="Creating a culture that can say &quot;no&quot;" />
  <psc:chapter start="12:56" title="Summary: Stop starting, start finishing" />
</psc:chapters>
    <itunes:duration>827</itunes:duration>
    <itunes:keywords>AgileManagement, ProductPriorities, WIPLimits, TeamProductivity, FeatureCompletion, SoftwareDevelopment, TechLeadership, ChangingFocus, ProductStrategy, WorkInProgress, FocusManagement, AgileTeams, DeliveryEffectiveness, OrganizationalAgility, ProjectMana</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>6</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>How Technical Silos Create Invisible Bottlenecks</itunes:title>
    <title>How Technical Silos Create Invisible Bottlenecks</title>
    <itunes:summary><![CDATA[In this episode, Gino Marckx and Wayne Hetherington explore why organizing teams around technical components creates dependencies that slow down your entire organization. Discover: Why component teams introduce crippling dependenciesHow "islands of knowledge" become serious bottlenecksThe hidden costs of teams protecting "their territory"Practical steps to break down silos without reorganizing everythingWhy self-service platforms and cross-team collaboration work  Perfect for technical leader...]]></itunes:summary>
    <description><![CDATA[<p>In this episode, Gino Marckx and Wayne Hetherington explore why organizing teams around technical components creates dependencies that slow down your entire organization.</p><p>Discover:</p><ul><li>Why component teams introduce crippling dependencies</li><li>How &quot;islands of knowledge&quot; become serious bottlenecks</li><li>The hidden costs of teams protecting &quot;their territory&quot;</li><li>Practical steps to break down silos without reorganizing everything</li><li>Why self-service platforms and cross-team collaboration work</li></ul><p><br/></p><p>Perfect for technical leaders, project managers, and architects struggling with cross-team dependencies!</p><p>#ComponentTeams #OrganizationalDesign #TeamStructure #ConwaysLaw</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>In this episode, Gino Marckx and Wayne Hetherington explore why organizing teams around technical components creates dependencies that slow down your entire organization.</p><p>Discover:</p><ul><li>Why component teams introduce crippling dependencies</li><li>How &quot;islands of knowledge&quot; become serious bottlenecks</li><li>The hidden costs of teams protecting &quot;their territory&quot;</li><li>Practical steps to break down silos without reorganizing everything</li><li>Why self-service platforms and cross-team collaboration work</li></ul><p><br/></p><p>Perfect for technical leaders, project managers, and architects struggling with cross-team dependencies!</p><p>#ComponentTeams #OrganizationalDesign #TeamStructure #ConwaysLaw</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/16906288-how-technical-silos-create-invisible-bottlenecks.mp3" length="11140331" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-16906288</guid>
    <pubDate>Tue, 15 Apr 2025 08:00:00 -0400</pubDate>
    <podcast:transcript url="https://www.buzzsprout.com/2322157/16906288/transcript" type="text/html" />
    <podcast:chapters url="https://www.buzzsprout.com/2322157/16906288/chapters.json" type="application/json" />
    <psc:chapters>
  <psc:chapter start="0:00" title="Introduction" />
  <psc:chapter start="0:37" title="Component team organization pattern" />
  <psc:chapter start="1:25" title="Good intentions behind component teams" />
  <psc:chapter start="2:18" title="Conway&#39;s Law and organizational structure" />
  <psc:chapter start="3:46" title="Evolution from functional to component teams" />
  <psc:chapter start="4:27" title="The dependency problem" />
  <psc:chapter start="6:01" title="Knowledge isolation and bottlenecks" />
  <psc:chapter start="7:21" title="Priority conflicts between teams" />
  <psc:chapter start="8:39" title="Value stream teams as an alternative" />
  <psc:chapter start="9:11" title="Practical steps without reorganizing" />
  <psc:chapter start="10:06" title=" Platform teams and self-service" />
  <psc:chapter start="10:35" title=" Knowledge-sharing sessions" />
  <psc:chapter start="11:42" title="Visualization and planning" />
  <psc:chapter start="12:41" title="Leadership perspective" />
  <psc:chapter start="12:51" title="Feature-based planning" />
</psc:chapters>
    <itunes:duration>924</itunes:duration>
    <itunes:keywords>Component Teams, Organizational Design, Technical Silos, Conway&#39;s Law, Team Structure, Dependencies, Bottlenecks, Agile Teams, DevOps, Cross-Functional Teams, Value Streams, Knowledge Silos, Platform Teams, Self-Service, Brown Bag Sessions, Visualization,</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>5</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>🚨 SPINNING WHEELS: The Hidden Cost of Working on Multiple Teams </itunes:title>
    <title>🚨 SPINNING WHEELS: The Hidden Cost of Working on Multiple Teams </title>
    <itunes:summary><![CDATA[Is your organization spreading people too thin across multiple teams? In this revealing episode, Hino and Wayne expose how the well-intentioned practice of assigning people to multiple teams is DESTROYING productivity and team ownership! 😱  🔥 You'll discover: Why your team members are stuck in ENDLESS standups with nothing to reportThe shocking productivity loss from constant context switching between teamsHow assigning scarce resources across multiple teams actually REINFORCES knowledge silo...]]></itunes:summary>
    <description><![CDATA[<p>Is your organization spreading people too thin across multiple teams? In this revealing episode, Hino and Wayne expose how the well-intentioned practice of assigning people to multiple teams is DESTROYING productivity and team ownership! 😱<br/><br/>🔥 <b>You&apos;ll discover:</b></p><ul><li>Why your team members are stuck in ENDLESS standups with nothing to report</li><li>The shocking productivity loss from constant context switching between teams</li><li>How assigning scarce resources across multiple teams actually REINFORCES knowledge silos</li><li>The real reason your &quot;resource optimization&quot; is causing project delays</li><li>Why team members assigned to multiple projects feel like &quot;fifth wheels&quot; instead of valued contributors</li></ul><p><br/>📱 SUBSCRIBE for new episodes every week that reveal the workplace practices secretly sabotaging your success!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>Is your organization spreading people too thin across multiple teams? In this revealing episode, Hino and Wayne expose how the well-intentioned practice of assigning people to multiple teams is DESTROYING productivity and team ownership! 😱<br/><br/>🔥 <b>You&apos;ll discover:</b></p><ul><li>Why your team members are stuck in ENDLESS standups with nothing to report</li><li>The shocking productivity loss from constant context switching between teams</li><li>How assigning scarce resources across multiple teams actually REINFORCES knowledge silos</li><li>The real reason your &quot;resource optimization&quot; is causing project delays</li><li>Why team members assigned to multiple projects feel like &quot;fifth wheels&quot; instead of valued contributors</li></ul><p><br/>📱 SUBSCRIBE for new episodes every week that reveal the workplace practices secretly sabotaging your success!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/16809826-spinning-wheels-the-hidden-cost-of-working-on-multiple-teams.mp3" length="13003582" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-16809826</guid>
    <pubDate>Tue, 01 Apr 2025 06:00:00 -0400</pubDate>
    <podcast:chapters url="https://www.buzzsprout.com/2322157/16809826/chapters.json" type="application/json" />
    <psc:chapters>
  <psc:chapter start="0:00" title="Introduction" />
  <psc:chapter start="0:44" title="The multi-team assignment problem" />
  <psc:chapter start="1:10" title="Structure issues causing inefficient workflows" />
  <psc:chapter start="2:33" title="Why companies assign people to multiple teams" />
  <psc:chapter start="5:08" title="The devastating effects on productivity" />
  <psc:chapter start="8:14" title="How multi-team assignments damage ownership" />
  <psc:chapter start="10:46" title="When dependencies block team progress" />
  <psc:chapter start="12:25" title="Solutions to fix fractional team assignments" />
  <psc:chapter start="14:26" title="Practical advice for maximizing workflow" />
</psc:chapters>
    <itunes:duration>1079</itunes:duration>
    <itunes:keywords>multiple teams, context switching, team structure, organizational design, too many standups, resource allocation, knowledge silos, team topologies, fractional assignments, agile teams, standups, productivity loss, team ownership, cognitive load, workflow </itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>4</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>🚨 THE KPI TRAP: Why Performance Metrics Destroy Team Accountability</itunes:title>
    <title>🚨 THE KPI TRAP: Why Performance Metrics Destroy Team Accountability</title>
    <itunes:summary><![CDATA[🔍 Ever been measured on KPIs that made you game the system? In this eye-opening episode about performance measurement mistakes, Gino Marckx and Wayne Hetherington reveal how your well-intentioned metrics might be DESTROYING team accountability and causing serious productivity issues! 😱  🔥 You'll discover: - Why tracking sprint velocity and story points might be HURTING your project - The shocking ways teams manipulate agile metrics to look good - How performance measurements designed for acco...]]></itunes:summary>
    <description><![CDATA[<p>🔍 Ever been measured on KPIs that made you game the system? In this eye-opening episode about performance measurement mistakes, <b>Gino Marckx</b> and <b>Wayne Hetherington</b> reveal how your well-intentioned metrics might be DESTROYING team accountability and causing serious productivity issues! 😱<br/><br/>🔥 You&apos;ll discover:<br/>- Why tracking sprint velocity and story points might be HURTING your project<br/>- The shocking ways teams manipulate agile metrics to look good<br/>- How performance measurements designed for accountability actually DESTROY team ownership<br/>- The ONE question to ask before implementing any KPI or measurement system<br/>- Why managers are completely WASTING TIME with metrics that don&apos;t align with organizational goals<br/><br/>📱 SUBSCRIBE for new episodes every week that reveal the workplace practices secretly sabotaging your success!</p><p><br/>Learn more about alternatives to velocity tracking and preventing metric manipulation on our website: https://xodiac.ca/</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>🔍 Ever been measured on KPIs that made you game the system? In this eye-opening episode about performance measurement mistakes, <b>Gino Marckx</b> and <b>Wayne Hetherington</b> reveal how your well-intentioned metrics might be DESTROYING team accountability and causing serious productivity issues! 😱<br/><br/>🔥 You&apos;ll discover:<br/>- Why tracking sprint velocity and story points might be HURTING your project<br/>- The shocking ways teams manipulate agile metrics to look good<br/>- How performance measurements designed for accountability actually DESTROY team ownership<br/>- The ONE question to ask before implementing any KPI or measurement system<br/>- Why managers are completely WASTING TIME with metrics that don&apos;t align with organizational goals<br/><br/>📱 SUBSCRIBE for new episodes every week that reveal the workplace practices secretly sabotaging your success!</p><p><br/>Learn more about alternatives to velocity tracking and preventing metric manipulation on our website: https://xodiac.ca/</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/16809473-the-kpi-trap-why-performance-metrics-destroy-team-accountability.mp3" length="10428588" type="audio/mpeg" />
    <link>https://xodiac.ca/</link>
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-16809473</guid>
    <pubDate>Thu, 20 Mar 2025 07:00:00 -0400</pubDate>
    <podcast:transcript url="https://www.buzzsprout.com/2322157/16809473/transcript" type="text/html" />
    <podcast:chapters url="https://www.buzzsprout.com/2322157/16809473/chapters.json" type="application/json" />
    <psc:chapters>
  <psc:chapter start="0:00" title="Introduction" />
  <psc:chapter start="0:42" title="The KPI alignment problem" />
  <psc:chapter start="1:15" title="Real-world story points manipulation" />
  <psc:chapter start="2:37" title="Why KPIs fail in practice" />
  <psc:chapter start="6:09" title="The accountability paradox explained" />
  <psc:chapter start="7:22" title="How teams game the system" />
  <psc:chapter start="8:25" title="When metrics create blame cultures" />
  <psc:chapter start="9:34" title="Measuring what actually matters" />
  <psc:chapter start="11:06" title=" Creating truly actionable metrics" />
</psc:chapters>
    <itunes:duration>865</itunes:duration>
    <itunes:keywords>KPI problems, performance metrics, team accountability, agile metrics, KPIs gone wrong, story points, measuring performance, metrics mistakes, KPI pitfalls, metrics that hurt teams, velocity tracking, KPI alternatives, agile measurement, sprint velocity, </itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>3</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>Turning Intentions into Impact</itunes:title>
    <title>Turning Intentions into Impact</title>
    <itunes:summary><![CDATA[Welcome to the first episode of "Good Intentions and Bad Outcomes", featuring hosts Gino Marckx and Wayne Hetherington. In this first episode, dive into the nuanced world of OKRs (Objectives and Key Results) and explore how workplace challenges arise when good intentions don't always lead to the desired outcomes. Join Gino and Wayne as they examine the common pitfalls of using performance targets as key results, a practice that can inadvertently pull teams away from their core objectives. Thi...]]></itunes:summary>
    <description><![CDATA[<p>Welcome to the first episode of &quot;Good Intentions and Bad Outcomes&quot;, featuring hosts Gino Marckx and Wayne Hetherington. In this first episode, dive into the nuanced world of OKRs (Objectives and Key Results) and explore how workplace challenges arise when good intentions don&apos;t always lead to the desired outcomes.</p><p>Join Gino and Wayne as they examine the common pitfalls of using performance targets as key results, a practice that can inadvertently pull teams away from their core objectives. This episode offers valuable insights into how setting performance targets might impact team motivation and why it often results in maintaining the status quo rather than fostering growth and innovation.</p><p>Key discussion points include:</p><ul><li>The foundational purpose of OKRs and their role in enhancing team motivation.</li><li>Strategies to set effective stretch goals that push teams beyond mediocrity.</li><li>Leadership approaches to cultivating a more autonomous and engaged team environment.</li><li>Practical alternatives to traditional performance targets for improved alignment and success.</li></ul><p>Be part of this insightful conversation and learn how to transform good intentions into impactful outcomes. We also encourage you to share your own workplace challenges or OKR experiences for discussion in future episodes.</p><p>Tune in and let&apos;s turn your good intentions into great achievements!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>Welcome to the first episode of &quot;Good Intentions and Bad Outcomes&quot;, featuring hosts Gino Marckx and Wayne Hetherington. In this first episode, dive into the nuanced world of OKRs (Objectives and Key Results) and explore how workplace challenges arise when good intentions don&apos;t always lead to the desired outcomes.</p><p>Join Gino and Wayne as they examine the common pitfalls of using performance targets as key results, a practice that can inadvertently pull teams away from their core objectives. This episode offers valuable insights into how setting performance targets might impact team motivation and why it often results in maintaining the status quo rather than fostering growth and innovation.</p><p>Key discussion points include:</p><ul><li>The foundational purpose of OKRs and their role in enhancing team motivation.</li><li>Strategies to set effective stretch goals that push teams beyond mediocrity.</li><li>Leadership approaches to cultivating a more autonomous and engaged team environment.</li><li>Practical alternatives to traditional performance targets for improved alignment and success.</li></ul><p>Be part of this insightful conversation and learn how to transform good intentions into impactful outcomes. We also encourage you to share your own workplace challenges or OKR experiences for discussion in future episodes.</p><p>Tune in and let&apos;s turn your good intentions into great achievements!</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/15923860-turning-intentions-into-impact.mp3" length="7879939" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-15923860</guid>
    <pubDate>Fri, 22 Nov 2024 13:00:00 -0500</pubDate>
    <itunes:duration>652</itunes:duration>
    <itunes:keywords>OKRs (Objectives and Key Results), Workplace Challenges,  Performance Targets, Team Motivation, Leadership Strategies, Unintended Consequences, Stretch Goals, Team Alignment, Employee Engagement, Business Growth, Management Practices, Organizational Devel</itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>1</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
  <item>
    <itunes:title>The planning fallacy</itunes:title>
    <title>The planning fallacy</title>
    <itunes:summary><![CDATA[Is there such a thing as too much planning? Listen to what John and Gino have to say about this.  Contact us at feedback@goodintentionsbadoutcomes.org ]]></itunes:summary>
    <description><![CDATA[<p>Is there such a thing as too much planning? Listen to what John and Gino have to say about this.</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></description>
    <content:encoded><![CDATA[<p>Is there such a thing as too much planning? Listen to what John and Gino have to say about this.</p> <p>Contact us at feedback@goodintentionsbadoutcomes.org</p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2322157/episodes/14581523-the-planning-fallacy.mp3" length="10704749" type="audio/mpeg" />
    <itunes:author>Xodiac</itunes:author>
    <guid isPermaLink="false">Buzzsprout-14581523</guid>
    <pubDate>Mon, 26 Feb 2024 17:00:00 -0500</pubDate>
    <itunes:duration>888</itunes:duration>
    <itunes:keywords></itunes:keywords>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
</channel>
</rss>
