We just started a four-part blog series about designing Jive SBS. You can use this approach when someone requests a new space in your employee environment, for example, and use as a list of checkpoints against the design of your current All Content page. Not needed so much for Groups.

Nova, I'm going to upload a framework for onboarding new communities here. Would love your feedback! We developed it for a specific client, then generalized it, but these things tend to be in continuous improvement phase...

Weird. I assume you're logged in when you're trying to open it? If you're not logged in, it should prompt you to do so.

I've set collaboration options as myself being the only one who can edit. The fact that Kevin is able to view and download it makes me very puzzled. Perhaps try flushing the cache on your browser before trying to hit it again?

Looking at the Flower, my guess is the intranet sites are big on the publish. We are looking at moving content off the intranet and into the community. Since thatcontent is publish petal, are there any suggestions or examples of how to move content and "sell" the value of gaining more petals?Mike

Migrating is beyond my pay grade, but selling the value of more "petals" is certainly doable. Assuming you need to sell this to Corp. Communications first (?), a good approach is to:

1: Neutralize the existing scenario

"Yes, we can do everything in Jive SBS that we can do in the existing intranet." If this is NOT true, e.g., requirements dictate that corp comm must lock down portions of a user's Your View page so that corpcomm messages are ensured of delivery to employees, or perhaps the ability to personalize content based on user role is required, then know that customization in Jive SBS will be required to complete this. And if your intranet is a portal that aggregates multiple APPLICATIONS, then it should stay as-is. But, if it's just plain ol' content, and Your View is left up to users to own, then you're golden.

2: Sell new capabilities

Employees will now be able to participate in conversations about corporate news articles - can lead to greater fidelity to the company (measured by HR's annual employee engagement survey)

Executives can now blog to be more in touch with the troops (or corp comm can word-smith what they write for them) - they can moderate comments on exec blogs to keep the corporate worriers happy

Since SBS tends to become the place everyone knows to go to plug into the employee buzz overall, Corp Comm will get more eyeballs on their stuff

CorpComm will have a better feel for what's going on across the company at any given time, and can tailor communications in real time based on that information.

Communities of Practice can emerge across the organization, and SMEs can more easily answer questions in a dynamically updated knowledge base that is searchable and discoverable by others.

Team meetings can be made more productive because team members can create their own collaboration groups, in which they co-create agendas, get questions answered on demand (no need to wait until we're all on a conference call!), and even take meeting minutes and assign action items.

Users can decide to interact with the new intranet completely through RSS or their email inbox, if they wish.

Since you already have a successful external community, you may need to do some "revisioning" if your colleagues see the separation of External Community and Company Website as a good pattern to follow for internal as well.

Thanks. I think that selling the “you get more” and “it is easier and faster” are the easy part. Since we do not want to have a community look like a set of simple, flat, linked HTML pages (IMHO), mapping the information from the current flat pages into the dynamic community is the real work. Any case studies or examples?

You could also use Community Everywhere and just add discussion capabilities into your existing intranet sites - the discussions would take place in Jive, and they'd show up in both Jive and on the intranet page.

Intranet web team does not seem to be able to do that. Also, from what I heard, implementation is not as feature rich and robust as the name implies. We are also looking at this as a consolidation, information source reduction, cost saving measure. Adding Community everywhere to the web pages would add complexity and, initially, more work.

Hi Gia, I really liked the series and have found great value from it. I was wondering if there'd been an update since the initial posting. Given it's some 4 years down the track is it likely that new methods, thinking and technology may have changed the way designing a community now gets done.

I also understand you'll be back downunder in March so I look forward to seeing you again.