I managed software delivery for thirty years and retired because of a word: synergy

I spent thirty-one years managing software delivery teams, starting back when we shipped releases on physical discs and a bug meant somebody drove to the client's office with a floppy in their pocket. By the end I was a senior delivery manager overseeing three project teams at a mid-sized software house that built custom systems for other businesses.

I've seen every management fad come and go. Waterfall, then agile, then scrum, then something called scrumban that I still don't fully understand, then whatever the consultants were selling that particular year. Each time, some bright twenty-six-year-old with a certification and a lanyard would arrive to tell me my twenty years of shipping working software the old-fashioned way, by actually talking to the developers, was obsolete.

What never changed, through all of it, was the actual work of managing people. Knowing that your best backend developer goes quiet and snappy right before he's about to burn out, and that the fix isn't a performance review, it's telling him to take Friday off before he asks. Knowing that the junior tester who never speaks up in standups will tell you everything that's actually broken if you catch her alone by the coffee machine. That kind of management isn't in any framework. I built it over three decades of paying attention.

The last two years, the company brought in a new VP of delivery who spoke almost entirely in phrases I couldn't translate into anything useful. Every meeting had words like synergy, and alignment, and leveraging cross-functional velocity, and I would sit there taking notes trying to figure out what he actually wanted my team to do differently on Monday morning. Half the time the answer, once you cut through it, was nothing, he just wanted us to say it differently in the status report.

The real problem started when they layered a new project management tool on top of everything, one that tracked "engagement metrics" for each team member, essentially scoring how many messages people sent in the chat system, how quickly they replied, how many meetings they attended. My best developer, the quiet one who burns out silently, scored terribly on this thing because he does his best work heads-down with his notifications off. The system flagged him as "low engagement." I had to sit in a review explaining that a man who ships flawless code for six hours straight without checking his messages is not disengaged, he's the opposite, and getting laughed at, gently, by people who'd never shipped a line of production code in their lives.

I fought that battle for about a year. I lost most of the small skirmishes and a few of the bigger ones. What finally did it wasn't one dramatic blowup, it was death by a thousand meetings about things that used to just get handled. I found myself spending four hours a day in calls justifying decisions I used to make by walking twenty feet across an office, and maybe forty minutes a day actually managing anyone.

I put in my notice on an ordinary Tuesday. My director, genuinely a decent man caught in a system bigger than him, asked what it would take to keep me. I told him honestly, it would take going back to a world where I manage people instead of managing a dashboard about people, and we both knew that wasn't coming back.

I still do a little freelance project consulting, mostly for smaller shops that haven't yet discovered the joy of measuring engagement instead of output. Somebody asked me recently what advice I'd give a new delivery manager starting out today. I told them, learn the frameworks because you'll need the vocabulary to survive meetings, but never let the framework replace the twenty minutes you spend actually listening to the person sitting across from you. That's the whole job. It always was.