What to actually do at a wireless conference

Wireless conferences fall into three categories, and knowing which one you are attending changes how you should spend your time.

Vendor conferences — a manufacturer's own event. Excellent for roadmap detail and direct access to product managers, useless for comparison.

Trade shows — large exhibition floors. Good for seeing hardware in person and a compressed round of supplier meetings. Poor for learning anything technical.

Independent technical conferences — smaller, community-run, sessions run by practitioners. This is where the actual knowledge transfer happens.

Before you go

Pick three questions. Not topics — questions. "How are people handling MAC randomisation with MAB?" is a question. "IoT security" is a topic, and topics produce brochures.

Book vendor meetings in advance, and make them technical. Ask for a systems engineer, not an account manager. Send your questions ahead.

Check who is speaking, not what the session is called. Session titles are written by marketing departments.

While you are there

Go to the sessions where the speaker admits something failed. A talk titled "Our 6 GHz rollout and what we got wrong" contains more transferable knowledge than any number of success stories.

Ask vendors what their product is bad at. The answer tells you the actual limitation and whether the person in front of you is worth talking to further.

Spend real time in the hands-on labs. Twenty minutes with a spectrum analyser you have never used beats four keynotes.

Talk to other customers, not vendors. The most useful conversation at any conference is with somebody who deployed the thing you are evaluating, eighteen months ago, at similar scale. Find them in the coffee queue.

After

Write it up within 48 hours — one page, three headings: what I learned, what I need to test, who I need to follow up with. This is also how you justify the trip next year.

Book the follow-ups immediately. Conference goodwill has a half-life of about a fortnight.

Which ones are worth it depends on your role and region, and it changes year to year — which is why we keep a running calendar rather than publishing a static list.