00:00:02

Good evening, my esteemed enterprise DevOps practitioners. I'm Chris Corer, an advocate for mapping DevOps practices and complexity science for SJ technologies. And I'm here tonight to talk to you about the seven horses of abductive reasoning. So once upon a time, a socialite gathered up this village and said, I'm inviting everyone to a party, not just a socially elite. Isn't that wonderful? And a farmer replied, I don't know, maybe in the socialite feeling snubbed stormed off in a huff. Coincidentally enough, the next morning the farmer's horse had run away and the town's people said, isn't that bad? And the farmer said again, I don't know, maybe later that evening, the horse Kim's home was seven wild horses. And the people said, isn't that great? You must be the richest person around for miles now. But persistently, the farmer said, I don't know, maybe later that week the farmer's child breaks their leg trying to tame one of these horses.

00:01:06

And the townspeople said, isn't that terrible? But still, the farmer said, I don't know, maybe. Well, it was later that year that war breaks out and a conscription officer comes to town and says, I have no use for an old farmer or a child with a broken leg, but I'll take you such light. And some thought this was great and some thought this was bad. But still the farmer said, I don't know, maybe. So time passes, the farmer prospers with a healthy child and these eight horses and the Warrens and the socialite returns to a vestige of the life they once knew. House in shambles and nowhere to go. Nowhere to go, but to work for the farmer. And the townspeople said, I remember you. You used to be such a big shot. Now look at you. Isn't that sad? And being glad to be alive and have a place in the world.

00:01:59

The socialite simply said, I don't know, maybe. See, nature is an integrated process of immense complexity and it's really impossible to tell if anything that happens is good or bad. 'cause we never know what the consequences will ultimately be. This is story is adapted from an Alan Watts lecture and it is really about requisite variety. See, nature bets on a few different horses. And survival of the fittest is not about winning or losing, it's about survival. The farmer was focused on survival of the village, not any pettiness between him and his socialite. And this type of collaboration demands a flatter ontology. So theory X says, you're bad people and I need to manage you to get you to do stuff. And theory y it says, we can all hold hands and sing kumbaya, and we need some of both. But this takes a different type of reasoning. So there's really three kinds of reasoning. You've got deductive logic, which is top down inductive logic, which is bottom up and abductive logic, which simply asks, what seems most probable, what's most likely to happen here? So deductive reasoning, all people are mortal. Socrates is a person, therefore Socrates is mortal, which is a fair deduction. Unlike this dog that is deduced, it might be a cat 'cause they both have four legs.

00:03:16

Inductive reasoning. This ignite talk has 20 slides. The other Ignite talks have 20 slides. Probably all the Ignite talks have 20 slides, which is a fair induction. Unlike this penguin that's induced. It might be an old TV show 'cause they're both black and white. In abductive reasoning, just ask what's most likely if you keep the DP next to the Colgate? It's only a matter of time before you brush your teeth with muscle ointment,

00:03:41

<laugh>.

00:03:45

And this brings us to parallel, safe to fail experiments. So where's the gravitational pool? Where's the inertia? And could this be flatter? If we're gonna roll a lot a wagon down these hills to see which one didn't fall in a pit, where might we test that before we took a ride? Yes. And this hierarchy doesn't help feedback get to leadership. So top down is good for command and control, um, and broadcasting info. But the signal to noise ratio on that feedback is gonna be low. This is like Shannon theory. So some structure is necessary. What we've learned from Zappos and the Holacracy is if there are no managers, then everybody's a manager and you end up having to try to deal with all these different priorities simultaneously with nowhere to escalate. So how can you collaborate with your customers employees on a peer level to deliver more feedback and value? Do you have a map and scratching a itch in removing a parasite? Or not the same thing, but both are helpful? So you can follow me on Twitter, you can follow SJ Technologies and you can come talk to me at the booth tomorrow if you'd like to discuss mapping. Will I see you there? I don't know, maybe

00:05:00

<laugh>.