TECH PEOPLE LEADERSHIP NEWSLETTER

Every week or so I collect a set of articles that have caught my eye about leadership and management in the tech industry.
The articles cover a wide range - everything from the basics of running meetings, to the subtleties of managing remote teams, to the underpinnings of giving feedback and difficult conversations.
Articles I circulate in the newsletter are collected below in the archive. Feel free to browse, and free to sign up!
I keep your email safe, and I don't spam.
THE ARCHIVE

0
“I defined stupidity as overlooking or dismissing conspicuously crucial information”
Interesting piece, identifying things that influence us to be stupid. Sounds like a throw-away listicle post, but it’s not. If we could, occasionally, ask “am I about to be stupid?”, and check on the factors he identifies, we might avoid some costly mistakes…
Karen Catlin is a coach (and colleague) and advocate for more inclusive workplaces. Her book is a complete, practical and thorough look at the ways managers (and anybody, really) can help improve real diversity and inclusion in the workplace on a daily basis. Super useful as we head into 2019.
The phrase “Manager Mind” popped up in a client session this week, and it helped clarify for me the huge differences between the manager and maker (coder, designer, writer) mindsets. Getting clear on these differences will, I hope, help you be a better manager of makers, or, if you make stuff, help you understand where your manager is coming from.
There’s some really great commentary in here: running one on ones, tips for first-time managers and much more. It’s a set of clear learnings from an experienced, together person (IMHO!).
“Teams look to their leaders to calibrate their responses to stress, failure, and adversity, in addition to understanding what celebration looks like.”
This is a long piece, but valuable. Lots of useful and practical insights gained from building Yammer. A good emphasis on structures and processes that help the leader get out of the way. Good stuff (some of it related to the next post, interestingly).
I’m always interested in “no manager” experiments, and this seems like a good one. No BS, a simple model and some neat ideas (like a “team parent” in charge of the welfare of the team). You’re probably not going to move to a no-manager setup, but you may get some good ideas from this anyway (and if you are, great!).