TECH PEOPLE LEADERSHIP NEWSLETTER
A weekly newsletter of curated links giving help, advice and opinion to leaders in teh tech industry.
THE ARCHIVE
FEEDBACK
13 Questions to Get More Feedback From Your Team - Programming Leadership - Medium
Easy read, useful stuff. Exactly what it says - ways to start the “I want feedback” conversation with your team.
Disrupting Bias in Feedback — Jill Wetzler
A cool, practical post outlining specific ways to notice, and then disrupt our own biases when giving feedback. Great piece.
MEETINGS
“Nice” cultures miss ideas, fail to resolve real conflict, have baked-in inefficiencies. But “brutally honest”, often a response to “nice”, is as bad. Respect, connection and caring - hard to do, but they work.
“Good as it feels, this emphasis on niceness leads to poor decision-making and low levels of creativity by limiting the number of inputs a group will consider”
This is cool: a careful analysis of the “shoulder tap” interruption, how it doesn’t work fro remote employees, and why that might be a good thing.
“When employees go remote, it can feel to decision-makers like some of their control is evaporating into the ether because they can no longer tap those employees on the shoulder and expect immediate answers. But instead of evaporating into the ether, that control instead transfers to the remote employees themselves. This is a good thing”
Lots of great stuff here. An interesting POV on “social cohesion”: Bezos doesn ’t like it. A much longer conversation to be had there. For my part I generally agree, but I think it’s a subtle point: you can have respect, connection, and even emotional safety without having “social cohesion”. Discuss!
A classic communication model, breaking down how to get across what you really want to communicate. As with many of these models, you may not want to use all the parts all the time, but use them to discern what you are really wanting to communicate (emotion? thoughts? logic? desires?).
This is a riff on the Jeff Bezos letter to shareholders from last week, but a good one. Some decisions you can make quickly, with low information, and reverse later, some you can’t. And, as always, the art is telling the difference. A good read.
Also known as “Maslow’s Hammer” - “if all you have is a hammer, everything looks like a nail”. This just struck me as one of the Classic Tech Mistakes which occurs at all kinds of levels - everything from choosing an algorithm to deciding what business the company is in, so I loved this detailed history and explanation.