Skip navigation

JiveWorld16

3 Posts authored by: rcarney

Adib Abrahim and Alexander Derno work in entirely different industries, but found themselves in cultural change that lead to a similar result - an internal Community!

 

Adib shared that prior to 2013 American Airlines was undergoing a brand modernization process that meant major change.  Leadership was ready for change, yet they recognized that employee needs (to be heard and a part of change) were vital to healthy change.  At this point, they chose to develop their internal community.

Why Jive?  Per Adib, Jive enabled:

  • real-time communication
  • transparency
  • engagement

 

In 2013 they launched their Jive community and continuously adapt it according to community need.  Adib has a fun top 10 list of what he's 'learned throughout the process'

  1. Jive is fun
  2. You've heard it before, but it's true, you need buy-in
  3. Get leadership to hold each other accountable
  4. Tie it into your culture initiative
  5. Demonstrate small changes based on the metrics
  6. Don't be afraid to try something new
  7. You will never be ready for social so just jump in
  8. Not everyone wants to be social and that's ok
  9. Don't try and do it all at once
  10. Your'e never ever ever done

 

Alexander's story of organic community developed by a grass roots group of employees with no distinct goal, only a passion and ideas to implement change, was inspiring.  The storyline of evolution from social media (wikis, blogs, etc.) in 2006, to the creation of a Jive community in 2012, was fascinating.

I had a schedule conflict and had leave Alexander's section a little early.  Sorry, Alexander. 

There was no exaggeration fromJennifer Kelley when she introduced this session by declaring that spam attacks have significantly shifted in frequency and technique over the past 15-18 months.  Spammers have become human-centric and more adaptive.  Spammers are creating accounts and emails that appear legitimate and are difficult to detect; until the damage is already under way and crippling your community.

 

Sam Creek shared his first hand experience with the early 2015 'Korean' spam events.  They experienced a period of time where spam attacks filled message boards, the community communication tools became spam repeaters, and community analytics were destroyed.  Every reactive measure lead to greater adaptation of the spammer.  On February 14, 2015 the creation of 100 spam accounts and over 10,000 spam posts forced the community to be taken temporarily offline.

 

Sam and Jive took initial measures to mitigate the attack.  Jive blocked non-sanctioned party IP blocks, banned 2 S. Korean Telecom IPs from posting, and

invited CA Technology to become part of the Mollom Spam Prevention Service Beta.  The CA Technology Community team:

  • turned off private messaging
  • added nofollow rules to external URLs
  • Allow permanent bans
  • added keyword interceptors
  • added a spam link interceptor that requires moderation for users under point threshold
  • moved spam to private space to be analyzed before deletion
  • and worked with their IT team for complex blocks

 

Sam shared that ultimately, none of those efforts were effective.  Their number one issue was that the community had an open door.  In order to secure the 'front door' they set up a black list (which allowed no access), a grey list (requiring moderation), and eventually a white list process.  The white list process cut the added work load of moderation from 2.5 hours a day to .5 hours a day.

 

(White List Process)

 

 

In the Winter of 2015 Jive released Cloud Spam Prevention.  In Sam's experience, the white list process + Cloud Spam Prevention lead to great success and less stress.

 

In Summation, a proactive approach is the best strategy.  Jennifer's proactive suggestions are to implement

  • New user account moderation
  • A points threshold
  • Message governor interceptor
  • Domain blacklisting
  • Link moderation
  • Create 'spam quarantine' private/secret group
  • Define action plan, after-hours moderator coverage
  • Enlist members' help - advise the process to follow r.e. spam/abuse

 

Recommended groups for further conversation:

Spam Management Ideas

Jive External Communities

Ryan Rutan welcomed attendees with an introduction and invitation to the 2016 Tri-Hackathon, Wednesday at 2:15-3:15pm.  The Tri-Hackathon looks like a fun twist on exploring the world of development.  Attendees will compete in coding for use cases, answering trivia about developer culture, and seeking the high score on Gun.Smoke!  Arcade style tickets will be redeemable for awesome stuff!  Find more information at Win Great Prizes at the JiveWorld16 Tri-Hackathon!

 

Most of us are aware that Jive is a platform with building blocks (tiles, rest api, apps, analytics, external storage, mobile, cartridges, activity streams).  This platform structure allows and encourages the development of add-ons.  Ryan and Yuval Twig recapped 2016 Jive devloped add-ons: Jive gmail, Google docs integration for Jive-n, Connector for Zendesk, Connector for ServiceNow, and integrations with Zapier, Sysomos, and more.  Jive will continue to develop add-ons, but they would like to encourage and support other interested developers as well.

In 2015, partners and customers developed and released the following integrations:

  • Partner Solutions
    • TemboSocial Polls
    • Recognition (HR focus)
    • SmarterPath (social learning experience)
  • Customer Solutions:
    • ThoughtWorks - built bulk content management
    • More sessions available later today

 

To ensure that partner and customer developed add-ons are quality, Jive is introducing a new certification process, Jive Certified Solutions.  Jive Certified Solutions will focus on four areas:

     1. Business viability - will the integrated solution be around for a while?

     2. Infrastructure/Security - is the solution quality and in sound standing?

     3. Integration Quality - is the solution doing it right?

     4. Customer Support - will the integration impact the end user experience and how will end users get support?

 

Ryan and Yuval highlighted many new approaches for supporting developers.  In particular, Yuval introduced the new Jive iPaas infastructure.  iPaaS will have a Free option available for cloud instances.  Non-cloud instances will want to inquire about cost.

  • The iPaas wizard is a great starting point for any Jive project
  • The Jive Simulator allows you to test locally, leveraging the iPaas sandbox, before production

 

To find more information about how Jive is supporting developers, be sure to follow the Developers | JiveWorld track, and join the newly streamlined Jive Developers group.