Live data from Hacker News

Open Salaries: Outcomes

blog.lunarlogic.io

191–200 of 225 posts

Re: Open Salaries: Outcomes

#191
post #63

I read about this idea once as a case study. I think it was first tried at a manufacturing company[0] in Brazil where everyone from the CEO down to the packers in the dispatch shed has their salary decided by a consensus employees. It's a 3000 person company with a revenue of $160m now. [0] https://en.wikipedia.org/wiki/Ricardo_Semler http://www.freibergs.com/resources/articles/leadership/semco... https://hbr.org/198…

That's eerily similar to a scene from Atlas Shrugged.

Re: Open Salaries: Outcomes

#192
post #123

Earlier quoted context omitted.

> You could say the takeaway is don't work for companies out to screw their workers, but that's most of them. By definition, if most companies are underpaying their workers, they're actually paying market rate.

Not necessarily. Employees aren't always aware of how much other companies pay. I define underpaying as "other companies in the market would gladly poach these employees". But just because there are tons of companies willing to poach them, doesn't mean that the employees know this information.

That definition breaks down big time though depending on the nature of the business.

I know one of my senior engineers could get more but I know he'd 1) work more hours, 2) have less freedom, 3) have less flexibility.

I can't pay him what others would pay because it's a consulting business and it's getting harder and harder to get the high rates for the work we usually close.

I'm not screwing him. I make it up in other areas which is why he's still with me.

But he's suggested his market rate is like 30% more when I know the hours he'd have to put in for that are at least 30% more.

So other companies would gladly poach him but it's not apples to apples, and I'm not going to play the game of "high salary" and then squeeze my people to make it make sense.

Re: Open Salaries: Outcomes

#193
post #86

Earlier quoted context omitted.

no two employees with the exact same job title should have more than 10% difference in pay. If someone is making 40% more than others with same title then they should be promoted to higher title and if they dont deserve that title then why is the company paying them so much. It is one thing to want to minimize salary costs but another to disrespect employees with absurdly low salary.

Are titles really that meaningful? I've never worked at a place that cared much about them. Also, on a practical note, that would require 17 different titles for the same type of job if you have a 5x variation in compensation. That seems kinda crazy.

Employees care about them because getting a new title is an official recognition of their accomplishments to themselves and their coworkers, it looks good on a resume, and can definitely be meaningful for optics with clients.

I really don't care that much about them myself. I do use a few different titles depending on the client however.

Re: Open Salaries: Outcomes

#194

Companies love open salaries. Why? They can now pay a developer with 5 years of experience and the developer with one year experience the same low salary for the same position. Salary should be based on the individual (relevant experience and education) not just a job title. Why would an employee give away one of the only bargaining chips they have to get a higher salary? When I was working a regular job, I was regul…

Where are these rancid lies coming from?

Companies hate public salaries, and there is ample evidence everywhere to look, including efforts to legally prohibit employees from disclosing their salaries and unenforceable claims in employee handbooks.

More information can never make a market more inefficient.

Re: Open Salaries: Outcomes

#195
While this sounds awesome in theory, I don't think I'd find it fun to have everyone deciding on what everyone in the company should be paid. It seems like weird office politics, jealousy, and unrelated things would get involved. This is all just my opinion, but I feel like even though this idea is good in theory, it will be ruined by people, just like valve's org structure model.

The truth is, no one knows what anyone should be paid, really. The market decides it. I feel like this kind of policy just creates a powderkeg of opinion and emotion. Maybe it works for a team of 25 (at least as far as we can see), but definitely not for a company of 500.

Please everyone just put your salaries in Glassdoor and call it a day. Everyone make sure they get paid market or above, be a responsible adult and look out for yourself.

Re: Open Salaries: Outcomes

#196
post #75

Hmm. My experience tells me that a lot of this depends on the details of the team, and that there isn't a right-for-everyone policy. My story: I worked for a company that paid a bit below market salaries, for the SF Bay Area. I was on a team with two more junior engineers. At one point one disclosed to me that they felt underpaid. That led to a salary discussion where I explained that the company habitually underpaid…

Anytime two people compare salaries, at least one person gets angry. Sometimes two.

So true. Most people can't handle it. It's all relative to them and it's not usually logical.

I worked for a small startup some time ago where the owner was paying me more than she paid herself but eventually we only had 2 employees left and everything became transparent. My friend (in sales) became all upset about his salary in relation to mine and they gave him a bump. I was eventually the last one left though.

That was my first professional job and it's ironic my buddy in sales couldn't negotiate a rate he thought was fair. He's actually quite good.

People are perfectly fine working for YEARS with their own valuation and then all of a sudden they think they're worth more because someone else is making more.

And then they don't even offer a compelling reason for why they think they are worth more, which is really why they weren't being paid what they think they should have gotten in the first place.

It's every employee's responsibility to know their value and to be able to articulate it. That's a very important dynamic of the workforce whether people like it or not.

My favorite collegiate course of all time had only one agenda - to teach us to think differently in a way to be compelling and persuade. Every project was related to that premise. We don't have enough of these types of courses and that shifts more power to the employers.

Re: Open Salaries: Outcomes

#197

Earlier quoted context omitted.

There was a choice and these people would just not see the salaries list and participate in salary raise process. But we went all in, everyone was ok with revealing their salaries.

So there was the implicit threat that if you didn't join, you wouldn't be eligible for raises? Also, how could you enforce them not seeing the list? It's illegal for an employer to deter the discussion of compensation amongst employees.

They would get raises in an old way, from CEO. We are based in Poland, and as far as I know there is nothing illigal about it. Someone mentioned shoulder surfing - I believe people who would not join, would be decent enough to play by the rules and not do this.

Re: Open Salaries: Outcomes

#198

Earlier quoted context omitted.

Decreasing variance while increasing median pay is obviously a pretty big downside for everyone who is paid above median.

Your post reads like a very bleak argument against the minimum wage. Increasing the median should mean that those above the median also see an increase through economics. If the price something is $X then the price of a premium something is still going to be greater than $X.

Not really. Increasing the median by itself does not bring down the pay for top performers. The problem is decreasing variance, which does and fixed formula or transparent salaries are both designed to limit variance.

Personally, I'd never want to work somewhere where my salary is set by a formula of my "experience" level.

Re: Open Salaries: Outcomes

#199
post #86
post #75

Hmm. My experience tells me that a lot of this depends on the details of the team, and that there isn't a right-for-everyone policy. My story: I worked for a company that paid a bit below market salaries, for the SF Bay Area. I was on a team with two more junior engineers. At one point one disclosed to me that they felt underpaid. That led to a salary discussion where I explained that the company habitually underpaid…

no two employees with the exact same job title should have more than 10% difference in pay. If someone is making 40% more than others with same title then they should be promoted to higher title and if they dont deserve that title then why is the company paying them so much. It is one thing to want to minimize salary costs but another to disrespect employees with absurdly low salary.

OK, next thing there's 9000 job titles. Where's a win in this? If it just salary levels, then why bother with titles? Call it just "salary level N+1" and that's it.

Re: Open Salaries: Outcomes

#200

Earlier quoted context omitted.

>but we decided to go for open salaries anyway What happened to the people who didn't want to reveal their compensation. Was is it revealed anyways?

There was a choice and these people would just not see the salaries list and participate in salary raise process. But we went all in, everyone was ok with revealing their salaries.

That suggests either a very like-minded company (with 25 people very likely, with larger sizes less so) or tremendous amount of peer pressure. After all, if out of 25 people 24 decide to share, and 25th wants to work in this company, they don't really have a choice, do they? That person has to work with all these people after it.
Post reply on HN