Notes on The Starfish and The Spider 02/28/2011
I just recently finished reading The Starfish and The Spider: The Unstoppable Power of Leaderless Organizations by Ori Brafman and Rod A. Beckstrom. It was a neat overview of the different elements of decentralized organizations and many of the ways in which they operate and can be superior to centralized organizations. The book starts with the story of the modern science around memory. Scientists for ages thought that specific neurons and parts of the brain were assigned to specific memories. However, after a lot of testing, they found something surprising about accessing and storing memories in the brain: they are in fact not stored in specific neurons; they are stored everywhere. There turned out to be no hierarchy or chain of command in the brain; memory turned out to be fully distributed. This distributed structure makes the brain more resilient and is the reason why unpleasant memories are difficult to eliminate. The first major example of a decentralized organization outside of the brain centered around Sean Fanning and Napster. The havoc that Napster wreaked on the music industry as well as the freedom it brought to students and consumers of music were clear examples of the power of decentralized/peer-to-peer organizations. Another example the book looked at was Al Queda, where the leader is hidden, and different terrorist cells operate autonomously. Wikipedia is another important example, where collaborators around the world contribute and police it, all voluntarily. When the founder of Wikipedia was asked by the authors who runs its servers, he responded, "I don't know. The users just take care of it." That seemed pretty neat (and scary) to me. The key takeaway here was that all of these organizations were using the absence of clear and commanding hierarchy structure as an asset. MGM's Mistake and Apache's Mystery The book analyzed the way MGM fought Grokster (another P2P file sharing program) in the Supreme Court and compared this to the story of the Apache tribe. When MGM was awarded a winning verdict, they were able to take down a fairly centralized organization for file sharing (Grokster wasn't fully P2P like eMule). The lesson there was that a centralized organization can fall when you kill its center. On the flip side, the story of the Apache ends differently. When Cortez and the Spanish army arrived, they conquered and annihilated the other tribes who were centralized societies. The Spanish couldn't defeat the Apache just like the record labels in the end couldn't squash file sharing when it became fully distributed. The Apache distributed political power and had little centralization; therefore, the Spanish could never really fully conquer them. A central organization operates on coercion. An open organization operates on leading by example. People follow someone because they want to, not because they have to. When attacked, a decentralized organization becomes more decentralized. Napster was centralized and so fell quickly when attacked. eMule was fully open source and distributed with no declared leader or owner. No matter how hard you attack it, you can never fully destroy something so decentralized as that. The Spider, The Starfish, and The President of the Internet When the head of a major telco went to Europe for a business meeting pitching the Internet as it was just being rolled out, he was questioned as to who was the president of this new organization (the Internet). It was impossible for his business colleagues to understand that there was no president of the Internet; it's a network of networks that just works together through mutual agreement rather than hierarchical ruling. This was very hard for people to get initially (he had to in the end say that he was in the fact the "President" of the Internet in order to appease his audience). This was a classic example of people who mistook a starfish for a spider. A spider has 8 legs with a central body. If you chop off its head, it dies. A starfish is totally different. It has separate control of its legs, and its organs are replicated throughout its body. If you chop off any part, it will grow back. In fact, it can replicate itself fully from just one arm. This seems so incredibly cool to me. For the starfish to move, its arms convince each other to do it; there is no central brain. I absolutely love this metaphor for how certain organizations can operate. The book explained how Alcoholics Anonymous (AA) is an organization that is a starfish. No one owns it. There is no central intelligence; intelligence spreads throughout the system itself. In this way, a decentralized organization sneaks up on you, mutates, and grows quickly. The Accordion Principle: Industries swing back and forth between being centralized and decentralized. A Sea of Starfish The book went through many examples of products or organizations that took advantage of starfish principles to thrive: Skype, Craigslist, Apache web server software, Wikipedia, Burning Man, and the Quakers. Several principles came out of these examples. Put people into an open system, and they will automatically want to contribute. A catalyst is responsible for sparking ideas and then getting out of the way. Here are his or her main tools: genuine interest in others, passion, meeting people where they are, trust, inspiration, tolerance for ambiguity, being ok with saying he or she doesn't know, a hands off approach, and an ability to recede. A leaderless organization operates through norms, not rules. Taking on Decentralization When attacked, a centralized organization get more centralized. Think of army bunkers getting more fortified. The only ways to attack a decentralized organization is through ideology (convincing them of a new way) or to centralize them by giving them a scarce resource (like money or cows) in order to create internal competition and hierarchy. It is somewhat sad that a right to property and money almost always leads to centralizing an organization. Fight starfish with starfish. Hybrid Organizations (The "Combo Special") The decision around centralization doesn't have to binary. Many organizations have successfully used starfish principles in certain parts of their operations and not others. An example of this is eBay, where the decentralized user ratings are critical to eBay's competitive advantage. The company itself is a spider, but it operates as a centralized company that decentralized the customer experience. They kept centralized what people wanted to know would be secure and regulated: money (i.e., payment through PayPal). Other examples are Amazon reviews and Oprah book clubs, which decentralized by giving customers an important role. Companies who have open sourced part of their software (like Sun) are further examples. In HR, getting employee ideas and open brainstorming after alignment interviews between random pairs of people across the entire organization is a way to source decentralized opinions for centralized decision making. The Sweet Spot The "Sweet Spot" refers to the level of decentralization that's just right for a given organization, and this changes over time and across companies.This chapter looked at the example of Toyota versus GM. GM was way more centralized and used a traditional assembly line process; Toyota used lean principles and let line employees fully dictate how the operations would run. Toyota bet GM that this was not due to culture, race, work ethic, or anything outside of the pure decentralization of operations. Toyota offered to demonstrate this to GM, and this was the start of the partnership that became Nummi, where team leadership had control as opposed to some central authority; Nummi quickly became the most efficient and profitable plant in GM. Another example of a product that finds some happy medium between centralization and decentralization is iTunes, which allows people to download music quickly and get individual songs (rather than buy full CDs) but does so in a way that's legal and ok with the music industry. The New World This final chapter went through the 10 rules of how modern organizations operate, taking into account the starfish principles outlined in earlier chapters:
This was a fun read and now makes me think about centralized and decentralized organizations pretty differently. Add Comment I rarely whine or complain about stuff I don't like, but it's about time I aired some of my frustration. I think paper, hand signatures in this day and age are stupid and insecure. They can easily be forged/reproduced, and often times people spend little effort in making sure they sign things carefully and the same way every time. In addition, they require using paper (a limited resource) and extra effort and time. I need to print out 2 copies of a contract, sign them both with a pen, put them in an envelope, mail it to the other person, and then wait to get a fully executed copy back in the mail (remembering to follow up if it doesn't come). Faxing gets rid of the envelope and mailing step, but it's often still slow, cumbersome, and low quality (and you're stuck with another paper copy that you then need to scan back into your computer and store in a folder). This just seems so operationally inefficient to me. Using secure e-signatures, for example, seems like so much better of a solution. I know there are various laws that require physical signatures (such as in real estate transactions and consumer home purchases), but I think that needs to change and be modernized. There are so many better, easier to use technologies in existence that are more secure and more efficient. As I understand, there are 3 ways to authenticate a person: something you know (e.g., password), something you are (e.g., biometrics)/something you do (e.g., signature, voice perhaps), and something you have (e.g., RSA token). At this point, I understand some of these technologies may still be a bit expensive to roll out on a large scale, but I really think this is where things are going in the future. But that's not all. For my work on AMA, I had to negotiate and sign a lot of complex legal contracts. I saw so much inefficiency with respect to the work required to revise and collaborate on contracts with multiple counterparties and attorneys. And making sure you don't drop the ball on any important revision or issue is all up to you and your organizational/checklist-tracking abilities. Managing the contract after execution is similarly manual, requiring calendaring, databasing, scanning, and manually indexing/categorizing the critical terms, references, and dates. I don't know how many people suffer through these pains, and I'm hoping to learn through any feedback or comments people leave. What do you all think? I definitely think there's a better way to do things, and that's what I'm hoping to achieve through Redlyne. I recently enjoyed listening to the audio version of Dan Ariely's The Upside of Irrationality. He's also the author of Predictably Irrational, which I hope to read soon. The author, a behavioral economist and psychologist, begins by introducing an irrational behavior that affects all of us: procrastination. He says that procrastination is universal. When he sought a special treatment for a rare condition he had, he needed to inject himself with very uncomfortable medications on a weekly basis. In order to get himself to not procrastinate, he motivated himself with watching movies on his injection days, thereby associating good with bad. As humans, we prefer short-term, not long-term goals. We routinely fail to take short-term pains for long-term goals. He explains that there is a lot of human-incompatible technology out there that doesn't take into account our fallibility (like the stock market). While his first book (Predictably Irrational) is about the downsides of irrationality, this book is about its upsides. The first part of the book is about defying logic at work. Throughout the text, the author explained in detail the scientific studies used to come up with the conclusions presented. It was neat to understand how the experiments were designed.
The book was informative and entertaining from the experiment-design standpoint, and as someone who likes learning about psychology, I enjoyed the book very much. Notes on Nancy Duarte Talk at UCLA 02/22/2011
Earlier this quarter, Nancy Duarte spoke to us at UCLA Anderson about presentation design. She's the author of two great books on the subject: slide:ology and Resonate, and her firm designs presentations for extremely influential business leaders and politicians, in addition to teaching people how to design impactful slides. She started her talk with a personal story about herself and then gave us a debrief on what she just did. She explained the structure of her introductory story as a structure we can use for any story meant to grasp people's attention:
She said that PowerPoint should not be an exhaustive report; it should be visual and persuasive. You can save the details for handouts to give people at the end. If you have to give a report, give an executive summary, distribute it as a document, let the audience read it, and then just discuss as human beings. That's a lot better than cramming numbers in a PowerPoint. Only project visuals that are mnemonic for the audience to remember your message, not for you to remember what to say. Start your presentation with a unique point of view and the stakes for the audience. Incorporate story to show the transformation of a hero from beginning to end. This can apply to business presentations where a team that performs an analysis and comes up with a result can be the hero. To bring it to a more subtle level, she argues the presenter is actually not the hero; the audience is the hero. The presenter's role is that of mentor or yoda. She spent months studying dramatic story structure from classic Greek dramas to the most effective speeches of all time (MLK, Gandhi, Neru, Steve Jobs). She studied the visual/emotional shape of story to come up with a sine wave representing going back and forth between "what is now" and "what could be." She says this is the secret to taking your audience on a ride with you through your speech. Her argument definitely seemed persuasive to me. She broke down every second of Steve Jobs' iPhone launch PowerPoint that she worked on and pointed out his strategies to us. She pointed out how he literally marveled at his own product and modeled the emotion he wanted his audience to feel. The "star" moment was something they'll always remember: when he turned on the iPhone for the first time and showed scrolling. Jobs mentioned Wayne Gretzky in his speech, quoting "skate to where puck is going to be, not where it has been." From MLK and Neru's speeches, we learned about the use of metaphor, repetition, political reference, scripture, and emotions. In terms of connecting to audiences, Duarte's happy that people can now give live feedback on Twitter as they're listening to good or bad speakers. She advocates addressing hostile reactions explicitly in one's talk in order to inoculate them. She spent some time also describing her creative process. She first storyboards everything with Post It's that she can then move around. She does this to find holes. Then she just puts the Post It's into PowerPoint. Some useful links: Below are two related videos as well: The Five Rules presentation, and her TEDxEast talk on uncovering the common structure of the best communicators. Overall, the talk was useful, and as a personal lover of clean, simple, visual slide design, I definitely enjoyed meeting Nancy and hearing her speak. Book Report: The 4-Hour Workweek 02/05/2011
I recently finished reading The 4-Hour Workweek by Tim Ferriss. I can honestly say it was a game-and mind-changing book. The overall concept has to do with lifestyle design: structuring and optimizing every part of your life so that you can make concrete progress towards living your dreams here and now, rather than in the distant future. The author has made himself an expert in many fields, such as entrepreneurship, travel, Japanese, tango, health, martial arts, online marketing, and product design. As a person with many interests and hobbies myself, I have respect for a fellow Renaissance Man. My own philosophy has a lot in common with Tim's, which is why I found his book really striking a chord within me. However, it also made me realize how much of my own behavior and habits is self-destructive and pointless, even though I've been proud of those same habits for many years (e.g., "time management" and "promptness with email"). At times, those skills are helpful, but TIm does a great job explaining the danger behind them. This book had so many details and concrete suggestions that there is no way I can do them justice in a blog post that I want to keep relatively short. I will just try to highlight the most relevant or interesting suggestions. A lot of info can be found at 4hourblog.com. The overall book can be summarized by a simple acronym: DEAL.
The parts of the book that I question the most or do not fully agree with have to do with the cautions about technology and reading. I think it is clearly the case that there is too much information out there, and it is easy to get sucked into it. However, I think that if a person finds enjoyment or fulfillment from reading books or listening to audiobooks (also prohibited by the author, except for his audiobooks), then that's ok. In addition, I think it's fine to pursue businesses where you want to be actively involved and enjoy that. In general, the author's viewpoint is a little extreme (obviously to make a statement) but more or less correct. I definitely recommend this book to any other perfectionists, work-a-holics, and Renaissance Men and Women out there. I recently went to a Hacker News meetup featuring a great speech by Giles Bowkett, a self-made wizard of Ruby on Rails, online marketing guru, and personal coach. Giles has recently tried the challenge of launching one mini-business per month. He did this to test the limits of creativity, see what lessons he could learn, and hopefully make some money doing it as well. He managed to achieve all three goals. He did this by first becoming a master of Ruby on Rails and speaking at tech conferences and blogging on the subject to build a reputation. His background was also in acting, and he's found ways to combine his interests in acting, coaching, and technology to make money through online mini-businesses. A lot of the lessons he taught (like the power of virtual assistants) reminded me of the life-changing and mind-altering lessons I learned in The Four-Hour Workweek, which I recently completed reading and can't wait to blog about. The books he read that helped him with his challenge were the following:
Overall, it was a fun and engagement presentation, and I look forward to the next meetup. Book Report: Purple Cow 02/02/2011
![]() I recently read Purple Cow by Seth Godin. I had heard of this long-time marketing classic for a while and finally got around to reading it. It was my first book by Seth Godin, and I enjoyed his simple, to-the-point style. The entire book was thus pretty quick to read. The title of the book comes from the idea that when you first drive to the countryside, cows look pretty cool. However, cows get pretty boring after a while. However, a purple cow would be pretty remarkable, even after seeing normal cows for a while. This is the core concept behind the book. Your offering must be remarkable, just like a purple cow. You can no longer rely on advertising on a marketing department to simply selling existing products; you must innovate and focus on the product itself. The method he argues for is to create remarkable products that people seek out. He calls such a product an "idea virus" that you must get to the right "sneezers" who can spread it. These sneezers are early adopters in a specific market niche that you directly appeal to. After you've had success doing this, you must reinvest your profits to create new remarkable products as the existing ones become commonplace. He argues that you should welcome criticism and in fact do things that provoke it. Appealing to the center of the market and the masses is bad; you appeal to no one and your message becomes bland. He argues for the opposite. If you show up in a parody, you're doing the right thing. He brought up the Japanese word "otaku," which means something more than a hobby but less than an obsession. You must find consumers with otaku who will try your product, learn it, and spread word about it. It is helpful to target markets with already existing otaku. For example, go to sci fi conventions to find sci fi fans. The key is to change the product, not the ads. A slogan is just for sneezers to pass on your idea properly. Don't use committees or compromise on your crazy, directed ideas. Leave design mavericks alone to do what they want and create remarkable products. Once you get sneezers, get their permission to keep them posted on progress, and give them tools to spread the word. If you can, build marketing into your product directly so it's obvious how to spread information about it. He recommends launching 10 products with 1/10 of the ad budget each instead of 1 product with the full ad budget in order to learn 10 separate, useful lessons. Overall, there were four key Purple Cow takeaways in the book:
I enjoyed the book and can see how it is such a foundational text for influencing a lot of current thinking about these subjects. Yesterday, Craig Newmark came to talk to us at UCLA Anderson (Professor Jonathan Greenblatt led the conversation). It was an interesting discussion and went into many areas I wasn't expecting. Below are some of my notes and takeaways.
Overall, I was impressed by his emphasis on just doing what he thought was right, on pleasing his community, keeping his site simple and focused, and using social media and nontraditional mechanisms to promote philanthropy. | About Max Mednik
Max is an avid entrepreneur and student of life. He is a graduate of Stanford and founder of Ridacto and AMA Capital. He is a member of the business school class of 2012 at UCLA Anderson. He lives in Los Angeles with his family and spends his free time enjoying his many hobbies and interests. ArchivesJanuary 2012 CategoriesAll SubscribeConnectFollow Me on TwitterShazam Tags |









RSS Feed



