3. About this presentation - Description of usage during IOD 2009 - Scenario at the event - Lessons Learned
4. Background - 2.500+ Pokens used - Every delegate received one poken - „Session“ Pokens were used to distribute presentation - Pokens were handed out during onsite registration without briefing
5. Positioning - New device to share contacts - Stay connected post event - Optional tool to use
6. Communications - Printed OnSite Guide - Digital Signs - Poken Information Desk - Speakers Briefing (Calls) - Twitter/Newsletter
8. Poken Information Desk / Learned - 20-50 Requests per day - Main Question: „How to setup profile?“ - Second Question: „Problem's with IE6 browser“ - Inquery to get Pokens for other event
11. „ Session Pokens“ - 350+ Sessions had an individual Poken - Attendees were able to connect with session using their Poken
12. Session Pokens / DATA - Code of Session - Title - Landing Page for Download - Segment / Brand / Industry - Speaker
13. Session Pokens / FACTs - PreLoad via WebInterface - Effort: 3 Minutes per Poken - Auto Populated using CoScripter - Formating of special Data File for CoScripter
14. Session Pokens / Learned - Limit amount of Data on Poken Card - Reduce effort of last minute changes - Have arround 10% spare Pokens for sessions - Logistical effort of Poken deployment: low
15. Poken Customization - Hardware is same hardware as „regular Poken“ - Poken „face“ replaced by custom shape - Added „IBM Profiles“ to list of available networks - Poken website has different banner and Poken Cards have fixed background
16. Learned from Feedback - Communicate that device is „ready to use“ - Cards populate with details as soon as people enter them - Connection is not lost even if user is not registered by the time of connection
17. General / Learned - Be aware of what „you poke someone“ means - We expected 50%+ utilization and achived got much more (still counting) - It takes less than 60 seconds to explain what a Poken does :) - Support by vendor is helpful (24 before/after Event start)