Taking over the lead for something new is never an easy task. New ProjectNew TeamNew ProductNew Test ProcessNew _________________ If you are new to the project, there is generally a lot of upheaval going on, maybe you’ve been brought on to help with the last push, perhaps other people were kicked out. Whatever the reason, your goal always remains the same – how do I provide value to this “thing” that I’m now a contributor…
The person that reaches out, isn’t the one who lost the argument – they are the one that cares about the solution, the problem or issue and understand it’s importance in finishing the project. Being the person who reaches out, isn’t a sign of weakness – it’s a sign of a leader that knows what comes first in delivering a project, isn’t the code or the final product – but the team itself.
If you are consistently restarting a project, starting a class over, wiping your IDE to start afresh page of code the problem might be in not understanding what you’re actually trying to deliver. When we don’t know what someone wants at the end, we keep adding stuff until it looks like something no one would want – so we REBOOT – and start again. And then we start doing a whole bunch of work, much…
We all have Bad days, when things go horribly wrong, when we don’t think we’ll recover and when the world looks like it’s on a permanent tilt. But bad days end when you go to bed. Don’t let bad days turn into bad weeks and don’t let them go any further than that. This is especially true when you’re leading a team because they need to know that all it was, was a bad day…
Yes, they go boink. That is what happens, when an organization has all the information in the world to help their customers and uses none of it. It’s akin to getting the call to sign up for new services when you just cancelled a week ago and the representative has no idea to why. What might be better is if they called, knowing your case history to inform you that they fixed it should you…