/Leadership

Making ‘Big Changes’ Successfully

- Pat Kua tl;dr: (1) Quantify the problem and success criteria. (2) Start with a tracer bullet. (3) Work in small, end-to-end increments. (4) Prioritize increments by risk and value. (5) Use ratcheting to prevent regressions. (6) Start what you finish.

featured in #239


Why "Bring Solutions Not Problems" Doesn't Work

- Lara Hogan tl;dr: When a leader uses this line, it means (1) Your leader can’t / won’t listen or care about this thing, or (2) You need to step up your game and adapt. Lara also lists open questions to ask in place i.e. "What could we try?" or "If you could wave a magic wand, what one thing would you change?"

featured in #238


A Manager’s Guide to Holding Your Team Accountable

- Dave Bailey tl;dr: Holding people accountable feels uncomfortable so we can let it slip. Accountability and feedback are essential to high-functioning teams, and Dave provides a primer on both feedback and accountability, highlighting questions we can ask our team to ensure both are present.

featured in #236


Attitude and Behavior

- Ed Batista tl;dr: We assume attitude drives behavior but, in fact, our behavior also shifts our attitude. A misalignment of behavior and attitude i.e. you should do something but don't feel like it results in cognitive dissonance. Ed outlines strategies to counter this (meditation, journaling, etc...) but states they should come from a sense of authenticity and agency.

featured in #235


Coachability: The Overlooked Factor In People Development

- Cate Huston tl;dr: "Coachability" has two axes on a matrix - receptiveness and actionability. Being both receptive and actionable is ideal but can come in an unhealthy form as a people pleaser. The healthier way to operate is when you know yourself, "when everything feels very clear" and feedback fits into your mental model.

featured in #234


10 Admirable Attributes Of A Great Technical Lead

tl;dr: (1) Having an opinion yet not being opinionated on everything. (2) Filled with energy yet calm in all situations. (3) Disown their team’s successes and own their team’s issues, and seven more traits.

featured in #234


Clarity Is An Underrated Skill

- Tom Gamon tl;dr: When talking about code, you'll generally refer to hundreds of lines of code so clarity is key. Some tips: (1) make the implicit explicit - avoid words like "clearly" and "obviously", (2) Be succinct, (3) Avoid ambiguous pronouns.

featured in #230


The Engineering Leader’s Guide To Crafting A Personal Brand That Stands Out From The Crowd

- Anjuan Simmons tl;dr: After several years as a public speaker, Anjuan helps us create a playbook for creating a personal brand and the "potholes" that can throw you off. Most tactics center around public speaking, Simmons also dives into developing a social brand.

featured in #229


The Art Of Self-organizing Engineering Teams

- Tom Sommer tl;dr: "Purpose, mastery, and autonomy are helpful concepts to enable self-organization. They allow us to guide and create alignment, set up effective processes and workflows, and provide the ability to adjust and change as needed." Tom outlines each in this post.

featured in #229


What Good Leaders Do When Replacing Bad Leaders

tl;dr: 1) Acknowledge the contributions of the previous leader. 2) Create space for forgiveness. It will allow people to let go of the past and make room for a new vision and direction. 3) Seek to understand your employees’ experience. Ask them what they want and need going forward.

featured in #229