The problem of growth
Saturday, October 20th, 2007I am fascinated by the problem of growth. When a company is successful, and I will define that as having business wins and a ton of work to do and not necessarily based on any kind of revenue number, the web way is to add more people. Well, I have no idea if that is actually right.
From what I’ve seen in my two start-ups the only reasonable way to handle hiring is to treat it like you do any other product / development initiative. You figure out some kind of NPV and if the numbers makes sense then you hire. Sure, in PM and PD you end up doing a bunch of things outside the process because minor changes / enhancements need to get done and not everything is worth an NPV but allow for those and just take my argument already, ok?
But I wonder when in a company’s evolution that it shifts from NPV to personal desire, gut feel, or desire to build an empire. At FairMarket we had a rule that required the CEO to interview every candidate and he was the toughest to pass. It kept a bunch of bad folks out but it also slowed the process and in some cases we lost good candidates too. But it is pretty easy to track the start of the bloat to when he stopped being able to interview everyone. As a friend of mine in an SF company says, “A hires A, then A hires B, then B hires C” which I’ve always taken to mean that the further you get away from the original or core folks then the more likely you are to get lower talent. That’s when you start to hear, “A body in the chair is better than nothing.”
So, I’m reading this CNET articleabout Google having doubled in size in the last 12 months and the associated problems the new employees are having in figuring out the place and it doesn’t seem that surprising. Still, I think this is a first world problem that Google is facing and that they’re continuing to focus on hiring the best and the brightest folks and that they’ll probably figure it out. Hell, I’d actually like to work on the team tasked with solving that problem! I can imagine a couple systems or tools that the engineering heavy and cash rich company could crank out and use to on-board the new folks. Maybe a new gphone with a 411 number right to a process support team?
But for young companies without the benefits of a Google I think the problem is more challenging even if the numbers are smaller. When do you ramp in advance of revenue? When do you ask people to do more and not grow teams? How do you focus instead of falling into the land grab game where growth is key and revenue / sustainability is secondary?
I am impressed when I hear that Facebook has hired a ton of people and then find out they have grown to a whopping 300 people! 300 isn’t so bad. But I do feel for the original folks there. 300 is about 100 to 150 past where you can know everyone pretty well. They’ll be hearing about social clubs, have lunch time debates about maintaining the culture, discussions about people who are joining just fo the stock and yetr don’t know that CTRL-ALT-DEL is the key combination required to unlock your computer in the morning, and probably have some new hires asking about work life balance. Growth is sexy and growth is cool but even when you’re the darling of the internet age, loving all the press, and thinking about changing the world something is lost when you move past code releases that involve everyone in the company staying up all night together and working on a common goal.
Good luck to big and small alike.