On a good day, hiring people for your team is a challenge. A quick look at some articles I’ve written on interviewing further confirms how tricky this can be. Running a Technical Interview One Rule for Interviews How Not to Prep for an Interview – Part 2 Now Not to Prep for an Interview – Part I Stop the Memory Questions Getting Past the Gatekeeper Hire Someone Better Senior Years but Junior Experience Selling Yourself…
If you want to be having those hard conversations with your team – switching roles, letting people go, moving on to different careers, etc, etc – and you want to generate a response that the team can work with and move the ball forward, you won’t be able to do it without having generated a certain level of trust and authenticity before that first discussion. Otherwise you’ll end up with a lot of people on…
Could this have been an email? Should this have been an email? No we should have been discussing these topics Were too many people in the room? There were a lot of people in the room, but only a quarter of them need to be there, the rest would not have said anything regardless. Were people missing? Yes. What’s the difference between the people that were missing and the ones that were there? The people…
There has always been a problem when it comes to high-pressure projects. Who is doing the most? Whether it’s how many hours you are putting in, how green your presence icon is, how green your github check-ins look, how many meetings you have, or who is pumping out the most bugs – the question never goes away. It’s a dumb question because when you think about it – if one person is doing most of…
You will mess up. It won’t be perfect. You will get it wrong. You’ll probably stumble. They might laugh at you. But maybe… You’ll learn something new. Realize where you went wrong. Figure out where you really want to go. Meet a new friend. But you’ll never know if you don’t try. Forget what could go wrong and please, just try.