Otherwise, they never go anywhere. They stay on the ground, hoping to become something else, but they never go anywhere. Someone needs to pick it up, run with it, and hold onto it when the going gets rough – because that’s when it needs to be held onto the most.
All work has a base and from there we customize it. We find what we like and we seek to tweak it. There are so many TikToks, Reels, etc, that walk all of this and show base products being customized to fit your needs. It’s not about IF your product is going to be customized, it’s WHEN it’s going to be customized so you might as well start building it to be extended.
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?