Adopting a new way of working

`0:40:14`

almost have to plant a new seed somewhere else, let's just say, and then grow something new because it's very hard to change in flight and change what you have and change what you're used to. So what we often encourage people to do is keep working the way you're working, but some future project, some low criticality project, try this new method on that. So if it doesn't work, because it's probably not going to work very well the first time, just like if I gave you a guitar and you never played before, it'd be unreasonable for me to expect you to play well. You're going to suck for a while. So go pick some things that don't matter if you suck at them for a while and try this method over there and go, oh, you know what? I'm actually getting quite good. Now let's try to bring this into some more critical stuff. I think that's the important way to approach these sorts of projects, which is to take

`0:40:59`

the criticality out. Because what ends up happening is that when people try to try something new on something really critical and it doesn't work, they'll never try it again. They've destroyed all future opportunities to try this again, because everyone knows how bad it went last time on something that really mattered. And they would've gone, we could have done it our old way. Our old way worked. It kind of sucked, but it worked. And so now you're comparing two things that aren't really comparable, but you're always going to go with the momentum that you had versus the new thing. And so you got to be careful with that. So I know I'm rambling a bit on it, but that's my general sense and feel on how to adopt a different way of working. There's also this cool down period after one of these, what do you call these? A sprint or what's the term for it? No, I hate that term. I don't like the word sprint because how do you feel after a sprint?