Many organizations have used social software tools; emails, video conference, online chat, forum, etc. Newer applications of social software associated with web 2.0 such as wiki, blog, social bookmarking and tagging are also have been used in organizations. Most of the tools were used as a knowledge management tool for knowledge building, knowledge sharing, knowledge networking, information dissemination, etc. Some research conducted case studies of social software usage in companies to support business process. The results are varied, some gain success and some get failure. It is said that most success comes that the use of social software are intended as solution to answer business process’s needs.
The key of social software is in the “social” thing. Participation and involvement of the users, which is bottom up approach make these tools “survive” in the context of organization. Without users’ participation, I think social software will have no use. People in organization, of course need to communicate and collaborate each other, which makes sense if it is said that social software can be used in all business processes, but to what extend? If I think that social software means emails, it is reasonable. But if I see from the newer application related to web 2.0, sometimes it is still quite difficult to imagine that all those processes need blog, wiki, social bookmarking or tagging.
However, I try to create a metrics between social software tools (blog, wiki, forum, social bookmarking, tagging, social network service, and instant messaging) and business process classification (core and support processes). I also believe that the use of the tools are not the same in nature, and the needs of business processes are not the same. So, I conclude that different business process needs different tools to support it. The result is that all the processes can make use at least one of the tool I’ve mentioned above. The organization can adopt the social tools to support its business process, but once again, the adoption needs plan and work. It is easy just to install the tools. But what is important is that the tool can accomodate the needs of the users and business process itself.
One thing that is more interesting is the adoption of social software tools in one organization is not the same with other organizations, so I think social software adoption will be very various and quite dynamic in nature. Some factors that need to be checked in adopting these tools are organization’s culture, change management, user’s behaviour and management support. The adoption is not about technical thing, the management part is as much as important as the technical part. In fact, it could be more to be a concern.
The driver of social software, I think is the users. Use, participate and enjoy. When the users feel that, I think the adoption would be just fine.
How can we make social software adoption to support business process in organization to be a success? – check business process need. - fact that business process need social software tool. – analyze business process need and tool to be adopted. – prepare change management in adopting new technology (management) and the tools to be implemented (technical). – monitor the implementation. – evaluate the implementation.
How do we know that the use of social software enhance business process? – reduce working time. – increase the work that is processed. – save costs. - yield greater production.
How can we measure that the use of social software can increase production and quality? – increase sales. – reduce complains.
How do we find out that the use of social software can support decision making? – real time and more feedbacks from customers. – more information and knowledge exchange can be performed.