Something didn’t go right. Your code broke. Your project cracked. You have two choices, let it stay that way or build it back to where it was, to where it will work, to where it will be broken. It might have failed spectacularly and you might be regretting it – don’t, it happen, now find your way back.
The team that takes the time out, the team that takes a step back and ponders what is happening, the team that puts all pencils down because something is just plain and clearly wrong. Is the team that will always come through in the end. That moment to regroup, that hour, or the day it takes to do it, will serve the team better than continuing to plow through on the wrong thing. Give your…
Answers should not include… “I do this…” “I’m the best at this…” “My job is X…” “Only I can do that…” “I run this…” “I monitor that…” “I’m backup for Y…” What do you bring, not what you are, what do you bring to the team?
So I should continue doing nothing? If something happened when I did nothing why I should engage in more activity to do something? It’s a waste and effort of energy and what if nothing happens from me doing something, now I’ve spent all that time and gone nowhere. Confused? This is the circle of confusion where you are trying to convince yourself to do or to not do something. You can wrap yourself up in…
When it comes to being a part of a team, we all buy into wanting the team to succeed. Why not? It’s why we’re there. At some point, the workload becomes too much (it always does) and the team struggles to find new paths for efficiencies and growth. It doesn’t happen quickly, they have to flounder and fight against the current because they are now not only fighting against what is ingrained within them but…