Can we fix trade shows? Our veteran showman suggests some open source solutions.
Put together the badges I've worn at trade shows, and you'd have enough to tile a wall. I've played about every role you can play at a show: panelist, attendee, exhibitor, keynote speaker, organizer, booth builder, reporter and promoter. And I've been at it since the Dawn of Disco.
What amazes me, after all these years, is how technologies have gone through one revolution after another, while the their trade shows have hardly changed at all. Take a time machine back to Comdex in 1984 and, aside from wireless graces like cell phones and wi-fi, it will look pretty much like the one we'll see this Fall.
One reason is that trade shows are markets in the ancient and literal sense of the word. They are the industrial equivalents of the tents and stalls that gathered at crossroads and village plazas back when trade began, long before the birth of currency and the study of economics. For the industrial categories we call "markets", trade shows provide a literal marketplace where buyers, sellers and experts on specialties can gather to meet, do business and advance agreements about what makes their category worthwhile. For a few days every year the virtual market becomes a real one.
Today the term "market" applies to every category and subcategory, to specialties within specialties. Some trade shows broadly support whole industrial pies, while others serve various slices. The largest trade show in the world, Cebit in Germany, covers information technology and telecommunications. I've never been to Cebit, but I have been to Comdex -- its domestic equivalent -- a dozen times or more. Mostly, however, I attend niche shows. In the last few years, in addition to Linux shows, I've attended (and often spoken at) shows about identity management, open source, emerging technologies, computing and communications platforms, Macintosh and OS X, Jabber, BSD, Apache, embedded technology, interactivity, new products and technologies, computer product distribution, blogging, peer-to-peer, activist politics, privacy and security, technology impact on people, customer service, government technology and electronic commerce -- to name just the shows I can remember without looking at old calendars.
While the subjects of these conferences varied widely, and while they were variously called conferences, conventions, shows, events, expos, workshops and "-cons" of various sorts, they generally held to long-established trade show conventions. Let's look at those.
First, trade shows gather five types of people:
Shows make money from Exhibitors and attendees. Exhibitors spend many thousands of dollars for booth space, while attendees spend either a small sum to visit exhibitors or a larger sum to attend keynotes and breakout sessions.
Many trade show formalities are highly defaulted by their venues as well. Hotels and convention centers exist in large measure to serve trade shows. Doing that requires highly formalized architectures and ritualized procedures. Flexible meeting space, for example, is achieved by partitioning larger rooms into smaller ones. Speakers are expected to stand behind podiums, and panels to sit behind tables on stages at the fronts of rooms. Projectors are provided for presentations or video enlargements of the speakers and panelists.
These architectural and procedural defaults make two assumptions:
Yet, thanks to the Net, markets today are more connected than ever, and less hierarchical. ("Hyperlinks subvert hierarchy", David Weinberger says.) Customers, along with everybody else, are educating themselves, and each other, directly. More market participants are in positions to teach as well as learn. Large corporate players are no longer the primary sources of wisdom about the markets they lead. Every market's wisdom today is highly distributed, and able to distribute itself any way it pleases: emails, personal publications on line, wikis, IM, IRC and other forms of "social" computing -- as well as through ad hoc meetings in meat space.
So it's no surprise to hear that attrition is a problem in the trade show business, and that the networked marketplace is part of it. Meetings & Conventions, in its January issue, said
The instances of attendees circumventing traditional registration to book through online third-party providers has avalanched, leaving planners increasingly frustrated and making attrition a major issue for associations.
In 2004, a number of hotels will team up with planners to fight the problem on a united front. "Hotel companies traditionally have stayed on the sidelines and said, 'We are protected by a contract. It's the customer's problem,'" says Joel Pyser, vice president of field sales for Bethesda, Md.-based Marriott International Inc. "Well, we can't afford to do that any longer. No one enjoys presenting a customer with an attrition bill. We have to partner with them to solve it."
Note that the customer in this case is the company that puts on the trade show. Not the hotel guest who attends the trade show. That individual is still a "consumer":
Web surfing for the lowest rate has become a consumer sport. It also is a major thorn for planners managing room blocks. The Alexandria, Va.-based International Society of Hospitality Consultants estimates online bookings accounted for 30 to 40 percent of all reservations booked within a four-week arrival window in 2003 -- up 20 percent over pre-9/11 numbers.
Of course, this top-down perspective will remain ingrained to the degree that the bulk of income flows from large corporate customers. Still, it seems to me, that this whole industry could benefit from the same open source value system and development methods that caused the growth of Linux and the Net.
In that spirit I'd like to share the best of what I've learned from the best of the trade shows I've attended over the last few years. Here goes.
Hold collegial meetings, not sessions. Some of the best sessions at conferences are the BoFs, or birds-of-a-feather sessions after hours. O'Reilly does an excellent job of at least aspiring to this format, even in its standard sessions.
Insist on long Q&A periods after lectures, with lots of working microphones to pass around the audience.
Record all sessions, and make them available in open audio formats on line. This will also help sell attendees on coming to the next conference.
Use conversation-friendly venues. Pop!Tech is held in an old opera house in downtown Camden, Maine. The feeling of the whole place is very cozy and comfortable, and somehow it helps make the audience more involved with each talk.
Try forbidding vendor pitches. The first BloggerCon wasn't a vendor venue. It was held at Harvard, in lecture rooms. But vendor pitches were still discouraged, and it helped open conversation to topics that transcended market economics.
Make the Web a living and permanent resource and document archive. Here nobody beats O'Reilly's system, which not only includes the company's own writers, but pointage to writing done by outsiders covering or attending the event.
Provide wireless net connections. It was at Esther Dyson's PC Forum that I first witnessed a complete power shift from stage to audience, thanks to Net-connected wi-fi. That was three years ago. Since then many other events have added wi-fi, but the practice is far from standard. It should be.
Start topical conversations in advance of the show. Jerry Michalski pioneered this when he was involved in PC Forum, many years ago. Today his retreats are meetings for a persistent community that stays in touch by email, wiki and other methods. Countless constructive new conversations have been started and sustained by these off-conference methods.
Hold hack-a-thons. Your event's name doesn't need to end in "hack" for hack-a-thons to work. ApacheCon launches itself with a hack-a-thon that's not to be missed, even if you're not a hacker. It begins the event with a sense that stuff can be done.
If you have any other ideas, send them here, or to your friendly conference planner. If we do this thing right, we might just revolutionize another industry.
Doc Searls is Senior Editor of Linux Journal. His monthly column is Linux For Suits, and his bi-weekly newsletter is SuitWatch.