The Software Manager Playbook (WIP)

What is this?

This playbook summarizes the first 20 years of my journey serving and leading software organization. In these two decades, I've overseen thousands of software releases - coding, designing, planning, growing teams, mentoring fellow engineers and managers.

I've made mistakes and took many wrong turns. I'm sharing this so you don't have to go through that.

Who are you?

I’m Max. My software journey started at 7 on a CoCo2, and that original passion is still with me. I've worn many hats: developer, team lead, architect, manager, director. The titles never mattered to me, it's always been about the software. I've gone back and forth between more and less technical seasons, coached managers and individual contributors, served organizations large and small (5 to 50). I delivered hundreds of software projects. I still code.

Why are you sharing this?

Two decades in the field has provided me with some insights about what works and what doesn't. Some of what I learned aligns with the ambient wisdom, other things don't. By penning this down, I hope to provide a repeatable framework to create and maintain software organizations that are performant and fun to be a part of.

Anecdotally, colleagues have told me this information was useful to them. I hope it can be helpful to others as well.

Are all aspects of the Software Manager's role covered here?

No, a lot of stuff is still missing. This guide is a work in progress.