Assumptions are needed when you have too many variables at play. When everything is fluid, you need something solid at play to minimize the variables at work. The key then when making assumptions is to make sure you know what you’re assuming, why and knowing what the impact will be. Then your assumption has reason and strength in moving forward. It might change over time, but at least now you’ll have a reason for it.
If you’re following the traditional school calendar (not for post-education but grade school only. You’re halfway there through all the goals you had wanted to achieve. Don’t give up if you haven’t started – but get started now.
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.