Successfully reported this slideshow.

The Social Enterprise is a Garden. Dig it!



1 of 10
1 of 10

More Related Content

Related Books

Free with a 30 day trial from Scribd

See all

The Social Enterprise is a Garden. Dig it!

  1. 1. The Social Enterprise is a Garden. Dig it!
  2. 2. The Social Enterprise is a Garden. Dig it! Full Adoption. Deep Engagement. 100% Real Business Value…   ThesePiecesfruits everyone tries to harvest •  are the of information when deploying enterprise collaboration software. But, without of information can •  More pieces experience, weeds immediately pop-up. Some try a data off •  Even more pieces of hands approach: build it and they will come. Others are so top-down involved that a frost comes early. Many enterprise collaboration deployments don’t blossom over night. Organizations that don’t have a plan or a dedicated project team will not see the results they may have hoped for. But don’t get discouraged. We’re going to share with you simple but powerful tips to reap the benefits of internal social collaboration for your business. With use cases to plant, conversations to seed, and the right governance models to line the path, we’ll present the best ways to grow success.
  3. 3. Create the Best Environment Soil: Cultivate a Culture of Sharing envision and put to use as soon as they join the network. This is the terra firma to success. Start by   communicating why Water: Shower Support   openness and sharing are critical to the Without adequate planning business. Is it to increase and preparation, collaboration competitive intelligence, software rollouts can soak up to develop an innovative culture, or provide time and energy. To this end, it deeper insights for sales reps? Inspire is important to have a small employees and get their buy-in ahead of time.   but committed project team. To stay with our metaphor, your garden needs regular watering. It is Sunshine: High Visibility & Clear important to have a small but committed project Communication about Usage   team to advocate core activities, such as: collecting requirements, helping employees get Have senior managers started, initiating discussions, clarifying success shine rays of attention on criteria, and more. The Project Team should be the benefits of social well aware of both the business and technology collaboration from the get- requirements, so that decisions on these activities go. Present concrete use are well-informed. Bottom line: no one should be cases employees can foggy on the expectations and preparations.
  4. 4. Get Ready to Plant Prepare High-Yield Use Cases   Cross-Pollinate Use Cases   What business outcomes are you looking To make collaboration highly sustainable, the for? The answers are often overly simplistic initial use cases should be setup to create such as, “Increase the speed with which cross-functional interactions. Although having a employees find experts and answers.” Let’s get couple use cases focus on a homogenous team more specific here. Ask which projects are most or project is fine, design most use cases to cut critical, what are the success criteria, what are across multiple departments, management the timelines. This should be done for about five layers, communities, and geographies. The solid use cases. It’s best to ensure the use result will be greater activity with greater cases are designed for most if not all of the insights, sharing sources, and serendipity to users. These first use cases quickly propagate. showcase the value of collaboration. After the project teams propel the It also helps to include the social bees in your discussions, the subsequent bulk of organization for the initial use cases. These folks users discover a vibrant sharing may not have the most seniority and experience, community and but are high-energy, socially plugged in, strong follow the pattern communicators and natural leaders, and more by creating their likely to create the buzz that drives activity. own bottom-up use Make sure to have enough users to start. If only cases, self-formed a small percentage of users are involved, they groups, and so may have to remember, search for, and manually forth. invite other users to make collaboration really
  5. 5. Get Ready to Plant Continued… happen. This type of thinking instead of just doing can bury a collaboration project before it sees the light of day. In other words, the more users, the more activity you’ll start to see. Seeds of Thought   Now that you have started setting up the right conditions for growing your network, it’s time to create the initial content that the bulk of users will see on day one, and hear about in the invitation and other call-outs. The main goal is to provide immediate value to users so they To help seed the content, enroll not just the come back. Show examples of high-valued social bees previously mentioned, but also work conversations. For example, your vice identify an advocate for each use case and president of sales could share a story of how an from each group and department. Invite these employee closed one of their biggest deals, folks into the collaboration instance before the followed by conversations about how they could bulk of users. These early users can also help apply those sales tips to other deals. Build to confirm the validity and value of the initial momentum by starting discussions for each subject hierarchy, which is covered next. practical use case.
  6. 6. The Trellis of Use Cases The Support Structure   Tips for Building the Hierarchy   Receiving a stream of insights from your 1.  Brainstorm topics of conversations colleagues is useful, but only if it’s relevant to needed to promote business objectives your work. Make sure your social platform gives 2.  Determine sensitivity of subjects ahead of users the ability to organize and subscribe to time: public verses private. discussions based on relevant topics, groups, projects or individuals involved. tibbr Subjects, 3.  Don’t over structure it. Leave room for for example, organize relevant information into employees create subjects as needed. these distinct categories. The flexible structure enhances the discovery and filtering of information so that it goes to the right people. Think of subjects as the trellis of use cases, your support framework. The initial subject hierarchy should be built before the first phase launch, then employees can explore and follow discussions that are relevant to them. It also helps to not overly-administer the subject hierarchy. Allow some flexibility and let the users create, alter and evolve the hierarchy.
  7. 7. Integrate Highly Contextual Data Streams Your knowledge workers are swamped. The average knowledge worker has to access about nine different applications per day, which really slows down the time it takes to find the right information to make a decision. Therefore an important part of the collaboration solution is to enable users to pull in just the information they want from these applications – and act on it, in context – all in one unified interface. Your enterprise social network should stream the updates you need when you need them. For example, marketing manager George just entered a purchase requisition and needs final approval from legal before he can launch a new pay-per-click campaign. Rather than trying to find the right person in legal to ask them for a status update, he simply posts a question under the latest update from the procurement system and the right person from legal responds with an ETA. This way, your employees can collaborate in context to close the loop on key business decisions.
  8. 8. A green thumb… How tibbr Strategy Services Help   Propelling a successful collaborative environment comes with experience. tibbr strategy services work with our clients to ensure full adoption and tangible business outcomes from the beginning. These services include: •  Identifying Key Use Cases •  Tips to Involve Senior Management •  Best Examples for Pre-Seeding Content By following the tips in this guide early as well •  Templates for Creating the Right Taxonomy as periodically, you will make it easy for others •  KPIs to Measure Progress to collaborate and achieve real business •  Best Practices for Creating a Simple outcomes early on. Clients who follow these Governance Model best practices find that users quickly get tibbr CMs cultivate these best practices for directly involved in creating their own subjects adoption and engagement. But, it’s important to as well as determining their own use cases. note that every customer is different. What is It’s necessary to foster those initial best in one engagement often varies depending experiences to then start tracking the change on your specific circumstances. In that way, use management necessary for collaboration to this guide as starting point and when you’re bloom in today’s business landscape. ready to make adoption and engagement grow, reach out to us.
  9. 9. References Sub-Head   •  Slide 1: •  Slide 3: •  Soil •  Sunshine: •  Water: •  Slide 4: •  Shovel & Gloves •  Bee •  Slide 5: Seeds •  Slide 8: Irrigation •  Slide 9: community manager
  10. 10. About tibbr tibbr connects people, applications and data in context and, in an entirely personal way. tibbr is the universal enterprise social platform revolutionizing the way we work, collaborate, learn and share. tibbr brings together what matters-to individuals or groups-to get work done better, faster. With flexible deployment options, tibbr can be delivered on premise or in the cloud, minimizing IT resources and getting all your employees started within days.