5 Non-Verbal Behaviors Killing Team Health
- Raviraj Achar tl;dr: Raviraj shares annoying non-verbal behaviors, how he avoids exhibiting them, and how to deal with them. These include: (1) Silent but Irritated - the person that rolls their eyes when they hear something “stupid” or exhales heavily when someone disagrees with them. (2) Annoying Interrupter - they appear eager to interrupt the speaker and can’t seem to wait for their turn. This behavior can be distracting when the speaker is trying to make their point. (3) Ever Confused - The person gives a puzzled look to everything you say but asks no follow-up questions.featured in #506
Meetings For An Effective Eng Organization
- Will Larson tl;dr: "I’d like to recommend 6 core meetings that I recommend every organization start with, and that I’ve found can go a surprisingly long way. These six are split across three operational meetings, two developmental meetings and finally a monthly engineering Q&A to learn what the organization is really thinking about." Will discusses each in depth.featured in #506
Meetings For An Effective Eng Organization
- Will Larson tl;dr: "I’d like to recommend 6 core meetings that I recommend every organization start with, and that I’ve found can go a surprisingly long way. These six are split across three operational meetings, two developmental meetings and finally a monthly engineering Q&A to learn what the organization is really thinking about." Will discusses each in depth.featured in #505
featured in #504
featured in #504
featured in #503
featured in #503
Performance Management: The Rising Tide
- James Stanier tl;dr: A good performance management system includes: (1) Clear definitions of performance expectations for each role. (2) Regular performance review processes - self-assessment, manager assessment, peer feedback. (3) Calibration to ensure fairness and consistency across the organization. (4) Performance Improvement Plan process for underperforming employees. (5) Compensation process tied to performance outcomes. James discusses how this generates a power curve over time.featured in #502
featured in #502
Using Metrics To Measure Individual Developer Performance
- Laura Tacho tl;dr: Laura reframes this into another question that leaders need to ask to evaluate reports: “what data are you going to use to evaluate my performance?” Her high level advice, which the article dives into: (1) Determine how you want to measure performance first, then find metrics to measure what's important to your company. (2) Focus on outcomes over output, using output metrics mainly to debug missed outcomes. (3) Watch out for metrics encouraging the wrong behaviors. (4) Metrics alone aren't enough - you still need active performance management and feedback.featured in #502