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 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…
You might be able to do it faster, and you might know more of what happens behind the scenes, but if you’re always jumping in, you’re never going to see what they can do, on their own, when you’re not around. Let them work, see what they can do when you’re not around, give them reign, and see what happens. Trust is built on seeing what they can do when you are not hovering over…
We all know have an idea of what’s next. But what do we do to get there, what do we need to do to prep for it? We have no idea. But oddly enough when we get there we go – “oh yeah, I should have done this, this and this.” Take the time, ask yourself what you need to get ready, write it down, figure it out and move start grinding it out.
I missed a number of posts in September, what can I say it was busy and that carried forward into October. Here’s how it goes when you miss a deadline. Day 1 – I’ll get it tomorrow. Day 2 – Okay, well I already missed one, so what’s one more? Day 3 – Tomorrow, I promise tomorrow. Day 4 – Do I really want to do this? Nothing has changed in my life? Day 5…