4 ms·
I think this is a great step and something that needs to be talked about more. To me breaking the strict hierarchy is the new remote work. What I’ve seen work
by mountainriver 5y ago
I think this is a great step and something that needs to be talked about more. To me breaking the strict hierarchy is the new remote work.
What I’ve seen work really well is treat all products like open source projects. Some people call this “inner source” but that term is a bit muddled.
Work is organized around projects and functionality, not dumb middle management. The group around the project keeps an open backlog, anyone is welcome to participate in meetings or pickup tickets.
Those that contribute the most get the most say, a true meritocracy.
Developers are simply judged based on the scope of their contributions.
It’s dead simple and it works really really well
- BigRedDog1669 5y ago> Developers are simply judged based on the scope of their contributions. How would you do that? Lines of code?
- prmoustache 5y agoSome metrics always have to be implemented to make sure the teams fulfill their role. Metrics depend on the kind of role. As a sys admin team we were relying on uptime of the services we were managing.
- fhd2 5y agoFWIW, I did that for years quite successfully in an organisation with about 80 engineers! At that scale, it works, in my experience, not worse than an org with lots of managers - they're gonna do infighting amongst each other at a certain size anyway :P