The importance of team creation within your Social Business software deployment

I am often asked about what types of teams are needed within the Social Business platform deployment. This is a very open ended question, but I have taken some time to think about two clear instances namely; the permanent team and the ad-hoc team.

This blog looks at which type of teams need to be created under which circumstances within the Social Business Community…

When does permanent team creation make sense

Typically permanent teams always focus on continuous ways to improve collaboration within the organisation and deal with the many complexities of managing these solutions. Here are some insights:

  • Within Larger organisations in which a lot of content and information is being shared regularly
  • Where organisations are just getting started with emergent collaboration initiatives and are hiring full-time employees.
  • When Organisations are seeking to continuously incorporate employee feedback into their knowledge repository.
  • When organisations are changing dynamically.

When does Ad-Hoc team creation make sense

Teams here get together for a particular initiative, but employees retain their day jobs and positions. They meet regularly to discuss ideas and resolve problems but they are not 100% committed to enterprise collaboration on a full time basis. Here are some further insights:

  • Organisations where documentation and or content is not actively shared. Small teams can be created around particular projects where documentation and content is shared over a defined period of time.
  • Large companies that seek to assign distributed responsibility to a group of employees.
  • Smaller organisations that don’t have the resources to appoint a permanent dedicated team.

In each instance it is important for the teams, permanent or ad-hoc, to understand how involved the employees need to be and how they will receive the information they need:

  • Select the people that you want to be part of the team; you don’t need to limit this to a closed group. You may ask around and share the news of a new collaborative project to see who puts their hand up.
  • Outline how involved each of the participants is going to be.
  • Discuss whether you think this should be a permanent or an ad-hoc team.
  • Address where the budget can come from and come up with a few options.
  • Arrange for regular initial meetings to ensure that the deployment is successful.

What Enterprise Collaboration can deliver to your Organisation

Other than the ability to perform a variety of tasks, creating more efficient and streamlined processes for the enterprise and greater chance of increased and better innovations, Social Business Software has further distinct advantages. In this blog, I am going to highlight a few:

Collective Intelligence:

This is defined as the pooling of small and incremental community contributions into a coherent, useful body of knowledge. By posting a question to a community regarding a certain problem or issue, the community, through aggregation and discussion forums deliver a great solution.

Expertise location:

This is about finding the right expert within your community. This person who can deliver the right solution, the right idea and even the right innovation. Here you focus on selective intelligence as opposed to collective intelligence. Here you are trying to find someone with the exact knowledge you need.

Emergent Structures:

This is when employees discover how things work in an organisation. This will present a user with the actual and perhaps informal ways goals are attained in the organisation.

Interest Cultivation:

This is aimed at collecting people and content around a common interest with the goal of growing the community and increasing the level of engagement. Highly active people, with the right things to say, rise in ranking prominence within the Social Business platform. This can be linked to HR KPI’s which can elevate an employee even leading to promotion.