Skip to main content
Joel Tosi

Joel Tosi

Co-founder & CTO of Dojo & Co and co-author of "Signals & Levers," "Coaching for Learning," and "Creating Your Dojo"

Oct 21, 2026

6:56
Joel, how about you? I mean, was it agile or was it, I'm not trying to play framework bingo here, but what was your origin story when it comes to improvement?
7:06
I think it was maybe I had a longer duration, like an organization that I was at where I actually first met Elizabeth going on probably two decades ago now.
7:18
I remember early on, I was trying to do some improvement work there, again, kind of still in the engineering space.
7:25
And ultimately, when I ended up leaving and Elizabeth came in, I was sitting down with a bunch of our directors and executives, and somebody had made a comment around, why do you all think we need to get better? And everybody kind of goes around the room and everybody says, well, we're pretty good the way we are, right? And everybody said, you know, the stock price is high.
7:45
We have a lot of employees.
7:46
We're getting a lot of things done.
7:48
And when it came over to me, I looked around and I just said, I don't want to be okay.

22 MINS LATER

29:51
lots to say on that.
1:47
And I'm actually curious, Joel, since you wrote all of them, which one is your favorite Better in 30?
1:52
That's kind of like asking which one's your favorite child, right? Isn't that an unfair question? That's fair.
2:00
I think I'll tell you this.
2:02
Probably the most approachable one would be my favorite, at least top of mind.
2:07
And the reason why I say most approachable is one that even before the book is out, I've mentioned it to groups I've been with and teams I've been with, and it's using the language.
2:18
And so what I mean by that is In the book, we talk about signals, obviously, and signals and levers.
2:23
And early on, one of the early on veteran 30s is just asking yourself to find other signals that you might not be paying attention to.
6:00
Christopher McConkey- Pay and then sort of pay attention like try to tune in to these other things and assess whether they are seem to be valid signals of something going well or poorly,
3:52
[laughs]
3:53
So, any given story might be done that day or it might be done next month, right? Now, that's not an estimation problem, right? And so when we think about...
4:03
If we, when we, when we chart that out, you know, the variability, the average is 12, and it's the, it, it's probably somewhere betw- if we did it in a Shewhart chart, say it's between zero and, like, say 30 days, because we actually do, like, a 99% confidence interval.
4:16
And so what's interesting, though, about when you look at variability is you can ask yourself a few questions.
4:21
The first question is, is the variability that's happening in the system causing me to make different decisions? Well, for this product owner, it was cau- the amount of variability that they were feeling was causing them to feel like they never knew what the team was gonna get done ever.
4:37
So the variability was causing, uh, the product owner problems.
4:41
Now, of course, that had systemic effects where the team was then stressed and they, you know, always starting lots of things, which then be, you know, kind of reinforced this kind of doom loop they had.
7:38
What's, what's the connection from realizing that it was, like, the dependencies and other things?
3:33
Hey, Joel, you get to take this one.
3:34
get to take it all right uh so the systems thinking uh is put me on the spot so systems thinking is just the idea that uh there there is no direct uh cause and effect uh of our decisions right so like you know the body is an example of a system uh keeping it healthy is not just a function of of just exercising it's also a facet of how you eat and how you live and it's what you the decisions you make feedback into your body and your body is adapting to the system That's probably kind of a little esoteric, but when we think about software and the books really about software delivery, software delivery is a function of a system.
4:13
And so what we mean by that is The way an organization goes about building, delivering and shipping software is a function of a system.
4:25
It's not just the process as it's defined, it's all of the things that are influencing the way the software gets built.
4:32
So things that are very concrete.
4:34
There's pressure from the market.
4:36
There's monetary concerns.
5:45
But Joel, what goes wrong with that? Why can't we capture it on a whiteboard? Because it feels like we should be able to if we could just write down enough of the interacting elements and systems.
25:43
And that is pulling a lever.
25:45
In the early days of some of my engineering, I worked on trading systems without giving away too much information.
25:53
There was a big initiative.
25:55
The organization I was with was buying another trading platform, and so we had to merge data.
26:02
And I was in charge of some of the data dissipation.
26:06
I remember it was like August.
26:09
And somebody said to me, well, we need a status.

10 MINS LATER

35:47
Joel, what about you? What's your favorite part of the book?
11:26
So tell us about this adaptive socio-technical system.
11:30
Sure.
11:31
Uh, so we'll start with the kind of simpler, more evident parts, the, the socio aspect of it.
11:37
Software is built by people, uh, interacting with people for use by people.
11:42
Even if machines end up using it, it's for the benefit of people.
11:45
So there's a definitely a social aspect, socio aspect of that.
11:49
People being complex creatures, that of course just adds to the, uh, unpredictability of the system.

41 MINS LATER

52:45
So, uh, that's why it's so important, more important today than ever before to be able to read the signals and figure out what levers you have at your disposal.
37:25
So can you talk about how that might help, uh, leaders distinguish between signal and noise?
37:31
So, uh, so yeah, uh, Elizabeth was pointing at me 'cause I, I got really excited about variability, uh, and Shewhart charts when I was first introduced to it, uh, uh, geez, maybe about 10 years ago by, uh, a good friend, Mark Rabin.
37:43
Uh, and he was talking about it, like, uh, in healthcare, um, and, and helping hospitals.
37:47
When I saw it, I was like, "This is amazing," because it's the same kind of things that were happening, uh, in software.
37:53
Like in hospitals, they were, uh, seeing issues with, uh, mortality rates, and the people were reacting to like if, if a...
38:00
You know, which they should react to a person dying.
38:01
But the whole idea was there's a reason why you're having these fluctuations, and there's a reason why, uh, software's delivery is a function of a system, as we've kind of already covered, and it's gonna have natural occurring variability.
41:19
Um, so can you just, um, unpack that a bit, and how does causal modeling maybe provide a, a better alternative?
39:01
What about the lever?
39:02
Yeah, on the lever side, levers are really just the things, the decisions we make to try and influence the system at large.
39:11
We would be remiss if we didn't mention Elizabeth and I were both highly influenced by Danella Meadows and a bunch of her groundbreaking work in systems thinking.
39:18
And in one of her, call it a metaphor or call it her frame, she talks about nine levels or 10 levels of levers in the system and various kind of leverage points.
39:28
And so what we were trying to get across with levers is that when you're trying to influence the system, you're in essence pulling a lever.
39:35
Now, kind of like how much leverage you get kind of depends upon a multitude of things and where you're acting in the system and your relevant.
39:42
And so it's it's a really beautiful metaphor.

6 MINS LATER

45:54
Yes.

We value your privacy

We use cookies to understand how you use our platform and to improve your experience. Click “Accept All” to consent, or “Decline non-essential” to opt out of non-essential cookies. Read our Privacy Policy.