Hacker News new | ask | show | jobs
by sheepmullet 2987 days ago
> For context this is an org that has been, historically, in the dysfunctional area of the operating spectrum, high employee churn, lots of technical debt, no testing to speak of in flagship product

> P.S. Team size is 10 devs, core team of 4 in U.S.A co-located, all others remote international.

My advice would be to bring in a good dev manager and stay away from trying to narrowly define dev productivity metrics.

A good dev manager will be able to bring you up to average and fix the obvious problems.

If you are part of a larger company then the business side is probably using OKRs (objective-key results) or something similar to track at a higher level. Start looking at and making sure your team is contributing to these.

As a senior manager your teams self-assigned dev metrics are meaningless to me. It's not going to be enough to justify more staff, pay rises, different work, etc.