A community of technology community managers, leaders, and builders.

4: Echo Chamber

Mary @ Chef
Tori @ Oracle Java
Frederico @ Canonical
Heather @ Java
Tom @ OpenStack
Dawn @ Puppet
Jeanette @ Detroit
Beth @ MS Visual Studio
Cat @ Google
Julia @

Echo Chamber

  • how do we find “the rest” of the audience?
  • how to we make sure when we’re gathering data on what we can do we’re talking to everyone, and not just the “echo chamber”?

How do you know if you’re in an echo chamber
    “everything we do [developers] love”

looking for best pracives to make sure you’re getting the full audience

always talking to the same people with the same ideas

always ask a tame user cohort

“I see the same speakers, the same topics”

when feedback starts getting repetitive

when you don’t see a diversity of use cases

you have people who waited two years to present their list of problems

    Learn who the influencers are, and learn who the others are.
    Talk to people!
    Time box the feedback you get from a contact
    eg 6 month feedback project, then byeee
    but the same people can keep signing up
    Ensure that people know their feedback is actually welcome
    Blast the message through every communication medium you got
    a defined list of things to participate in, tailored for the audience
    avoid jargon
    talk about the negative things
    don’t panic :slight_smile:
    training people in the community on what they can do
    try and get to the point of self-governance, so when someone says something harsh, there is push back
    internal CRM (non marketing) where customers have opted in - always ask and put them in immediately
    then choose the people and contact them
    balance ‘maintaining relationships’ and creating an ‘old boys club’
    social science experiments - monkeys - if one monkey went to a particular area in the floor, they would hose down all the monkeys. after time, if a new monkey went near the area, older monkeys would jump on it. After all original monkeys had been replaced, and no remaining monkeys had ever been hosed the behaviour would still remain. Devs/sysadmins can have the same response - “this problem is wrong/stupid/just don’t go there”.
    intentionally construct echo chambers as a way to get a new person with certain skills on board
    read engineering without borders canada fail report - embrace the things that you didn’t do well
    get echo chamber participants out of their comfort zone
    create a space where the old timers aren’t there already
    travel around the world
    quantify naysayers
    don’t assume longstanding things are actually true eg the thing that 4 users said 2 years ago becomes truth
    capture knowledge from people who are leaving

Thanks to for being the kind sponsor for this forum!