Going to DevLearn? You'll get about six total hours on the expo floor. And in that time, you have one job: play demos and make all the mistakes you can.
Here's how most of us do DevLearn. We land Tuesday night, open the app, and star every booth that sounds promising. By Wednesday afternoon our feet hurt, the tote bag is heavier than the carry-on, and every demo we've watched went beautifully.
That's the problem. They were supposed to.
On Monday, someone will ask which of those vendors can fix the thing you went to Las Vegas to fix. A beautiful demo can't answer that. The answer is in what happens after a learner gets it wrong: does the conversation remember the mistake, or does everything quietly reset?
You Have About Six Hours. Spend Them Breaking Things
DevLearn 2026 runs November 4–6 at the MGM Grand. The expo hall is open Wednesday and Thursday, close to 15 hours in all, but most of that time overlaps with sessions and lunch. Take those out and you have about six hours on the floor:
- Wednesday: 9:00–10:00 am, 1:30–2:30 pm, 3:30–3:45 pm, and 4:15–6:00 pm
- Thursday: 9:00–10:00 am and 1:45–2:45 pm
(DevLearn says the schedule is subject to change, so check the app before you plan around it.)
Six hours is plenty if you stop judging demos by how well they go and start judging them by how well they go wrong. Your people already get it wrong on the job. The program you buy has to change what happens next.
Full disclosure: Blueline will be on that floor too, at booth 333, where you can play AI-driven simulations of real decision-making dilemmas and get a breakdown of how you did in each of them. So run this test on us first.
Wednesday Morning: Pick a Moment Before You Pick a Booth
The natural move is to scroll the exhibitor list and star whatever looks interesting. The trouble is that every booth then shows you the scenario it chose, and by Thursday you've seen a dozen polished scenarios you can't compare.
So before 9:00 am, write down one moment that's costing your business, and the metric it hits. New managers who put off the first hard performance conversation while first-year turnover climbs. Account managers who go quiet when a renewal stalls. Then search the exhibitor list for the four or five booths that say they can help with that moment, and ask each one to show you the scenario closest to it.
At the Booth: Ask to Drive
Most demos are driven by the person who knows exactly which answers make the product shine. You see the one path where nothing goes wrong. Your people will spend their working lives on all the other paths.
So ask to take the controls, then make the mistakes your people make. Stay vague. Argue before you've asked a single question. Promise something you can't deliver. Then watch three things:
- Does the character react the way the real person would, or does the conversation carry on as if nothing happened?
- Does your mistake follow you into the next part of the conversation, or does everything reset?
- Does the feedback name the decision you got wrong, or just hand you a score?
We've written more about what to watch for when a learner makes the wrong call.
Thursday, 1:45 pm: Go Back to Your Top Two
In the last hour, the floor turns into a giveaway hunt around the prize drawing. Skip the hunt. A giveaway usually costs you a badge scan, and a scan means a follow-up. Back at the office, the decision tends to drift toward whoever follows up most, not whoever handled your moment best.
Spend the hour on your top two instead. Ask each one the same question: if we built this moment with you, what business metric would you measure, and how? Before you leave the expo hall, write a paragraph on each: the moment, what happened when you broke the demo, and what they said they would measure. Those two paragraphs are your Monday meeting.
Why Demos Go Right
None of this is a knock on any one vendor. A booth demo has a few minutes to earn your attention, so it's built to look its best for a few minutes. In that time, looking real is easy. Changing what your people do on the job is not. Your own test, with your own mistakes, shows you what the polished path leaves out. When you get to the full evaluation after DevLearn, start with how to evaluate a simulation vendor.
Skipping that test has a cost, and it shows up quietly. A program chosen because the demo felt good usually gets measured the same way, on completions and satisfaction scores. Both can look fine while the moment you were sent to fix keeps happening. Months later it surfaces as a lost account or a resignation, and nobody connects it back to the purchase.
Try It on Us
Take the account managers who go quiet when a renewal stalls.
Before we build a High-Stakes Performance Simulation for that moment, we use Decision-Consequence Mapping™ (DCM™) to map its key decisions, the common mistake, the move that works, and what each one leads to. That map runs on BluEQ™, Blueline's proprietary behavioral intelligence infrastructure. It carries the DCM™ design into every conversation, so each character remembers what the learner did and responds the way the real person would.
So when a learner goes quiet with the simulated buyer, the buyer gets less friendly and stays that way into the next conversation. The mistake follows them. Afterward, you see each learner's decision path: who made the key decision in time, who didn't, and where.
What we'd measure is simple: how often your people still make the common mistake, checked again at 30, 60, and 90 days to see whether the change lasts, and the business metric that mistake costs. Together, they feed ROLI (Return on Learning Investment).
Your Floor Card
Screenshot this before you fly:
- Wednesday, before 9:00 am: My moment is ______. The metric it hits is ______. My four or five booths are ______.
- At the booth: I drive, and I make the mistakes. Does the character react? Does the mistake follow me? Does the feedback name my decision?
- Thursday, 1:45 pm: Back to my top two. What would you measure, and how? One paragraph each.
See You on the Floor
Bring your moment to booth 333 and try to break our demos. Afterward, you'll get a full breakdown that shows you each decision you made and where it led (for good or ill).
Bringing a colleague? Send them Blueline's DevLearn invite and code MEETUS300, which takes an additional $300 off DevLearn's Last Chance rate (through October 30).
Whether you make it to Las Vegas or not, bring the same moment to a private demo. And if you need to make the case to your manager, the ROLI Blueprint shows how to measure Return on Learning Investment.
You'll come home with a full tote bag either way. Come home with an answer, too.
Source: DevLearn 2026 Conference & Expo, Schedule at a Glance, accessed October 13, 2026.
