Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/afternoon/engineering-management-resources

A list of resources for engineering managers of all levels
https://github.com/afternoon/engineering-management-resources

Last synced: 3 months ago
JSON representation

A list of resources for engineering managers of all levels

Lists

README 

        
Engineering Management Resources

================================



Please help me build this list. Send me pull requests for great resources you've found.



Top K

-----



- [High Output Management](https://smile.amazon.com/High-Output-Management-Andrew-Grove/dp/0679762884/ref=smi_www_rco2_go_smi_g2609328962?_encoding=UTF8&*Version*=1&*entries*=0&ie=UTF8) - "A manager’s output = the output of his organization + the output of the neighboring organizations under his influence." Andy Grove's classic text on management practices. [Ben Horowitz raves about it](http://a16z.com/2015/11/13/high-output-management/). [Lighthouse have a handy top 10 quotes](https://getlighthouse.com/blog/andy-grove-quotes-leadership-high-output-management/) which gives you a flavour.

- [Lean Enterprise: How High Performance Organizations Innovate at Scale](https://info.thoughtworks.com/lean-enterprise-book.html). This book is an entire theory of organisation design. It's aimed at enterprises, not startups, but it is packed with ideas and case studies for applying lean principles to software organisations. Contains many jumping off points, e.g. to continuous delivery, to lean, to psychological safety. Highly recommended. _#book_  _#mustread_

- [Google re:Work](https://rework.withgoogle.com/). "Let's Make Work Better. Practices, research, and ideas from Google and other organizations to put people first." A data-driven approach to understanding teams, managers, goal-setting, hiring, everything.

- [First Round Review](http://firstround.com/review/). An excellent blog on building tech startups from VC firm First Round Capital. Follows the template of "Get person who's best at X to blog about X" where X is hiring, giving feedback, product management, pricing, and so on. _#blog_

- [Software Lead Weekly](http://softwareleadweekly.com/). Weekyl email of management resources curated by Oren Ellenbogen, VP Eng at Forter. 10,000 subscribers.

- [Harvard Business Review](https://hbr.org/). An incredibly deep well of business knowledge, including management.



Culture

----------



- [How Google Works](http://www.howgoogleworks.net/) by Eric Schmidt and Jonathan Rosenberg (key early product guy at Google): a journey through how Google is structured and how it got there _#book_.

- [Netflix Culture: Freedom & Responsibility](http://www.slideshare.net/reed2001/culture-1798664). A classic from Reed Hastings, Netflix CEO



Teams

-----



- [Tuckman's Forming Storming Norming Performing model of team development](http://www.businessballs.com/tuckmanformingstormingnormingperforming.htm).



Models of management

--------------------



- [What We Got Wrong About Self-Management: Embracing Natural Hierarchy at

  Work](https://open.buffer.com/self-management-hierarchy/)

  ([Buffer](https://buffer.com/)).

- [I'm Not a Servant - I’m a Host! A New Metaphor for Leadership in Agile?](https://www.infoq.com/articles/host-leadership-agile)



Motivation

----------



- [Drive](http://www.danpink.com/books/drive/) by [Dan

  Pink](http://www.danpink.com/): autonomy, mastery and purpose _#book_

  _#mustread_



One-on-ones

-----------



- [High Output Management](https://smile.amazon.com/High-Output-Management-Andrew-Grove/dp/0679762884/ref=smi_www_rco2_go_smi_g2609328962?_encoding=UTF8&*Version*=1&*entries*=0&ie=UTF8) has a great chapter on this. One key idea for me: make them at least an hour long to avoid superficial status updates and get into the big topics.

- [A Step-By-Step Guide To Better One-On-Ones](https://www.officevibe.com/blog/guide-to-better-one-on-ones) - Officevibe.

- [How to Make Your One-on-Ones with Employees More Productive](https://hbr.org/2016/08/how-to-make-your-one-on-ones-with-employees-more-productive)

- [Conducting Effective and Regular One-on-Ones](https://moz.com/blog/conducting-effective-and-regular-oneonones)

- [Instrument-Rated Management: Treating Conditions vs Symptoms](https://smallbusinessforum.co/instrument-rated-management-treating-conditions-vs-symptoms-2ad493affb3b). Touching blog post on helping people in your team who aren't satisfied, which may mean them moving on. This conversation is very familiar.



Coaching

--------



Giving feedback

---------------



- [Radical Candor: The Surprising Secret to Being a Good Boss](http://firstround.com/review/radical-candor-the-surprising-secret-to-being-a-good-boss/)



Goal setting

------------



- [Getting started with OKRs](https://www.betterworks.com/okr/)



Career development

------------------



- [Rent The Runway's Engineering Ladder](http://dresscode.renttherunway.com/blog/ladder). Classic post from Camille Fournier sharing RTR engineering's role definitions.

- [Spotify Technology Career Steps](https://labs.spotify.com/2016/02/15/spotify-technology-career-steps/). Spotify's career path/ladder.

- [Bad Managers: 5 Signs You Shouldn’t be a Manager](https://getlighthouse.com/blog/bad-manager/)

- [15 Signs Your Employee Is Ready to Become a Manager](http://www.inc.com/young-entrepreneur-council/15-signs-your-employee-is-ready-to-become-a-manager.html)



Training (budgets, etc)

-----------------------



Compensation

------------



- [Introducing the New Buffer Salary Formula, Calculate-Your-Salary App and The

  Whole Team’s New Salaries](https://open.buffer.com/transparent-salaries/)

  ([Buffer](https://buffer.com/))



Operations

----------



- [How to write a

  post-mortem](https://blog.serverdensity.com/how-to-write-a-postmortem/)

  ([Server Density](https://serverdensity.com/))



Hiring

------



Diversity and bias

------------------



Teams

-----



- [What Google Learned From Its Quest to Build the Perfect Team](http://www.nytimes.com/2016/02/28/magazine/what-google-learned-from-its-quest-to-build-the-perfect-team.html): Google crunched lots of data about 180+ teams. They found that psychological safety is far and away the most important team dynamic. Teams that listen to one another and show sensitivity to feelings and needs are the most successful (see also the Google re:Work blog post [the five keys to a successful Google team](https://rework.withgoogle.com/blog/five-keys-to-a-successful-google-team/))



Delivery

--------



- [Working Backwards](http://www.allthingsdistributed.com/2006/11/working_backwards.html). Post from Werner Vogels about how Amazon thinks about the outcome for the customer before building something.