3 ms·

Great observation! I didn't think about the FOSS model of management as I was writing this - only startups. The meritocracy model works even better with FOSS

Great observation! I didn't think about the FOSS model of management as I was writing this - only startups. The meritocracy model works even better with FOSS - blowhards who can't deliver don't get very far when there is nothing but delivery to be done. Both models (FOSS/Startups) are somewhat vulnerable to those who are the loudest winning by sheer volume. In both cases the BDFL/CEO can intervene but it wastes time/energy when it's needed most.

drawkbox 12y ago
True, OSS is also usually more philanthropic in that many times it isn't directly a paid situation or most times which changes the dynamic. However many people do OSS to attract business with as well or specifically to do business on that isn't controlled by a company i.e. Linux, Rails, Python etc. I am sure in a flat company, compensation is probably the toughest part as it can easily turn into a popularity/tribal thing possibly unless there is some set ranges and agreed upon structure. I wonder in a flat company if compensation needs to be more open.
- RKoutnik 12y ago
  I haven't heard of enough companies that are open about their open compensation, but Buffer seems to have it handled pretty well: https://open.bufferapp.com/introducing-open-salaries-at-buffer-including-our-transparent-formula-and-all-individual-salaries/ https://open.bufferapp.com/introducing-open-salaries-at-buff... The difficulty lies in quantifying experience - there loads of ways to pull that off (and none of them quite wrong). Years of experience, type of hackery, FOSS contributions, etc. I'd say the best option would be to pick one and stick with it. If you're properly open about it, those who take issue with your system won't apply.
- rhizome 12y ago
  Open-Book Management: http://en.wikipedia.org/wiki/Open-book_management http://en.wikipedia.org/wiki/Open-book_management

drawkbox 12y ago

True, OSS is also usually more philanthropic in that many times it isn't directly a paid situation or most times which changes the dynamic. However many people do OSS to attract business with as well or specifically to do business on that isn't controlled by a company i.e. Linux, Rails, Python etc. I am sure in a flat company, compensation is probably the toughest part as it can easily turn into a popularity/tribal thing possibly unless there is some set ranges and agreed upon structure. I wonder in a flat company if compensation needs to be more open.

RKoutnik 12y ago
I haven't heard of enough companies that are open about their open compensation, but Buffer seems to have it handled pretty well: https://open.bufferapp.com/introducing-open-salaries-at-buffer-including-our-transparent-formula-and-all-individual-salaries/ https://open.bufferapp.com/introducing-open-salaries-at-buff... The difficulty lies in quantifying experience - there loads of ways to pull that off (and none of them quite wrong). Years of experience, type of hackery, FOSS contributions, etc. I'd say the best option would be to pick one and stick with it. If you're properly open about it, those who take issue with your system won't apply.
rhizome 12y ago
Open-Book Management: http://en.wikipedia.org/wiki/Open-book_management http://en.wikipedia.org/wiki/Open-book_management