Personally, this has lead to me getting messed with my managers ~never, which is a very high-order bit in my work happiness.
I am not knocking the system, as I agree that a meritocratic structure can work in small social systems, but there are some risk. The primary ones would be new member exclusion which can be hidden behind the meritocratic mantle of "it's the best choice", and fiefdom building that can result from the finite number of members that can function in a social group or that can reliably be recalled/indexed by members with in a group.
It may be possible to have numerous self contained and self structured groups operating within a larger organization, assuming the time tables allow for them to establish, and that new member barriers are not so obvious that they decrease retention. Facebook may be knowingly or unknowingly leveraging their Employer Brand to mitigate the risk of attrition within hierarchy-lite system.
The problem isn't traditional office politics, as far as I've seen. The problem is that sometimes the influential engineers can be shortsighted about other teams' needs and it can actually be hard for management to step in and say hey look.
In case this wasn't a phonetic typo and you're really not aware, the word you are looking for is "cliques". Cheers!
Isn't this the definition of politics? Trust is a personal feeling based on other opinion and your own experience while level should be based on documented achievements in the company.
Same with influence over authority. Influence is just another word for politics.
Political status becomes the primary product at work. Actual work performance of individuals and teams becomes secondary.
Decisions become increasingly irrational because the interests of low-status individuals - including customers, suppliers, and other employees - start being seen as an annoying distractions from personal profit/status.
If that's reversed and performance becomes more important than status, you're already in a healthier place.
Empires can be very profitable. But they're also miserable places to work, and they rarely have much customer good will.
Still toxic.
For instance, a lot of non-software companies may pay more and provide a director or executive level title to a developer and give them a team just to get them in the door.
What these people don't immediately realize is they are giving up being a "tier-1" employee at the organization. First and foremost if you are at say, a tire company, software is most likely a cost center and not central to the strategy. This means they wont attract good developers, and have to do things like above to get them in the door.
If you want to work with really passionate and talented software developers, you'll want to be at a primarily software organization, or one that sees the logistics of software central to the business strategy.
If, say, a Software Architect and a Senior Director have the same pay and the same perks and the same bonus structure, and it really does take a talented person the same amount of time to climb that high from (say) Software Engineer and Manager, then they're parallel.
If any of that favors one side over the other then they're not.
I doubt any company is going to give access to enough data to prove or disprove the claim; but the default believability isn't very high.
I have a doubt: "the same pay and the same perks" things seem okay but "the same bonus structure" seems difficult to understand.
A manager has more visibility, more access to business info then he/she will have more chance to be eligible to "bonus" than an engineer has.
So, it'd great if you elaborate on how a Software Engineer and a supposedly equal Manager can have "the same bonus structure".
Many large software companies have very similar structure.
Since I had personal experience working in these companies here what I found as problem:
- Management has decision making power.
- Management has ability to control $$ (bonus allocation, etc.)
- Management has access to more information than employees on "individual contributor" track
It is important to note that system work up to mid-level managers. I.e., it is works well when there is "team lead" and "manager". Manager ensures that the team is not bothered by politics and get all necessary resources while team lead ensures that things are done.
But when you come to mid-level and up even if the pay is comparable, the life is much better for managers. For example, if you are in 40s it is important to have job security. Senior managers and VPs will know when are layoffs are coming or certain groups will be sacked (since they have access to more informations). They can prepare for it. If you are "software architect", you are in the blind until the day of layoffs.
Companies that are set up well also give minimal control over bonus allocation or salaries. These things should be controlled by HR and recruiting, along with salary and compensation policies based on role and level. Managers supposedly have the best view on IC performance, so within some band they should be able to influence rate increases and promotions. Anything outside of that would need to be a conversation between the manager/IC and HR. My advise here is if you feel there is a deviation in your pay, get your manager to bat for you, do not go to HR yourself.
And by design, management will have access to more information than individual contributors, but that's the purpose of the role. This person brings in information, priorities, and resources to the team to execute. This is where the "power" idea comes in, but anyone in this position long enough would tell you its more of a "responsibility." It's not always clear what is right and what isn't, nor even a way to really prove it ex post facto. Could it give someone enough perspective to make self-interested decisions that ICs could not? Probably.
I suppose the question is, is that bad and how is it bad, and how would you eliminate it?
Edit: My wishful novelist inside me says its the software program that automates resource allocation, charter, and IC development. You could essentially build an autonomously managed organization with IC roles being the only true human employees.
Relaying on HR for anything related to company development and future (i.e., bonuses) is very very dangerous. I was there and you have to see shenanigans and company politics in that case.
So the problem is:
1. you can give power to HRs to allocate bonuses
2. you can give power to EVPs and VPs to allocate bonuses
It is much better to give this power to EVPs and VPs.
> And by design, management will have access to more information than
> individual contributors, but that's the purpose of the role.
And that cause of the problem :( ICs will have less information and thus when things come to making decisions, people on management track will make better decisions (since they are have more information) and thus subsequent promotion. I was also there...
Either way - I think you may have misinterpreted my remarks about HR.
A lot of flip flopping and lack of follow through.
Who made that decision? We did. Can we give up on that and try something else? Of course.
I kinda like to have at least a shepherd for the day to day decisions, if not a commander.
In practice in my current environment it's been the occasional PM that takes some ownership that fills that role, but in many groups I see the floundering without leadership.
Internally I think they think they're making progress because everyone on the team is always happy with their decisions, I may just be the old curmudgeon that's frustrated with what I see as wasted effort.
This essay was illuminating:
Tyranny of Structurelessness
https://en.wikipedia.org/wiki/The_Tyranny_of_Structurelessne...
"Contrary to what we would like to believe, there is no such thing as a structureless group."
The same essay was linked to me a previous time I made a similar public complaint :)
Your peers form an agile group to deliberate. You have non-management product owners and stakeholders to guide you (shepherd you).
You have a supervisor who deals with HR business like time off, but is unrelated to your product decisions.
The feedback my own manager shared with me that had been collected from my reports was that they appreciated what I was trying to do, but that they also wanted me to have a more active technical leadership/decision-making roles.
What I'd failed to do was talk enough specifically with the rest of the team around what they wanted the roles to be, vs just assuming they'd want maximum autonomy. This will vary depending on composition of team, familiarity of the devs on the team with the problem area and stack, etc.
It will also depend on if managers are expected to be almost-purely people-managers or if they're also expected to be domain knowledge leaders as well.
There's no one-size-fits-all approach, but the thing I've seen that separates a good manager from a bad manager is being able to adjust their approach in things like that based on the situation vs sticking to a script.
I'm saying this as a candidate that didn't get selected. I got great actionable feedback on how to be a better leader, and I'll keep my fingers crossed when there is another opportunity available.
i.e. when it comes down to the icon, your group should agree to trust the designer, and then trust the designer. The benefits are numerous: 1) People get to make the decisions within their realm of expertise, 2) No aimless debate, products are built faster, 3) If there was a bad decision, there is one person who made the decision, but the whole team should share accountability since they all agreed to trust the person who made that decision.
The process by which that decision is made is the process by which you select a person to make that decision. Ideally, that happens at the hiring level, so once, for example, a designer is assigned to your team, you already know that s/he is good enough to pick the right color. You don't have to engage in office politics to discover whether or not you can trust him/her, and you don't have to engage in office politics to allocate praise/blame in the event of particularly good/bad decisions.
there also is a ted talk by semco ceo ricardo semler: https://www.youtube.com/watch?v=k4vzhweOefs
Not a peer.
I favor democratic decision making processes.
Use voting systems appropriate for the task. Roman eval for new hires, go/no go. Approval voting for triage, new features. JADs for "visions". Creative writing exercise for post-mortems. Etc.
"Democratic" does not mean winner-takes-all, which is suboptimal.
"Democratic" does not mean consensus.
I rather don't agree with this one.
'Voting' should almost never, ever be used.
For so many reasons.
Rarely should everyone have an 'equal say'. You are not 'equal citizens' in this. Second - is that it leads to politics - 'I helped you last time, you help me this time' etc. Unless you get into crazy things like 'hidden ballots'.
There is no substitute for leadership.
Often, a mediocre decision, executed upon well, will lead to better outcomes than 'great decisions' wherein their is fudging, lack of insight etc..
In situations that require broad input, a decent moderator should be able to assess the 'consensus' and go with that.
In many design situations, architects and designers should basically set the direction, absent issues brought up by team members.
Things like 'should we all use the same IDE' or 'what IDE's can we use' - obviously require a lot of input from team members and maximum flexibility.
But things like API design ... that needs to be really well curated and it's best left to the experts - with strong feedback from team members.
Second this, true in my experience as well.
It's not about making everyone equal at all times. What's important is how do you choose a leader and when.
In silicon valley contacts are as valuable as money and a person with manager in his title will build contacts faster and achieve more than a developer who actually might have made more impact for his employer.
People with manager in title can work from home more often, travel on company paid trips more often and in general have a better social life than developers. At the end of the day managers can make a developers life bad if he/she wants too. That is what matters.
the best thing about it? engineers who aren't good at the strategic, human high-touch, or political issues, but excel at execution and implementation aren't managing teams of people -- they're busy executing and getting paid (and further promotions) based on their ability to execute, not on their ability to manage herds of programmers.
as a software engineer, i love that my boss is my boss because he's good at managing teams of software engineers. not because he's the best software engineer in the house.
politics in the end is a part of life; it should not dominate or overshadow goal oriented work, but it is a natural, unavoidable consequence of people holding different viewpoints.
on the other hand, all the openness strategies they suggest are great, and these do work well in practice to mitigate conflict [but politics does not equal conflict].
This is nice in theory. But when your "peers" with Manager in their title have access to more information and more decision-making power, it is not in fact a parallel track. Just saying people are equal doesn't make it so, and it doesn't change the underlying organizational structures.