/Management Process

The Wall Of Technical Debt

- Mathias Verraes tl;dr: "The Wall of Technical Debt is a surface in your office where you visualize your tech debt on sticky notes. It has a profound impact on how we choose to add, reduce, pay back, or ignore debt."

featured in #173

The Importance Of Design Patterns When Leading Large Teams

- Byron Delpinal tl;dr: Guiding multiple teams toward a single goal is difficult. Here’s how software design patterns can encourage open lines of communication, make alignment possible, and help those teams thrive.

featured in #171

Work Is Work

tl;dr: Org design is fetishized by corporate America always looking for some hack. There isn't one. Organizations are imperfect and, at very best, scale linearly. Despite that, there are tips on how to design a scaling organization here.

featured in #169

The #1 Bug Predictor Is Not Technical, It's Organizational Complexity

- August Lilleaas tl;dr: Microsoft Research conducted a post-mortem into why Vista failed. Organizational complexity - the distance between decision maker and developer - was the most accurate predictor of bugs. 

featured in #166

Tech Lead Expectations for Engineering Projects

- Gergely Orosz tl;dr: Framework of how Gergely manages his team at Uber including the initial team setup, how risks are managed, stakeholder communication and more.

featured in #166

How GitHub’s CTO Architects Engineering Teams That Scale

- Jason Warner tl;dr: Software distribution is based on a social network, and it works well. It's a system of checks and balances refined over time. As engineers we perceive it to be slow, which is not always the case. There is a stark difference in quality between managed (Linux, Debian) and unmanaged (Chrome Extensions, PyPi) distribution. 

featured in #165

Essential Meetings To Have With Your People As A Manager

- Ajahne Santa Anna tl;dr: In-depth guide on how to hold the following meetings - one-on-ones, skip level, career conversations, goal reviews & performance reviews.

featured in #155

Four Magic Numbers For Measuring Software Delivery

- Dave Lush tl;dr: (1) Lead Time  - time it takes to validate, design, implement and ship a new valuable thing (2) Deployment Frequency  - The no of times per developer per day we ship to production (3) Change Failure Percentage  -  When you deploy to production so regularly, do you keep breaking it? (4) Mean Time to Recovery / Resolution . Click through the link here if you're paywalled.

featured in #144

Using 6 Page and 2 Page Documents To Make Organizational Decisions

- Ian Nowland tl;dr: Why these documents are effective, when to use them, how to approach writing them, followed by how they should be reviewed in a meeting. Click the link in this tweet if paywalled.

featured in #139

Daily Stand-up Meeting, Weekly Staff Meeting – Or No Meeting?

- Claire Lew tl;dr: Organizational knowledge sharing is beneficial to productivity, but sharing is costly and difficult to implement. This guides on the finding the right cadence to share effectively. Click the link in this tweet if paywalled.

featured in #139