The Reasoning Show

The Reasoning Show AI moves fast. Thinking clearly matters more.

The Reasoning Show cuts through the hype to explore how the smartest people in enterprise AI actually make decisions — the strategy, the tradeoffs, and the hard lessons no press release mentions.

Every week, hosts Aaron Delp and Brian Gracely sit down with the founders building the tools, investors funding the shift, and operators running AI in the real world. Not hype. Not panic. Just clear-headed conversations with people who have to make actual decisions.

Because the AI revolution isn't just happening. It's being reasoned through.

New shows every Wednesday and Sunday.

Topics: Enterprise AI strategy · LLMs in production · AI leadership · Agentic AI · Digital Sovereignty · Machine Learning · AI startups · Cloud Computing

All Episodes

The Reasoning Show

Chaos Engineering and Team Health

September 18, 2019 • Aaron Delp & Brian Gracely

0:00 | 31:33

SHOW: 415

DESCRIPTION: Brian talks with Paul Osman (@paulosman, SRE Engineering Manager @UnderArmour) about aligning business value to Chaos Engineering, measuring its impact, and changing team culture to embrace the chaos.

SHOW SPONSOR LINKS:

PricingWire: Monetization & Pricing Strategy for Software & Technology Innovators
PricingWire - Pricing Metric Decision Guide

Digital Ocean Homepage
Get Started Now and Get a free $50 Credit on Digital Ocean
[FREE] Try an IT Pro Challenge
Get 20% off VelocityConf passes using discount code CLOUD

CLOUD NEWS OF THE WEEK:

SHOW INTERVIEW LINKS:

Paul’s Books (Microservices with JavaScript, Microservices Development)
[video] Embracing Chaos - DevOps Day Austin
[Velocity] Managing Chaos: Chaos Engineering and Team Health
Under Armour Homepage
“Chaos Engineering” on previous episodes of The Cloudcast

SHOW NOTES:

Topic 1 - Welcome to the show. Before we get into Chaos Engineering, let’s talk a little bit about your background and some of the things you did prior to joining Under Armour.

Topic 2 - We’ve talked about Chaos Engineering a few times on the show before. At a company level, what are some of the things (Connected Health) where it makes sense for Under Armour to be investing in Chaos Engineering and developing expertise around this discipline?

Topic 3 - Walk us through how a team at Under Armour thinks about Chaos Engineering, from the business need to think about scheduling it (or not scheduling it), measuring it, and then communicating the results back within your team and to management.

Topic 4 - I think people think that Chaos is a periodic event, like a DR test, but in reality, it needs to be somewhat of an on-going activity. How do you connect the dots between this on-going Chaos and actual problems in your systems - and how/when to measure problems (or what to measure)?

Topic 5 - What is the most difficult part about getting the team culture to understand that Chaos is an important part of day-to-day activities and dealing with “failure” being part of the system?

FEEDBACK?