Admittedly, I’ve benefited greatly from criticism. Much of my expertise as a coder can be traced to thoughtful co-workers who sought to evaluate the strengths and weaknesses of my work in a constructive manner, instilling values in engineering that serve me to this day.
Similarly the organizers of a traditional curated event will benefit from criticism. By now the organizers of the recent TAM8 skeptic conference event in Vegas know well of the problems with the reception of July 8th. (The music was too loud, e.g., driving most attendees from the room prematurely.)
But when it comes to open ‘unconferences’ like SkeptiCamp, your suggestions and criticisms (however well-intentioned and thoughtful) may not be effective in the ways you have come to expect of traditional events.
Let’s say you attend an open event for the first time. While you found great value in the effort you nevertheless found certain aspects of it falling short. Examples might include: “breaks should be longer” or that “there were not enough women speakers” or “speakers should be kept on time.”
Because SkeptiCamp is a young event model intended to be accessible to inexperienced amateurs, you should expect a few rough spots with events, especially as they are getting established.
You might have great ideas to improve upon the effort and remedy the problems. Your suggestions may be met with appreciation and thanks, but don’t count on them influencing future events. Reasons will vary: organizers are aware of the problems and choose to solve them in other ways. Or, they don’t consider the problems to be serious. Or, they may not even be the ones organizing the next event (where you are addressing the wrong people.)
You might get frustrated at such a pathetic non-response and end up dismissing open events as a pointless exercise. However, you might benefit by considering that you failed to understand how open events are different from our traditional events.
In short, words are cheap. You improve open events in two key ways: through involvement and sharing your experience as an organizer.
First, you improve open events not by complaining to others (even in nice ways) but rather by taking advantage of the ‘open’ organization of the event and getting involved as an organizer. If ‘breaks should be longer’ attend the organizer meetings to argue for the scheduling policy. If you think there should be more women speakers then lead the ‘speaker wrangling’ effort.
Second, you improve open events by sharing your experience as an organizer in the SkeptiCamp wiki where pages exist to express “What Went Wrong” as well as “What Went Right“. This enables our growing throng of part-time amateur organizers to learn from each other, to develop and refine a set of practices that can be employed by all, including many future first-time organizers.
To speak mere lip-service to openness and collaboration will consign SkeptiCamp to the dustbin, depriving us of its potential to create substantive events anywhere around the world. But to take openness seriously, to organize events with transparency, to put action to one’s ideas, and by using the wiki to learn from our mistakes and build upon our successes, we have a shot at making this work in a big way.








