Seems like this is something transparent salary policies might change.
There are plenty of other things that are much more powerful motivators than money, and a good company to work for is probably not the one paying you the most. Otherwise everyone would be in finance working 100 hour weeks and loving it. The issue isn't that someone was paid $X is that they felt they were worth $Y and the other incentives and motivators weren't sufficient to overcome that. If they were paid less than they could command elsewhere but doing work that mattered to them and challenged them, felt valued by the company, were part of a good team, had flexibility in work life balance, were given opportunities to develop and learn, had prospects for advancement and the myriad other things that different people value (and sometimes value very differently) then the situation may have been very different.
From what I've seen, the problem often arise not with people hired at a low pay because they didn't know better, but hired at a low pay because that was the market price at the time. They end up having less pay than people with the same experience (or even less) who were hired later when the market salary was higher.
I disagree. There may be some instances of this, but there are also instances of people who love their job and would not change it for more money.
Money isn't the only motivator.
One doesn't follow from the other, and I don't agree that there's inherent evil just because the salary was lower than elsewhere.
The important characteristics of the companies he's talking about is that they're in an unstable equilibrium dependent on wage ignorance. Meaning that wage info itself would destabilize them rather than any of the mentioned toxicity.
I think he's excluded "companies that underpay but are stable in the presence of wage info" from the class that "should [be expected to] crash and burn".
Random number: 50% of employees consider their employment as a stepping stone.
Most people I know in similar roles to mine act in a similar way. So I'm not so sure that most companies are really out there trying to underpay their employees. In terms of running the business, I want to pay people fairly for a good day's work.
But are you a line manager or is part of your performance KPI's the profit of your unit? Or are you an owner in a small business whose own income is directly influenced by salary expenditure, like when you're running a (small) body shop or sell hours? Those are all very different situations to be in.
> open salaries would be problematic for me, because I've made some bad bets on new hires who are overpaid compared to what they deliver, but where it's not reasonable to fire them either.
Open salaries would give you precisely the leverage you need to reduce those employees' salaries. "Your initial salary was X, expecting better-than-average performance. Your performance has been comparable to Amy and Ben, so your salary now matches theirs." They would either accept the reduction or would leave, without you having to fire them.
The bigger problem would be it would tend to reduce the variance in salaries (why does Carl get 50% more than I do?), which may result in under-paying top performers, reducing their incentive to stay.
In the end, though, the dissatisfaction is an edge-triggered phenomenon, not a level-triggered phenomenon. The introduction of an open-salary model to an opaque-salary environment seems tough for everyone, especially if there is a large disconnect between people's perception of their peer's performance vs. their actual salary. But in an open-salary environment, especially one with a feedback loop, it seems like it would be difficult to get into that state in the first place.
By definition, if most companies are underpaying their workers, they're actually paying market rate.
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.
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.
It got out, people got pissed, which they should have been.
Well, we're lucky enough to be in an industry where there are more jobs than qualified candidate. So if you know your market value, make clear what you want when interviewing, you can find a job that will pay you what you're worth.
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.
Is that an argument? If yes, I don't see it. If people believe that they couldn't earn more they are probably "perfectly fine" due to this missing information. Then they learn what their peers make and think - rightfully* - "just a moment, I do the same job, to the same quality, why is my peer earning more than I am?" which in itself is already a compelling reason (so, your next point usually does not apply).
> 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.
And open-salary makes this easier and harder to screw people over using information-asymmetry.
* Yes, there are some people who just don't work as good as their peers and that's the reason they don't earn as much. From all I've seen over the years I am absolutely sure that this doesn't count for a significant part of the workforce compared to the part of the workforce that does a job comparable to their peers but still earns less income.
I'd rather say that the main discomfort coming from salary discussions is not caused by money, but about having some people acknowledge that they're not as "good" or valuable (in that setting) as they'd like to think. Social status and "saving face" is very important, and open salaries essentially force some people to be publicly downranked - either by having salaries reflecting their worth (showing some people as not equal to others) or by having mostly salaries (downplaying people who do deserve more).
Often, ignorance actually is bliss; as the lower paid people can keep believing that they're equally valued - opening the salaries can't make them equally valued, they're still be low-paid, but now they'll be angry about it.
So true. I actually had to have a very candid conversation with my business partner and explain to him that my time is more valuable than his based on how and where I contribute and market value, I can't put in time in direct proportion to the time he puts in.
It was a tough thing to discuss but he understood and it was a very good conversation to have so we could move forward with a better understanding. This wasn't a salary conversation but a value conversation which forced him to really think of both of us and the company.
There are also intangibles that people overlook. If someone is more pleasant to collaborate with and adds more value culturally, that could be why they are paid more. Most companies aren't running an assembly line where doing the same job may be more likely.
When salary "discrepancies" are found out, employees won't learn a lesson and take ownership for their situation. They'll spend time investing in their skill-set but they won't spend a little time here and there to do market research or go interview a few times each year or every other year. There's also specialists who can tell you what market rate is for your position if you need help. If you don't accept this as part of the workforce, be prepared to be earn less. That's on you.
Then our experiences differ (which is sad but okay) - I have seen, multiple times, the situation that not only the person who uttered it thought it was true but the better paid peers agreed (and yes, they agreed in private, not only in public where they had to fear to be judged if they said "well no, he is not as good as he thinks").
The dynamics weren't changed, you were all just able to finally see the reality of your situation: you were being taken advantage of and no one told you.
If anything this changed the situation from a developer leaving without notice for a higher paying role at a different company into a situation where the company could have retained them.
Meh, job titles are just buckets. Comp is also a bunch of buckets.
Why should these buckets be necessarily tied in size?
Lots of flatter organizations have a smaller number of titles but larger comp buckets.
There is nothing necessarily wrong with this.
I've had plenty of experiences where people in equivalent job titles had vastly different productivity (and, justifiably, vastly different titles).
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.
I really don't care that much about them myself. I do use a few different titles depending on the client however.
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 people, and I was happy to share my salary with them so they would know they're not the only ones underpaid (and also, implicitly, so they'd know if they were getting taken advantage of, since I'm all about employees looking out for each other).
As it turned out, however, I was making around 40% more than both of them. Some of that was due to more experience, but it was more a matter of me being underpaid versus them being outright screwed. Naturally they went and asked for a well-deserved raise, and the company, of course, said no.
This changed the team dynamics in a fundamental, toxic way. It engendered bitterness from them not only toward the company but to me as well, which ultimately led to all of us leaving the company for greener pastures but with lots of bad feelings all around.
You could say the takeaway is don't work for companies out to screw their workers, but that's most of them.