4 Replies Latest reply on Sep 28, 2015 9:07 AM by scottwdennis

    What are the best ways to prepare for a JiveX implementation?

    sharakarasic

      Hi all,

       

      After a long sales cycle, we've finally decided to move forward with JiveX. I will soon meet with Social Edge. To those of you who've already implemented a JiveX community, what are the best things I can do to prepare for setting up JiveX? Scott Dennis !

        • Re: What are the best ways to prepare for a JiveX implementation?
          scottwdennis

          Congratulations sharakarasic!

           

          Our experience with Social Edge Consulting and the Jive implementation team was very positive and so far our implementation and launch have been a fun ride.

           

          Advice:

          1. Use the secret group that Jive or SE will create for you in this community as your communication and project management hub.  This worked really well for us and we're actually doing the same with our new LMS clients in our own platform now too.
          2. Don't wait - get in and start building now.  Create a private sandbox space that you can experiment in and start learning all about permissions, groups, widgets, integration, gamification, etc.  There is a ton to learn but Jive is really flexible and powerful
          3. Leverage the community - there are a lot of people in here very ready and willing to help you.
          4. Don't let the cart get before the horse - get your community team into the platform and building but if you are like us, you will have lots of people wanting access (internal and external peeps) before you are ready for public launch.  Push back on this as you will likely be tweaking permissions, SSO, etc.

           

          Jordan Dayton, Biray Seitz and rcarney; what else am I forgetting?

          1 person found this helpful
            • Re: What are the best ways to prepare for a JiveX implementation?
              sharakarasic

              Thank you Scott! Very helpful advice. I'll be posting updates. ;-)

              • Re: What are the best ways to prepare for a JiveX implementation?
                cflanagan17

                sharakarasic

                Scott Dennis advice is dead-on. I'd add one more After #2 above

                1. Invite trusted advocates both from your brand and your company into a "Planning" site you create on your sandbox.
                  1. Use this to get them familiar with the tool.
                  2. Have them try out creating groups for topics they think will be necessary to improve engagement / business results.
                  3. Run regular "virtual" calls with this group. Share what you know. Ask them what they think (do they have questions, ideas for how to use the community when launched?, do they have feedback that is important to consider for launch configuration or policies?).
                  4. Use this "planning" / secret / exclusive access time and team to listen and learn from this smaller group. They will help you a ton make decisions, set policies and launch communities people will want.
                1 person found this helpful
                  • Re: What are the best ways to prepare for a JiveX implementation?
                    scottwdennis

                    We had a phase we called "Closed Beta" where the new site was actually open at a new url but not hooked into our SSO idp.  We invited about 70 people - internal and external - to manually create accounts and come kick the tires.  Those interested in more that a cursory glance were added to a secret beta group that had a series of tasks for people to try listed on the group overview page.  Each task was described as the topic of a discussion so that people could go try out the task and then come discuss how it went for them.  We also had a general questions area on the overview page and a leader board for the points associated with the tasks and the rudimentary gamification we were experimenting with.  Some of our biggest advocates and power users in the old community really thrived in this initial period of new challenges and intensified interaction with the community team (then three of us and now four).