Audiences are Messy Too

March 10, 2008

sarah-lacy-125x250.jpgYesterday I wrote about customers being messy, and that it is our job to work with, rather than expect them to use our products and services only as the engineers intended.

Well, audiences can be the same! The Sarah Lacy keynote interview of Mark Zuckerberg yesterday was a very educational event. As a public speaker with 20 years experience, I shared the audience's impatience with her style and also felt her pain as the session eventually erupted in loud shouting protest. A lot of blame is being dispensed, and I think SXSW has some responsibility on the table too. Seems that people who weren't there are being more forgiving however the energy in the room was very hard to dispute.

For me, it's a great opportunity to take some notes to serve as reminders for events in the future. Jeff Jarvis has some examples. I've condensed the collective ideas into a pocket-handy bullet list.

  1. The larger the audience, the more it makes sense to plan for contingencies. Once you are in process, the titanic effect kicks in and it is not easy to know if things are going south, and then be able to act on it.
  2. Know when to use the old rules and the new rules.
  3. Use the best practices of Speaking 1.0:
    • Have a more formal introduction so the audience are informed about the speaker's expertise.
    • Event organizer should prep the speakers and remind them to repeat questions from audience if not captured by the microphone, for the recording and more importantly to keep all in the audience part of the conversation.
    • Have chairs that are comfortable and complementary to the speakers. Do everything you can to help them be at ease and look good so their knowledge can shine through. The chairs were too low to the floor at this keynote, which may have contributed to Sarah Lacy's body language problems and also made it harder to see them on stage.
    • The interviewer's job is to shine a light on the featured guest. It is not to draw attention to oneself.
    • The specific venue will dictate how much of your flashlight has the inquisitive and honoring bulb (the Lannan interviews are superb when people come to hear insights from someone they love) or the probing and investigative bulb (as the Columbia University event with Iran's President Ahmadinejad).
    • If there are pre-arranged questions, and you have been honored with a scoop, don't blow it! (Sarah announced that Facebook was launching a French version and stole the thunder away from Mark Zuckerberg.)
    • Interviewer's job is to ask questions, not make statements. The guest's job is to answer questions, not repeat PR taglines (paragraph 6).
  4. Use the best practices of Speaking 2.0:
    • Engage your audience in advance to find out what they want to know from this person who is so private and inaccessible.
    • Being casual does not equal being flip or disrespectful. I thought the comment about his dripping wet t-shirt (from nervousness on a previous interview) was out of place.
    • Bring the audience in to your past experiences with the guest, don't use them to exclude people. This translated as unpleasantly coy, superior, and lacking the highly valued transparency of 2.0.
    • Listen to your customers. When things are not going well, own up to it (don't blame the audience) and take a minute to re-adjust. Ask for help. Apologize. There are numerous 2.0 behaviors that can have haters turn into fan boys if you know about and are willing to use them. I'm not saying this is easy because it isn't. But opportunity exists to help us all become stronger, clearer, and more competent.

Things happen and Sarah, to her credit, is holding up against the barrage of criticism Here's her point of view. Learn, laugh, and move on.

We Have a New Site Design

February 25, 2008

bare feet studios 2007 web site designTime to stir up the water and get a new blog design. Our previous design was very minimalist. We've decided too minimalist. We want you to be able to see the range of topics we care about, the various projects we are managing, and have room for things like Twitter and Comments too! Please tell us what you think. We splurged and bought this theme from a top Wordpress designer, Brian Gardner. (Internet oddball perhaps, but I like paying for quality services.)

One of the coolest things about blog software is how the design elements and the content are separated, kind of like how editorial and advertising once used to be. :-) In theory, it's possible to swap out a new "theme" on the Wordpress blog, and the database of posts and comments simply gets wrapped in a new look.

In reality of course, it's not that easy because inevitably we want to tweak a little here, change a color there, add a widget, hide a widget, and make all new graphics too! It's so emblematic of the state of the web these days. On the one hand the glass is half-full: so many things are free and creativity abounds. OTOH, the glass is half-empty: it takes hours and hours to find stuff and make it work the way we want it to, a full spectrum of brain matter is useful when managing the wide and deep terrain that covers coding, design, and ultimately writing a coherent message!

I interviewed a marketing exec from IBM back in 2002. He said they had already survived 11 iterations of their web site over the past 6-7 years! Meanwhile, many small businesses are content to have one iteration every 10 or 11 years! (OK - so maybe I exagerrate a little.) Here's a list of things to think about to see if it is time to redo your website.

We want some of our clients to update their sites; "unfortunately," we built them with the most modern tools available at the time, so the sites are surviving, if not thriving. If it's not broken, don't fix it makes sense. But then there is the question: what opportunities are being missed that can only be gained with new technology?

One last thought. I used "we" a lot in this post. Really, it is Shane who gets the big kudos as he researched the WP themes, did all the extra programming, and even added some upgrades to the templates that he is sending back to Brian, the original developer. Mahalo nui Shane. You are no ka oi!