Jive SBS Design Practices, Part 1

March 8th, 2010 by Gia Lyons Leave a reply »

The following is a result of Jive Strategic Consulting Practice’s extensive work with many large clients who have deployed Jive Social Business Software. It is Part 1 of a four-part series.

It’s not about you, Corporate MarComm. It’s about we.

It’s not just another website, and yet many approach the design of their community site the same way they approached their intranet or corporate Internet site.

Which are usually all about one-way communication and passive consumption.

To avoid doing this with your community’s design, try using what we here at Jive call, “Barry’s Community Flower” to figure out what your community is all about. This thing actually grew (ha ha!) from Gene Smith’s Social Software Building Blocks (which grew from a few other frameworks), but we like to name our stuff after the peeps who bring it to our frontal lobes.

What do the petals mean?


Can you identify what the main characteristic is?

To spark your thinking, check out these communities, powered by Jive SBS.  See if you can figure out what the main characteristic is.

Identify your community’s top three characteristics

Now, pick the petal that best reflects what it is you’re trying to accomplish with your community, based on:

  1. Corporate objectives“ACME Inc. needs to get abc from the community”; and
  2. Member objectives“I really don’t care what YOU need, ACME Inc., but I want to do xyz here.” (more on this in Part 2)
How to pick your petals
  1. A facilitator draws the flower on a whiteboard/flipchart/napkin/back of her hand.
  2. Everybody gets to pick JUST ONE petal, silently. Shh.
    Note 1:
    It’s not like people are going to do ONLY that one thing, so don’t get your panties in a wad. They’re all relevant, but one has to be primary if you want an elegantly designed site.
    Note 2:
    Don’t think too much about the differences between these characteristics, as they will quickly all seem to mean the same thing, or overlap so much that you cannot make a choice.
  3. The facilitator goes around the room, asking for each person’s vote – she places a mark next to each petal that receives one.
  4. Usually, one petal will emerge as the primary community characteristic, and the next two petals that received the most votes become the two secondary ones.

Voila! You have determined the primary and two secondary characteristics of your community! Yay!

Now what?

First, make sure that your characteristics are in line with the community’s overall objectives. For example, talk/hug it out re: how “Relationships” will help meet the company’s objectives of “Driving Growth” – and make sure somebody is either taking notes or recording your conversation. Gold often emerges here.

If you simply cannot find a connection between the characteristics you’ve chosen and the objectives of your community, stick a tack in that discussion, and stay tuned for Part 2 in this series.

Advertisement

11 comments

  1. Luke says:

    Very cool Gia. Really like the graphic. Well done. – Luke

  2. This is timely. I’ve starting to try and really rethink the internal comms paradigm re the intranet and how social media changes the game. This is making me wonder what an ‘enterprise flower’ might look like. Maybe it’s a flow-er as in a river or stream.

    • Gia Lyons says:

      Interesting idea, Russell. We’ve actually modified the community flower to be more helpful when designing employee communities – see the parenthetical petal labels. Are there any petals missing that might be specific to employee communities? I’d like to think more about adding “Process,” as in “improve business processes.” Hmm…

  3. Nova says:

    Yes, addressing processes would be good. Gia, when you say parenthetical petal labels, do you mean the smaller text below the larger labels?

  4. Nova says:

    P.S. On picking the petals, I always find sticky dots to be a great way to visualize a vote in a facilitation. And you can color code if you need a contextual vote.

  5. Ron Berndt says:

    Nice work Gia and team. Looking forward to the next installments of this. Ron.

    • Gia Lyons says:

      Thanks, Ron – interested to hear if it’s applicable to your situation, actually. You’ve got… shall we say… a “sophisticated” environment. 😉