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
Nice story about how looking at improving everything by small increments can make a massive difference over time. (Yeah, obvious, but it raised the question, at least for me, of “huh, OK, well what can I improve a little bit that I routinely overlook?”).
A good look at what really “hiring for fit” might mean. Strong article.
“When we hire for fit without thinking about what a fit means to us, we use an unfortunate proxy: similarity to hiring managers. The result: homogeneous teams, with poor results for employee experience and the bottom line”
My notes on breaking through stuck conversations. You’ve tried being clear and direct. You’ve tried repeating yourself. You are baffled by the responses and are about to start giving up, or getting loud and insistent. A “WTF moment”. A breakdown of what to do instead.
“We have inherited and unquestioningly perpetuated management practices that date back to the Industrial Revolution. Systems and processes, hierarchy and outdated structures impede our ability to transform our organisations to be future-ready”
Interestingly, I think this is still true in the tech industry, although to a much lessor extent than outlined here. But take a look.
Simple. Handy. Lines up with Jeff Bezos’ Type 1 and Type 2 decisions to a degree. Useful.
Followup to a link I posted a couple of weeks ago. Woman are confident, and express it, but don’t get heard.
This is wild! An in-depth report from Stripe on developer efficiency and its dollar effects on business (hint: large). An amazing document.
Questions like: “In your opinion, as a whole, how productive are developers at your company?” and “How much of a negative impact does each of the following have on your personal morale?” I’m going to spoil the answer: 1) overwork 81% and 2) changing priorities 79%.
A good set of questions to ask about your calendar (doesn’t apply just to CEOs, by the way). I would add: make the overall question you are asking be more pointed: “what do I really, really need to keep?”. Everything else should go.