My apologies to those who’ve been waiting for Parts 9 and 10 of this series; there have been a number of things on my mind, and I wanted to freewheel along, dwelling on other subjects, while pondering on this. It’s like when you want to remember something and can’t ….. the best way out seems to be to let your subconscious “agent” do the work while you move on to something else … striving to remember only makes the problem worse…. you know what I mean.
Anyway. Ecosystem. A big word and probably meaning many things to many people. If I go “define ecosystem” via Google, the first result returned is this:
The complex of a community of organisms and its environment functioning as an ecological unit.
What was that again? [Or, as my primary school PE teacher Mr Deefholts used to say, while cupping his ear, “How much?”). You may have found that definition more helpful than I did, but I doubt it somehow. But then it looked like a “sponsored” result, so I will move on.
The next definition of ecosystem looks something like this:
An ecosystem is a system whose members benefit from each other’s participation via symbiotic relationships (positive sum relationships). It is a term that originated from biology, and refers to self-sustaining systems.
The third definition goes like this:
e·co·sys·tem (Ä“‘kÅ-sÄs‘tÉ™m, Ä•k‘Å-) 
n.
An ecological community together with its environment, functioning as a unit.
Elsewhere I found this:
a functional unit consisting of all the living organisms (plants, animals, and microbes) in a given area, and all the non-living physical and chemical factors of their environment, linked together through nutrient cycling and energy flow
And this:
a community of living things and the environment in which they live
Why am I spending so much time on this? I think that there’s a lot for us to learn, a lot for us to understand about what makes a virtual community tick. And we’re going to have to arrive at a common view as to what an ecosystem is, in the context of communities and social networks.
danah boyd, in a related context I was privy to, recently said “I don’t think that you can evaluate a system’s technological worth out of the context of its users and their intentions and expectations”.
I think danah’s bang on the money, as usual; I really like her insights. [danah, I hope you don’t mind me quoting you “out of context”].
Where I work, we’ve been going through the laborious process of bringing together our network, process, product and IT skills into one coherent “converged” unit. We did this because we believed that was the only way to get real focus on improving the customer experience. A customer experience that is comprised of the platforms, the people, the processes and the customer alignment.
Too often, people tend to think of the “platform” as the ecosystem. I think this is wrong. So let’s try and define ecosystem again, in the context of Facebook and the Enterprise, drawing on some of the definitions earlier:
- An ecosystem is a community, an integral functional unit.
- An ecosystem consists of living organisms as well as physical and chemical environmental factors.
- An ecosystem promotes the flow of nutrients and energy.
It is in the context of this definition of ecosystem that I want to look at Facebook and the Enterprise. Most people are comfortable with the social network and community aspects of all this; many are also comfortable with the idea that there are many overlapping communities, and that a person belongs to more than one community.
We have to get used to the fact that every enterprise is a community. That the boundaries of the enterprise extend. That this extension encapsulates the enterprise’s customers, partners, supply chain and customer chain. That neither customers nor supply chain participants “belong” to just one enterprise.
There was a time when enterprises had platforms, the platforms were proprietary, and as a consequence the ecosystems were proprietary as well. In fact we had siloed platforms and siloed ecosystems. That was over a quarter of a century ago. As systems became more open, so did platforms, and as a result the ecosystems became more open as well. This openness created a lot of value, drove a lot of the economic growth we have witnessed, created many new winners and a few new losers. The entire opensource movement is an example of the value generated by open ecosystems.
Take the case of the Indian offshore software industry. When I started working in software, everything was proprietary and siloed. Way back in 1980, there was already a well-established offshore software industry. But it wasn’t much use. The model was broken. So you had things like Tata Burroughs Limited, providing proprietary offshore services to Burroughs customers, only available through Burroughs onsite services, with everyone well and truly locked in. Most of the value stayed with the vendor not the customer, and growth was stifled as a result. Then along came the break-up of Ma Bell, the emancipation of System V, the (coincidental) emergence of the PC, the AT bus and the clone, of X-Open and POSIX and a zillion flavours of Unix, and voila, even before Linux, the seeds had been sown. And today you have Infosys and Wipro and Tech Mahindra.
And IBM, with its zillion different proprietary operating systems and its departmental silos, struggled to continue. Found itself needing to reinvent itself. And did. Around Linux. [By the way, ten years ago, who would have believed that the day would come when Apple would be worth more than IBM? Other than Steve, of course :-). Incidentally, Apple’s case is fascinating in the context of what makes an ecosystem open or closed, why such a “proprietary” stack succeeded. Why Apple themselves appear to be telling the world that 25% of the purchasers of iPhone intend to hack it and use it for a network other than the one it was tied to. Why the dinosaurs of the music industry unwittingly helped Apple along. All to be covered in a separate post. ]
Back to ecosystems. While there have been significant technological advances over the past few decades, one of the biggest barriers to the ecosystem model is itself technological.
The firewall.
I’m no expert, but to me the firewall was designed to form a perimeter around an enterprise, a thou-shalt-not-pass barrier with intensive checks. The concept of the firewall seems to be based on the world consisting of disconnected islands of enterprise. This will change. This must change. The overlapping communities model that is emerging requires it to change.
The borders of the enterprise will have to get more and more porous, until a time comes where the border has disappeared. People will belong to multiple communities, those multiple communities will overlap in many and varied ways. Innovation will blossom at the edges of the communities, as professions collide, as the distinctions between some of the professions continue to blur. And it is up to us to ensure that technology does not become a barrier for such creativity. The historical firewall is just an example of such a barrier. The concept of the firewall will continue, but perhaps it will become more personal. Like identity. Like authentication and permissioning.
I will write more about ecosystems. In the meantime, I thought I’d share some ecosystem principles, again in the context of Facebook and the Enterprise:
- 1. The ecosystem does not constrain its people, processes or platforms; they are free to enter or leave at will.
- 2. The ecosystem is nourished by information. Information that is created by the actions, conversations and transactions of its people. Information that helps define, shape and grow the ecosystem.
- 3. People must be free to take out whatever they put in. Just like people make deposits and withdrawals in the banking sector, people should be able to make information deposits and withdrawals in such an ecosystem.
- 4. In addition to being nourished by information, the ecosystem thrives on an alternate source of energy. The interactions between the people. The information derived from those interactions, information that is not available except as a consequence of those interactions. This energy is unique to a given ecosystem, and is jointly and severally “owned” by the ecosystem and its participants.
- 5. These interactions are themselves encouraged and intensified by applications. Applications that are built on to open multisided platforms that form the heart of the ecosystem. Applications that are meaningless without the people who use them, or the information they create. Applications that catalyse value within the ecosystem and assist its growth.
- 6. Within an ecosystem, there’s a lot of NEA about. Nobody owns many things. Everybody can use many things. Anybody can improve many things. There’s a lot of personal responsibility (as in what you say and do and make available) as well as communal responsibility ( as in what actions a community takes). Facebook, in this context, is a provider and enabler of the environment in which an ecosystem is built. It is not the ecosystem. But, in my opinion, it’s a good enabler of ecosystems.
- 7. Within an ecosystem, there’s a lot of YOYOW about as well. You own your own words. You own your own apps, their configurations, their environment, their capacity, their performance, their bugs and their fixes. You own your own data. You own your own relationships.
You own your own you. And with that ownership there comes a set of rights as well as duties. Liberty, not licence.
More later. I’ve rambled on enough. Time for some feedback.
In part 9b I will use the feedback to leaven my heretical mutterings, bringing together the disparate strands of Apple’s success, the role of opensource, contract versus covenant, all in the context of Facebook and the Enterprise. As soon as time permits.
Like this:
Like Loading...
