Whatever it is, make sure everyone is calling it the same thing. Make sure everyone knows the reason that it is called that “thing”. Ensure the name and meaning are clear to everyone, put it into your lexicon. If there is feeling behind it, make sure everyone feels it. We can call things whatever we want, we can change the name daily (if we want to confuse everyone at large) and we can keep iterating…
I call it the Upfront – it might have other names to you, but this is possibly the least offensive one. What happens at the Upfront? The upfront is a meeting where everyone that is attending knows that brutal honesty is required. There is no room for niceties and hand holding, it’s an all out discussion that would take place in a warroom if it were happening. There is a big problem and it requires…
Three times. Three times until your estimates mean something on what you are working on. The First Time – You’re new to whatever it is you’re creating. You are learning as you create, you are going down rabbit holes and filtering out new ideas and throwing away initial designs. The Second Time – You know enough to be dangerous, but you are still learning. You have picked up some tricks, did a learning and validation…
Team Meetings are tricky to run because invariably it interrupts someone’s day when they are deep into a problem. I’ve been on all sides of a team meeting and know this to be the case. But it’s a necessity when you have more than one person on your team (that means you). It’s a check-in to make sure everyone is on the right thing, everyone is pushing forward and if people need help, they are…
If you aren’t challenging your team, you aren’t helping them grow. One of my most memorable performance reviews was one I was giving where I told the developer he was doing a great job, I wish I had ten of him, I’m learning from him, etc, etc. It was all true. His response – “That’s great to hear, now how do I get better?” The question threw me for a loop because I hadn’t thought…