I'm 95% convinced that companies larger than 50 people can't acquire truly outstanding people without having a decentralized system that doesn't reward power grabs and people pyramids.
I wonder if it's even possible to have a system that doesn't reward power grabs and pyramids at a certain company size. Maybe the number isn't 50; maybe it's slightly lower or slightly higher. But certainly above Dunbar's number, we start to see organizations where departmental siloing and fiefdoms emerge. Politics seems inevitable in these situations, and the people who a) want to play the game, and b) are good at playing the game are the people who win the game.
The game exists because all it takes is one or two people to will it into existence. If a power vacuum opens up, or if enough competing VPs and Directors emerge, then someone is going to try to get ahead through politics. The only way to counter that is to play politics. Office politics, as a whole, is an emergent property of the individual players' political strategies and counter-strategies.
I have yet to work for, or with, a large company where office politics wasn't a significant factor. It's a bigger problem at some companies than at others. But it's always there. It can never be completely curtailed; it can only be mitigated. The best way to mitigate politics is to implement communications, reward, promotion, and advancement policies that don't incentivize politics as much as other systems might. This is a nontrivial challenge, especially at big scale.
Somewhat related: I used to believe that if some company could manage being a BigCorp and still keeping the lean startuppy feeling in terms of work conditions, individual creativity and management transparency, that would be Google. I don't know whether they ever tried, but from what I hear and see (from the outside, never been even close to being inside) they haven't succeeded and became a by-the-book BigCorp with the usual problems.
Or did you mean you were hoping for a Valve style structure, and they weren't going there?
Here is what is going to happen next: He is going to get his own ideas about what I should work on, his own theories as to how to make the company grow faster, and his own vision as to what I should make.
Prior to that it was obvious to everyone that I was killing it. I made the company a million dollars in my first month just by writing a custom classifier for adword optimization (this was back before some of this stuff was automated or startup-ified). But when he takes over what is going to happen next? He is going to take credit for his "idea" because he set me on the "path" to solving the problem or making more money. Fuck that noise, it's parasitism and par for the course for management.
You also take on the task of making sure everyone's individual skills and aspirations line up with the company's, that teams are developing well in parallel toward a unified vision, and so much more.
Do you really want that job? If what fired you up most was your ability to kill it as an individual contributor, why not stay in that role and help hire someone else to take on the management side?
It sounds somewhat petty, but I can sympathize because the company I work for is going through a similar transition and I've seen the strains that even a single extra manager can have on communication. If the CTO is the one who approves your raises, and now the CTO's opinion of you is not shaped by you but by reports of you created by an intermediate third-party, a lot of somewhat complex interacting variables just got introduced into the equation.
If you start out at the bottom of a huge company like Google, you get used to that from the beginning. If you join a company with <=25 people and watch it grow, then you can really feel the transition sometimes.
But I don't think that means management is parasitic. The fact is that at a certain size all organizations need management, and a good manager helps you be productive. Whether you are recognized for that or whether credit gets usurped by your manager is a separate question.
Seems pretty tightly coupled to me. Losing individual contributors capable of implementing million dollar AdWord campaigns, for example, is going to have a big impact on the manager's team's productivity. So I think recognition and productivity are very tightly coupled.
As a CTO I have a foot in both camps, and I have to say there's a lot about management that developers don't know. In fact, my best management is never even known by my staff, they simply deal with a metric ton less bullshit due to a thankless move on my part—ignorance is bliss. Granted, it's probably easier for NNPMs to hang around an organization than NNPPs by virtue of tangibility, but I've seen enough NNPPs to know that programming is far from the transparent, egalitarian utopia that tech folks wish for.
Why makes you axiomatically claim "of course" managers are going to be sociopaths? That is not a given at all. There are good actors and bad actors on all sides. Do you think there aren't developers who play games to protect their turf and do the minimum to get by while collecting a paycheck from a business that they contribute nothing meaningful to?
You should try to keep your staff in the loop. Hiding things just means that you end up with a far bigger mess when you aren't able to shield them from it. If you keep your staff in the loop from day 1, it becomes far easier to deal with problems later. Because they won't even be problems then, just challenges that everyone knows about.
And after all, it sounds like you were to be involved in the interview process. You would have had an opportunity to help select a candidate you could work with. Maybe it still wouldn't have worked out, but it just seems unfortunate to me that you didn't even give it a try. Of course there could have been other factors you haven't mentioned.
Don't get me wrong, I really appreciated my time there and the people there are all really nice, in fact the company I founded recently is with two former FreshBookers, but I just want more freedom than people are usually willing to give me.
It is typical for a company to outgrow its early hires capability to manage that growth well; approx 50 people is a fundamental transition for most. This is difficult, often painful, and is likely to go more smoothly by adding relevant experience and maturity to the team. When the dust settles it's a different company and, if done well, capable of much more than it was.
The irony is that you work in advertising which itself is parasitism.
She didn't get the job.
I have hired people at salaries greater and lesser than mine. Occasionally, the person above me was earning less than me and in several cases the person under me was earning significantly more than me.
The only question should be: is the person in the correct position and earning the amount they are being paid.
This known as Peter Principle
My belief is that management & compensation should be completely decoupled, so people wouldn't seek to do management for "career advancement", but because they actually enjoy management. For example, I hired a product manager last year and he really loves the work. It allows him to mix small engineering projects with product strategy, requirements elaboration, and his considerable people skills. But I don't see him as a "superior" to my other engineers -- he is just a contributor, like my other engineers.
The "pay scale" for management should be similar to the pay scale for advanced individual work, in my opinion. Unfortunately, that's not the market we live in, so I can see why people would choose to seek management for "advancement" reasons, but this is just an unfortunate side effect of the market and ultimately causes a lot of talented contributors to do work they don't really love. Why? Essentially, for the money & prestige that needlessly comes with it.
One route to that is by getting out of mainline production coding and going meta: designing new systems, programming languages, tools etc. Good work if you can get it, but prone to failure. Another route is to become a manager. There's plenty of demand for managers with technical ability, a clear route for advancement and much lower risk of failure.
I'm thinking of the recent Ask HN "What happens to older developers?" Which I answered in some detail here https://news.ycombinator.com/item?id=7373301
There's lots of reasons for wanting to get into management, and I've found that one of the main motivators is wanting to get out of direct code-slinging software development as the majority of their day and use their experience for the company good in different ways -- basically new challenges and all that...but keep a similar level of pay. And very few people these days want to stay at a single job for more than a few years. So for a very experienced developer, they may start to feel "trapped" in their career and may not even know it.
Sorry, I don't want to be contradictory or make you defend what's obviously a working system for you guys. Just food for thought.
The managers your describing sound more like PM's.
So decisions on who gets promoted are made by people for whom getting promoted chimes with their value system.
I come across mentions of WWII era projects, designs of famous aircraft etc where the designs were incredibly well suited to the needs, and produced in incredibly short time-frames. Some of that is obviously the war-time focus, but I also notice that in many of those projects the lead position is not a non-technical manager, but a technical chief engineer where management functions must have been subservient. Unfortunately, there isn't a huge amount written about the organizational day-to-day project structures during WWII.
I think at least some of the appeal of startups and smaller companies for technically oriented people is that division of responsibility is not as formalized and contributions can flow more easily between different domains. But again, startups are structured where technical founders are at the levers of control, and that's inverted from how many companies end up organized as they grow.
http://www.amazon.com/Skunk-Works-Personal-Memoir-Lockheed/d...
Imagine a carpenter who sets his sights on working hard at carpentry and being a good carpenter so that he can eventually advance his career by becoming a plumber. Makes no sense, right? These are completely unrelated skills. Maybe plumbing pays more (reverse the roles if I got that wrong) but that doesn't make it an "advancement". Certainly one could make the move, but it's a lateral move, not a logical progression.
Management is the same way. It's a different field. Yet somehow we have this idea that if you do well enough in some other field, "advancing" into management is a logical next step. It makes no sense.
The current way it works in trades like that is to move up to being a foreman or a site supervisor or similar. It's no different really.
Ideally companies with management gaps want to move experienced tradesmen into these roles rather than put "management professionals" who wouldn't know a 2x4 from a band saw into them.
Segregating out "management" as an entirely separate discipline makes a kind of sense, and it's why management is taught as a separate skill set with certificates and MBAs and all that. But I think the results have been mixed (90s Apple is given as a textbook example). For every professional manager who does a good job, I think it's possible to find somebody who moved into management who does as good or better because they understand the problem domain of their reports better.
Wholly agree though that it's a separate set of skills, but I think those skills usually work best when layered on top of practical experience in the field.
Yeah, you're right in that. It obviously doesn't work that way, there are far fewer management positions than people who could be promoted up into those positions. Even in some of the most hilariously top heavy organizations I've seen, this holds true.
I guess we have a cultural model of the "career" that somebody can start "in the mail room" and work their way up to CEO. Any deviation from that as a possible path is seen as veering off course or failing or "career ending" and you just end up in mere "jobs". You're right of course that this is unfair as the vast majority of people will never be on a career path that looks like this.
There's also an old fashioned class-based hold over in organization structure: nobles and commoners. This has been held over as "management" and "workers" or in the military as "officers and enlisted" and it seems that a great deal of our organizational theory, promotional structure and cultural ideas about progression are based on this: the "organizers and communicators" and the "producers".
Is there a better way? Maybe. But I don't think current counter-approaches work well over the long run, e.g. flat org structures. As a species we seem to naturally arrange ourselves into hierarchical structures, and if one isn't imposed on a group, one will emerge.
So I guess the idea of management, and it being a career path, is complex and is simply an optimization on these issues.
I've also been in organizations with very explicit, upward moving career trajectories that didn't end up in management per se. For example, one very large R&D organization I worked in was broken down like this.
You had the "employee". They all theoretically started as a "researcher I". As you progressed into "researcher II" then "research associate" then "research scientist" you were offered two choices go into "people management" and become an "associate manager" where you did normal people management stuff, some HR functions, signed off on time cards and did promotion stuff, but otherwise didn't involve yourself in the day-to-day of an employee's work life. Employees were simply "resources".
Or go into a research track. If you went research track you would then end up as a "research scientist" then a "principle research scientist" and then a "senior research scientist" (with research fellows etc.) Around the time you became a "principle" you were then offered two choices, stay in research, or go into program management. A program manager "owned" a program and requested "resources" from associate managers who were then matrixed under you. You directed their day-to-day, but if there were employee problems, you took it up with their associate manager who then dealt with it.
However, and this was the trick, if you stayed purely research, you'd of course continue doing research, but at that level, you were more valuable assisting the PM or the sales/marketing team (even R&D firms have this) with your expertise in getting research grants, writing proposals, etc. Quite often a PM would assume all the contract management stuff and the Senior Research Scientist would end up running the day-to-day of the lower level researchers. In the aforementioned military model, this ended up looking like an officer and his sergeant major. Or in academia, the principle researcher and his post-doc, with all the grad students. In practice, you'd end up becoming a manager.
However, in the line of "mail clerk" to "ceo", you were out of the game already. Nobody viewed it as a failure, Senior Scientists were revered like high priests there. But a priest cannot become a noble or a king. Only if you were an Associate Manager, or to a lesser extent a PM, would you have a shot at the line. Progressing AMs and PMs ended up assuming other roles, a bit of sales work, and for AMs a bit of PM work. I'll let you decide on the downsides and upsides (there are actually quite a few) of this system.
Some PMs ended up floating back over to Senior Scientist level, because they were already good at doing all the administrivia, but wanted to get their knuckles dirty in research again. Unfortunately, they usually found themselves more mired in more paperwork than pure research, and nobody wanted to take the pay cut and work as a Researcher II again where your time is 100% research. The economics simply don't work out to have a Senior Scientist running lab tests and squeezing pipettes all day. But they're the only ones with enough domain knowledge to write the grant proposal that will bring in a $30m 5 year program.
It can make sense.
A leader needs the respect of those she/he leads. It is easier to command respect when you are perceived as a technical expert or authority.
Promoting the Dilberts to bosses is an attempt at giving the engineers what they say they want: bosses with Dilbert's engineering skills.
Once you start admitting that "managing people" is just a job that you can do well or badly, and that can be really important or just administrative trivia, then that worldview shatters.
Unfortunately it seems very well embedded in the general culture, even in tech where it's not totally unthinkable for someone to earn more money (and provide more value) to the firm than the person who manages them.
Would it still make sense to pay them as much to just write code as it would for them to take on a more decision making role?
Yeah, that's not going to work.
Highly capable people given and environment that fostered their production.
Not everything generated was immediately commercial. But it was a very productive environment, and this had strong commercial implications. It also created a lot of public good, immediately and/or eventually.
Not every institution can afford a Bell Labs or a PARC. [1] But letting people do what they are good at, is perhaps not such a bad idea.
--
[1] P.S. I suppose that from one perspective, not even Bell nor Xerox could... although I don't subscribe to the argument, at least and especially not at such a simplistic level.
Before I started a startup, I was a software engineer at a large firm, and it was clear they were grooming me for management because I was a strong individual contributor and had "put in my time": 3 years as an engineer. Advancement at this firm was measured by "how many reports" you had, as in "direct reports", or people managed by you, and if you just did superior individual work but had no one "under you", you weren't advancing. So they sent me to a couple of training courses about management and started prepping me for the path.
This was one of the many reasons I quit this BigCo to start my own startup.
I am now the co-founder & CTO of Parse.ly (http://parse.ly). In our first two years after starting up, I spent all my time building stuff -- which is exactly what I wanted. Ironically, because the company has grown and now has a 13-person product team, I am now technically "managing" my engineering team with 13 "direct reports". But at our company, we have completely decoupled management from individual contribution -- certainly, if a strong individual contributor shows an interest in management, we'll consider it. But becoming a "manager" is not how you "advance" here -- you advance by doing great work. Our first employee who joined in 2009 is a great programmer and he is still with the company, but he's still doing what he loves: building & shipping stuff. Based on our frank conversations on the topic, I think he would quit if I forced him to be a manager. The appropriate reward for doing great work isn't a "promotion to management" -- that's actually a punishment for a great individual contributor. The right reward is to ensure you continue to provide an environment where that great work can continue for that contributor, and where they can continue to grow their skills and apply themselves productively in the role.