(Update – swapped Sam’s live UStream embed for Michael’s recorded YouTube embed)
This is an expansion on my Brrism talk on Systems Theory and how it can be applied to social media (systems).
There are a couple of benefits of using something like systems theory when designing a social media system, plus a couple of drawbacks. Perhaps most importantly, it helps with the big picture before worrying about API calls, jscript vs php, etc. The main drawback is that is won’t tell you how to make your social media system actually grow and thrive.
If you’re interested in the history of systems theory, General Systems Theory, Bertalanffy, et al, then my previous post touched on that, plus there are good wikipedia pages to read (linked to in this sentence). This article will concentrate on the overview, the next article will introduce to a particular systems approach and I’ll conclude this mini-series with an example application.
What is a System?
The word ‘system’ has become somewhat diluted and it’s meaning confused. However, systems are relatively easy to spot and describe.
Firstly a system has components. A ruler is not a measurement system, it’s just a straight bit of metal or plastic with some marks on it. A feather is not a flight system, it’s very well adapted to direct airflow, perhaps with display markings, certainly helps with insulation, but it’s not a system.
All those components are contained within a boundary. Sometimes that boundary is fairly obvious, like the Yellow-Bellied Sap-Sucker. Sometimes the boundaries are more arbitrary, this website might be considered a system but there’s no physical boundary. Ultimately, the boundary is where you want it to be, but should be relevant to the system you’re looking at. But remember, the wider the system the more complex, too tight and you might not have a system at all!
There is a theoretical construct called the closed system, in reality all systems are open. This means there are inputs and outputs that cross the boundary. What this stuff is that crosses the boundary will depend on the system. You might have information, raw materials, written articles, even abstract concepts like trust. The point is that stuff crosses the boundary and you can describe it.
There is an important caveat to all this stuff crossing the boundary, there has to be a transformation between the input and output. Otherwise you’ve got a pipe! A pipe is not a system.
A communications system is a system because although part of the input (your message) is hopefully the same as the output (your message), there is a pile of associated data about the sender and receiver that is transformed in moving your message to your recipient. There are also internal transformations of the input message through encoders, compressions algorithms, decoders, etc.
Systems are also in a hierarchy of systems that form their environment. My little Sap-Sucker lives in the rainforest that is its ecosystem, that is part of a wider global system, and so on. It also has a digestive system, neural system, and so on down the scale. Systems within systems.
And lastly, but most importantly, systems display something called emergent properties. In social systems this is the law of unintended consequences. Behaviours that arise from the interaction between all the components and sub-systems, variations in inputs, changes in the environment. The point being that you can’t define them all when you analyse the system.
So far, so mechanistic. How do we apply this to social media? More >>
Nice blog post, John – and a very good follow up to your excellent Brrism Talk last Wednesday. I have now uploaded the video to YouTube and I’ve made sure that embedding is enabled. You can see the video (and grab the embed code) here:
http://www.youtube.com/watch?v=fjKoMe7W6H8
Cheers Michael, I’ve updated the posts with the YouTube embedded code, I’ve kept the links to Sam’s UStream in the text.