
Sign up to save your podcasts
Or


Transcript:
Joe Krebs 0:10
Agile FM radio for the Agile community, www agile.fm. Thank you for tuning in to another episode of agile FM today I have, you know, I've been waiting for Joshua Kerievsky for a long, long time, because your name came across in conference, manuals and content and everywhere since 1996, or something like that when industrial logic was founded. I have Joshua here on the podcast, he is the CEO and founder of that company. And there are two things we want to talk about that both related to the joy of agility today, because that is the title of his brand new book, that is to be released very soon, as well as his keynote for the Agile 2022 conference in Nashville. Before we go all into this, welcome to the podcast, Joshua.
Joshua Kerievsky 1:07
Joe, thank you so much for having me. It's a real pleasure to be here, obviously. And we just appreciate the opportunity to chat with you.
Joe Krebs 1:15
That is fantastic, Joshua. Well, as I said, you have been in the Agile community for a long, long time you even have released the book. We're not gonna talk about this book. It's an award winning book, it's refactoring to patterns that was released in 2004. Now, the next book is on the shelf joy of agility that took 18 years as an 18 year break was the release and the writing of the first book such a pain that it took 18 years.
Joshua Kerievsky 1:43
Oh, gosh, well, writing books is hard, hard work. I mean, you know, it's if you want to write a book that has any kind of enduring value, then yeah, you have to really dig deep. But yeah, I did. I mean, a lot of elearning in between those periods. elearning is very challenging in its own right, and multimedia elearning content that really helps people learn skills and spend a lot of time doing that in between. But yeah, agile is also a complicated topic. So I really was learning and learning and learning and not wanting to encode stuff in a book before I felt like I had something that I thought could be very valuable to share.
Joe Krebs 2:18
Yeah, your LinkedIn profile reads extremely humble, you know, lifelong learner. Since 1996, you have been in the Agile community, you will call yourself a global citizen. But you know, if I read this profile, correct, you have definitely a little bit of an affiliation with Italy and everything related to Italy. So you're global citizen, but you are biased, right?
Joshua Kerievsky 2:45
Well, yeah, I mean, I grew up in New York City, which I you know, is a true melting pot. So I'm so so thankful that I that happened because you know, in New York City, you have every race and gender and just every kind of imaginable person under the sun and so you just developed an incredible appreciation for different kinds of people and different kinds of food. And then luckily in my in my business travels I've gotten to you know, travel to many parts of the globe and I really just love that I love appreciating how things are different elsewhere and it's it's a it's a pleasure to meet people I you know, a lot of times I get mistaken for the natives when I go to a particular countries like France they start speaking to me in French I don't know why or you know, in Brazil they think they can speak to me in Portuguese it doesn't happen in Japan but I'm working on that.
Joe Krebs 3:50
That is awesome. What does it look like? Is it the food is it the fashion and lifestyle or?
Joshua Kerievsky 3:56
I don't know I guess I don't look to America or something.
Joe Krebs 4:01
You also you also describe yourself as a tennis player as far as I you know what I what I think I can tell is like you're pretty good in in the sport of tennis. Do you see any connection between tennis and agility?
Joshua Kerievsky 4:14
Well, to be quite honest, I mean if we were not recording this podcast I'd my eyes would be glued to Wimbledon right now because Emma Raducanu is an up and coming British star and she's she's she was down to set so she's an amazing athletes but yeah, I love to watch tennis I love I love the tennis is a very mental, emotional and physical game. It really and it's a deeply mental game at a certain point with the pros. They know that a lot of times they all have the same skill level, but it's the mental game that becomes so important and some of the top players even have, you know, therapists or, you know, these psychologists that travel with them. You and help help them because you know, how you think out there on the court makes a huge difference to your performance. I love to watch, watch tennis and play tennis. It's a it's a lifelong love of mine. And I see a lot of analogies between sports and business.
Joe Krebs 5:21
Absolutely. I mean, you're definitely right mentally, right, I most likely did not play on a level as you do. But I used to play some tennis and it's not easy to serve on a match point against you. Right, and, and how to deal with a situation like that. So definitely, there's a there's definitely a mental challenge if especially if it's closed game.
Joshua Kerievsky 5:42
Oh, absolutely. Absolutely. Yeah, I mean, being able to relax, I've discovered is so utterly important, if you can, if you can just not get tense. And so again, that comes back to emotions comes back to the mental game. So I'm not that good. I injured myself too much lately, as I'm getting older, and I'm trying to learn how to play injury free.
Joe Krebs 6:03
Yeah. And we need you injury free in Nashville, because you're going to do the the keynotes, we need you on stage for that. So move all the tennis past that also it's the book is called The Joy of agility, not the joy of tennis. So let's talk a little bit about that. Right? You have a website out, it's called The Joy of agility.com. It's obviously linked to the, to the book, which is currently still on pre-order. So you people can pre-order it, you have anything, just before we go a little bit into depth of what's going on in the book is that when it's going to be published, and for sale, it will
Joshua Kerievsky 6:39
be you know, in print, it will be in print February 7 2023. So you can pre-order it now. And yeah, I'm, you know, I'm really excited about this book, I'm, it took a lot of work, it took it in went in directions that I didn't expect as I wrote it. So it definitely follow a very agile approach to writing. And that means that there's a lot of emergence and evolutionary design, like, you know, I don't pre plan every chapter or every, the structure of the book was not pre planned. Okay, yeah, kind of emerged. And what emerged kind of surprised me, it took me took me completely by surprise. But what eventually emerged, and yeah, we can get into that, but I'm super excited about this book. It's very, very different from most agile books.
Joe Krebs 7:33
Okay. All right. So let's, let's organize this a little bit. I'm curious to hear what kind of detours you had, I think every author out there their property dealt with some corrections in the writing process. But I expect you in particular, to deal with those kinds of changes in a very interesting way, you know, just based on your background, in the Agile community. So what came out as a as a finding where you felt like the book took a turn?
Joshua Kerievsky 8:00
Well, I mean, what I what I started to do, before I ever conceived, the book was simply to to note that first of all, I love stories, I find that stories are the stickiest things around in terms of sticking to your brain, a good story can stick really well, much better. So then like a hypothesis, or some kind of Maxim, or whatever a story or story can be sticky. So I love stories. I've been telling stories for years. And I started a small collection of stories to explain to people what does agility really look like? So I started writing these stories. And whenever I write anything, you know, I put it in front of people as soon as possible. early draft, hey, what do you think? Yeah, this makes sense to you. Anything you'd suggest to improve so I do continuous integration with other humans? Continuous refinement of the language. And so my, my writings go through tremendous amount of refinement over time. But anyway, I started collecting some stories about what is real agility look like? And I'm, you know, part of me is what's driving me is that Agile is not sprinting. Agile is not doing stand up meetings, we've come to some people have come to think that Agile is just these rituals, you know, for the roles. So if you put the roles and the rituals together, you're agile, well, we're not really I mean, there's, there's people that are agile, who never even use the word agile. We don't sprint and do stand up meetings, right? A lawyer could be agile, a surgeon you could be agile, a dancer could be agile. A team of accountants could actually be really agile when it comes to some challenge. Agility is existed for centuries, and I wanted to have highlight what does that look like? I also wanted to deal with a, you know, ongoing question that people have for me, which is, I created these four modern Agile principles. And people say, great, that's awesome. But what did we do? What do we do? You're not telling us what to do. You're just given us principles. So the book also is trying to say, Okay, if you want to know what to do, here's some things that people do when they're really, really agile. And so it's looking at all kinds of aspects of what people do when they're agile. However, it's not specific to any given profession, or any given human endeavor. I covered live stories about biking, I have stories about entrepreneurship. I have stories about you know, psychological safety, or one fellow who created a bunch of balloons, water balloons that could be created in seconds. I mean, there's all kinds of stories that ultimately point back to different aspects of agility.
Joe Krebs 11:04
So how do these six mantras that you outline in in your book, so the whole book is organized around 6 mantras? How do they connect to what you just said?
Joshua Kerievsky 11:15
Alright, so first of all, I didn't know I'd be writing about mantras, identity at all that was, that was where the emergence came in. So what happened was, I started writing stories of agility. My favorite stories, and that grew, and grew, that pile of stories grew. And I started to realize, oh, you know, this could be a book. So at some point, I had, I don't know, 60 stories, 70 stories, maybe, maybe more, and I showed them to a book agent. And he said, Well, this is great. But that's not organized. I mean, it's, it's got to be organized, which I knew I just hadn't done that yet. So I was like, alright, alright, alright, it's time to start organizing them. How am I gonna do this? And I'd have to read the read the stories very closely again, and think well, what, what is this really trying to say? And of all the stories I wrote, some of them are personal stories. Some of them are stories of others that I admire. But there's a coach from UCLA. He's he's passed away, but his name was the coach John Wooden. And he's considered one of the greatest coaches of all time. And he's written books, many books have been written about him. There was some stuff that I encountered in writing my book that I did, I did a lot of research on what and I'm continuing to research wouldn't I'm actually reading a book, written by Kareem Abdul Jabbar, the famous, I think seven foot two basketball player from Harlem, not too far from where I grew up. And he wrote a book about it's called, you know, Coach John Wooden and me. And it's an incredible detailed account of their relationship and 50 years. What I learned there was that Coach Wooden use mantras to help his team to help his players become champions, and that there are certain mantras that are repeated every day, many times per day. So I started to really love this concept of mantras. And one of John wooden's most important mantra was, be quick, but don't hurry. Right. And that was something on top of my mind, so I started looking again at the categories of these stories, where does each story fit and it's a lot of them started to clearly fit into that category. Be quick, but don't hurry. For example, Tom DeMarco, is well known for many, many boxes, an industry icon and Guru. And one of his books that I love the most is called slack. It's not about the tool. Slack was written long before that, but it's about having time. Having slack in your schedule, having time spaces in your schedule, to just think to just learn to slow down a little bit maybe to improve to get faster ultimately, and that's that's a story it's like, well, this clearly belongs in that area. Don't be quick, but don't hurry. So you know, basically the stories started to coalesce into different sections, which I started to see as mantras be quick but don't I didn't make these up right. A lot of these are mantras that others said so be quick but don't hurry to John Wooden-ism. Another mantra in the book is drive out fear. And that's, you know, W Edwards Deming, very, very, very famous for saying that that the leaders job is to drive out fear. But a lot of the stories I have were about you How do you drive out fear? How do you do that? What do people do to make that possible? So, over time, you know, the mantras evolved, you know, a few times I'd be like, Okay, that's the mantra. And then a couple months later, I'm like, nope, I gotta revise it. It's slightly different. And there's more to it than that.
Joe Krebs 15:18
So, six members, you have like these grouping categories where you organize your stories in?
Joshua Kerievsky 15:24
That's correct. That is correct. Yeah. So now that all of that exists, I look at that. And I say, wow, you know, that's like the DNA of agility right there. If you can practice these mantras, you will get closer and closer and closer to being genuinely agile. And I'm not talking about following the framework, following a manifesto, following someone's process. This is about actual genuine agility, which is being quick, easy and graceful, and your movement or your bearing, or being quick, resourceful, and adaptable in life and challenges and how you approach things. And those words, I all of those words, I think of it this way. It's like this is like a wave just came over you I just set a definition or two. I don't think I think any given definition has to be explored. You have to get deeper into it. What does that really mean? What does what do we mean by quick? And what do we not mean? We don't mean hurrying. We don't mean rushing, we also don't mean going slow, in a bad way, like, add slow, or you're just like, oh, my gosh, this is taking forever. You know, imagine ordering something at a store where you're like this should have come out by now. You know, you don't go to a drive thru and wait an hour for the for the food to be delivered. Good, slow, there's bad slow. So there's what's the difference between good and bad? Slow? Sometimes you got to slow down.
Joe Krebs 16:50
Yeah, what was interesting, what you said, I think is something along the lines of this is not about you know, sprinting at agility, right, or the daily standup. The word sprinting, in particular, how does that relate for you in terms of quick and hurrying?
Joshua Kerievsky 17:06
Well, I think it's, I mean, you know, it's, you're trying to get to a point where the John would would call it quickness under control. So he would have a freshman from various high schools around America, who are champion freshman champion players in their high schools. Now they get to university now they're at UCLA, a premier school. Well, guess what, they're not going to get to play much. The veterans would play the the the upperclassmen would play the most, even Kareem Abdul Jabbar sat on the bench as a freshman. But the thing that they learned was not to hurry, and most of them hurried. And most of them would just do things in an uncontrolled way. Wouldn't wanted quickness under control. So he first had to slow them down to the point where they can understand the wooden style of playing, then they could practice doing it faster and faster and faster and faster. Right. So both elements, were there slowing good slowing down to learn, and then speeding up speeding up speeding up through tons of practice.
Joe Krebs 18:15
It's very interesting. In the reason I'm asking for that is because I myself, like recently I've been working on on and things like that, where we'll be like, removed the time box and just like work on something, see the results. And, you know, I refer to that as the, as the Kata, but it's very similar to what you're describing it. That's why I'm so intrigued by this, right, because there's a certain speed to work, but you know, it doesn't mean necessarily or cutting corners, or, you know, cutting quality obviously, that is also an important factor. Another mantra that is goes along the line, and I'm intrigued to hear what you say about that one is grow a solution by starting minimal and in walk and evolving. Why is tha a mantra? I think that resonates very well with somebody who has read the Agile Manifesto, for example, I think that just goes into spirit with that. But what did you find in your research on that? And why did it become a mantra?
Joshua Kerievsky 19:17
It's, it's one of those mantras that I struggled the most with in the book because I thought is this is this too specific? Is this not really the level of a mantra, but ultimately kept it in because the stories in that section are so powerful, and so helpful, I think, to to understand, you know, the doing of agility. So, let's just let's just go back to tennis for a second. Let's say you're brand new to tennis, love to. A good instructor is going to teach you the minimum necessary to just do a forehand or backhand a minimum. They're not going to get into all the nuances of bending your legs. This for bad or, you know, they're just going to try to get you initially to do the the basic strokes start minimal and evolve from there, right? So you could look at it from the point of view of like learning a sport, or let's say learning an instrument, right or I, before I moved in my old house, we built a shed in the back. And, you know, basically made a big mistake, it was a costly mistake. What we should have done was great, we're gonna build this shed in the back, not sure where to position it, but we kind of think over there would be a good place to put it. And it would have been great to then say, Great, let's go buy some cardboard. And let's erect the shed the shed with some cardboard and see what it feels like. Because that's a cheap, quick stock minimal solution to feeling out and we didn't do that. Because I make mistakes all the time. Right? I'm I'm not a pillar of agility, I make plenty of mistakes. So yeah, they went ahead and poured concrete, and then started to erect some of the wood siding. And then I realized, wow, this is blocking one of my daughter's views. No, and I knew it would, but I didn't realize how bad it would look. And as soon as we saw that, we're like, oh, no, no, no, no, no, this is not going to work, we have got to move the shed over so that it's in between these two windows. And $3,000 later, they moved the shed and we could have, we could have failed faster. And we could have learned faster with just a quick and dirty cardboard version of this right? To get a feel. And then you know, if you go back to like famous architects like Christopher Alexander, who wrote thw books, the pattern language and a timeless way of building. That's what they would do. They would put cheap, quick stuff up to see what does it feel like? How is this going to work for you and and then evolve, it evolves. So evolutionary design is at the heart and soul of that mantra, start minimal and evolve. It applies to all kinds of things.
Joe Krebs 22:14
Yeah. Once you pour cement, right.
Joshua Kerievsky 22:18
Yeah, that's.
Joe Krebs 22:21
foundational. And then that's, that's where the headaches begin. But, you know, as you said, like some architects might even keep the structure up for a while and just live with it and feel over time. Right. So because your perception might change.
Joshua Kerievsky 22:36
Yeah, exactly. The same same applies to an article. Here's the quick, early, rough draft, or even the idea for the article, what do you think, give me feedback? Yeah. You know, just being able to learn faster, cheaply, right, cheap, quick experiments. That's a key. That's a key to agility. And it's a key in all sorts of endeavors. So, you know, that that ended up in the book,
Joe Krebs 23:02
if I will take you back to Tennis, as an example. So it's also motivational right to start with a forehand , backhand, simple routine of some sort, and then build on top of that, but you have the feeling of success as a player or as a learner, which is obviously very important in that step, rather than getting frustrated with an information overload.
Joshua Kerievsky 23:24
Yes, absolutely. Absolutely. I now on the counter side of this, though, I will say that a lot of times, some of the biggest successes we've had with teams in the software field has been where we bring them into, and I think they, these are willing co conspirators people that want to actually try this. We've talked to them, like do you want to do you want to try like real full on agility and software development? No, yes, no, if they want to do it, and they're willing to try it for, let's say, three, four or five months, they say, Great. Here's the experiment. We're going to be doing all of these awesome practices we've learned from continuous flow, to story mapping to continuous integration and continuous deployment or continuous refactoring. All the good stuff, right? We're going to do it all at once. We're not going to be like, Hey, you're so immature, that the only thing you could do right now is learn this one practice. And then maybe six months later, we'll have another practice. That's very slow. That's right. So there's all kinds of approaches to being agile. I don't I don't claim to say there's one way. I don't think any framework would never want you to do that, too. Frameworks are meant to be adaptable. That's right. But ultimately, you're trying to get to your outcome. You're trying to have success, and there's many ways to achieve success. And it's not just like one way. So
Joe Krebs 24:51
it's the art of coaching, right? That's why it's the art of coaching.
Joshua Kerievsky 24:56
The art of coaching. Yeah, absolutely. Absolutely. You know, I got some inspiration. from Charles Duhigg, he's a Pulitzer Prize winning author. And he wrote The Power of Habit, he wrote, I think it's smarter, better faster. And I think it was in smarter, better, faster, he talks about the Japanese railway system, the bullet trains. And that was a situation where, you know, they, they didn't take their trains and go from like, let's say 50 miles per hour to 60 miles per hour, or 60 miles per hour. And they said, Listen, we want the trains to go 120 miles per hour. And this is the 1950s we're talking about, which seemed crazy, but they said, You have carte blanche, you can do whatever you want to make this happen. Right. So they put this big, hairy, audacious goal into the lab. So the railroad engineers and said, you know, do what you want, but please make this happen. Now, that's, to me that that was defined in the new new product development game in the Harvard Business Review back in the 80s. The article by the two Japanese gentleman, I forget their names at the moment. Because they, they would say, Give a big, audacious goal to the team. And then let them let them manage that give them the freedom to manage that.
Joe Krebs 26:18
And there was all examples like this in the worldwide going to the moon, you know, like the railroad, people can come together and, and group and build a team and, and achieve something outstanding. If there is a definition of that goal. That is really cool. Joshua, I also want to connect a little bit your book in the title of your book and the joy of agility.com. With your talk in Nashville, right? So we kind of do a keynote in Nashville. So first and foremost, I can't even believe I'm saying this after two years of COVID. We're back in person, there is a conference in Nashville.
Joshua Kerievsky 27:01
I'm excited. I'm also a little apprehensive because I don't want to catch COVID. But, you know, I think I'm there to I'm really there to deliver this important message to the community. I feel like again, I mean, I worked so hard on this book, I can't begin to tell you how hard I worked on it. And I feel like this is a message that the the Agile community desperately needs. There are tons of people that have abandoned agile, because they view it now as this horrible project management, rigid thing that basically hurts them more than helps them. There's a lot of, there's a lot of there's a lack of joy, let's just say in a great deal of agile implementations. And I could easily have focused on that, you know, I mean, I could have easily spent the day in a row wrote a book about how bad things are. But that, to me wasn't very helpful. I wanted to focus on what excites me so much about agility. What brings me joy, from agility. And that, that's, that's the focus, of the book.
Joe Krebs 28:06
Great, and we're going to be there in Nashville, I think there's going to be a good gathering. For me, personally, I'll be there as well. It's like the starting point of agile conferences, again, being in person. I know, there have been other conferences in person. But just personally, for me, this is like the starting point again, and I hope and I gonna fall deep in fall, again, with more cases and cancellations of conferences. So I hope there is this is the beginning of something good. Again, so we can, especially in the Agile community can regroup again, see each other meet, collaborate and do all the great stuff. So maybe that's the starting point.
Joshua Kerievsky 28:45
That'd be wonderful. It's going to be wonderful. And I'm really looking forward to it. I think, you know, the, the chance to get together with like minded folks is just there's nothing like it. The the the Zoom has been great, and the other video platforms, but there's just nothing like getting together with like minded people and having productive conversations and, you know, so forth. So I'm super excited. I've been working extremely hard on the keynote as well. We're doing a lot of work on sort of a way of assessing agility, then we'll be having some fun with that during the keynote. So I'm excited about that. And yeah, it's for me, it's gonna be the second time I've given a keynote. So for anyone who has not given a keynote at the Agile conference, you might be hating me right now. Why is he getting a second shot at this thing? Well, I put myself forward and said, I've got something really important to say and I have this new book and I really feel like this is a key the key thing for for our community to hear. And, you know, of course I'd love to sell some books, but you know, I really love agility so much that it's not about Money for me. It's never been about money I could have been certifying people. For years we don't, we haven't certified a single soul. We are big into training, but not into certifications that don't have any merit. So, to me, it's not about money. It's about the joy of agility, sharing that joy. And that's free. There's no payments involved in that learning, you know, to to succeed over your obstacles and challenges by being more agile. That is a wonderful thing.
Joe Krebs 30:32
Right. And that is the subtitle of your book, how to solve problems and succeed sooner. And that goes right along. What you just say. Now, just at the end, Josh, what is this? This has been great, a great conversation. Thank you. I know you pointed out that this was hard work to put this book together. I hope it was not too hard and too painful so that the next book will wait for another 18 years. So anyway, I do want to thank you for spending your time and sharing your thoughts around and as some people got already two, three stories out from you. There's plenty of stories in your book. Some folks will probably get some other stories in the keynote in Nashville. I just want to say thank you and point everybody one more time to joy of agility.com. That's the website for the book, and actually much, much more.
Joshua Kerievsky 31:26
Thank you so much, Joe. Yeah, it's been an absolute pleasure talking to you. And I look forward to seeing you in Nashville.
Joe Krebs 31:33
Great. Thank you. Thank you for listening to Agile FM, the radio for the Agile community. I'm your host show Gramps. If you're interested in more programming and additional podcasts, please go to www agile.fm. Talk to you soon.
Transcript:
Joe Krebs 00:20
Welcome to another episode of agile FM. Today is back to Agile FM show just as we spoke in, I looked it up may 2020. Already on this podcast. And last time this was interesting. We talked about wikispeed a lot cars. And you were sitting, I remember that vividly you were sitting in a Tesla, we were doing the recording straight from a Tesla. And today we're going to talk about Tesla. What's the irony of that after two years later? This is awesome. Welcome back.
Joe Justice 00:53
What an amazing full circle. Joe, it's my honor and privilege to be collaborating with you and your entire audience again, today. Thank you so much. In the meantime, I did work at Tesla and operate the Agile program at Tesla. And I learned a lot. And I'd be happy to update the community on what I learned while working in the company.
Joe Krebs 01:16
Yeah, so I just recently traveled to to Austin for for business reasons and took a cab back to the airport. And I kept traveling and traveling and traveling on that highway. I don't know what number that was. But I was still passing this new headquarter of Tesla just buildings in under construction right now. But I believe somebody said it's the biggest building in the country or something like that, and in square footage or something. And it's obviously under construction. But it is massive. And it's impressive. And it shows something about growth of this company. And I want to talk a little bit about what supports that growth, I want to talk a little bit about what's the agile mindset of of Tesla, this company is so on fire that sometimes it feels like it's not transparent and what's going on. At least that's my perception, right? And you're gonna debunk this because it is actually very transparent.
Joe Justice 02:10
Bizarrely about transparency, I have not ever worked in a company as transparent as Tesla, except when I ran my own company, wikispeed, wikispeed was the accounting was public, anyone could join anywhere in the world, they could simply join the company, and they were as inside as anyone else. Tesla is the closest to that I've ever seen. And that from a company with 110,000 employees and 500,000 suppliers is shocking. Most people think by the time you have more than seven employees, you probably can't afford to be transparent anymore. And Tesla has destroyed that. For example, when Elon gives what do I want to call it? I guess marching orders. When Elon says this is important. He does it through Twitter. That's how the employees see it, too. That's why it's so important that Twitter be a public record where you'll be able to say what you believe is important whether or not everyone agrees, which is Elon stance, Elon stances, Twitter should be the global Town Square where anyone can say what they think is important and not be censored. The reason why well, well, one of them is that's how Elon uses it for the business. When Elon wants to say, here's the update of the master plan, He does it through Twitter, like employees don't get it sooner than that. They look at Twitter, too. So the company is truly led in the open.
Joe Krebs 03:42
It's very different to other companies out there, right where you have to get a legal approval for going on Twitter first.
Joe Justice 03:48
Yes, yeah. Where it's you get tweets, where where other CEOs, for example, try to sound hip and cool. But it's gone through a PR department. It's gone through marketing. It was part of a quarterly release plan that was planned six months ago. And it's completely different in Elon's case. Truly, that's when the employees get the information as well.
Joe Krebs 04:16
Unbelievable, that is fantastic. So what he was or what Tesla is in the news very lately is working from home for working from home being you know, being removed, or at least like trying to be reduced to coming back to the site. Does that impact you being in Hawaii at all?
Unknown Speaker 04:34
Well, I'm no longer an employee at Tesla Oh, yeah. The mechanics under Elon statement of you need to be back in the office work from home will no longer be accepted. except in exceptional cases and you need to make the case to Elon. There are maybe two interesting topics here for for this audience.
Joe Krebs 04:58
Yes.
Joe Justice 04:59
One is order, so I'll get it out of the way first. And that is Elon saying except in exceptional circumstances, and you need to make that case to Elon. Elon has a very effective business strategy, in my opinion, called, he calls it doing your chores. And what this means is their chores, a business leader, especially the CEO, but anyone in the business has to do every day where the company suffers or even fails. And that is, for example, you yourself, viewing what are the exceptional circumstances to work from home, not delegating that to someone who might not have your same point of view right now. Elon is so deeply involved in the company that Elon does Elon's chores every day. It's these types of conversations. Okay, talk to me to Elon, why do you think you need to work from home and no one else should? Do you understand why I believe it's important to not work from home. So that's the simpler concept. Do your chores phenomenally effective? Most leaders delegate that stuff? Elon doesn't. And many, many years in this has made Elon, the very effective manager. by some measures, Elon is the most effective manager, leader, executive of all time, by some measures. Objectively, I mean, CEO of five companies simultaneously, they're all top profit, all top impact in their fields globally. This is a new phenomenon. Nonsense, possibly the Yellow Emperor of China has this occurred. So the do your chores, ethos is part of it, then the larger issue is, why not work from home? What's the issue there? Or what's the advantage to not working from home? Why is this? Why is this so important that in Elon is limited? Right? seconds on planet Earth? Elon is investing many of those seconds convincing, people are demanding that they cannot work from home. Why is this essential to the success of these Musk companies. And the core of it is Tesla makes physical products. If you're developing software for Tesla, if you're doing procurement for Tesla, if you're doing any resources for Tesla. The goal is to be within touching distance of the machines and the materials that you're supporting. Will wait what does that mean, if you're a software developer, if you're developing autopilot, the assisted driving functionality for Tesla cars. And it's also used all across the other Musk companies for other areas, right and it has artificial intelligence stacks is part of it, etc. Like auto labeler. Your goal is to be within touching distance of the machines that are etching the circuit boards for the autopilot computer, or the machines that put the autopilot computer into the cars when they're sold. Why the feedback loop of being directly in the point of production accelerates the creative process. Yeah, it also lets you physically mob if you were writing only a virtual product. If your product were virtual, like let's say you make an app for cooking recipes, yeah. And it's completely virtual. You could be remote. No, Tesla does not actually have very many really virtual products. Even the Tesla app, which I have on my phone now has a feature called Summon, where you can call the car to you physically, it will attempt to come pick you up if it needs to leak do so. And you can open the trunk honk the horn, vent the windows, you can make the car dance, plays music and wiggles the windows up and down like an ocean wave. It's actually very entertaining in my opinion. And developers are making changes to robots to factory floor automation, to procurement automation, and to the cars automation and car sensor suites. And the cars are getting 60 new parts a day. That includes electronics and circuits. So if you're writing something for the Tesla app, you think of course I could do that remote. Well, it also controls talks to the cars. And if the cars are getting 60 new parts a day, every day you are updating your code to be working well with the cars are checking at least making sure your known stable interfaces are still valid and your test cases are still valid. And you're checking information security going back and forth to the car in the app. That is way faster if you are within touching distance of the car's manufacturer. Now there's a last part of this. I've been working with them the mob mentality who advocates mob in primarily software development, but I've been using mob for hardware development and hardware engineering, okay and bringing peace to them. And they propose and have some very intriguing data to back it up. That if you have five people 4, 3, 2 people, and you have a choice, they can work alone on different pieces of work, or they can work together on one piece of work. The quality is so much higher that the overall speed is far higher, because of the reduced time in bug tracking, bug finding and bug fixing and bug deployment. And the data appears completely sound. It appears mob is dramatically faster when you accommodate time to find, fix and deploy bugs. And people report higher job satisfaction and higher pace of skills improvement. Yeah, so if you could work remote, even in a remote mob that would be next best. In person mob has an even higher rate of learning is what they're tracking. Yeah. But it isn't. Really virtual product in person mob has advantages, but virtual mob wouldn't be next best. And of course, never work alone if you truly want to be innovative quickly.
Joe Krebs 11:18
Yeah. While this is. So I had like, a few years ago, actually, it just reminded me I had Woody Zuill on my podcast, to go into the, you know, like, I don't know if he wants to be called creative, but definitely one of the leading causes of mob programming. So that's very interesting. So that is an aspect that is also happening at Tesla and is obviously in person. And that's one of the reasons why Elon Musk is promoting in person because of mob. And then the next one would be virtual mob. And that's I think I, you know, using a lot of these tools, like zoom and etc. You know, they're great for some meetings and training, etc. Right. But I, I don't know, just by evaluating this, how effective it would be for mob programming, right. Other tools come into the mix.
Unknown Speaker 12:08
Any desk seems to help a lot, any desk through any video chat system or service? Yeah, Zoom allows breakout rooms, you can dynamically re partition sub mobs. So if you are in a larger group, like I was at Tesla, often Around 50 people, sub mobs can use Breakout Room functionality at will to form task specific mobs from larger group. And that works well. It is even easier in person, you're never waiting for a tool. No one's screen isn't sharing. I mean, if you listen to an audio recording of virtual development, remote development, there is so much waiting. Yeah, of my microphones not working? Oh, you're muted. Sorry, my headset battery died. We missed the last 20 minutes. And you just don't have those issues. You have different issues, but not those issues. Yeah, and you're in person. If pace of innovation is the only thing that matters in the long run in-person mob is the only way you would choose to work currently.
Joe Krebs 13:18
So and this comes from somebody you know, who's obviously promoting in person work, who is for many, many people on this planet on the most beautiful spot on earth in Hawaii. So you know what the chances are, if you're promoting this means you're leaving the island at some point.
Joe Justice 13:36
Here is the challenge. It is easy to talk about work. And you can talk about work remotely, that's fine. You're not actually doing work. And if what I'm doing is reflecting on what I learned at Tesla and writing books, creating podcasts, delivering keynotes remote trainings, that's fine. But I'm freaking out. I guess this is a version of what people would call Island fever. Maybe this is entrepreneurial Island fever, because I haven't built anything. Yeah. And if you actually want to create something new, create something innovative, not just talk about work. You've got to be there. You've got to physically be there. So I remodeled my condo, so I can build something,. But I'm currently shopping for factory land all around the world. I was looking in Japan yesterday, I was looking in Germany the day before. I have a small piece of factory land on the mainland United States. And absolutely my goal is to get back into product development and product production. And for that you have to be co located. And in fact, if you want to be very fast, you need to live there. You need to actually sleep there. So you have to think Where's someplace that I can go not have much overhead not have much slow down and living here,
Joe Krebs 15:04
right. But it makes total sense from a. And obviously, we can only speculate what you would you would be doing with all the land, you know. And obviously land is not something you could easily get in our way so I can see why you're exploring other territories. Tesla just won't come back to that one time because what's also fascinating is to hear that you talk a lot about agile you are a certified scrum trainer, right? Is scrum a thing? Or is it more like agile a thing is, I would my guess is correct me if I'm wrong, they would be agile, but and that the organization is thinking about change and innovation rather than a specific process. But what's what's uh, what are we did the teams look like is there like a variety of things is, you know, Spotify is very transparent also how they work. And these things, just curious. Scrum is way too slow for what Tesla is doing. But scrum has a beautiful place in the world of business. So most companies around the world have annual or yearly or longer budgets. And they allocate the majority of the finances at least at a coarse level, sometimes even at a fine detailed level for a year or longer. That's normal. That's how most companies around the world allocate budgets. That means if you're going to respond to change, like a chip shortage, or a supplier change, where a new product in production, responding to customer feedback, you would need to politically advocate for re allocating capital inside the budget cycle, which is costly. You have to make presentations, you have to make reports, you have to make friends, you have to be congenial. It helps if you're handsome, you start to get politicking, which is a massive overhead most companies have about 60% of all headcount dedicated to that, yeah, to allocating politicking and shaking hands appropriately and respectfully making reports and not actually building the product. Well, it'd be phenomenally more capital efficient. If you had near 100% of staff directly improving the product like sweating, welding, programming, nearly 100% of staff, which is Tesla's goal, because of the capital efficiency involved. That means you can't take these people's time to be negotiating for budget change. So you need another mechanism for budget to change. That's very fast. That's very nimble, right? Okay. So Scrum is a awesome step towards that, what what scrum does, from my perspective, as a certified scrum trainer, is it introduces 30 day or less budgets, we call those sprints. It's a funded release, including testing, including design, a lot of companies don't do this, even though it's part they say they're doing Scrum, and don't actually have 30 day or less budget cadences, because that means disrupting their current budgeting cycle, I get that step by step, please get there. But part of the goal of Scrum is to do that, and you won't be able to move past scrum until you do. So that is the hard work some companies still have to do. It's an interesting thing. Once you've achieved 30 day or less budget allocation, and Scrum has an accountability just for that called the product owner and maximizing the value of those iterations and a list of what those are called a product backlog. And as long as the product backlog can change with feedback at any time, you have increased your agility. I'm actually predates agile in my definition, it's actually not an agile method, but it moves you towards agility. If you actually do 30 day or less budget cycles, and have a mechanism to change what the next budget cycle is at any time called the product backlog and some coalition to do it in scrum it's accountability called the product owner. Let Scrum. If you're already at 30 day or less budgets, and you're already able to produce product within 30 days, test it certified, give it to customers. That's huge. Most companies are not there. Most companies need Scrum. If you're already there, you're 30 days or less. Now the five events of Scrum, the three accountabilities of Scrum, the three outputs are artifacts of Scrum. Those are overhead now, those are now slowing you down. And that is where Tesla is. Tesla is at 60 new part introductions a day and 61 or more part deletions a day so the total part count is going down to keep serviceability becoming simpler and warehousing becoming simpler, continuous aggressive simplification that you there is no time to do so. sprint planning, much less Scaled Agile Framework which is even slower than pure Scrum, iteration planning, big room planning, there's no room for that in any of the Musk companies. Now there's room for that in a lot of companies. Yeah, if a company has an annual longer budget, I will recommend Scaled Agile Framework to help them get to quarterly releases through the train system and bigger and planning. Once they've accomplished that I'll recommend cross functional Scrum teams that manage their own dependencies inside to get to 30 day or less budgets and releases. Once we're less than 30 days, you get, you're attempting to do what the Musk companies are doing, especially if you've gotten under a week. You can sort of keep scrum useful down to a week. Less than that, it's actually just silly, you can make it work, but it's not adding value. That is where you do what the Musk companies are doing. And you actually shouldn't call it agile anymore. Because the Agile Manifesto says we're going to allocate budget, we're going to release product with customer feedback from a couple of weeks to a couple of months with a preference to the shorter timescale. So if you're past a couple of weeks, you're past agility, but I don't know what to call it. So I still call it agile at Tesla. In Tesla, there was not a name for it. There was not Yeah, so what what would it look like? Is it like Kanban-esque? Or is it like, with like, teams that just like totally self manage? building their own way of working? Is it something that results out of the mob? What is what would you see there on the ground?
Joe Justice 21:37
It is not exactly Kanban. It's like combine if you had just one column just doing column, so like a focus. But someone who is familiar with Kanban, and WIP reduction and flow theories would be feel very at home. Yeah, and so but it's simpler than Kanban. It's like combined with one column. And it's a lot like open space. So for those of us who attended the global scrum gathering Denver, which was just last week, I don't mean to make this recording sound so old three years now. But I was I actually it ended yesterday, closed yesterday. Much of that conference, as are many agile conferences was run with a technology called open space, where people propose agenda items self allocate to which agenda they want to go to. And they use the law of two feet to change sessions at any time. They can also be a butterfly or a bumblebee. And these are actually very valuable roles. As silly as they may sound, depending on what is useful to you. Tesla does not call it open space, they actually don't name it. It looks a lot like open space. Okay. So whether you're a software developer, or a product designer, or a manufacturing engineer, or a manufacturing line worker, which by the way, you are all of those things. I mean, everyone does everything. I don't know if I can really explain that without people doing it. But it's, it's true, no matter what you were hired to do, you are going to be lifting 20 kilograms every day, putting metal into robots mixing paint, you are going to be working with CAD, you're going to be working with procurement software, you're going to be working with a lot of AI software, no matter what you were hired to do. So you walk into the company, and you are in the factory, no matter what you were hired to do, you enter the factory, and it's 12 hour shifts. So in my case, I would come in at 5am. Actually, I'd often come in at 4am. But that's another part of the story. For now, let's say your shift starts at five. So you're already there. You're at 5am. And you walk up to well, everywhere in the factory are these monitors, they're usually suspended from the ceiling, but they could be coming off pylons. They're all around. But most of the time they're above you just above head height. So you almost hit your head on them. And that's important. You can see them easily. It's also available on your phone. But you don't want to have to get your phone out to check these things. You look at them all the time. And these boards did not have a name. I have since named them. And I talked about these and I teach them. I call them justice boards. I've named them after me. So they are justice boards. What these boards show you is what are all the funded projects like what is Tesla spending money on or SpaceX? When I visited SpaceX, it was the same what is this company funding money on right now this second, these are real time they're driven by Tesla's vision. So Tesla vision is an AI stack it is not going to solve all your problems for you. But what it's very good at doing is auto labeling. looking at pictures or now video multi channel 8k video now but looking at vision and labeling what's there who Is there this employee? Okay, what robots are there? How much does it probably cost to run those robots? About how many cubic meters of the factory? Does it look like they're using? Okay, well, what's the cost to Tesla to consume about that many cubic meters of factory, and they automatically gas and the gas isn't perfect, but the value is no engineer has to think about it. It's automatic. They guessed the cost of whatever group is working. And then that group has to say, through an app on their phone, what am I doing? And how do I think we could measure the value, so they could say, We're re-programming three of the paint robots, we think we can reduce the time a car spends in paint by 11 seconds, what we're really they don't take time guessing a number, they just say we think we could reduce the time a car spends in paint, which happens to measured in seconds. Well, what the AI then does, is it calculates the value to the company, if the cars spent any less time in paint, without defect rate going up with quality increasing, and without consuming more cubic meters of the factory or more robots, or if you do, it's offset by the time reduced in pain. And that becomes a row on the Justice board. Now what I added, since leaving, I've had a chance to reflect right, so what you can do remote well is reflect you can sit and think is these boards were unique per area, and you could toggle through them on your phone. What I added is to the justice board, is there's a row for each of these. And they dynamically sort up and down based on value ratio, which is more valuable versus expense that's at the top, which is lower value versus expense. Now, when I was in Tesla, we were encouraged to guess at that, and use the law of two feet to go to the highest value product that we thought we could meaningfully add value to or we were really passionate to learn. And we thought it was worth the investment in our learning. And we were asked to make that call, there was no manager allocating yourself allocate like attending an open space conference. And you can use the law of two feet to go to a different work group anytime. And what these work groups are changes in real time because people can propose them from their phones, they can just go to a new area and start working on a new idea and propose it with their phone. Well, now the Justice board dynamically ranks highest value top lowest value bottom. And if what you propose is the bottom, and it doesn't look and you don't have a great idea of how to dramatically increase its value, you should probably use the love to feet and abandon it immediately.Right? You're just managing money.
Joe Krebs 27:44
What a great concept is like, you know, like open space. I've used it, you know, obviously in a lot of conferences and I had Harrison on here one time on on agile FM to speak what an interesting concept, right? But now to use it actually, it turns out so if I would I'm in the development stages, right? So what's super fascinating is like you're talking about about group work, you're talking about crowdsourcing of ideas. I heard recently, I forgot the reference I have to look it up with that is obviously when I heard the sentence somebody saying the next 10 years, we see more innovation that in the last 100 years combined. And, and companies obviously need to be prepared for that. Do you see that as a recipe for it? Is this because you said 110,000 employees, the company obviously grew very, very fast to that number you guys are doing or have been doing things in during your employment, you observe things of crowdsourcing? Do you think that's scalable bigger, if that company is growing? Like what's what's your advice for companies that are possibly looking at that stat saying like in the next 10 years, there's so much innovation, I'll be ready for this. What should we do?
Joe Justice 28:57
There are two enablers that I'm aware of now, one is Musk's philosophy of do your chores. And you have to do those every day. That's what prevents the company from becoming siloed. Hierarchical. Like when you join Tesla. You're given the anti handbook handbook. It's four pages long, and it's been leaked online. And it looked exactly like the one I was given. So I believe that page is completely correct. It's four pages, that is your training. And then safety training and you're in Tesla. It takes four hours total you're in, you get your work shoes, you get two pairs of safety shoes, and you get the AI apps downloaded on your phone which replaced management. So there's effectively no managers in the Musk companies. AI has replaced that which is the idea of digital self management, which moves towards the goal of 100% of staff directly improving the product, which is higher financial efficiency, higher capital efficiency, part of the anti handbook handbook, and it's very few words for agents who will be part of it. So As you can talk to anyone, you can go anywhere, you can do anything. And in fact, if you see a bottleneck, if you see a problem, and you don't go work it, we will hold you accountable for that. So it is your job no matter where you saw it. And it says you can talk to anyone, anywhere, you can talk to Elon, if talking to Elon is the fastest way to resolve this bottleneck, you must do that. And if anyone tries to stop you, they will be fired immediately. This is what prevents the hierarchy. Now, what that means, conversely, is if someone prevents you from talking to Elon, for example, about removing a bottleneck, not because you're like, hey, what kind of pizza do you like, but because you you want to I mean, you could do that, too, he lines up pretty friendly person, but especially about a bottleneck to the organization. Someone actually has to fire them immediately. And so Elon actually has to check. Is that happening? Are these words still what is running the company? So that's part of the do your chores, if you are in the position of deciding who gets paid, who doesn't who's on staff who's not who has access inside the company, who doesn't what we usually call employment. But now in the Wikipedia global contribution model, it's more like who has author access, right? But whatever, if you're in the position of determining that you have to do your chores every day. Now, the second part of that is you can automate a lot of those chores I just mentioned, digital self management, right? This is truly, in my opinion, the musk company's superpower. What Elon is doing is intensely funding, and joining the mobs to automate away wait states. If someone is waiting to ask a manager or an expert Did I do a good job? If we can, that should be an app on your phone and running on the monitors above you. So you never have to wait to talk to another human. The idea of Elon's chores are being automated to the extent they can be. And that is part of the goal is that is what x.com is supposed to be supposed to become eventually, which is a domain of just a Url domain on the internet that Elon owns an aspiration for x.com, which was tweeted to Elon, a couple of years ago, and Elon replied, Yes, that's exactly what I should do. You're right, is for it to become the parent organization that keeps the other companies lean and valuable, and radically innovating. So you don't have the founders departure complex, where when the founder when the founder departs the company dramatically slows down, it falls into corruption falls into debacle and decay. Well, the attempt to solve for the founders dilemma because Elon says, Look, by the time someone is 70, they probably shouldn't have a job, their brain is corroded, biologically, that Intel neural link does what neural link supposed to do. You should not be running a company and Elon says no one should be CEO forever. So you can count that down. That's 20 something else? Yeah, 21 years from now. Until Musk says, you know, I would be incompetent it'd be criminal derived from Elon to have Elon having financial authority of the companies on a day to day basis. So that's the timeline where x.com needs to have replaced most of Elon's chores, if not all with automation. Then you have a rules engine, like playing a video game to keep the rate of innovation high to keep the politics out to keep silos out to keep a flat nimble organization at any size. Elon, because of an aggressive workday, is able to do that across five companies simultaneously, all around the world. So you can a human can you just have to make it your passion. Just like if you love to watch sports every day. And you watched two full sports games everyday if you were deeply passionate, and on the weekends, maybe watch four. Well, if your business is that level of passion, even doing your chores, the unfun part of it, then you can scale this you can keep this innovation high so we can continue to have founders and even not founders, even board members who are at this level of performance. However, what Musk is not currently selling, not now, is any of the digital self management. So if you want to compete you better be building your own
Joe Krebs 34:50
This is awesome. Yeah. Joe this is maybe there's somebody listening right now as it's like wow, this is a very open and transparent conversation where and you know in And I want to say thank you for being so transparent. What's interesting is, I have seen some, I think it was somewhere on social media, I have seen you post something, and Elon Musk actually liked it, right? So you got a like, so I hope that people when they find this episode that they also gonna like it right? And possibly vote, vote this episode up. And because they enjoyed the conversation, for the parents out there listening to this, I decided to get my kids prepared for the workforce, and the workplace in the future. What I'm learning is do your chores and work in groups, right, and be able to work in groups? I think that's what I'm hearing when that should be promoted. What you don't want to tell your kids is that hierarchies don't matter. At least until the 18th. Right.
Joe Justice 35:51
Joe uour was hilarious.
Joe Krebs 35:54
Yeah, this was an awesome conversation, right? I love it. And looking back two years ago, coming back to where we started. Two years ago, you did not work for Tesla at that point, and what kind of vision and everything now we talked about Tesla tremendous amount of information, and that is fantastic to digest and getting some insights. Now with your little cliffhanger on I'm trying to buy land, we can only assume what's going to happen in two years from now. When we speak again. I hope it's not going to take two years to talk about again, but hey, let's see what's what's in the making always curious.
Joe Justice 36:33
Joe, it's my honor and privilege to be part of Agile FM, Agile.FM to the moon.
Joe Krebs 36:39
Thank you. Thank you for listening to Agile FM, the radio for the Agile community. I'm your host Joe Krebs. If you're interested in more programming and additional podcasts, please go to www agile.fm. Talk to you soon.
Transcript:
Joe Krebs 0:20
Welcome to another episode of Agile FM today I'm here with Tracy Defoe from the learning factor, I believe in Canada because your domain name is the learning factor.ca.
Tracy Defoe 0:35
that's right. I'm in Vancouver, Canada on the Pacific coast.
Joe Krebs 0:39
Fantastic. Tracy, we want to talk a little bit about a lot of things here today, we want to talk about Kata. We want to talk about maybe bring a little bit order into the various kinds of terms that are floating around and getting possibly the Agile community a little bit, you know, warmed up to Kata thinking, and most importantly, where they can go and you know what's out there because you are not only a community builder, you are building
community builders, right. So there is a lot going on in your in your work before we get started though, because I myself have been working a lot lately. In recent, let's say 12-24 months on something that's called the Agile Kata that is not the topic necessarily of today, even though we could explore that, right? We're really talking about the core of the Agile Kata, which is the improvement kata, the coaching kata things that were published a while back by Mike Rother. So just to give it a little orientation here now first Tracy, the learning factor. Just curious, your company name what is the learning factor is somehow related to Kata and Kata thinking Lean thinking.
Tracy Defoe 1:57
No, the learning factor greatly predates when even my learning about Canada but my background is in education. So I have a master's degree in adult education, curriculum actually an instruction. And so I was doing I've been for a long time been doing consulting in adult learning and I'm actually a specialist in what people learn at work. So most of the time, if you once you've left school 75% of new things you learn, you'll learn at work and I'm a specialist in workplace learning. Particularly I'm interested actually in what you might think of as frontline learning so blue collar learning, literacy, numeracy, technology advancements. All of that took me into of course, then helping supervisors and managers and they're the people who introduced me to Lean and through that. I was in a good position when Mike Rother was first publishing his first book, to get involved in the Kata community here in the Pacific Northwest where there was actually Mike did some of his research here in
the West Coast. So I got to meet some people about 2010. Who helped me get passionate about the Kata.
Joe Krebs 3:08
Yeah, that was the Toyota kata by Mike Rother.
Tracy Defoe 3:10
Toyota Kata Yeah, the original Toyota kata research book was in 2009, I think.
Joe Krebs 3:15
Right? So, and since then you have obviously stepped into this. In the Kata world, you did a lot of coaching. That's my understanding, you have worked with some companies out there also, although on the software side, we might have some listeners right now, on this on this podcast, you might be thinking, Lean and Toyota factoring. There are companies out there that are using this for for other means to produce something different than a car.
Tracy Defoe 3:44
Well, the cool thing for me about the improvement kata and coaching Kata is they're just a really excellent model for continuous learning, and learning together and having a non hierarchical relationship between managers and workers or between the coach and the learner. Basically, we teach coaches to listen and ask questions, and not to tell people what they think the answers are. And that's really great training for anybody who's in a management position or a coaching position,
Joe Krebs 4:18
right. And those two cutters, they really belong to each other. So the improvement kata, the coaching kata, I mean that we're using the word kata a lot, right? It doesn't exist in plural. It's my understanding. It's just kata. But it's these two things that really go hand in hand.
Tracy Defoe 4:35
Yeah, the word Kata is a Japanese word that comes mostly you would hear it from martial arts, but it's used in other things and it has two meanings. The I guess nobody's gonna see this but the I have it on a pin. The Japanese characters mean both the method and a way so it's, it's a way to be but also the way to learn to be and we If we save, you know, everybody always talks about the Karate Kid movie where the guys teaching him wax on wax off. And then that turns out to be the move that helps him win his match or something like that. But also, if you practice the improvement kata, it's a method to learn more scientific thinking patterns, right? So what leaves behind is a mindset. And on the coaching side, if you practice the coaching kata, it leaves behind a kind of curiosity and discipline around not talent. So turning from a command and control kind of coach are telling you no, do this do that to the kind of person who's invested in developing people and seeing other people do stuff. So I think the the Mike Rother, the author of the Toyota kata books always says, It's not about the Coaching Questions. It's not about the improvement kind of steps. It's the mindset and the skills that they leave behind.
Joe Krebs 6:02
Right, this is fascinating. They did improvement Kata is something that reminded me when I started way, way back with something called Scrum in the Agile community. And we often hear in the community. And sometimes I say that to is that Scrum is easy to teach, you know, but hard to do. The first time when I came across the Kata, it felt very similar to that. So it's like that is is it's very simple steps. We don't have to go into the details. It's a great improvement kata, it's four, or sometimes five steps, depending on how you see it right. But what are your What is Your Experience? Why is it that some companies, what are they struggling with when they are trying to use the product the first time,
Tracy Defoe 6:46
the first step of the improvement Kata is to understand the direction or the challenge that you need to go. And an enormous number of companies don't have a clear strategic direction, or a clear business strategy that people know. So that already says, you know, you have the benefit of everybody understanding where they go is that they can align their actions and move together like towards it, and I do my part of that job, and you do yours and we end up somewhere better. So the first step sounds easy. Oh, you know, your your your executive suite people will give you your strategic direction very clearly, and you will understand what to do. That doesn't happen very much. So that first one already, people end up having to craft their own challenge. Or guess what they think based on maybe a statement or a five year KPI or something a ey performance indicator, you know where they're supposed to go. So that's step one. But imagining now we have that, then the second step, which is to grasp your current condition, is to get a good look at where are we now? So it's like, where do we want to be in six months? Or whatever? a month? Where are we now? And that takes process analysis skills, or some way of asking, answering the questions. How is how am I performing over time? What are the steps in our process? How are we measuring it, etc. So there are sort of skills built in to each step. So that's where we going that's the challenge. Where are we now? How are we doing that's during condition, target condition? Where do we want to be in a little while, so usually a week or two. And that, again, there's a bit of skill around having a good look at where we are now and saying apples to apples, like direct comparison, what we want to change how we're doing, that we hypothesize will give us a different result. And it is, I think it is the structures, all of that is before you start experimenting. So you know, you know where you are, and you know where you want to be in 10 days or two weeks, then the next coaching question. And the next step really is to say, what do we believe is in our way, what do we perceive is in the way, and it's very important that they don't have to be factually or data proven to be in your way at first when you list them all down? Because confronting your perceptions is really, really cool. Yeah, you know, like, it's really often people will write down all these things that they think are in their way. And then as you say, Okay, pick one. And then let's work on that one. What do you want to learn about it? What what test or change do you want to run? After you've tried to run the way you think you can run you're gonna see all these obstacles we call them obstacles are things in your way. And mostly, we want to learn about them. So people sort of that part always make sense to people pick something, kick it, see what happened and make a change, run it. And then of course, the last step of that fourth stage is to reflect on what you learned. Right? And this is what Mike always says the writing it down and reflecting is what makes it scientific, because we use that to inform our next step. Step or next kicker, the obstacle. But I find many, many people are not very comfortable with reflection. Like they're, they're literally not used to it. And they'd rather take a swing, you know, just try again, without literally saying what is the data show us is happening? What do our observations show us is happening and what our learning show us is happening? And that's where I think the Yeah, can you talked about them being a pair, I always think of them as a duo, the improvement kata and coaching kata, but it's kind of like a food term for me, you know, they like they go together. And I think that the powerfulness of the structure is partly that it's, it gives you a lot of structure. So you don't there's a lot of room for creativity there. Because a lot of things are held in place. Right? The questions are known, you know, what questions you will be asked, the steps aren't known. And so in between those things, there's time to listen and learn. But also, I think people don't know how to reflect they literally are perplexed that you're asking them, Did you learn anything else? What did you learn about what you thought was going to happen? What did you learn about your process? What you learned about your team? What did you learn about your assumptions? And people are like, Oh, my gosh, she's just keeps asking me this stuff. But in about two weeks, or three weeks, people are like, piling on what they learned, like, they're really understanding that you want to see what they learned.
Joe Krebs 11:33
What I think one point you just mentioned, was like data too. Sometimes some answers to those questions you just said, right, before a newcomer to kata, maybe something like I don't have any answers for those questions, right? Because I haven't collected the data points before. I have no reference point. But I think that's what the kata also takes care of right? It's, over time people want because they know the questions as you said, right, and they will be preparing for those things in a different way. So the kata has a behavioral change.
Tracy Defoe 12:06
Yeah, in a mindset change, but also we It comes with what we call starter kata, or prescriptive tools to use in the beginning. So that you, you are like not leaving anything out. And also the starter kata will tell you like, what is what do we expect to see? We use a storyboard which is like a giant A3. I don't know if you use A3, but it's a giant A3. And is there was derived during my process research from the A3 that he saw at Toyota, and the conversations around the A3 that became the coaching kata. But the, you know, what do I expect as a coach to see in current condition, I expect to see a run chart, a process diagram, some process metrics, how do we know how this is working? When it's working? How do we know outcome? How did it what happened when it was over? And some description of the conditions that this was happening under which we call process characteristics, but the people I have coached who came from agile and I don't know if this is common, or if it was idiosyncratic, had never done a run chart?
Joe Krebs 13:07
Yes, that's right.
Tracy Defoe 13:08
But to teach her how to do the run chart the first week, and at first, she didn't see any value in having each time what was the what was the number and making a little chart, I'm making W's in the air with my hands down, up and down. But in fact, the pattern like once you have some data points, we start to look at the pattern, and what can you learn from the pattern. And making it visual means we all agree, this is what it looks like. And it's it's a simple visual tool, pen and pencil, you can do it in software, but you can also just do it with a pencil and a piece of paper.
Joe Krebs 13:47
Yeah. So that's very interesting. So you have applied this agile kata, we have probably a lot of listeners here from agile, coming from IT groups, not exclusively, there is a lot of business agility. But you have applied these kind of concepts in the context of software engineering.
Tracy Defoe 14:06
I've coached people who worked in software a couple times, actually. And there's their starting positions and their strengths and their habits. Were kind of expanded by learning the kata that gave them a bigger look. But like I said, never seen a run chart before. And it's not unusual in manufacturing to sometimes run into people who have never kept track of how this is performing over each trial in a chart, but that's basically what a run chart is.
Joe Krebs 14:40
Yeah. Very interesting, right. So just come back to my in-coming kind point about the Agile Kata, right? So this is being utilized. And there's like an agile culture, as you know, and it's it's all around and surrounding this. So this is a very interesting thing, and I'm pretty sure the listeners were now make connections between those four steps. You just write to the Agile world because that is really what we're dealing with in Agile transformations, or what people are talking about in business agility. When I , many, many years ago, is probably 20 years ago, when I getting more and more involved in the Agile community. It was a grassroots movement. It agile, right? So everything was like bottom some people did it. And there was like, a lot of polished kinds of things. It was a lot of sharing of experiences, but it has like to have this energy. I'm sensing this in the Kata community too.
Tracy Defoe 15:39
Yes, we always say the Kata community is a sharing community. And lots and lots of people will share their stuff with you or present or help you. The reason I got so much help because I'm remember, I'm just an adult education teacher from Vancouver, British Columbia, Canada, but the people across the American state line in Washington State House ROIC and Mark Rosenthal for two. They were people who were practicing before way before I was for sure. And they just opened their doors to me and how let me hang around his factory and see how he was using it every day with 13 Different storyboards on the go. And Mark taught me what I a lot of what I know about process analysis and how to how to manage the started was up. And board and things like that. And I didn't pay them. They were just community members who said you want to learn come and learn. And I think the Kata has a pretty because we're enthusiastic. And because we see that it's, we say it's a meta skill, that scientific thinking part you can apply to lots of places in your life. And so we're happy to share that with people.
Joe Krebs 16:53
Yeah. And you in particular, right. So I just want to ask, because you're very humble here right now in all the work you do. And in the in the community space, there is even a club. There is a I call it a club, but I'm not invited to. It's the Kata
Tracy Defoe 17:09
Girl Geeks, yes, yes, no, unless you identify as female. We don't ask any questions on screening, okay, but I in 2020, m plus C. So early COVID days, I was contacted by a young woman in the UK, well, younger than me, sorry, Gemma. And she had was trying to learn the Kata and was really confused. And she reached out somebody on LinkedIn said, You should talk to Tracy Defoe. And so she called me and I said I would coach her. So I coached her remotely. And at the end of she wanted to be a coach. But firstly, we really do say in the Kata community, be a learner before your coach. So getting some experience as the person answering the questions, reading the storyboard, studying your own process, studying your thinking and stuff. So we do that first. So I coached her through I'm gonna say maybe it was May, June, July, August, or something like that. And she said, Okay, now I'm a coach. And I said, No. Now you need more practice.
And so we decided to invite some more women into our group, and that group grew up to be Kata Girl geeks, we have a website and a home we meet every Monday, we have members from, oh, I'm gonna say Eastern Europe, Africa, the Middle East, the UK, Canada, the United States, all the way through, like, as many time zones as we can think. And we actually match up people. In addition to teaching people, we match them up for free coaching. So we've had many, many, many coaches and second coaches go through and and we're think we're pretty good at turning new learners into coaches fairly quickly. One month or six months or so for most
Joe Krebs 18:53
people, I'll definitely put the link into the Show page so that people can click on it and, you know, possibly read more about this. And
Tracy Defoe 19:01
I'm not gender centric. So I also have a group for men and women. That which is actually older than kata girl geeks. So it's called Kata school Cascadia. There are Kata schools all over the world. They're regionally based. Cascadia is a term for the west coast of North America. It is an earthquake zone and a biological song. And it includes Canada and the US. And since since we were a group of people in Canada in the US before we became a kata school, that's why we took that name. And we meet every Friday for free with a drop-in zoom. There's two there's one for beginners and one for coaches and we just try to bring the community together. And then we also offer some trainings or conference. We have a conference in July 2022. And we have online training where people can sign up in
and learn We also do some free training. And I will occasionally match people up with a coach if they can't find a coach. So we're just out there trying to build the community. And our mission is to rock people's worlds.
Joe Krebs 20:12
That was the intriguing part. For me when I first really came across the car several years ago as like, I write about it, I found it intriguing, interesting. And then I went on websites, and I learn more, etc. And what's very interesting, is it is this helping to bring people into this topic. And as you said, I made It's the passion I make since then, have been very much here we are. Oh, here we are. Exactly.
Tracy Defoe 20:41
Oh, well, I think that actually started with Mike Rother, he made although he sells a couple of books, he made a lot of material available under Creative Commons. And so following that lots of people who have subsequently created new material or new downloadable things, we offer them under Creative Comments. So they're usable. You can use them for non commercial use. Yeah.
Joe Krebs 21:05
You just use the word online and online help and bringing people together in different time zones. When I looked at some videos on YouTube, about cycle, coaching cycles, etc, etc. A lot of these things were in person in these videos, because they were pre pandemic, what do you think has changed with a Kata? If so, anything with a workplace, the coaching relationship, the Kata itself? Do you see anything in the last few years on the improvement Kata?
Tracy Defoe 21:35
I had? I had the opportunity to remotely coach somebody in 2017, I think. And we were using WebEx. And I'm only laughing because yeah, it was funny. It was terrible. And I actually didn't think it would work to remotely coach because I thought, the body language and the together at the board that this really meant something. But to my surprise, it did actually work. And so we were using, I started remote coaching people then after that, if they asked, there's a lot of advantages to the remote coaching, if you're, if you're paying for coaching, no travel time. Yeah, so you're paying for 20 minutes instead of a half a day, right? Yeah, the other thing is, I think you can have a wide variety of experiences as a coach. So a lot of the time, as you said, within a company, it's your leader, who's your coach. But if you're going remote, you have the opportunity as a coach to coach people where you do not understand their process. And this makes you a better coach. Because you don't give it you can't give advice because you literally don't know enough about it to give advice, you can't give direction, all you can do is follow that one of our categories calls it the golden thread, you can follow the golden thread of logic, across the actions and the things that the person says the improver says that they want to do. And this is like a really great liberation for a coach to not even think about the process. Just think about the learning. Think about the person and how they're doing. So I think we've seen a lot more remote coaching, yeah, for sure, during the pandemic, and
we've also expanded our community. So I wasn't in daily contact with people in the UK, or Sweden or Germany, before the pandemic. But now, some of my favorite co workers are in Ireland, or they're, you know, someplace like South America, someplace where I would not normally think of connecting with people around the Kata.
Joe Krebs 23:46
That is really fascinating. And I feel like everybody can hear you and what you're saying and the passion you have for this topic, from early stages of business education, in our being in the Kata world, and obviously that drives you in all aspects. For everybody out there. I wanted to bring you the topic I wanted to bring Tracy in into agile FM, that everybody can see, even though it's called Toyota kata, this is not only for car makers.
Tracy Defoe 24:18
No, actually the Toyota came for the publisher. Right? Exactly. Mike wanted to call the first book beyond what we can see. Because it's about that on the invisible routines, the managers running in their head and it's about the invisible thinking that the learner is doing. Yeah, but I think his publisher said there's pretty big money in anything we slap Toyota on so they call it Toyota kata
Joe Krebs 24:43
but might be misleading for somebody says, Oh, that is for car manufacturer.
Tracy Defoe 24:48
We're not making cars. I know
We are not making cars right.
Joe Krebs 24:52
So maybe maybe that podcast helped a little bit for people to see you can improve possibly anything with this Kata.
Tracy Defoe 24:59
Yeah, and And we know a lot of people use the kata pattern for their personal improvement too. So, we often encourage people as they're learning to take their first project or their first thing, something that they personally can 100% We always say put their arms around, but something they can't control of. And for that reason, people often do something, not necessarily in their work life as their very first project. And I know that it is you can do it for any any issue or problem or thing you want to improve parenting your relationship with somebody your finances, you want to lose weight, you want to get more active, more creative, you want to get more sleep, we can Kata that stuff.
Joe Krebs 25:42
So yeah, it has, it's great. And for all of those things you just mentioned, the Toyota kata, or, as we just said, improvement, kata does coaching kata together, would make great sense. If somebody is really interested here on Agile transformations, you can certainly try that too. Or just look at the Agile Kata agilekata.org, which is an extension of what we just talked about. And it's very specific to Agile, and we are on agile FM. So I thought it would mention this.
Tracy Defoe 26:10
Yes, yeah, I don't like I said, I've coached a few people who work in Agile, but it's not my world.
Joe Krebs 26:17
Yeah. Okay. All right. So there's two reference points for everyone. I want to say thank you, Tracy. That's Tracy with the learning factor.ca. In Canada, if somebody wants to check out and have a starting point for a conversation with you about Kata. And what you can use, you will
Tracy Defoe 26:34
find Kata Girl Geeks, we have a website and we're on LinkedIn too. If you want to join because you identify as female and you're interested in attending, it's just I want to join I want to join at KataGirlGeeks.com and Kata school Cascadia. We also have free resource board. So you'll find us at KataSchoolCascadia.org Or you can email me [email protected] is where easy to find. And we have a whole big bunch of free resources and videos all laid out for people who are isolated or trying to learn on their own. So we want to Well, as I says on our website, if you're looking for the Kata community, welcome home. So we want people to feel at home and we want them to feel welcome. So
Joe Krebs 27:21
alright, and there's even an invitation to start something there. So this is not just to join. This is also to create something if there is a gap or Yeah. Oh, yes.
So I think you're the things you're doing with the Agile Kata. Marriage are amazing. Yeah, thank you.
Tracy Defoe 27:38
Thank you for that.
Joe Krebs 27:40
Tracy, I want to thank you and everything else will be on the show page of this episode. And maybe we continue the conversation if at some later point in time and see, you know what else is happening in the Kata world? Always appreciate it. Thank you.
Tracy Defoe 27:55
Thank you so much for having me.
Transcript:
Joe Krebs 0:10
Agile FM Radio for the Agile community. www.agile.fm.
Welcome to another episode of Agile FM. Today I have Claire Sudbury with me. She's the queen of questions at Made Tech, we're going to go through what that actually means she is out of Manchester, UK. She is a fellow podcaster. Also in the Agile space with a podcast that's called Making Tech Better. That title implies that we can be better, which is something we want to explore in this podcast, I'm going to share all the contact details LinkedIn, Twitter, how you can get in touch with Clare on the show page. But before we go right into the topic of Agile software development, I think that's where you had to find an umbrella term. That's for today. Welcome to the podcast.
Clare Sudbery 1:00
Thank you. Hello.
Joe Krebs 1:04
Thanks for joining me here to this to this podcast. And I have to confess, for a few episodes, we've been talking cultural topics, leadership topics, sometimes really scrum related topics, etc. This is very different because we're gonna explore the tech space a little bit. You're the host of a podcast that explores these techniques, that leads to better software, better technology, like better products using technology, we want to explore some of those now I have to also confess that my software engineering background a few years ago, I developed it in smalltalk and Java, etc. But it's been a while. So I'm super curious to see what's going on in the software development, what kind of trends we're gonna see, especially around XP. So what is the queen of question do?
Clare Sudbery 1:54
That's a very good question. Well, so I mean, the most obvious place in which I am the queen of questions is the fact that I host a podcast. So I spend a lot of time asking my guests questions. But I also am just a person who asks a lot of questions. I've always been a person who asks a lot of questions. Whenever I'm a pupil in a classroom, I'm always that annoying person who has their hand hand up and is asking yet more questions of the teacher when everybody else is wants to go home. I always want to know more. I always want to understand things in detail. So it applies when I'm podcasting. But it also applies when I'm in technical leadership. So when I'm leading teams, as software engineers, I'm asking how could we do things differently? How can we do things better? Are we doing the right things? Are we even asking the right questions? So I'm asking questions about questions.
Joe Krebs 2:46
Meta questions, wonderful.
Clare Sudbery 2:50
But I'm also asking our clients, so we are a consultancy, I work for made tech and I'm asking our clients, you know, what are the problems that you really need to solve, which aren't necessarily always have questions, the problems that they think they need to solve? So it's also about knowing what are the right questions to ask to really get to the nub of the problem, and therefore make sure that we're on the right path to an effective solution.
Joe Krebs 3:15
Yeah, this is awesome. I mean, the maybe today, this just makes you a little bit more uncomfortable, because I have some questions for you. But I noticed that in your profile, and one thing really stood out, and it was the title of a professional software developer, you labeled yourself in one of your professions, right. And it's interesting, the word professional, obviously, right software development as a lot of software, software development going on. But the word professional, there's, there's a lot in there, right? When you get in front of a software developer.
Clare Sudbery 3:48
Now, that was actually the company that I worked for, had simply decided that that's what they were going to call software developers. And I do actually remember thinking that surely that word is redundant, because if we're being paid for it, then we are professionals. And so that was one of those were really it was outside of my control. There was simply a decision that this is what we are going to call our software developers. We're going to call them professional software developers. But it is it's a good question. Because funnily enough, I was talking to one of our podcast guests the other day, Charlene Hunter, about teaching software engineers, which is something that I also get involved in, I helped to train up our junior developers at made tech. And she was saying that in our training program, we are making a distinction between coders and professional software developers. So what we do is we take people we expect them to have learned to do some coding. And then what we say is, being able to code is not necessarily the same thing as being a professional software developer. So if you can write code, that's fantastic. That's a really good start. But just because you can write code doesn't necessarily mean that you can collaborate as part of a team to create a software product with users in mind that is developed for an organization that has a particular direction that it's trying to move in. And that has its own definition of where the value lies. So writing code in and of itself is not necessarily enough to be able to develop a significant software product that has users and will continue to develop and improve throughout its life. So I think that there is a distinction, in fact, being a professional software developer is more than just writing code.
Joe Krebs 5:42
Yeah, I think it's also when I just think about like being professional about writing code, it's it also means to possibly say no to a release, if you don't feel like the quality is there, right or being professional about the quality, you're producing the quality you're observing possibly on the team being pushed into possibly where which you feel uncomfortable space and pushing back.
Clare Sudbery 6:07
But there's so much in there. I mean, I've already my brains going off in five different directions. But there is the there is the pushing back element is something that software developers find extremely difficult. And I think to be honest, most people would, because it implies a certain level of conflict. And what's something that's really common that we see in software development is that we have stakeholders and business owners who have deadlines that they're trying to meet, and they become, and everybody becomes extremely focused on the deadline, and forget about quality because they're in such a panic to reach this deadline. Sometimes those deadlines are genuinely important. Like, you know, a thing, like the obvious trivial example is if you're working with a concert venue, and you're working to sell tickets to an event, well, once the event is gone, doesn't matter what you do, it's useless. So you that's a very hard deadline. And in fact, in the way that our podcast works is we deliver episodes every Tuesday morning at five o'clock, not every Tuesday morning, every other Tuesday morning at five o'clock once a fortnight, and where we are very strict about that. So that means that we have hard deadlines once a fortnight. But most of the deadlines that people are given are actually quite arbitrary, have been decided, based on quite odd criteria. When you look into it, actually, nobody's going to die. If you don't meet this deadline. People become absolutely fixated on the deadline. And often often the sprint structure of Scrum, software development and other forms of agile that focus on a sprint that can also become an arbitrary deadline. That means that people are are putting quality to one side simply because they feel like they're in a rush to meet this deadline.. It's incredibly difficult for people to say, No, slow down, stop, wait a minute, what about the quality, and particularly for software engineers to say, You know what this job that we do requires a lot of brainpower, it requires a lot of thought, it requires a lot of conversation. And if we feel that we have to be sitting at our keyboards tapping away writing code every minute of the day, and any time not spent, coding is wasted. Then actually, quality suffers. And not just quality, but our health, our mental health. But still people find it so hard to say, Whoa, you know what I would like time to think I'd like time to pause, I'd like to step away from my desk and go for a walk or have a meeting with a colleague have a conversation to a diagram. People find it very hard to say that in the face of the pressure to meet the deadline and to look productive. So yes, I think pushing back is is important, but also surprisingly difficult. And I think sometimes people say well, why didn't you push back without taking account of the fact that that is hard?
Joe Krebs 9:22
Oh, it's definitely hard. Right? Just like while you were talking about the deadlines is like, I totally agree with you these deadlines. Sometimes they come out and you when you asked him questions about how did this deadline, this date, have something come up? It's like, hardly anybody knows how that date actually emerged. But that's the date. Sometimes I have seen dates that would fall on a Sunday. And I was like, what because it was the first of December, let's say, Sunday, let's say are you really planning on releasing on Sunday? No, no, no, of course not. Right. So and but people do think about these deadlines, obviously. Why? Because there's obviously a business reason. Hopefully associated with that, but what I want to explore with you a little bit is the other party just said, and that is the, besides the deadlines to pause to think. And that's something I want to run by you because I might be out of touch at this point. But I'm gonna run this by you. When I worked on software development projects myself. There was a high degree of visualization collaboration among team members, I would say and maybe that is the statement that is either right or wrong, it was we hear from you about whiteboarding electronically or in person, just the idea of collaborating together to for six people solving common, like a complex problem of some sort. I'm not saying that collaborating constantly. I'm not saying there will be lots of modeling or anything behind this, but I'm just saying like, I feel like lately, what I'm observing when I work with teams is more like the coding aspect and more chatter on Slack or, and things like that, less more like face to face to face. What's your take on that?
Clare Sudbery 11:09
Well, first of all, I don't feel like really anybody can necessarily authoritatively make blanket statements about what's happening in the industry, because, you know, I only have my own experience to go on. And that experience, it will be broader than some because I've been working in consultancy for the last five years. So that means that I have been able to see across companies and across teams, so I haven't just been in one context for the last five years. But I wouldn't say that I have observed that as a trend. What I would say is that it is difficult, always always has been. And I suspect it always will be to persuade people that the best way to work is highly collaborative. So the best way to work, I would agree with what you were implying the best way to work is for people to spend time whiteboarding for people to spend time having those conversations for people to take a tech take a step back from the keyboard, and actually stop and talk and think about what they're doing. I think that it has also been particularly difficult in the last 18 months because of the pandemic and lockdown. So a lot of my colleagues have said how much they miss actual physical whiteboards. So now if we want to draw a diagram or have a in inverted commas whiteboarding session, we have to use tools like Miro, which are very good tools. But when you're not physically standing up and moving around and physically moving, post it around, I do think it you lose something, I think there's actually you know, there's something about the physical interaction with things that can really make a difference about how it interacts with your brain. So I do think that lock down has maybe exacerbated a tendency for software developers to want to work individually. And to just want to get stuck into looking at the code and not want to be bothered with having to talk to other people about it. I think that there is, I think we've been encouraged to categorize ourselves as developers of being a particular type of person that likes to have a one to one relationship with our computers and not be bothered to have to talk to other human beings. I particularly when I first started in my career, 25 years ago, I thought that that was the appeal for me, I'll be completely honest, I wanted to talk to a computer and not have to talk to people. I didn't like it when people came and stood at my elbow and tried to have real conversations with me, I preferred it if we could converse via email or, you know, the equivalent of slack. And that was when I wasn't working from home. So it was very easy to have physical conversations with people. And yet, I still prefered to have virtual conversations. And I had to be persuaded and I have very much been persuaded that now I realize now I prefer to I want you know, My ideal is to be in an office with my colleagues, to be able to use whiteboards to have a lot of collaboration, a lot of communication, a lot of time away from the keyboard. But I that was a journey that I went on. And that's a journey that I'm constantly bringing other people on as a consultant. And I think that there are lots of pressures that work against that one of them we've already talked about, which is the deadline. It's the idea that everybody must be productive. It's the idea. It's kind of treating the human beings as though they were components in a factory, that if they're not actually don't actually have their fingers on the keyboards and are not writing code, then they're not productive to this idea that you can measure productivity by lines of code, which is wrong, but it's beguiling. You know, it's you can see why People might think it might be true. And anything that stands in the way of that feels as though it's slowing you down. So it feels as though oh no, if I have to go and have a conversation with somebody I have, I have to go in a meeting, then all of those people in that meeting aren't producing code. So time is being lost. And, and that's, that is a conversation that as a consultant, I have to have over and over again, and I'm not sure that that will ever change. I think that in my ideal would be that everybody realizes that the gold standard is first of all, for for software engineers to be ideally pairing a high proportion of the time or even mobbing (mob programming) for people to regularly stop draw diagrams have conversations for people to give themselves time to think without feeling they have like they have to ask for permission for it to become standard for people to go for walks and give just give their brains time to think for people to know about the for instance, the fact that there's tons of research that suggests that our brains process things in the background, when we're not consciously thinking about them that actually we benefit from having time away from just banging our head against whatever problem it is we're trying to solve. But I don't, I don't know if we'll ever get to a point where that is just the accepted norm. I wonder whether and I have no I don't know anything about your career. But I wonder whether you fit the reason you feel like there's been a change is because this this kind of golden period that you had in the past was maybe just that you were working in an environment where people bought it and had managed to learn those lessons.
Joe Krebs 16:40
Better? Oh, yeah. It was just more like a more visual thing. Maybe it was more common to go to a whiteboard, maybe it was so different at that time to go to a whiteboard, maybe it was more acceptable to say, Hey, I'm gonna go with my colleague XYZ on a long walk. And while we talk, we talk about a complex problem. And we come back with fresh new ideas. Why? Because I think that is, that's just something I took. But that could be just me by walking, and you're definitely closer to the, to the source here. In this case, where I want to talk a little bit about the social aspects of software development to like the pairing and everything. How would you get people to towards more pairing? How do you encourage people to do more pairing who feel like like you what you just said about yourself? Right? When I would be in dialogue with the machine, I'd be the person.
Clare Sudbery 17:33
Yeah, yeah. And the way that I learned which I think is the best way is, is by having an experience of it. Because when I first joined the industry, I mean, I've been in the industry now for 21 years, but there was a gap in the middle of four years. So it's about 25 years since I first became a software engineer. And about 12 years in so about 15 years ago, my math is falling apart a bit at this point. But a while ago, I first heard of pair programming, and somebody mentioned it, and I said, Oh, what's that? And they said, Oh, it's when two people sit together. So software engineers sit together and write the code together all day, every day. And I said, that sounds ridiculous. And it sounds like hell. Horrible. Why would I want to be shackled to another software engineer all day, every day? What if I want the loo? What if I want to make a cup of tea? What if I, what if I feel like you know, and this is something that I never didn't necessarily feel confident to say out loud to anything, anybody other than my friends. But what if I feel like surfing the internet for a while and you know, I want a bit of downtime. And of course, actually, that's what everybody does. And, and I also thought that I have a very individual relationship with with the code, and somebody else would just get in the way of that. And, and then I tried it. And the way that I tried it was by being involved in XP workshops. So this was on my own time, I think the very first time I did any pairing was a day long workshop organized by XP, Manchester, which is where I'm based. And we split into pairs for short sessions. So I think it was something like four hour long sessions. And in each one, we wrote some code and then we threw it away. And then we joined another pair and started again and then at the end, we throw it away again. So those two things, they were very radical to me the idea that we might throw our code away, and also the idea that we might be working in pairs and I was really quite scared because I'm you know, I'm a little bit shy and I was convinced that everybody they knew more than me that they were all much more experienced. The other thing that the other thing that I was introduced to as part of this, the very same workshop was test driven development, which I was also new to, whereas a lot of these people had done it but before, and I just thought, Well, I'm not going to know what's going on, I'm going to expose my ignorance, I'm going to feel inadequate. And I'm going to slow down my pair every time because they're going to know what they're doing. And I'm not. And first of all, I discovered that they were very nice. They didn't mind if I slowed things down, they didn't mind that I asked the millions of questions that I always ask because I always have been a big asker of questions, they were happy to answer those questions. And that actually, a lot of the questions that I was asking, made them think as well as we use to them. And also, I discovered, there were actually things that I knew that they didn't know, which without the pairing I wouldn't have ever discovered. So I would have continued believing that I'm the only person in the world that Google's every other thing. And I'm the only person that forgets the names of things all the time, and I have to keep looking stuff up. And I don't carry an encyclopedia around in my brain, it's very easy to believe that everybody else knows exactly what they're doing. And you're the only one that doesn't, until you pair you don't realize, oh, actually, it's not just you, it's everybody. And also you realize that you there's a lot more value in what you know, than you realize, as soon as you're working with somebody else, and are able to teach them something that you know, then you start to see the value of your own knowledge. And then the other thing that I realized was that I absolutely have a tendency to disappear down rabbit holes. And again, that I'm not the only one. And when you're used to working alone, so I had been working in environments where not only did we not pair, but we didn't have daily stand up's, it was quite normal for you to be given a piece of work and then disappear for several weeks, there might be regular meetings, but they certainly weren't daily catch up's. And you were pretty much left to your own devices, which is fine until you get stuck. And if you don't feel confident to admit that you're stuck, then you get more stuck. And the more stuck you get, the harder it gets to ask for help. And the harder it gets to admit that you haven't actually made progress for a significant amount of time because you're stuck. And it's horrible, horrible, this awful kind of hole that you disappear into. And so that's that's one way in which it's very helpful to have somebody sitting right next to you who can instantly help you. But the other thing is that I mentioned before, which is going down rabbit holes, which is a slightly different thing. That's where you think you've worked out which direction you want to go in, and you've decided on a particular direction. And you actually might start to realize after a while, I'm not sure this is getting me anywhere. But I've started so I feel like I need to finish. It's kind of it's the sunk cost fallacy in miniature. When there's somebody sitting next to you, they're gonna say, What are you doing right now? Why are you doing that? You know, are we and you can say to each other, are we actually going in the right direction right now? Are we doing the right thing? Do we need to pause? And I mean, it's not a panacea, because it is entirely possible. And I'm sure many people who have paired will have had this experience, it's possible for a pair to disappear down a rabbit hole, you can both persuade each other that you're going in the right direction, they'll disappear down a rabbit hole, but it's less likely. And there are more checks and balances. And then yeah, I mean, I could go on for hours about all the benefits of pairing but but the other obvious one is that you share knowledge. So the other thing that was very much a feature of the early part of my career is that there would be people within the company within the team, who knew all the stuff, who'd been working on the product for a long time, who had deep domain knowledge and deep tech stack knowledge of the stack that we were working with. And we're really the only people who could solve a plethora of problems because they were the only people that have that deep knowledge. And that become this heart became this horrible self fulfilling prophecy that we can't ask that man over there for help, because he's too busy doing a really crucial job that nobody else can do. And he doesn't have time to share his deep knowledge with anybody else because he's too busy fighting all the fires that only he can fight. I just realized that I said he because at the time, I was the only female software developer on the team. But of course, it doesn't have to be a he. But, but you know that business of not being able to share knowledge goes away when you are regularly in the habit of pairing that there are nearly always two people who've had their eyes on any one piece of code. So there isn't only one person who knows how it works,
Joe Krebs 24:54
as opposed to knowledge sharing where, people have purpose when they come to work. They want to learn they have a career path too, it's not like, they feel like, Hey, I learned something. Today I went to work, I learned something from a colleague, I got a new, you know, it could be a trick with a tool, it could be learning something about how to apply patterns or something like that could be anything that somebody will take home with them, it's this, this was worth worth spending at work and appearing, definitely encourages there.
Clare Sudbery 25:26
And there's that lovely moment where you use a particular keyboard shortcut, or you use a feature of an IDE that your pair doesn't know about. They say, well hang on a minute. Oh, is that? That is cool. And you know, the amount that you learn as a result is fantastic. And I've been reminded of this recently with the podcast, in fact, because when we started making the podcast, it was very much my baby, and I was doing most of the work. And that became unrealistic. So I needed to teach colleagues how to, you know, do all the various different aspects of podcast production. And it was frustrating at first, because I had developed a rhythm and I had actually developed a much deeper knowledge than I didn't realize they had about how to produce a podcast and all of the various different editing and production tasks. And you know, how to record an interview, how to interview a guest how to lots and lots of different things. And I started to share that knowledge so that so that I wasn't the only person who could do it, it was just never a good position to be in, it's if you think that that's a good way of getting value as an individual it isn't. It's a millstone around your neck, you should never want to be the only person who knows how to do something. And so I started to teach my colleagues and at first, it was frustrating, because there were things that I could do really quickly. And I thought, I'll just tell them how to do it, and then they'll be able to do it too. And I would tell them, and first of all, they wouldn't get it instantly, because actually, I was given them really a lot of information. So they would come back to me with questions like hang on, I didn't quite get this bit, and what about this bit, and then second of all, the first time that they did it, they wouldn't do it as quickly as when I did it, not because there's anything special about me, but just because I had been doing it for longer. And that's that was frustrating, because the reason I was trying to hand off these tasks was to free my own time, and to just, you know, make the whole process more efficient. And initially, it didn't, it made it less efficient, because the you know, I was having to spend time teaching people, and they weren't yet be able to do it as fast as I could. But that, and it's very common that at that point people give up, because that happens all the time in software teams, people, you know, with the idea of the bus factor, I don't know if you if you heard that phrase, the bus factor, that somebody has a high bus factor, if if they are if they get run over by a bus, it will have a high impact on the teams. That gives them a high bus factor. And you want to reduce the bus factor. But in order to reduce the bus factor, you have to share knowledge. And in order to ship to share knowledge, you have to teach other people and you go through that whole process I've just described. And often people find that frustrating. And they give up. So they say, Oh, I tried to teach it to somebody else. But it was no good. They did. They didn't they didn't understand what I was saying. And it was too slow and too frustrating. So I've just decided I'm just going to keep holding all the knowledge to myself, not because I want to, but because anything else just feels too hard. And and that's very short termist. But but we know brains naturally are quite short term. So you have to, you have to encourage each other to take a long term view. But when you do you say okay, yes, this is short term pain for long term gain, that when I get all these people up to speed, I will be able to walk away at any moment and know that other people can pick up the slack. And that will in the long term be much more effective.
Joe Krebs 29:01
Yeah. Clare. All what you just said I want to link to another topic. Okay. Yeah, because I think there's there's something in there. Obviously, the the social aspects of collaboration, building a product together, sharing, not being in silos. I'm going to make another general statement. And that general statement is about there's a lot of people that refer to agile as iterative development, let's say right? So there's a there's iterative development going on. And they're working in short cycles, etc, etc. But what's also important is that it's iterative, incremental. So the increment that to just to stick to a term out of the scrum world, but you know, is a piece which we want to build at the end at least once at the end of the sprint. And that is that is a product that is potentially releasable. Yes, this is where the general statement comes in. I've seen teams struggle trouble building increments sprint by sprint by sprint, not even multiple increments per sprint just like one. But it's and it's obviously, I don't know if that is it is related to let's say this the silo thinking that learning that pairing all of those things you just mentioned, asking for help, etc. But sometimes he you know, we see still answers today when I work with lesser experienced teams. They're like, well, we got the software down but not tested, right? Or we got we got a piece of software here but not integrated. So why is it that it's 2021 Ron Jeffries wrote this XP book many, many years ago? Why do we still struggle? What's what's so what do you think is behind that in software engineering teams? I mean, it's the push back, is it possible, the deadline? Is this the knowledge? But what do you see when working with him? So maybe I'm totally wrong, maybe on your site teams are producing increment by increment on a daily basis.
Clare Sudbery 31:01
No, it's yet another thing that isn't easy, and does take effort and continued effort. And I think maybe what generally, what we're, what we're talking about here is the fact that people want there to be a manual, that you teach me how to do software development, I will learn how to do software development, and then I'll know how to do software development tick done. And it isn't that simple. It's it's continuous, you have to keep fighting these battles, keep having these conversations keep showing the value of doing things in certain ways. And the increment is a very important concept. So I tend to I like the phrase vertical slice. So the idea that what you want to do is deliver a vertical slice of your product from end to end. And that your definition of Done should be that it is in front of your users. So as you said, it's been tested, it's been integrated, it's been deployed, people are using it. And in order to have that mindset, you first of all have to have people who are who to skills cross a number of disciplines. So they have to understand how to make sure that testing is done, they have to know something about deployment. And that can be frustrating to people, I think, sometimes people, they want to be in a comfort zone. So people do tend to say, this is the thing that I like to do, this is the thing that I'm good at. So I'm going to stick to this thing. And then when I've done my bit, I'm just going to hand it off to somebody else and forget about it so that I can go back to doing the thing that I really enjoy doing. And in order to persuade people that it is worth seeing it through and caring about it all the way until it's in front of the users, you have to sometimes take them outside of their comfort zones. So that's one thing. Another thing is that it can be very tempting when you're looking for efficiencies, to think well, okay, these silos make sense, because you think of it like a production line, you know, my job is just to do this little bit of the process. And then I'm going to chuck it over the wall to the next person to do their little bit of a process. And that feels efficient. Because I can keep doing my little bits over and over again, I'm really quick at it, I know what I'm doing. But the problem is that unless something has gone all the way to production, you don't know whether you've built the right thing. You don't know if it works, you don't know whether it's going to come back again, with bugs or simply being told it's not fit for purpose. So it might not have bugs, but it might not be what our users actually wanted. Because the ability to have a dialogue with users and stakeholders and to really understand what the best thing is for us to create. That's highly complex, lots of things can happen. Even if you've got a really good relationship with your users, they can tell you exactly what they want. And then you deliver it and they realize that they were wrong. They didn't want what what they thought they wanted, or it doesn't actually do what they need it to do. There were things they hadn't thought of, or there are new things that have come into play. So getting something in front of your users quickly, so that when you discover that there are things wrong with it, because there always will no matter how effective your process there are ways of reducing the likelihood of that. But there will always be things that need to change. The quicker you can get things in front of the user, the quicker you can fix those problems. And the more likely it is you can remember how to fix it because when you made it in the first place, it was recently enough that you can still remember the detail. So that's that's why we want to deliver in vertical slices and why we want to deliver in increments but persuading people of that is a bit chicken and egg because until you have a very effective process that allows you to deliver vertical slices end to end. You won't see the benefit of it. and also you do have to persuade people that they're going to have to spend some time outside of their comfort zone that they're going to have to care about things that they don't immediately find interesting. You know, and also, you're gonna have to ask people to spend time with people that they might not feel comfortable about. So not everybody is delighted by the idea of being in contact with their users. Some people see this as being stressful people who are who are, you know, antagonistic and cause problems. And, and that's not because users are not necessarily like that. But it's because as soon as we start to divide ourselves, and it becomes very easy to get defensive. And as soon as two parties feel defensive, then each party feels as though they're, they're being attacked. And it's incredibly easy for groups of people to, to find themselves in that situation. And to start to see the I mean, there's, there's tons of psychology about it, the idea of the out group and the group. But as soon as you see a group of people as being other from yourself, then they they become net, potentially a source of stress. And it's, it's not simple to get development teams into a situation where they see their users as their collaborators, and they see their stakeholders as their collaborators. And they see that they can, they can take responsibility for and take an interest in, in all aspects of the software development lifecycle. It's not easy, and there are reasons why people will tend to gravitate into silos, and why people think that looks efficient. So it's a constant conversation, you have to prove it. And in order to prove it, you have to have certain things in place. So for instance, I'm a big fan of trunk based development, which is where every commit in the code goes to the main branch of your code, and then gets deployed as quickly as possible. Now, this is controversial, not everybody agrees with me. But there are a significant number of people who do that as soon as you create a feature branch, then you are diverging your codebase. And inevitably, at some point, you're going to have to merge that code. And by doing that, you're slowing down the speed at which your code can get in front of your users, you're not just slowing it down in time, you're also increasing the amount of complexity and therefore increasing the likelihood that something will go wrong, increasing the risk. So it's more likely that bugs will happen that merge conflicts will happen. And then you'll have to spend time fixing those bugs and fixing those merge conflicts instead of getting that code in front of your users. But in order to be able to get rid of branches, you have to work in a very specific way. You can't just write code in the way that you're used to, you have to think of every commit as potentially being something that will be deployed. And for a lot of people that sounds crazy, because they're used to pulling everything apart, and then putting it back together again. And and that you can't commit, you can't deploy every commit, that would sound crazy. To some people, it is possible, but it requires a different way of working, it's a skill that has to be learned. And then in order to learn it, you have to persuade people that it's worth learning. And it's it again, the reason it's chicken and egg is the reason you want people to learn, it's so that they can see the value of smart fast feedback loops, small vertical slices, getting things in front of the user as quickly as possible. But you can't demonstrate that until they have enough skill to be able to do that. In you know, and you have to persuade them why they would want to learn those skills in the first place by demonstrating it, but you can't demonstrate it if they can't do it. So, you know, it's it's long. Yeah, it's when you're seeing it work. It seems obvious. And it's frustrating if you can't persuade people. But if you haven't seen it work, it sounds painful, difficult and slow. So it's it's not easy.
Joe Krebs 38:59
It's not easy, but it has a focus on the increment, right? Which is so so important, because that is that is value. And I can only agree with you all the teams that are producing increments. There is a, you know, it's definitely boosts morale on a team because it means that we have value produce, right. So in these short cycles, so but it is so hard to produce, because sometimes it's what you just mentioned, or the imbalance on of skills on a team that we have too many engineers and just not enough QA. And that is, you know, we might have a lot of code, but it's not QA and if you're breaking down the silos, and if you're working as a team, and you're learning and sharing and get out of your comfort zone. Yeah, that increment might be achievable. By the by the end of the sprint. So there's a lot in there. But you know, I often see that as a as a key element of development. So towards the end of our conversation you and I do have to say came back to and I cannot just say Ron Jeffries with XP books as well, obviously, can Beck's book there. So I've just shout that out. That's also an important book. In this thing, how do you feel about I just to the end of our conversation here about throwaway software, I see like software being like produced in shorter cycles. You know, the business world ideas being built on more and more software than it has been ever cars, everything includes software at this point, everything. So how do you feel about throwaway software, like instead of, you know, refactoring or solid software engineering practices to build code, and if needed, we're going to throw out the system and building a system because the business will change so fast about these trends?
Clare Sudbery 40:40
Yeah, that was one of the things that came into my head when you talked Right, right back at the beginning, about quality about making sure that you have quality in your software where because actually, there are times, when you might say, in order to move quickly, we aren't going to dot every I and cross every T. Personally, I find that painful and difficult. Because I want to always produce a really good quality software piece of a really good quality product. But actually, yes, there are times and you what you have to do is you have to ask those questions, you have to say, is this something that is going to have longevity, and is this something that is going to be a crucial component that is going to be shared with other parts of our system, you know, so for instance, and it's not an easy thing to be able to detect. So for instance, software engineers are notoriously bad at knowing which bits of their code they should optimize. So you know, you will frequently see software engineers spending hours tweaking a piece of code to be the most efficient piece of code everywhere ever and, and not use too much memory and not not be too slow. And then once the whole thing is completed, you do some you run some performance tests, and you discovered that piece of code that they spent hours and hours and hours tweaking and optimizing hardly ever is hardly ever hit doesn't actually matter, it could have been 10 times as slow and it wouldn't matter because it's never called. Whereas the code that is called repeatedly and is slowing your product down is the one that you didn't realize, because you know, so premature optimization is something that you have to be aware of that. And you also have to know how to move fast. So for instance, you don't necessarily want to build a highly complex pipeline. At the beginning of your product project, you do want a pipeline, I would definitely say deploy as early as possible. I'm a big fan of The Walking skeleton, but don't necessarily make it all singing, all dancing, because what you might do is build in optimizations that you don't need. So wait until you're in production and then say, Okay, now what do we need to tweak? Where does the quality need to be? Which bits can we throw away? And it's not? I don't think there's an easy answer. So I think yes, there will, there will sometimes be things that you throw away, it's hard to know in advance which things they will be, there are definitely practices that you can use that will that will make it more likely that you can enhance and optimize your code. And I would definitely say building tests from the beginning, because they are almost almost always useful. And always be thinking about refactoring. But sometimes you know what that thing there might not need refactoring. It might be that nobody ever uses it. So yeah. And it might be that this thing here that you're building can be thrown away. And having that mindset that this is something that could be thrown away, is actually also very useful. The idea of building something and then throwing it away. And then building something else, which I mentioned a while ago, is something is a technique that's used in code cutters and in workshops. If you think of it as being disposable, then you then you can let go of it. And you can say, You know what, I'm going to build it throw away and then build another one. The problem is that if you say, Oh, it doesn't matter, because it's going to be thrown away. That's nearly always the thing that ends up being the absolute core. And in 20 years time, people are cursing your very existence. horrible thing.
Joe Krebs 44:27
You want to really make sure it's will be the intended to throw away otherwise he's outlast you.
Clare Sudbery 44:33
But it is important to recognize that that possibility and to always and this is why the increment is so important, right? This is why thinking small is really, really important. Let's do something tiny as a proof of concept. Let's not let's not design a giant system and try and build it. Let's design a tiny little example of whatever we believe is going to work and let's treat it as an experiment. That doesn't mean that we don't do it to a high standard. But if it's small, then everything is quicker. Everything is lower risk, you know, and you know, baking in quality is a lot quicker and easier when you're doing it to something small. And then you can throw it away when you discover that actually, it doesn't do what you thought it was going to do. You can have hypotheses, you can view it as an experiment. And that speeds you up.
Joe Krebs 45:28
That was awesome, Clare. Good conversation. I know this was a little techie or today for the Agile FM listeners, it was a lot of use of the word software. If you have listened to this podcast and you're not in the software development space, you can replace the word software with probably any other word. It would still make sense, I guess. And, but this was a little bit more software related software development, projects and features, etc. Great insights. I think we covered a lot of ground here, but maybe maybe we start small and maybe you come back one day to Agile FM and more topics and add to it.
Clare Sudbery 46:10
Fantastic. That would be fantastic. I'd love to Yes.
Joe Krebs 46:14
Thank you so much.
Clare Sudbery 46:16
Thank you for having me.
Joe Krebs 46:18
Thank you for listening to Agile FM, the radio for the Agile community. I'm your host Joe Krebs. If you're interested in more programming and additional podcasts, please go to www.agile.fm. Talk to you soon.
From the publisher's feed
Radio for the Agile Community