[ido]

Sure but in my original example the “1x” guy was not actually an acceptable performer. I just meant someone great could easily be 5x better, not that 1x is the average (their average peer would be >>1x).

I’ve learned from experience that it’s not worth compromising on a mediocre developer (even if in some situations I’d have to). Better take the short-term hit of trying to find someone good.

Also the 5x ones would mostly not be genius level, just actually motivated and talented. I think a lot of people that can do well are stuck in jobs that aren’t a good fit for them.

[cxr]

> but in my original example the “1x” guy was not actually an acceptable performer

It actually was. You said so yourself:

> perform “adequately” (the project got made to acceptable level)

You need to figure out whether you're talking about someone who is acceptable or not.

[ido]

Did you notice the quote marks around adequately? We managed to hobble along but it was obviously not going great. "It wasn't catastrophic" isn't my goal. I want stuff to go really well, not just about enough to not go out of business/not be in violation of contractual obligations (with a lot of slack getting picked up by their better performing peers).

Again it depends if you have an alternative, in my experience I always had it was just sometimes costly/inopportune/a pain in the ass in the short term to find someone better. Long term it was always better (I never regretted firing someone too quickly but often regretted firing someone too late).

I was also always worried about team morale but every time a low performer was fired it actually improved morale.