Skip to main content

Trade Shows: Of What Value Are They?

The esteemed Steve Johnson recently wrote a provocative blog entry on the merits - or lack thereof - of demoing at trade shows. He implies that showing demos is usually not very effective:
Nobody retains information from a trade show--everyone is yelling to be heard. Perhaps you could be a little quieter and much more effective. Let's use the demo where it belongs, much later in the sales cycle.
And he contends that collecting information about prospects' situations and problems is often a better use of trade show time:
At your next event, try just asking people who come by the booth a few simple qualifying questions about their problem and its urgency to them. If they answer in the affirmative, scan their badge or take their card and invite them to enjoy the show. Meanwhile send a set of materials to them through the mail or better yet, have a sales person contact them the week after the show.
In my opinion, Steve's key point is that:
The best demo is customized to the customers, their problems, and within the context of how we can specifically solve their problems.
If you've read SPIN Selling, you know that your best chance of making a high-value sale is to use a facilitative process that starts with asking a lot of questions. Only after you've fully understand the individual prospect's situation and problems do you describe your solution in detail.

Regarding trade shows, however, the more important questions to me are:
  1. Why are you an exhibitor at the trade show at all?
  2. Who is attending the trade show, and why?
What goals are you trying to achieve as an exhibitor at the trade show? If you're trying to sell product, then Steve's advice is important to keep in mind. But maybe you're trying to affect media coverage? Or maybe you're trying to gather intelligence on the attendees and competition? I wonder, though: perhaps you can achieve this latter goal just as effectively without being an exhibitor (and just being an attendee)?

It matters who is attending the trade show. Is media attending the trade show? Are tech geeks with little or no buying authority attending the show? Are actual prospects attending the show? Perhaps you should attempt to segment the population of the trade show into various personas.

The bottom line is that the issue isn't as simple as whether you should demo at trade shows. You need to research the expected trade show population and shape your goals accordingly. In the end, you may decide that being an exhibitor isn't the best way of achieving those goals.

Comments

Paul Young said…
Roger, one thing that everyone who posted on this topic quickly zoomed in on was the higher level question of "do we need to be here at all?" Unfortunately we can't always affect that since checkbox marketing has run amok.

There is also a perception issue if you've attended in the past and then pull out, I've seen attendees who actually badmouth a company for pulling out saying that they're probably about to go out of business or they're offended because they see the lack of attendance as a signal that the company doesn't believe that seeing the attendee is worthwhile.

Once you either choose to be at the show or accept that you must, the to demo or not to demo question should be fairly easy to answer based on your knowledge of the audience, product complexity, and ability of the people in the booth. I shudder at the thought of booth babes trying to demo my product :)
Wed Aug 29, 11:33:00 PM 2007
Post a Comment

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos
32 comments
Read more

What Product Managers Can Learn from the Apple iPod

The Story When Apple unveiled its iPod digital music player back in October 2001, I dismissed it as a  parity product . I already owned the Cowon iAUDIO CW100 MP3 player, loaded with my favorite tunes. There was Apple, generating great hype over the iPod as if it were a breakthrough product. The idea of a portable digital music player was nothing new. The first mass-produced MP3 players came out in 1998. In late 2001, the concept may have been new to a lot of Apple customers, but it wasn't new to me. I proudly showed my MP3 player to friends when they gushed about the iPod. Thus Apple's iPod was not an innovative product in and of itself. Years later, however, I realized the significance of ecosystem of which the iPod was a part. Apple had released iTunes (with technology purchased from  SoundJam MP ) and created the iTunes Store for finding and downloading music. Unlike Napster , it was a safe and legal way of distributing and acquiring music. The prior way of playing
2 comments
Read more

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardw
8 comments
Read more