Good intentions, bad outcomes

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 [email protected]

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 [email protected]

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 [email protected]

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 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're going.

Key Insights:

• OKRs are temporary and directional—they end when you reach your goal
• KPIs are permanent system health monitors—they never stop
• The same number can mean different things depending on why you're measuring it
• KPIs don't enable autonomous decision-making toward future goals
• Exception: Transform an unhealthy KPI into a temporary OKR when you need to fix it

Wayne'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.

Perfect for leaders struggling with goal-setting, team alignment, and making measurements that actually matter.

Got a workplace challenge where good intentions led to bad outcomes? Share it for a future episode!

Contact us at [email protected]

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 erodes while everyone pretends the system is working.

In this episode, we discuss:

• How the amber light anti-pattern destroys test discipline
• Why "defects vs bugs" classifications create similar problems
• The connection between failing CI/CD and "almost done" Kanban columns
• When radical solutions (like deleting your entire test suite) make sense
• How good intentions around "unblocking" teams lead to quality debt

Timestamps:
0:00 - The Amber Light Anti-Pattern Exposed 

1:45 - Why 90% Failed Tests Became "Good Enough" 

4:00 - The Hidden Psychology of Ignoring Quality 

5:14 - Defects vs Bugs: Another Dangerous Distinction 

6:41 - "Almost Done" Columns: The Kanban Version 

8:21 - The Nuclear Option: Delete Your Tests

Key insight: If you don't trust your feedback system enough to act on it, remove it entirely rather than work around it.

This is a shorter episode focusing on one powerful anti-pattern that many development teams will recognize. Whether you're dealing with flaky tests, unreliable builds, or teams that have learned to ignore quality signals, this conversation offers both diagnosis and cure.

Got a workplace situation where good intentions led to bad outcomes? We'd love to hear about it for a future episode.

Contact us at [email protected]

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 dependencies, and delivered work that other teams couldn't actually use. The result? Longer delivery timelines and frustrated stakeholders - exactly what the protection was supposed to prevent.

The Real Problem:
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.
What Works Instead:

Set up controlled feedback sessions instead of complete isolation
Use Scrum ceremonies strategically for stakeholder input
Create "office hours" for team availability
Implement communication boards for non-urgent questions
Remember that focus doesn't mean disconnection

Bottom Line: Teams need focus, not isolation. The goal is managing distractions, not eliminating all outside contact.

Timestamps:
0:00 - Introduction
0:35 - The "Team Protection" Problem
1:17 - Why Managers Try to Shield Teams
2:13 - When Good Intentions Go Wrong
3:33 - Better Ways to Handle Distractions
5:00 - Using Scrum for Controlled Feedback
6:32 - Office Hours and Communication Systems
8:05 - Keeping Teams Connected to the Big Picture
10:18 - Avoiding the "Special Project" Mentality
11:05 - Managing Emergency Work Without Chaos

About Good Intentions, Bad Outcomes:
A podcast about workplace challenges where good intentions create unintended consequences. Hosted by Gino Marckx and Wayne Hetherington.

#TeamManagement #Agile #ScrumMaster #Leadership #ProjectManagement #WorkplaceCollaboration

Subscribe for more insights on avoiding common workplace traps.

Contact us at [email protected]

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 lose ownership when goals are handed to them
The difference between goal-setting and alignment tools
How to turn OKRs into powerful negotiations instead of mandates
Why the person setting the goal matters more than the goal itself

Key Takeaway: OKRs work best when teams help create them, not when they're told to follow them. It's the difference between "your goal" and "my goal that you need to hit."

Timestamps:
0:00 - Introduction
0:38 - The Problem: Handing Teams Pre-Made OKRs
2:00 - Why This Approach Fails
4:32 - How OKRs Should Actually Work
5:37 - OKRs as Alignment Tools, Not Just Goal Setting
7:16 - The Power of Negotiation in Goal Setting
8:28 - Ownership vs. Accountability
9:33 - Real-World Example: Sports Team Management
10:15 - Wrap-up

Got a workplace situation where good intentions led to bad outcomes? We'd love to hear about it for a future episode!

About Good Intentions, Bad Outcomes:
A podcast exploring workplace challenges where well-meaning practices create unintended consequences. Hosted by Gino Marckx and Wayne Hetherington.

#OKRs #Leadership #TeamManagement #GoalSetting #WorkplaceCulture #Management #BusinessStrategy

Like this content? Subscribe for more insights on turning good intentions into great outcomes.

Contact us at [email protected]

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 measure") and share real-world examples of metrics gone wrong.

You'll discover:

• Why traditional project completion metrics can harm team dynamics
• How performance targets psychologically change employee behavior
• Two striking examples of well-intentioned metrics creating perverse incentives
• Alternative approaches focusing on employee engagement and organizational alignment
• The role of OKRs in setting direction without micromanaging actions
• Why annual performance reviews might be counterproductive

Key Insights:

• The difference between measuring for information vs. measuring for targets
• How financial incentives tied to metrics amplify problematic behaviors
• Why HR should focus on creating healthy workplaces rather than counting projects
• The importance of aligning individual growth with organizational outcomes

Whether you're in HR, management, or simply interested in workplace dynamics, this episode offers practical wisdom for creating performance systems that actually work.

Have a workplace situation with unintended consequences? Share it with us and we might feature it in a future episode!

Contact us at [email protected]

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 trap and elongated delivery times
• Apple vs. startup approaches to product perfection
• Customer segmentation strategies for faster releases
• Feature toggles and controlled rollouts
• Why production validation trumps test environment success
• Multidimensional planning: dirt road vs. highway implementations
• A fascinating airport dropdown case study that reveals unexpected user behavior

The counterintuitive insight: If you want to make a perfect product, go to your client with an imperfect product first.

Ideal for product managers, developers, startup founders, and anyone involved in product development who wants to ship faster without sacrificing quality.

Have a workplace situation with unintended bad outcomes? Share it with us for a future episode!

Contact us at [email protected]

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 drain productivity
 2:39 A different lens on a recurring issue
 2:58 Balancing collaboration with individual capacity
 3:28 Refocusing on the intention: communication
 4:14 Solution 1: Back-to-back scheduling to preserve deep work
 4:49 Solution 2: Supplier-team model for shared work
 5:31 Solution 3: Scrum of scrums or cross-team sync
 6:05 Solution 4: Joint planning and reviews for cross-team clarity
 6:44 Solution 5: Rotating representatives between teams
 7:10 Solution 6: Weekly cross-team progress alignments
 8:13 Making information sharing efficient and intentional
 8:52 Closing thoughts on time-conscious communication
 9:28 Don't follow the playbook—do what makes sense
 9:45 Wrap-up and invitation for listener stories

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.

In this episode, they explore alternatives that preserve the value of daily coordination while respecting people’s time, such as:
Organizing back-to-back meetings to protect blocks of focus time
Shifting to a supplier relationship for shared work
Implementing scrum-of-scrums or other cross-team alignment practices
Holding joint sprint planning and reviews to reduce duplicate discussions
Rotating team representatives to maintain connection without overload
Setting up weekly cross-team check-ins to keep things aligned

If your calendar ever made you think "When am I supposed to actually do the work?" you’ll relate to this one.

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!

Contact us at [email protected]