/Leadership

How To Start A New Role

- Mike Fisher tl;dr: Mike shares his 90-day plan for starting a new role as an executive. “These types of plans are not set in stone. You probably know very little about the company, the people, the operations, the issues, etc. despite numerous rounds of interviews. You will learn more in the first week of full time work than you will in all your interviews. You need to be nimble on your feet and prepared to deviate from your plan when necessary. If you were hired because of a crisis and you can’t wait a month or two to make a critical decision, obviously make the decision. Don’t wait just because your plan says so.”

featured in #555

Testing Strategy: Avoid The Waterfall Strategy Trap With Iterative Refinement

- Will Larson tl;dr: “If I could only popularize one idea about technical strategy, it would be that prematurely applying pressure to a strategy’s rollout prevents evaluating whether the strategy is effective. Pressure changes behavior in profound ways, and many of those changes are intended to make you believe your strategy is working while minimizing change to the status quo (if you’re an executive) or get your strategy repealed (if you’re not an executive). Neither is particular helpful.”

featured in #554

Conducting A Time Audit

- Andy Sparks tl;dr: The founder of Visa “preached that great managers spent 50% of their time managing themselves, 25% managing up, 20% managing across, and 5% managing down. In comparison, most actual managers preoccupy themselves with a hell of a lot more downward management than 5% of their time.”

featured in #554

What Does A Date Actually Mean?

- James Stanier tl;dr: “But this isn't an article about how bad we are at estimating, nor does it offer any solutions for you to getting better at estimating. In fact, I want to focus on why dates are pretty dangerous things to be throwing around in the first place, and what an alternative might look like that could save you a lot of pain.”

featured in #554

Interviewing For Evidence

- Daniel Terhorst-North tl;dr: “There are 4 primary types of evidence I look for in an interview, which are, in order of general importance, experiential, hypothetical, opinion, and credential. (1) Experiential evidence: things the candidate has done. (2) Hypothetical evidence: what the candidate thinks they would do in a given situation. (3) Credential evidence: what the candidate is qualified to do. (4) Opinion evidence: what they think about things.” Dan gives example questions of each. 

featured in #554

Simplifiers Go Far, Complexifiers Get Stuck

- Dave Kellogg tl;dr: “Strive to make things simple. Seek to understand them. Struggle to find apt metaphors for them. If you’re not burning real energy trying to simplify things for you audience, you are most like a complexifier. If so, the next time you’re about to explain to someone why something take so long, is so complicated, or requires 5 steps to be completed before the start, ask yourself — do I really believe this or I am making it complicated because I either don’t want or don’t know how to do it.”

featured in #553

How To Deliver Bad News When It's Not Your Fault

- Wes Kao tl;dr: “As much as we don’t want to shoot the messenger, we often associate negative feelings with people who tell us bad news. Wes’ principles for delivering bad news are: (1) Avoid negative words, like "however” and “unfortunately.” (2) Avoid giving too many details. (3) Don't accidentally accept blame. (4) Get to your point quickly. (5) Remind the person of their own agency.

featured in #553

Stop Avoiding Conflict On Your Teams

- Doug Turnbull tl;dr: “Can you give some space for everyone to have voice in the conflict? Can you create a space where you set up ground rules for conflict i.e. attacking the problem, not people. Can you maximize also “caring personally” dimension that gives air to the quiet voices? Can you encourage the employees who often come to complain 1-1, but struggle to speak up in group meetings?”

featured in #553

Measuring Developers' Jobs-To-Be-Done

- Abi Noda tl;dr: “To provide better insights, Google researchers identified the key goals developers are trying to achieve in their work and developed measurements for each goal. In this paper, they explain their process and share an example of how this new approach has benefited their teams.”

featured in #552

Antifragile

- Andrew Bosworth tl;dr: “Failures happen. In engineering we often face a choice between trying to eliminate failures or making our systems handle them more gracefully. Both approaches are important but in my experience fault tolerance is the more valuable. The reason is simple: we can only eliminate failures we can imagine while fault tolerance adds some resilience to failures we could not imagine. I have found the same to be true for groups of people.” Andrew discusses how to implement this in management.

featured in #552