Author Archive: Rachel Luxemburg

FITC San Francisco

FITC’s conferences have been a staple of the Flash community for roughly a decade, and this year, Shawn and his crew expanded their horizons to bring FITC to lovely, foggy, San Francisco.

I was there at the Adobe booth for much of the conference and I have to say the content was amazing – a fantastic lineup of community and Adobe speakers that made it extremely difficult to decide what sessions to attend. The booth wasn’t bad either, between a demo of Grant Skinner‘s Androideroids game, a huge pile of funky Flash Platform t-shirts, and other fun stuff as well. But of course you don’t go to a conference for the Adobe booth….. :)

Unfortunately the sessions weren’t recorded and even the stream from the Influxis Lounge doesn’t seem to be archived. But for a quick taste of what it was like to attend FITC SF, the team from the Adobe Edge was there to record some of the highlights:

FITC Mobile and 360|Flex DC are both on the calendar for September, and then it’s smooth sailing until Adobe MAX! We’re cooking up some fun stuff for the Community Lounge at MAX; more about that another day though.

Learning From When Things Go Wrong

Image via Wikipedia

One thing you learn early on in community work (as in life) is that not everything works out the way you think it will. This is especially true when you’re trying to start a new event or user group.

New user groups face a lot of challenges when they get started. Finding a place to meet is a huge issue for some. For others, it’s finding local speakers. Still others struggle with how to get the word out about the group and attract members. And then there’s the whole budget issue … it is not easy, and many groups can’t get takeoff velocity despite the best intentions.

Putting on a bigger event, like a conference or a camp, is even more challenging. Even a small conference in a less-expensive part of the country can run up a five-figure budget, and for the bigger conferences the costs spiral up fast. It’s not easy and when things don’t go as planned, it can cause a lot of financial havok for the organizers.

It’s always sad to hear when a conference fails, whether it’s one that has been around for many years or is trying to become a new conference. The fact is, trying something new is always a risk, and inherent to risk is the possibility of failure. You don’t get one without the other.

And that’s OK. It’s more than OK, in fact – it’s necessary. You cannot learn or grow or build anything new without risk.

Even worse, sometimes people who fail at bringing a new conference or user group into a community will feel they’re not able to participate at all; that they don’t have “what it takes”.

If that’s you – please, don’t take the wrong lessons from failure. Learn what you need to learn about why you failed, and take the steps necessary to fix them. Maybe you need to find a partner who has some of the skills you lack. Maybe you need to change your focus, or try a new approach to your outreach. Maybe you were too ambitious in your goals, or maybe you overestimated the demand in your area. Whatever it is, though – push through it.

And once you’ve learned what you need to learn, if the fire to make something happen is still there, try again.

Enhanced by Zemanta

Community Leadership Summit 2010

It’s been a week since I returned from the Community Leadership Summit in Portland and I’ve had a chance to digest the event. The CLS is a 2-day unconference organized by several longtime community managers, including Jono Bacon, Michael Van Riper, Marsee Henon, Dave Nielsen, and a bunch of others as well.

Unconferences are a tricky thing to pull off well, but the CLS team did a great job with this one. The 100+ CLS attendees came from all over the technology (and physical) map – there were tons of open source folks, representatives from major companies like Google, Oracle, Microsoft, PayPal, (and Adobe of course), Portland natives and people who’d flown in from Europe and even India. Piggy-backing the event on OSCON helped a lot, but I was far from the only person who came in just for CLS.

Sessions at an unconference are much more like focused discussions than they are presentations. The posted topic and what actually gets talked about can end up being very different. But that’s OK. I “led” two sessions (one on community conflict, the other on community lifecycles), but that essentially means I thought up a catchy title & put it up on the schedule board – the stars of my sessions (as all the others) were the participants.

I can’t say I walked away with any earth shattering new information but a few themes stood out:

We’re far more alike than different. Regardless of whether you’re involved in a technical open source community, a local block association, or anything in between, the challenges each community faces are remarkably similar.

It’s always a challenge. Conflict is virtually inevitable when strong-willed people are involved. You can’t avoid it but you can take steps to make conflict less frequent and painful.

Community == People. This one was particularly apt for technical communities. Your community is not composed of the tools you use or the bits you create – it’s the people at the other side of the screen.

I have a feeling I’ll be blogging more about these themes in the future as well. :)

For other takes on the weekend, check out the blog posts by Evan Hamilton and Andy Oram.