These days manufacturing businesses are more connected than ever before. Every manufacturing company (even smallest startup) has a tremendous need for collaboration – help multiple engineers to get involved into the design process, communication with suppliers, plan manufacturing processes, etc. Social networks and open web inspired many companies to develop collaboration software that mimic consumer social software. One of the main attribute of every social software (Facebook, G+, twitter and others) is so called "activity stream" or "news feed". The trend was strong and produced lots of copycats. The successful and lucky ones got acquired. Many of less successful died.
The idea of activity stream is very powerful. It allows you easy share and consume information. However, here is a thing – it is not protected from "noise vs. signal" problem. The more people you follow – more information will flow into your activity stream(s). You end up with messy stream of information you cannot keep up with. It is probably okay for public news or even for executives in a company interested to keep up with what is going on. However, it is probably not a good experience for engineers that need to work together on the same design or discuss next engineering or manufacturing change request. Also, it is probably not a very useful as a tool to communicate between departments and suppliers. And… this is absolutely wrong model to use for process management.
All problems I mentioned above is actually making the adoption os social system for collaboration questionable. I can see many confirmations to that. CMSWire article The Problem With Yammer? People Don’t Use It speaks exactly about the problem. Here is key passage:
But what if the problem is not about difficulty or learning curves but about culture? What if the problem with Yammer has nothing to do with the product itself and nothing to with usability, but rather with the fact that enterprise workers are holding onto email for dear life and are not prepared to give it up? Microsoft itself appears to be aware of this. The addition of complimentary Yammer for the new Office 365 plans appears to speak to that. However, if Microsoft’s updated offerings are a step in the right direction, they won’t solve the problem of social and collaboration in the enterprise.
Another interesting example – Facebook. Clearly the king of social networks recently introduced simple and very effective feature to get out of noise of your information stream – Save. It can quickly remind you old and well-known list of favorites. Navigate to TNW article – Facebook introduces Save, a new bookmarking feature to help tame your News Feed. Sounds like a simple feature, but it allows you to keep specific post out of noisy channel and focus on them later in a more controlled way.
These and many other examples made me think about what is needed to provide a better way to collaborate. My hunch is that "controlled list of topics" can better serve the need of engineers and other people to work together. How to make it? This is probably more tricky question. I can see it as the next logical step from email that still one of the most favorited tools to communicate. It also reminded me my post Why PLM shouldn’t miss next email move earlier this week.
What is my conclusion? Activity stream is a good way to present flow of information. However, the type of experience it creates is way too open and subject to be affected by information noise. I believe engineering tools should provide more tight way to communicate, exchange information and share data for collaboration purposes. This is main reason people are holding onto email as a best tool. New ways to collaborate is not here… yet. Just my thoughts…