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 optimization is and why it happens

- Real examples of teams improving metrics while overall delivery slows

- The disconnect between deployment and release

- Why focusing on what's in front of you can blind you to bigger problems

- Practical techniques to see the whole system (value stream mapping, theory of constraints)

💡 Key Takeaway:

Sometimes you need to "de-optimize" one part to optimize the whole system.

Perfect for: Engineering managers, product owners, Agile coaches, DevOps teams, and anyone interested in systems thinking and organizational efficiency.

🔗 Have a workplace situation you'd like us to discuss? Let us know in the comments!

#LocalOptimization #SystemsThinking #AgileTransformation #DevOps #SoftwareDelivery

---

Good Intentions and Outcomes Podcast - Exploring workplace challenges where good intentions lead to unintended consequences.

Contact us at feedback@goodintentionsbadoutcomes.org

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 cost of "just observing"
• Practical strategies for supporting without hovering

💡 MAIN TAKEAWAYS:
✅ Stick to feedback-focused events (like sprint reviews)
✅ Ask permission before attending planning sessions
✅ Limit your presence - less is often more
✅ Ask "How can I help?" instead of jumping in with answers
✅ Use "What would you do?" to empower team decisions
✅ Know when to give feedback and when to stay silent

⏱️ TIMESTAMPS:
0:00 Introduction
0:43 The Challenge: Well-Intentioned Leader Presence
2:17 Why Leaders Want to Be Involved
4:03 What Actually Happens When Leaders Show Up
6:24 The Power Differential Effect
7:26 How Autonomy Breaks Down
9:02 Real Example: The Story Point Incident
10:22 Having Difficult Conversations with Leaders
11:53 Solutions: How to Support Without Overbearing
13:14 Ask Permission, Don't Just Show Up
14:50 The Power of "How Can I Help?"
15:28 Resist the Urge to Fill the Silence
16:12 Quick Summary

🎙️ ABOUT THIS PODCAST:
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.

#Leadership #TeamAutonomy #AgileLeadership #ScrumMaster #Management #WorkplaceCulture #TeamDynamics #LeadershipDevelopment #GoodIntentions #PodcastEpisode

Contact us at feedback@goodintentionsbadoutcomes.org

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 traded one single point of failure for another.

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're only on AWS, or only on Azure, or only on Google Cloud, you're still vulnerable when that one provider has issues.

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's the only real answer.

We also talk about when it'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's a different calculation. It comes down to understanding how many nines of uptime you actually need and what you're willing to pay for it.

Timestamps:

0:00 - Introduction

0:33 - AWS outage hits half the world

1:16 - Why organizations move to cloud in the first place

2:50 - The promise of always-available infrastructure

4:39 - So why did everything go down?

5:28 - You still have a single point of failure

6:25 - The assumption of built-in redundancy

7:21 - Building real backup plans across providers

8:40 - How unlikely is a multi-cloud failure?

9:41 - The challenge of keeping environments consistent

10:58 - Cost vs. redundancy: the eternal tradeoff

11:34 - How many nines do you actually need?

12:39 - Making the right choice for your situation

13:24 - Wrap-up

Contact us at feedback@goodintentionsbadoutcomes.org