15 Roles every start up needs

Been plowing through the back catalog of my RSS feeds, trying to catch up after SXSW, and I found a great discussion over at Alley Insider about 15 roles every startup needs filled.
The most fascinating part is the back and forth, I think. The original post posits many of the 15 are unneeded or can be combined – we started with six, and I think to some extant that it was true that you can combine some in the short term. But very rapidly, most of those positions need to be expanded out into individuals. If anything, I think the 15 roles (plus the obvious omission of biz dev, called out in the comments) is a great map for scaling your organization from whatever it is you start out with.
Also, the discussion in the comments is really interesting – gives a lot of insight into some of the key challenges, debates, and viewpoints about team size and startups. Lately, personally, I’ve been landing on the side of larger teams – experts who aren’t torn between divided loyalties, and each important aspect of a job having a dedicated advocate. There’s a TON of internal debate about such things, though, and no shortage of people here at the company that feel smaller teams are more effective.
Personally, I think sometimes we let our nostalgia and our personal enjoyment get into this conversation a bit. It’s easy to look back on “the good old days” when we were all running around like chickens with our heads cut off, making a great project. But sometimes I look at our work now, an old project that I remember fondly as being a great project, side-by-side with a new project done via a process, and the work is almost always better now. And people have personal lives here, which I think is a pretty great accomplishment. Really, a lot of the times process probably gets a bad rap, as it has to compete in comparison with our nostalgia.
Nut that’s a whole different topic. Look at the roles, and tell me what you think – I think UX designer and biz dev are the obvious omissions. I also have a hunch toolsmith, lead developers and CSS coder could be combined, but I’m sure that’s probably a bit contentious.

Artichoking

Emoji Tales

Have you ever needed to say something, but felt that you just had too many words to say it with? Something like, “Hamburger [plus] Hamburger [equals sign] Smiley face. Poop!”? It’s out of this necessity that Emoji Tales was built. Emoji Tales allows you to construct short, profound, stories and truisms from the much ballyhooed emoji symbols used by the iPhone. Common use-cases might include, drafting a resignation, professing your love, or explaining your husbands death to loved ones.
But it doesn’t stop there friends. If you use Twitter to “tweet” the URL of your Emoji Tale creation, tag it with #emojitales. These tweets will be collected and re-tweeted by @emojitales for everyone to enjoy.
Thanks to Robert for creative direction, production gruntitude, and an unhealthy knack for hilarious Emoji Tales.

Formal Friday Salute: Out and About

Pretending to be all Sartorialist-y.

Hacking a Medium

What happens when you take dynamics from one medium and apply it to another? (And other random questions.)

Even before my McLuhan post a few days ago I had been thinking a lot about the idea of hacking a written medium: Essentially using it in different and news ways that it might not have been originally intended.

In the link to my recent Boards Magazine article I mentioned , “Also, I started the article with this, ‘If you don’t feel like reading this article here are the talking points.’ Which made me laugh, but also it was kind of my way to hack a printed article. (As a side note, I’ve been noticing that when I write I use a lot more parentheses than ever before, especially in print. I kind of think this is in place of hyperlinks.)” Essentially it was an attempt (not necessarily a good one) to apply the dynamics of one medium to another (just as I mentioned using parentheses a lot more lately, which seem like the closest thing writing has to a hyperlink).

Anyway, the comments to the McLuhan post made me think more about it (if you haven’t read them, I highly recommend it , as Adam , Charles and Barbara’s comments are all deserving of a post on their own). The first paragraph of Adam’s comment actually sent me reeling. (And on how many other sites do comments come in paragraphs? You guys are all so awesome.)

I’ve long maintained that communication online is ‘talking’ not writing. As you’ve explained, It’s the real-timeness coupled with multimedia-ness that makes it accoustic in nature. Some may think that typed words means writing, but if you were to have a conversation of tapped dots and dashes (morse), or gestured shapes and motions (sign language) you would summarize that experience as having just ‘talked’ to someone not ‘written’ to someone (though you have indeed just ‘written’ information onto a medium even if it were only air). The real-timeness, the wideness of bandwidth to stimulate multiple senses, that’s what makes it talking regardless of the tool being used.

Which got me thinking about what other ways I could mess around with the medium. For awhile I’ve been toying with the idea of doing email back and forth entries (of which I hope to have the first, I conversation with Johnny Vulkan, up soonish). In addition I’ve been thinking about questions and answers. But that seemed too straightforward, so I just thought I’d generally ask you all, what’s on your mind? What have you been thinking about? What should we talk about?

No idea if this will work. Also, if you’d like slightly more tough brief (as we learned from Brian Eno, limitations are helpful ), I’m going out to Montana in a few weeks to talk to a class about technology, media and the internet. What should I talk about? I figure I’ll go back through the archives to get a sense of what I’ve been thinking about, but I also thought it was worthwhile to open up the question.

So yeah, that’s about it. Not a ton of rhyme or reason here, so feel free to talk about whatever you’d like in the comments.

Compressing the Unread

Matt almost perfectly sums up my relationship with Google reader : “Here’s what I’ve come to realize about myself: I fully accept that there’s not a particular link in that ridiculous heap that will change my life. It’s been a while since I worried about missing a single killer post or app or XKCD or whatever; if it’s valuable enough, it’ll find me, I got it.”

Later on he also wonders something I’ve been asking myself (and some reader folks) since I got started: “Google, I want you to give me a button labeled ‘Compress into diamonds.’ When I click that button, spin your little algorithmic wheels and turn my reader into a personalized Memeorandum. Show me the most linked-to items in the bunch, and show me which of my feeds are linking to them. And take it a step further. You’ve got all that trends data that reflects the items I’m reading. Underneath the hood might very well be data about the links I click on in those posts. Use that information about me to compress my unread items into diamonds I will find uniquely wonderful.”

Google Reader is already turning into an awesome personal search engine, why shouldn’t it also act as your personal memeorandum ? (And if it doesn’t, I’ve been thinking for a long time this is a really good idea for a startup.)

COMMENTS OPEN

Taxing the Kidnapped

This is brutal in a sort of hilarious way: IRS Topic 357: Tax Information for Parents of Kidnapped Children . Just in case you thought the IRS was heartless, the topic concludes, “This tax treatment will cease to apply as of your first tax year beginning after the calendar year in which either there is a determination that the child is dead or the child would have reached age 18, whichever occurs first.”

via Marginal Revolution

COMMENTS OPEN

Snakes alive!

A few years ago, probably around 2004/2005, I took advantage of some source code that Jared Tarbell posted on levitated.net. I was really impressed with the code because the magic was mostly limited to about a dozen lines. Very clean and surprisingly robust!