By Ori Brafman and Rod A. Beckstrom
The Starfish and the Spider has gotten a lot of press and attention since it was published in 2006. As the subtitle states, it's about leaderless organizations and how they function. It's a quick read – I finished it in two sittings – and turns out to be a good entry-level text for understanding the difference between hierarchical and networked organizations. Like most such popularizations, it loses a little in the translation, and those who have read more complex texts on networks (such as Castells or Arquilla & Ronfeldt or, ahem, Spinuzzi) may feel like they're playing in the shallow end of the pool. But for those who are just getting into the literature or who want to get the concept and apply it rapidly, the book is definitely a good place to start.
The metaphor in the title refers to two organisms that are superficially similar, but organized differently. If you destroy a spider's head, you get a dead spider; if you cut up a starfish, you get two starfish. Since starfish are decentralized, they are more resilient and better able to recover from shocks that would kill more centralized organisms.
The authors apply this metaphor in a number of comparative cases – the Aztecs vs. the Apache, Napster vs. eDonkey, and classifieds vs. Craigslist, for instance – and abstract a number of principles that describe decentralized organizations:
“When attacked, a decentralized organization tends to become even more open and decentralized.” (p.21)
“It's easy to mistake starfish for spiders” (p.36) – i.e., decentralized for centralized organizations.
“An open system doesn't have central intelligence; the intelligence is spread throughout the system” (pp.39-40)
“Open systems can easily mutate” (p.40)
“The decentralized organization sneaks up on you.” (p.41)
“As industries become decentralized, overall profits decrease.” (p.45)
“Put people in an open system and they'll automatically want to contribute.” (p.74)
Some readers will recognize many of these principles from different sources, but they're well summarized here. On the other hand, the summaries tend to be a bit uncomplicated – networked organizations are sometimes decentralized operationally but very centralized doctrinally, such as Aum Shinrikyo, for instance – but the principles are a good overall sketch.
The authors spend most of their time describing such organizations and discussing how to make them work better. But they also offer advice for combating decentralized organizations:
Change their ideology (p.144)
Centralize them by centralizing key resources (p.151)
Decentralize yourself (p.155)
In a later chapter, the authors discuss hybrid organizations, organizations that are either “a centralized company that decentralizes the user experience,” such as eBay (p.164) or “a centralized company that decentralizes the internal parts of the business” (p.175). This is a good move, although it does not exhaust the dimensions along which companies can be centralized or decentralized. I was left wanting more of these dimensions and deeper discussion of them.
Finally, the authors outline the “new rules of the game.” I won't list the many rules here except to say that they follow naturally from what the authors discuss earlier; the chapter has the feel of a summary for those who have skimmed the book.
So would I recommend the book? I already have to at least one person, and I will to others. The book is a nice introduction to those who want to work up to more complex texts, but it also works well for its intended audience – C-level execs – and for undergraduates. Check it out.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.