EOF - The Last Silos Standing
For the many years I wrote Linux for Suits and the SuitWatch newsletter, I always insisted that Linux and business were joined by and logic rather than or.
I still believe that's true. But, I also believe that many businesses—especially the big ones—still don't get Linux, free software, open source or even the Internet itself. That's because they remain, in the immortal words of Walt Whitman, “demented with the mania of owning things”.
Oddly, the things they want to own most are not things at all, but customers. These companies still harbor the illusion that customers can be “acquired” like slaves and “managed” like cattle. The nicest ranches for customers are politely called “walled gardens”. I prefer an equally agricultural metaphor: silo.
The definition of silo I like best is “a tall cylindrical structure, usually beside a barn, in which fodder is stored”. (That's from the Free Dictionary.) Fodder, in the case of business, is customer data. That data includes specifics, such as name, address, purchase history and call records. It also might include customers' stated or inferred preferences, status with the company (frequent flyer grades, for example) and other variables.
The crowning irony of business silos is that they are built to maximize BI (Business Intelligence), yet they are blind to how they're not working. This form of inward-gazing ignorance is familiar to techies who have watched many silos come down in the computing and networking fields. Mainframes, closed on-line services and proprietary e-mail systems all come to mind. The Internet and its open protocols killed all those things, yet the lessons remain lost on every business that continues to believe that good “intelligence” about what customers actually want can be found inside the company's customer data silo.
For evidence I offer three examples: call centers, loyalty cards and mobile phones. All three are shining examples of a form of architecture that has been discredited, if not defeated, by the successes of Linux, FOSS and the Internet.
Look up “call center hell” in Google, and you'll get millions of results. (This morning, 8.65.) Two of the three top search results on Twitter are by people working in call centers. Most of these are “hold centers”, because putting callers on hold is what they do best. Conversation is not their forté. If you ever reach a human being at the end of a choice maze, you too often interact with a script rather than a human being. After an accident involving my rental car a couple years ago, the woman at the other end of the line reacted to my anger at her uncooperativeness by admitting that her options were limited, literally, by a script. There were only certain things she was allowed to say or hear. When the conversation stepped outside those lines—as it had to, since the accident was novel in several ways—both of us went nonlinear. The call crashed as badly as the four cars (including one cop car) involved in the pile-up.
Loyalty cards are the silliest thing since Green Stamps. By the middle of the last century, nearly every store gave away green stamps, achieving zero differentiation from every other store and adding friction to the entire economy in the process. Today, instead of collecting stamps and sticking them in books (to redeem later for a crappy grill or something), we collect cards that fatten our wallets without making us richer. Loyalty cards require retailers to maintain dual pricing for merchandise and add friction at the checkout counter, where too often the only benefit to the customer is a coupon for something they just bought. Worse, loyalty programs can't tell when or why people don't shop at a store. My family likes to shop at Trader Joe's, because that store avoids the hassles of both loyalty cards and coupons. There is nothing in other stores' loyalty programs that welcomes hearing this useful information.
Perhaps the worst business silos are the Siamese ones formed by cell-phone equipment makers and carriers. Although PCs—even closed ones with Apple and Microsoft operating systems—are open to endless varieties of third-party applications, we see nothing of the sort from the cell-phone business, with the notable exception of the iPhone, which is (as I write this) enjoying its billionth application download. That download, of course, will come from exactly one source: Apple's iTunes. One might consider this a step in the right direction—it's kind of like the one Windows 95 took by making it easy for countless developers to write applications that would run on even-more-countless PCs. The next step, however, has to come from outside the silos of both the equipment makers and the phone system carriers. More eyes make bugs shallower, as we say.
Time to debug some business silos.
Doc Searls is Senior Editor of Linux Journal. He is also a fellow with the Berkman Center for Internet and Society at Harvard University and the Center for Information Technology and Society at UC Santa Barbara.
Doc Searls is Senior Editor of Linux Journal
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- RSS Feeds
- A Topic for Discussion - Open Source Feature-Richness?
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Readers' Choice Awards
- The Secret Password Is...
- All the articles you talked
1 hour 20 min ago
- All the articles you talked
1 hour 23 min ago
- All the articles you talked
1 hour 24 min ago
5 hours 49 min ago
- Keeping track of IP address
7 hours 40 min ago
- Roll your own dynamic dns
12 hours 53 min ago
- Please correct the URL for Salt Stack's web site
16 hours 5 min ago
- Android is Linux -- why no better inter-operation
18 hours 20 min ago
- Connecting Android device to desktop Linux via USB
18 hours 49 min ago
- Find new cell phone and tablet pc
19 hours 47 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?