Found in 1 comment on Hacker News
chegra · 2010-08-27 · Original thread
hmm... I think the author is talking about a Sharper team. http://www.srds.co.uk/cedtraining/handouts/hand40.htm#Shaper

This can be good for getting the ball rolling and keep it rolling. There are several problems with a team like this: 1) Leads to lots of arguments and falling out. 2) The team in unbalance, it may lack creative elements. Might produce stuff but nothing world changing.

Start-ups have seen traits that they see as necessary for them to win. For instance, Shopify has identified the Resource Investigator/Plant team.http://37signals.com/svn/posts/2378-profitable-proud-shopify . They only hire creative programmers. What they have seen is that creative programmers might be slower but they make up for it by reducing the amount of code written. The problem with this team is that rarely creativity people follow through with stuff to the end. They like the creating part but once that is gone they don't want any part of it.

Just a side note Shopify team would whip the shit out of wePay team any given day. But they don't have the tough guy act going for them(Data taken from belbin's book).

The main thing I think start-ups should realize that a lot of studies have gone into what makes a good team. Belbin Team Role Theory is a must: http://www.amazon.co.uk/Management-Teams-They-Succeed-Fail/d....

The best team is a mixture of people, not a unbalance team.

Fresh book recommendations delivered straight to your inbox every Thursday.