Live data from Hacker News

The 15 Roles Absolutely Necessary in a Startup, No Matter How Small it is

micahelliott.blogspot.com

41–43 of 43 posts

Re: The 15 Roles Absolutely Necessary in a Startup, No Matter How Small it is

#41

I like to summarize it as: 1) Coders, to code 2) Designers, to make stuff people want (interaction / product design, NOT visual design) 3) Hustlers, to get the stuff to the people

That's almost the same conclusion he reaches in the blog. The only difference is that he includes the System Administrator role, for actually setting up and maintaining the platform that the code is going to run on.

Re: The 15 Roles Absolutely Necessary in a Startup, No Matter How Small it is

#42
post #39
post #29

Earlier quoted context omitted.

It's all in the viewpoint - I don't see "blogger" as dismissive at all and see "author" a bit pompous for the level of writing.

I don't see what the level of writing has to do with whether one is an author or not. You're the author of your comment, and a graffiti artist who draws a penis on a wall is the author of that graffiti. Author merely implies who created the thing. Anyway, all I was commenting is that I find it quite unpleasant when I write blog posts and people refer to me in the third person, as either "the author" or "the blogger",…

I think the best way to explain our differences is that we have varying preferences for specificity - I like "blogger" because it means "author of a blog post" the same way that I like "commenter" as "author of a comment".

And yes, just because you like the more generalized description of "author" doesn't change that they'll all 3rd person labels, which I'm not sure is pejorative either.

Re: The 15 Roles Absolutely Necessary in a Startup, No Matter How Small it is

#43
post #5

The pruned down list seems to be missing the very important "business development" role (which generally is mixed into other stuff.) Who's calling leads, creating deals, making contacts (substantial ones, not marketing-based ones) in the local business and technology community, understanding new feature requests, and basically making sure operating costs and revenue projections are on track?

I appreciate the call-out of an important omission from the article. I've learned that having a bizdev on the team is truly critical. That whacked me on the side of the head when I started thinking about Twitter's strategizing (http://www.techcrunch.com/2009/01/13/twitter-decides-to-hire...), and thinking about the shaping of various features that customers are not getting a chance to weigh in on. I've tried to wear the bizdev hat myself but it is all-consuming. Now I have a full-time bizdev partner and it's making a world of difference in focus/direction. The XP practice of "on-site customer" is really enabled by having bizdev pull the customers close early on.

Another valuable role I've discovered is that of the incubator (I'm not YC; doing OTBC in PDX). It's another secondary role similar to Lawyer, but can be very supportive in making sure you're focused on doing all the business stuff that hackers can easily lose sight of. I'm presently being shown the value of having a solid business plan, perfecting multi-length elevator pitches, and refining the more formal investor and sales pitches. This is all possible thanks to experienced entrepreneurial coaches who really want to see you succeed.

Lastly, the "consort" is a non-obvious role -- someone who can give validation to your thinking, and exchange predicament stories with you. You may find him through the incubator, or at a hacking event, or wherever. My main consort is an extremely capable hacker and our regular discussions are gold.

So with the core team containing the right hacking, creative, and outreach balance, you can make progress. But I want to stress that the supporting people (Lawyer, Consort, Coach, et al) provide a lot of necessary elements.

Post reply on HN