The question of how do startups move so fast comes up surprisingly often. I finally gave it some thought, after the question came up again in a recent meeting with one of my companies. Over the last year or so of working with startups, I came up with some observations:
1. Small teams, 1-3 people. Makes sense right? Less time lost, less arguing, etc. Less meetings.
2. Everybody resonates with the idea and generally agrees with direction. Since everyone is either a participant or expert in the field in which the site is created for, then everyone does not need to learn but knows instinctively what to do. Nobody is working on a product that they do not use themselves. It’s a great way to find people like yourselves, when you recruit from the level of common interest in a certain product area.
NOTE: It’s really hard sometimes to get someone to resonate with your idea. You may hire them for their intrinsic talent, but it may be really difficult to get them to feel the instinctive bond with your product area.
Sometimes it’s impossible. Doesn’t mean that great work can’t get done, but it does mean a level of independence can’t be achieved, as non-resonating employees need more directional advice than those who do resonate.
3. Along with 1, the teams usually only consist of engineers cranking away. Most of them are multi-talented to a point, so they play multiple roles of programmer, GUI, html/css, product manager, product visionary.
4. Strangely enough, I have not found location to be a common factor for moving fast. Certainly it enhances the process, but a lot of teams are working with people remotely, since engrs are so hard to find and many just don’t want to move. Somehow, they have found ways of working together and can still make progress. Lots of travel involved and constant communication are two of many key points in making it work. If I get a chance, I’ll dig into it more with some of the startups I work with as to how it’s working and how it’s not. In my startups, 6 out of the 8 companies have resources external to their main location, mostly engineers who are working in remote locations. I have not seen any dramatic slowdowns with their teams.
5. People are generally just cranking. They see something needs to get done and then they just do it. There is less the asking for permission. Everybody needs to get on the same page and just keep moving forward in a very independent way. Early on at Yahoo!, many of our engineers would just do stuff and we would rarely ask them to do some particular thing. The product would constantly evolve while we worried about other stuff. Although when we asked them to actually do something and if they did not agree, it never got done which was frustrating from another viewpoint. So it worked until they got to a point when their initial sensibilities finally turned out to be wrong. Sometimes they could be convinced that they were wrong, but sometimes not…
While speed may be intuitive to some, I think it’s harder to achieve than you think, unless you have the right people with the right sensibilities and right alignment in thinking.
One of the hardest things I’ve seen is when a non-engineer comes up with an idea and tries to get it done. Because they can’t write code themselves, they need to find someone who can. But more often than not, they find only someone who can code but not become resonant with the idea to just work on it and take vague direction and execute on it.
It’s the magic bullet that everyone searches for:
“Dang it, I just want to describe my idea to someone and that someone just deals with the details and makes it happen!”
Unfortunately, it’s the details that often count…you want something done right, you better sweat the details!