Why Yammer believes the traditional engineering organizational structure is dead

(written by lawrence krubner, however indented passages are often quotes). You can contact lawrence at: lawrence@krubner.com

Ruby Glasses sends me to a post about Yammer. I’m now working a contract gig at Timeout.com and the tech team uses Yammer to chat about tech news. So I was interested in the article. I also posted the article to Yammer, so the rest of the tech team would see it.

Taryn East picked 2 very good quotes out of the article:

Highlights for me:

Yammer’s biggest rule of thumb is “2 to 10 people, 2 to 10 weeks,” … If you employ the “2 to 10″ rule, it’ll also force you to release often, test your assumptions, and not over-invest in mistakes.


While everybody knows how expensive context switching is, it’s staggering that nobody builds that into their organization as a constraint. With total focus, you build one thing, ship it, and then are able to move onto something else.