Teams don’t come with Instructions, people on your team don’t either. Depending on where your codebase is at, that might come with next to nothing in terms of how things are done. Even if there are instructions, they are probably out of date, that’s because the team that was using them doesn’t need the instructions anymore, they know what to do, they know where to do it, they know what comes next, and where to…
The team needs a leader, the individual needs a mentor. You lead the team, by connecting with the individuals and figuring out what they need to buy into the vision. Some will resist, they can’t see it on the first, the second, or the eighteenth day. They have different viewpoints, different goals, and different ideas – the leader brings them into the focus of the team, not ignoring them but finding how they connect to…
The fastest way to build trust is to get everyone onto one page. We’re on this journey together, no one is getting off, we’ll see it through, whatever happens. We aren’t looking for experts, rockstars, ninjas, or gurus to solve our problems with and gift them all the problems we have – we are looking for someone to be there with us, to work with us, to support us and not leave partway through. Trust…
They stare you in the face and countdown to the end of a pre-defined time. What do they really do? They stare you in the face and give you the indication that this thing you’re working on, this thing you don’t want to do that you wish would end, will be over, at some point, boiled down to minutes and seconds (no one sets a timer for an over an hour). And they get you…
“On Paper we shouldn’t be doing this well” I’ve heard that statement many times and it always comes back to the team effort. When the project, the delivery, and the timeline start, it doesn’t matter how many people you have, how much cash is in the bank, and who has delivered more in the last quarter. All that matters is what the team can do and if the team can deliver past what is expected…