I’ve been on a project the last few months where I’ve had to do much of my own QA. I’ve had to write unit tests, write test plans, and test cases. I’ve had to debug assertions of what should and shouldn’t be. Turns out I’m not as great at QA (or diligent) as I thought I was. Worst yet, turns out there are a slew of errors in my code. So apologies to all of…
It’s not that you haven’t had time. It’s that you haven’t MADE the time. Put it this way – you don’t write things down for yourself, you know what you are doing, where to do it, and what happens when things go sideways. You’re writing it for the person who comes after you, who needs to figure all that goodness out. You’re writing it for the person on your team that isn’t here, that hasn’t…
Going with the flow is great until it starts going the wrong way. Then it’s just going somewhere you didn’t want to go, somewhere you didn’t want to end up. And now you’re wondering how you got here and where you go next. (Hint: It’s going against the flow).
A plan is only as good as it’s execution. Otherwise, it’s an elaboration of an idea. And we have plenty of those.
We coach for wins, not for growth. Growth happens behind the scenes, no one sees it unless they look deep beneath the covers. But it’s always there. So what would happen if we coached for growth instead, letting the wins happen when they happen, and see where we get from there? What would be the harm? What could go wrong? Just growth.