Not everything can. We used to have a great test to see if our code could survive. We pulled the network cable. That’s, no other fancy actions, just pure and simple, we pulled the cord to see what good our app would be if we yanked out the cord that powered everything. And better yet, we plugged it back in to see how it came back to life (if it did). You will suffer blips…
Did your new initiative break? Did it not go as expected? Was the team unhappy with what you tried to do that didn’t work? Did it blow up in your face? Good – that’s the idea, your leading should break at some point. If it’s not breaking, it means you’re not working on it, and if you’re not working on it, it means you’re not trying to get better, it means you’re coasting. And if…
When things break, you can do any of the following; Get mad that it broke. Complain that it broke. Run around screaming that someone broke it. Schedule a meeting to discuss that it broke. Argue about the level of brokenness within it. Or, you can get to fixing.
It’s up to you how you want to present your status. It doesn’t have to be what you did / didn’t do. It can be what you accomplished. It can be what you struggled with. It can be a slide presentation. It is a song. It can be anything you want. So make it yours, because it’s all about you, so it might as well be great.
I love debugging. Press F5 and walk step by step through everything you have just created. It’s awesome. Could you imagine debugging your life – pressing F5 and figuring out what is wrong with you? “Oh looks like you had a huge lunch and are now tired.” “Trying to do too much and need to slow down or drop something” “You’re stuck in an infinite loop because you can’t solve that problem” And on and…