10 ms·
Why successful startups stumble at 40 employees
- deleted 9y ago[deleted]
- mbesto 9y ago50, 100, 150, 500 employees - are, in my experience, the breaking points for many businesses. After 500, inertia generally takes over.
- frandroid 9y agoI understand 100 is double 50, and where you go from "a few teams" to "departments", but what's so different between 100 and 150?
- nilkn 9y agoI think the difference between 100 and 150 is that at 100 people, as long as the organizational structure is right, you can still play fast and loose with corporate culture. While it'll be a stretch, each person may be able to know every other person if not by name then at least by face and role. In other words, each person's "observable universe" inside the company is the whole company. At 150, no one can stay aware of everyone else. Your "observable universe" becomes a strict subset of the company, no matter who you are. There's no longer one company, but rather 150 different companies as seen by every employee. Direction must be constantly supplied from the top to apply corrective measures to all those different visions of the company.
- votepaunchy 9y agoThe change at 150 could be related to Dunbar's number. https://en.m.wikipedia.org/wiki/Dunbar%27s_number https://en.m.wikipedia.org/wiki/Dunbar%27s_number
- jaggederest 9y agoHere's my rough understanding, from experience anyway: 50 is the level at which systems and processes start to become critical - you can't just succeed accidentally through heroism, you have to deliberately set out to learn from and solve problems or you're sunk. 100 is the level at which people can no longer self-organize and need explicit constructs to manage organization. I.e. not just 'a pool of engineers who work on the product', but a X team and a Y team and a Z team. 150 is the level at which every person can no longer know everyone on a personal level at the company. You'll need some way to handle cooperation and communication that's not "Talk to Bob", and all hands meetings can only happen at best yearly. 500+ is the point at which things will generally become stabilized / ossified enough that the ongoing structure of the company either works or it doesn't and the difficulty of changing those things becomes exponentially higher. Reorganization is a significant misnomer.
- mbesto 9y agoBasically this.
- spyspy 9y agoIt always astounds me that growing the number of employees is one of the key metrics of "growth" startups looks for. As if an unprofitable company with 500 employees is somehow more prestigious than a profitable one with 50. Perhaps it's pressure from VCs to chase market share over profits, founder ego, or something else entirely, but it's always struck me as a troubling trend in the startup world. I recall (several years ago) looking up how many employees worked at Twitter and seeing it was over 900 and thinking, "What in god's name are those 900 people doing all day?"
- aaron-lebo 9y agoIt was the same way with Digg. Hundreds of employees to do what exactly? In hindsight, maybe not shocking it died. Reddit is doing the same, ~300 employees to run something that a team of 30 could (of course, not all are engineers). It's crazy. Reddit plans to expand to 300 employees by the end of the year from its current 230. That's already up from the 140 the company had at the beginning of 2017. Huffman declined to share revenue numbers, and the company is not profitable. https://www.bizjournals.com/bizwomen/news/latest-news/2017/08/reddit-raises-200m-for-new-1-8b-valuation.html https://www.bizjournals.com/bizwomen/news/latest-news/2017/0... Don't know how accurate this is, but Twitter is at 3500 employees now, down from 3900. https://www.statista.com/statistics/272140/employees-of-twitter/ https://www.statista.com/statistics/272140/employees-of-twit... There's something fundamentally wrong with the way the industry builds products.
- debacle 9y agoIt's the valuation trap. If twitter was satisfied with a valuation 2-3 orders of magnitude lower than what it is, it would be highly profitable right now.
- bluGill 9y agoThe question is CAN twitter be satisfied. I'm not talking if the investors, ego, or all those others will be satisfied, can it survive at all? The question is how many people are actually needed to keep the lights on. One person can read the latest CERT notices every day and decide "we need to upgrade our servers before we are hacked", but from there the upgrade can get hard: how many people are needed to to stage and test the upgrade. How many people are needed to keep the servers running? How many people are needed to ensure that twitter doesn't become a has been unable to keep up with their competition (who presumably is adding new features all the time)? The above is a complex question. I don't know the answers, so while I lean to agree with those thinking twitter should cut people until they are profitable I can never be entirely sure. Even if twitter took my advice and it worked out I can't be entirely sure their current path (too many people) wouldn't be better in the long term. Or alternatively if they continue on the current path I cannot be sure if cutting people would have been better.
- nathan_f77 9y agoFun fact: The author of this article (Steve Blank) founded Rocket Science Games, where Elon Musk worked as an intern.
- ggambetta 9y agoPlot twist: "Patrick the student" is actually Elon Musk.
- wolco 9y agoIt's different for each company. One founder told me that he couldn't manage more than 7 or 8. At that point you can't be involved in every decision.
- frandroid 9y agoMost managers can'd manage much more than 10 people, then you have to delegate to other managers...
- milesvp 9y agoThis was definitely the wisdom I've heard historically. I suspect the number may be slightly higher than it was 40 years ago due to digital communication, but a lot of what I hear is that it's just really hard to deal with all the personal, and interpersonal problems that crop up. This also makes me think if you're lucky and have a low drama team, you can do more than 10, but at the end of the day you're going to get a superlinear increase in interpersonal drama the more people you manage so this number is likely to remain small.
- twobyfour 9y agoOne principle of good management is that no one can properly manage more than roughly a half dozen direct reports (10 is the absolute limit, and at that point you're stretched way too thin). At 40-50 people you're hitting the point where you have 6-7 managers reporting to the CEO and each responsible for 6-7 direct reports. If you hire more people after that, you basically either have to severely overload someone's management capacity or start hiring a third layer of management. The company still feels too small for that much hierarchy so instead of adding management it increases the number of reports either of middle management or the CEO until the situation is untenable.
- godzillabrennus 9y agoAs someone who has been through this. The 40-50 employee threshold for a business requires competent people appointed to the management of departments. There are people who start companies and either fund raise or drive revenue to the point that they have the ability to hire that many people. Unfortunately, when they don't have the skills to hire the right people then the business tends to implode.
- snarf21 9y agoI think that is the difference. Under 50, you are hiring people to execute and the leader can still control everything. Above that you must hire managers to control pieces of what you used to control. You must trust them to do the right thing for the company. Most people who are successful at the 0-50 can't let go of that control.
- ZenoArrow 9y agoI'd suggest it has something to do with coordination. When you have a small team, you can more easily arrange for that team to all pull in the same direction. When you pass a certain threshold of employees (I'm not going to suggest 40, the number is clearly going to vary in the real world) a lot more effort is required to coordinate the work of employees. This means more middle managers, more meetings, more email traffic, more office politics as teams start to fragment, etc... All of these things can hamper productivity if not handled correctly.
- depsypher 9y agoCan't say I found this article all that enlightening. Having been an employee at several startups that have transitioned past the 30-40 headcount mark, there does seem to be a breakdown at that stage. What is the cause, and how do you deal with it? This article doesn't really address the causes or offer any true solutions though. Focus on culture? You need to do that from the start. Get new board members? So your advice is to get new advisors? Okay, but what steps can you actually implement to solve the problem? In my view the real problem is that good management is difficult and not well understood. Once your company grows to the point where a flat structure starts to have problems, the usual shift is to a hierarchical structure; not only a difficult transition, but also ends up trading your old problems for new ones. I wish the startup world did a better job of tackling these issues.
- sharemywin 9y agoThe problem is the "plan" would be for the company to grow 10x in the next 3-4 years. So, for every person on the team add 9 more people. now, keep your culture. Also, most of the people you hired were experts in the jobs not management.
- DannyBee 9y ago"Can't say I found this article all that enlightening. Having been an employee at several startups that have transitioned past the 30-40 headcount mark, there does seem to be a breakdown at that stage. What is the cause, and how do you deal with it? " I'll at least attempt to give you something that may be a little more enlightening. I suspect a bunch of it will come off as stupid babble to people who have smaller teams, and less so to people who have managed or transitioned larger organizations. I claim credit for none of it. There is no single cause of course. The unsatisfying answer is that "for the complex system that makes up a lot of these organizations, 30-40 is the number at which a lot of these systems become noticeably more unstable". There are a lot of possible reasons for this (not everyone has the same mind anymore, same incentives, etc, and over time, are gravitating towards certain things) The main reason for failure though, i believe, is that startups are very used to dealing with complicated problems (difficult but amenable to having an end state and answers, even though they involve tradeoffs) and not complex systems (things that don't stay still, there is no right answer, and there is no end state) , and so try to solve "the system" as if it was a complicated problem. People want to put in place "an answer" and have it work for a while. This rarely, if ever, works You give an example of this: The flat organizational system tend to not work as well at that size. People see this as a set of problems. So they try to solve them. Often, as you mention, by moving to hierarchical management. As you've aptly described, that just ends up trading one set of problems for another. That's because there is no actual solution to the problem. It's not a problem to be solved, in the same way "culture" is not a problem that can just be solved. It is an ever changing thing. You need a very different approach. Instead of trying to solve "the problem" (which is usually, in this case, something like "people running in too many directions", etc), one needs to try to step back, and try to understand all the attractors, variables, and factors that are currently causing your system to behave in a certain way. People often think they know the answer why ahead of time, but they are often wrong :P. Figure out where you can have influence in this system by nudging variables, and try to nudge things towards a certain direction and see what happens (IE choose something you want to see more of or less of, experiment, learn from what happens, try again). Incentivize the right things to happen, instead of directing the right things to happen. This is all a pretty general description (and there are actually very good books and courses and such on the above, even if not specifically written about startups). There are also certainly times where the system is failing bad enough you need to completely replace it, but that is due to a failure of leadership. There are also times where "hierarchical management" may be a valid experiment to try (it's just an example above). But i believe most startups just go directly into problem solving mode when they hit these kinds of issues, and that, again, rarely accomplishes much except frustration and failure. It really requires a mindset shift of not just trying to solve complicated problems and seeing everything as fitting into this mold. Even you mention "Okay, but what steps can you actually implement to solve the problem?". The steps you can take are to realize it's not a single problem, or even a collection of problems. These are just emergent properties of your system. Your goal is to nudge it into different emergent properties that are closer to what you want, not just try to solve the set of problems those properties produce. It's important to also realize you will never stop having to push the system in various directions. You are never going to reach this end state where everything is always going awesome with no work on anyone's part ever again. Systems may become meta-stable, and the timeframes on which it stays meta-stable may be long, but usually the only systems that are stable are dead ones ;)
- s73ver_ 9y agoI imagine it's because, at that point, you're running a real company, with needs for marketing, sales, health insurance, company policies regarding leave and all the other adult stuff that most people expect at a real company these days. And generally, the person who started the company doesn't have the skills/knowhow to handle all that (many were just line engineers or what have you the year or two before). These things can obviously be learned and dealt with, as evidenced by the fact that there are companies that continue after the stumble.
- convolvatron 9y agoalso consider that while there is funding, everything is great by definition. at least two places I worked at had to start showing results around then...it wasn't anything about scaling, they just didn't have anything to show
- fsloth 9y agoOne way is to look at the organization as a random graph. Relations between people - edges - describe business dependencies. If the growth has been completely organic to that point, there are chunks of undocumented and unnoticed connections. Unnoticed, until they break, I presume. The complexity grows as a square of the number of people. With 40 people there are 40 x 39 random edges (1560). With 20 (20×19) the number is 380. With 10 (10 x 9) 90. So, as back of the envelope estimate a company with 40 people is 17 times more complex than a company with 10. I'm just blowing hot air, but it seems to me people - engineers especially - are not discussing dependency graphs in relation to this problem as much as they could. Also, root cause analysis suddenly looks like a much more powerfull tool to discover the connections in the graph (if those hidden dependencies cause major pathologies).
- strictnein 9y agoThis is actually what I thought the article was going to be about.
- timdellinger 9y agoI agree that there's a missing playbook for that phase of companies... it would be great to see some collected wisdom on "these are the ways that companies run into problems in this phase" and "this is how to prevent / deal with those issues". Startups often have a fun "screw the corporate rules, we're doing it our way!" mentality that's perfect for the Search phase described by Steve Blank here. During my time in a Fortune 500 company, I came to see the reasons for some of the corporate rules and corporate culture... I saw the problems and potential problems that the rules and processes are in place to deal with. If you've never been in a large organization, it's a very different beast than a small one... I imagine that it's tough psychologically to institute rules and processes that you rebelled against in an earlier stage.
- analog31 9y agoMaybe the founder should hire or involve a senior manager as a mentor, long before they reach X employees. The mentor can say: "I see what you're doing here, but here's how a larger company does it, and here's why." I worked for a company that came within inches of imploding at around this point. I noticed that even before hitting that size, they were already going downhill and losing people. So maybe an issue is that a company doesn't do anything different at 40 employees, but the employees get less willing to put up with it, especially if they feel that they're not sharing in the rewards of the company's growth. And the new employees who are coming in, don't share the same "startup fever" and personal loyalty to the founders, that propelled the early employees. A mentor might be able to see this happening and steer the founders in the right direction.
- JBlue42 9y agoExcellent point. The company I worked (not a startup) had existed below 30 people for most of its multi-decade history. They started expanding rapidly the past few years and I came onboard when they were at 60 people. That double in the two years I was there. The higher-ups, who had started and run the company for decades, were strictly against not wanting to "seem corporate" or have too much organization / structure because it was "corporate". Yet, they kept running into ways that the structure would self-organize or that things would stagnant because they weren't being responsive to the large amount of employees below them. They wanted everyone to participate in a vision but the vision was basically "get bigger and don't be corporate" and rather muddied. Everyone I spoke with that had been there more than 5+ years, and that would be honest, had said the major changes in the company 'felt' like they came at 50 people, 70-80 people, and definitely after 100. It was interesting for a while but a bit of a shitshow. All the leadership felt they could run things they same way they always had instead of adjusting to the new paradigm - which is rather 'corporate' in my book.
- madaxe_again 9y agoI disagree with much of this, having taken my own business (ecommerce platform) through this point and having mentored a few others through it. Growing a business isn't about distinct phases. It's about a continuous, iterative programme of holistic improvement, where you are always working on the business, usually while working in the business. For instance, we followed a leapfrog model whereby we'd prioritise technical uplift (both product and internal tooling) and then structural uplift (hires, methods, practices, culture). When we were actively working on one we'd be planning another - and we worked like this from day zero, when we were just two dudes. It does differ between businesses and models. In the case of one business I consulted with, we (me, two founders) put together SOPs, defined the hell out of everything, hired like crazy (30+ in 3 months), and they got acquired for a large sum six months on. Muggins got doodley-squat, as until acquisition they were cash strapped, and afterwards the new owners wound it all up. What didn't survive the transition in either case was me. I hate working in process-driven tick-box-now orgs, which is why I started my own business in the first place, so hit the ejector button on my own org last year - my discomfort within the beast I grew manifested as a total deterioration of physical and mental health. Turns out I'm great at building them, which is a shame. So. It's easy enough to avoid humps if you're always planning ahead, always iterating, but the greater barrier is psychological - I guess few are willing to do the hard things you have to do to keep it on plan - like firing friends, "intensively monetising" customers, and generally playing a nerve-wracking seat of your pants game for years on end - because the cost is ultimately steep. Self hatred is like acid, and I honestly think most orgs fail because founders find it hard to completely compromise their values for the good of their business and employees.
- ChuckMcM 9y agoThen you're takeaway should be that if you wrote a book about your experience it would have solid sales :-). I think you were fortunate to have this sort of mindset from the beginning and I can tell you that it is not common. One of the 7 habits is to work on things that are important but not urgent. This is what you do when you're working on the next phase while executing on the current phase. I tell people it is like watching yourself drive. If you have the experience of teaching your kids to drive you might notice that they are much more likely to hit things when they are looking where they are driving, than they are when they are looking where they need to be. Another example I've heard is sailors walking with a cup off coffee on a ship that is moving with the waves. If the sailor watches the coffee to keep it from spilling, the coffee goes out of control and spills, but if the sailor looks to where they are going, the hand doesn't let the coffee spill. The same is true in business where if you focus so hard on how you are solving the current problem the next one hits you before you are ready for it. Whereas if you're thinking about the next problem while executing against the current one, then when the next one arrives you are already starting to execute against it. I'm serious about the book too. Its a very useful way of approaching running a business and many others would benefit from your experience if you could put it into book form.
- awjr 9y agoI think below 40, employees have multiple roles where you are expected to think on your feet. It attracts a certain type of person. Above 40, you are a cog in the machine. You really need to keep to your role and the company succeeds because of the role you do.
- posterboy 9y agoembedded questions in a headline should get the same sentencing as those ending in a question mark. It is not hard to point out the answer in the title. I won't try at it, thohgh, since I won't read the article (either way or because of) Betteridge's law of headlines.
- Walkman 9y agoBecause they are not successful? :D They keep being small for a reason.
- emagdnim2100 9y agoThe Marine Corps teaches the "rule of three:" each leader should have at most three direct reports.[0] In practice, leaders at the platoon level or higher (~40 people total on the infantry side) also get a senior enlisted advisor who serves as a trusted second-in-command but who isn't a direct report in the same way as your subordinate unit leaders. Additional folks beyond those three should report to one of the boss's subordinate leaders, not to the boss. The structure repeats up and down the line, sometimes with small tweaks: three rifle platoons to a company, three squads to a platoon, three fire teams to a squad. I always found this approach to be tremendously effective. If decentralized command were applied diligently from a company's earliest days, I believe it would sole a lot of the scaling issues organizations face. But it's difficult for most startup founders to give up control. [0] See, e.g., https://www.inc.com/magazine/19980401/906.html https://www.inc.com/magazine/19980401/906.html
- jakecopp 9y agoAre there any companies with a strict structure like this?
- bb611 9y agoI have always loved the USMC's leadership principals, but they have a hard time adhering to them in practice. Talk to pretty much any infantry officer who saw combat in the last 15 years and they have endless stories of chaotic command arrangements. My guess is that businesses have the same issue - it's great in theory, but the cost of failing to achieve it in practice is low at first so it creeps up over time. It takes a catastrophic event to force leadership to rearrange reporting relationships and clear up lines of communication again.
- BatFastard 9y agoMakes for a very deep hierarchy. I personally prefer flatter companies.
- JamesSwift 9y agoIt doesn't create a deep hierarchy really, and scales well due to it being a Log3 of the total employees. Seems very reasonable to me.
- stcredzero 9y agoHow long does it take for the typical company to go from 20 to 40 employees?
- throwawayaway0 9y agoI was an early hire at a data protection startup which inexplicably began behaving like a much larger and profitable company when product was still very flawed and barely usable. ~$100M of funding and many years later, that company has yet to become profitable and rather than shudder the doors, merged with a competitor. All common stock rendered completely worthless in the process, not that there was any hope left after all the dilution anyways. What I saw was a whole lot of empire building. Things seem to snowball very quickly once managers start getting hired and they're all aspiring for greater head count.
- pythonhulk 9y agoThis article is a decent attempt at explaining this phenomenon. Most early stage startups are co-founded by highly driven people, who work well even with the absence of processes and structure. This ethic will never translate to all your employees after a certain point. This is where process and structure come in and often, it is too late before it can be successfully implemented.
- wannabag 9y agoI like the high level CEO view of this problem since it's a good reminder that the overall phase needs re-think. That said, what this article hints to in the title and misses is that there are inherent problems for startups that are in fact related to the number of employees. Some commentators touched this subject as well and rightly so, when you reach around 20-40 employees you start having problems that are organizational. If not addressed properly these will cripple growing startups and in some cases even prevent them from reaching the next stage. I went through a couple of these failures myself and I can't stress it enough when discussing problems related to growth; there is a point when you can no longer communicate or work in the same way and you can't expect things to self organize. It takes quite some reorg including some hard decisions to get to a stable stage or in the best of case, transit smoothly but that takes someone very well aware of all the pitfalls.
- kevinojt 9y agoAs the VP engineering of a company in the Build process our CEO do most sales thing and won’t hire capable people and fire incapable people. What should I do?
- erikb 9y agoI can accept that there are different levels of growth and at each of them there can be trouble. But it's not just one level. You can just as well stumble at 5 employees (I experienced that), at 17 employees (experienced that) or at 80000 employees (experienced that; admittedly not a startup though).
- aristotle2 9y agoI've actually had to write an ebook (for content marketing purposes) on growing a company and going from 3 to 9 to 30, and so on. The most interesting thing is the Greiner's Growth Curve as well as Adizes Corporate Lifecycle. I'll leave the direct link to the pdf here even though it's gated content, so pls downvote. https://activecollab.com/downloads/GROWTH.pdf https://activecollab.com/downloads/GROWTH.pdf