It is Part 1 of a three-part series. —– There are generally two approaches to creating an initial Jive SBS structure: emergent , and prescribed . Since many organizations are in the process of a cultural evolution about how they collaborate and network when they first implement Jive SBS, the best approach to structure involves a combination of emergent and prescribed. Jive SBS can Home Content RSS Log in Connected Connected Home About Speaking Jive SBS Structure Best Practices, Part 1 September 14th, 2009 by admin Leave a reply » The following is a result of Jive Client Services ‘ extensive work with many large clients who have deployed Jive SBS for employee engagement purposes .

Read Jive SBS Structure Best Practices, Part 1 before reading this. Special shout-out to my colleague and friend, Kathryn Everest , for writing this entry. —– Jive SBS Spaces Types of Spaces In a large enterprise, space structures should reflect: key enterprise knowledge domains (e.g., products, customers, industries) where there is significant business value to be gained by improving collaboration at the enterprise level key strategic topics where your organization is trying to stimulate enterprise conversation and collaboration (e.g.,

The main defining aspect is that teams exist to do tasks. I’m finding lots of teams want to use social tools as a space to coordinate and communicate, and at the moment all we (my work) have to offer are our CoP tools. Our CoP spaces are more designed for learning and sharing, whereas team spaces need conversations to revolve around task objects. In my last post I pointed out the difference in the dynamics between Teams and CoPs . So although our CoP space offers the tools teams are asking for like blogs, forums, and wikis, these tools are not packaged