That's a very real possibility, so it's definitely something to be wary of and manage carefully, but if you adjust the made up math above to something more reasonable:
6x + 3x + 3x
Where your 10x reduces their own output to help the others triple theirs. This:
That's probably a better example... I consider myself a high output person, but that's usually offset by helping others, and part of my day "growing"... Most days I spend my pre-lunch hours reviewing emails, in meetings or reading things like HN articles. Afternoons I try to stay head down (headphones on) from 1pm onward.
Some people that you may be working with are simply resistant to actually expending a portion of their own day to learn/grow. Even if directed by others, or when you try to help. I do find that the best use of that bending of wills is participating in regular code reviews. Offer suggestions of things that should be changed before accepting, and other things that should be done differently in the future.
When you do that, you'll see your peers taking on more and growing over time. But it isn't easy, and will never be thatn 0x + 10x + 10x that was suggested upthread.
6x + 3x + 3x
Where your 10x reduces their own output to help the others triple theirs. This:
- doesn't decrease overall productivity (still 12)
- probably increases consistency across your product (with workloads being spread more evenly)
- increases bus factor
- will lead to productivity gains as the team grows