The book Loonshots by Safi Bahcall describes this phenomena quite well. There's a "phase transition" of incentives at around 150 people that can be fatal to many organizations. The secret sauce is how a startup goes past this headcount. Ideally many software companies quite honestly don't need more than 150 people!
When they say "100" or "150", do they usually mean total company size or number of engineering+product people?
How a startup loses its spark
71–80 of 287 posts
Re: How a startup loses its spark
#72I'll raise your spark for complete destruction. Here's an incomplete list that I keep around of the mechanisms that I've observed so far that have played a big part in the decline/destruction of an engineering team (and product thereof): 1. Too-technical leaders: As startup scales, there can sometimes be a mad dash to fill new leadership roles (e.g. VP of Eng, Arch, CTO, etc.). Super-star engineers present at startup…
Maybe by avoiding fast scaling, which implies avoiding VC money.
Re: How a startup loses its spark
#73I'll raise your spark for complete destruction. Here's an incomplete list that I keep around of the mechanisms that I've observed so far that have played a big part in the decline/destruction of an engineering team (and product thereof): 1. Too-technical leaders: As startup scales, there can sometimes be a mad dash to fill new leadership roles (e.g. VP of Eng, Arch, CTO, etc.). Super-star engineers present at startup…
1. Not correcting problem hires fast enough.
First time founders are often too hesitant to give negative feedback, demote a too-technical manager who should have stayed an IC, or remove a problem employee who isn’t working out.
The anecdote that comes to mind is a local startup that hired a C-level executive’s UI designer friend into their VP of Product role. He was wholly incapable of doing the job but they kept him in the job for 2 years to “give him a chance to grow into it.” Everyone below VP level openly talked about how the VP of Product was incompetent and how to work around him.
The company’s product initiatives ultimately failed to even get started and they had to pivot to entirely services based work. Do not stay at a startup that insists on keeping unqualified people in leadership positions long after everyone in the company has given up on them.
2. Firing the wrong people
The same startup was forced to downsize, largely because their product plans failed to even become defined enough to start under the incompetent VP of Product.
It was the perfect opportunity to fire the VP of Product and his sprawling empire of people who did very little, but they avoided that due to his connections to a C-level executive. Instead, they started cutting engineers. They focused on cutting engineers with the highest compensation out of a misguided effort to cut as few people as possible.
In the process, they lost their key engineers who were holding things together. They sent a message to everyone that incompetence is tolerated if you know the right people. And they lost even more core engineers who quit in the months after those layoffs.
Everyone makes hiring mistakes. It’s how you respond to those hiring mistakes that will seal the fate of the company.
Re: How a startup loses its spark
#74I disagree - as someone who has started up small companies and worked in megacorps, including FAANG and major banks, it’s entirely possible to build that intoxicating environment anywhere. It’s more about having a dynamic leader who assembles teams into collections of individuals who know precisely why they are there - and are given the work they excel at and the work they don’t the manager ensures someone who does h…
I think you’re being unnecessarily harsh and reductionist of the article’s arguments. I’ve experienced exactly this failure mode in startups.
The counter-example you described is an example of properly managing the N^2 complexity, not an example of it not existing.
Re: How a startup loses its spark
#75I'll raise your spark for complete destruction. Here's an incomplete list that I keep around of the mechanisms that I've observed so far that have played a big part in the decline/destruction of an engineering team (and product thereof): 1. Too-technical leaders: As startup scales, there can sometimes be a mad dash to fill new leadership roles (e.g. VP of Eng, Arch, CTO, etc.). Super-star engineers present at startup…
Maybe by avoiding fast scaling, which implies avoiding VC money.
It still had the same problems as above. Expanding slowly doesn’t automatically protect you from these things.
Re: How a startup loses its spark
#76The value of this recommendation cannot be overstated. Put another way: only hire when there is no other way to solve a problem, and even then do so carefully. Be willing to elongate timelines substantially as a result of this practice; the medium- and long-term costs of over hiring are much worse than the cost of later launches.
Unfortunately, the funding environment and growth expectations for startups often incentivize the opposite behavior.
Re: How a startup loses its spark
#77I think the best takeaway here is - don't hire until you absolutely have to.
Perhaps, though, if you only hire when you need, you can be more competitive with pay.
Re: How a startup loses its spark
#78Not necessarily. At the large companies I've worked at (>200 people), a UXR will drive the interview process with users, starting with compiling a list of questions from engineers, then conducting the interview sessions with users in which engineers can sit in, and then disseminating the insights and setting up a meeting to make the insights into a actionable engineering projects.
Working with UXRs is a dream, as they're trained to conduct interviews in an impartial way, leading to insights that are less biased and higher quality. Contrast to when I worked for startups and I or someone on my team would interview users, very often the feedback would end up contaminated because the interviewer would ask the wrong question, projected their biases into the questions, or even worse into the insights.
Re: How a startup loses its spark
#79I went through this cycle a few times. My favorite, and last successful startup was acquired by a gigantic international corporation four years in (2007), and I stuck around for another two years. After the product shipped, the need to support customers and sales definitely slowed things down. Our fantastic VP of Engineering became CTO, and hired a middle management moron as VP, and that was the end of the good times…
Hardest lesson I learned when I got promoted to upper leadership positions: Hiring middle management is incredibly hard. The number of absolute sharks in the candidate pool is wild. People will show up, sense that you’re new, and tell you everything you want to hear about how they’ll solve all of your problems. They’ll claim they’ve done exactly what you need at every prior company they’ve worked for. They’ll flatter you and tell you they’ve been waiting for an opportunity to work or someone like you.
Imagine the schmooze-iest IC candidate you’ve ever interviewed, but 5 times better and harder to see through. These people have charisma you wouldn’t believe (when you’re new) but they don’t really care to do the hard work. They just want to worm their way into the company and then extract. They’ll extract compensation for themselves, extract headcount to hire their friends and build an empire, extract compensation for their friends (who will return the favor at a future company), extract lucrative contracts for their contracting buddies (where they might even be in on the take). Years can pass before people realize they haven’t really done much despite producing a flurry of activity. They may have even driven away the good employees who got tired of their BS or were pushed out for identifying their incompetence.
I was unlucky-lucky to watch this play out under a fast rising CEO at a lesser known unicorn. The number of sharks who showed up and charmed him after he became successful was unbelievable. The same thing plays out with less experienced middle managers who get thrust into high-budget positions at smaller companies.
Re: How a startup loses its spark
#80Here is a specific example: schedule the company holiday party the night before the one major software release of the year so all the engineers are sitting at the party with heavy GPU laptops coding away on build issues after bug fixes.
Here is another specific example: recently hired workers on the business side become Directors and VPs three out of undergrad while engineers waiting for years for promotions are not given any.