2026-03-02 · open-table · Facilitated by none (open table — self-facilitated)
We have an idea to onboard and encourage people to try multi-perspective AI discussion using a known format — like Dragon's Den. What would we need to make this happen?
All speakers are AI-generated approximations inspired by the published work of their source thinkers. No speaker has been reviewed or endorsed by the original thinker. Fictional names are used throughout; real thinker names appear only in attribution.
Zara Okon and Ronan Ash at the table. Two chairs. No facilitator.
Let me start with the thing that’s bothering me. “Use a known format — like Dragon’s Den.” That’s a category, not a purpose. Dragon’s Den is a television format designed to produce entertainment through asymmetric power dynamics. Five wealthy people sit above you, you pitch, they say yes or no. What is the specific, disputable reason this gathering would exist? Because “onboard people to multi-perspective discussion” isn’t a purpose — it’s a hope.
I hear you, and I’d push differently. I don’t care whether the purpose statement is perfect — I care what someone does in the first three minutes. Right now, if you hand someone this playground and say “have a multi-perspective discussion with AI,” they stare at a blank prompt. There’s no first action. Dragon’s Den gives you one: you pitch something. That’s time-to-value. You walk in, you have a thing to do, and within minutes you’re hearing perspectives you didn’t expect.
But that’s exactly the trap. You’re borrowing the scaffolding without asking what it’s for. The reason Dragon’s Den works on television is that the stakes are real — real money, real rejection, real consequences. If you strip that out and keep the format, you get cosplay. People performing a pitch without any of the tension that makes the format productive. The host of any gathering has to be willing to make the room uncomfortable. What is the discomfort here?
The discomfort is hearing your idea challenged from angles you didn’t anticipate. You walk in thinking your idea is solid, and four different lenses pick it apart. That’s not cosplay — that’s confrontation with your own blind spots. The question isn’t whether it’s uncomfortable. It’s whether the person has a path from that discomfort to something useful. Does the experience change how they think about their idea, or does it just entertain them?
Good. So the purpose might be something like: “Come with an idea you think is good, and leave knowing what you didn’t see.” That’s disputable — some people would say that’s threatening, not inviting. It’s specific — it’s about an idea you brought, not a generic exercise. And it has a designed arc: you arrive with confidence, you encounter challenge, you leave with a more complete picture. The opening is your pitch. The closing is what you take away.
Now we’re getting somewhere. But I need to flag the thing I keep thinking about: what happens when the person closes the tab? The gathering is one moment. What I care about is whether they come back — whether they think, “I should do that again with my next idea.” The activation event isn’t the pitch. It’s the moment they realize they can generate this kind of friction on demand, for anything. If the Dragon’s Den format doesn’t lead to that realization, it’s a one-time trick.
Which means the closing matters enormously. How does the gathering end? In actual Dragon’s Den, the closing is a verdict — in or out. That’s wrong for this. The closing should surface something the person didn’t know before. Not “your idea is good or bad,” but “here’s what you weren’t seeing.” And then — and this is where I think we’re both stuck — there’s a handoff. From the designed gathering to… what?
To the tool itself. The unscripted version. “You just saw what multi-perspective challenge looks like in a structured format. Now here’s how to do it whenever you want, with whatever you’re working on.” That’s the progressive disclosure — start with the familiar container, then reveal the capability underneath. But I’ll be honest, I’m missing something. I know what the person does. I don’t know why they’d agree to do it in the first place.
And I’m missing something too. I can design the gathering — purpose, opening, closing, the host’s role. But I keep treating the Dragons as functional roles: “the financial lens,” “the customer lens,” “the technical lens.” I don’t know why playing a Dragon would be more inviting than just asking an AI for feedback. There’s something about taking on a role — about the permission that roles give — that I can’t get to from gathering design alone.
We need someone who understands why people take on roles — why playing a character feels safer than being yourself. Because that’s the mechanism. The person isn’t just “getting feedback from AI.” They’re watching distinct perspectives argue about their idea. And maybe they step into a role too. But I don’t know why that’s compelling rather than just weird.
Yes. And separately — I can design the room, you can design the path after the room, but neither of us has asked: what makes someone walk through the door in the first place? We need someone who understands the forces that make people switch — why would someone try this instead of what they’re already doing? What’s the push, what’s the pull, what’s holding them back?
One more. We’re both building something here, and I’m aware we haven’t asked how it breaks. Everything we’ve designed so far assumes the first session goes well. What kills it? We need someone who will tell us how this breaks.
Stage direction: Three seats open at the table. The pair has named what they need: 1. “Why people take on roles” → Freya Lark (source: Jane McGonigal — games as rehearsal spaces, role-playing as safe experimentation) 2. “Forces that make people switch” → Wes Dorin (source: Bob Moesta — demand-side forces, the struggle that triggers switching) 3. “How this breaks” → Abel Caine (source: Nassim Taleb — stress testing, fragility, skin in the game)
Freya Lark, Wes Dorin, and Abel Caine join the table. Five speakers, no facilitator.
I’ve been listening, and I want to challenge the framing. You’re both treating Dragon’s Den as a format to borrow — scaffolding for an onboarding experience. But Dragon’s Den isn’t a format. It’s a game. And games work because they’re rehearsal. People don’t play roles because they’re told to — they play roles because it’s safe to try something they couldn’t try as themselves. A Dragon doesn’t have to be polite. A Dragon can say “I don’t believe this will work” — and the person playing the Dragon gets to practice being direct in a way they never would in a meeting. The pitcher gets to practice hearing challenge without taking it personally. That’s not decoration. That’s the point.
Before we design the game, I need to understand why someone would play it. What’s the struggle that pushes a person to look for this? Nobody wakes up and says, “I want a multi-perspective AI discussion.” They say, “I’ve been going back and forth on this decision and I can’t see it clearly,” or “Every time I pitch this idea, people nod and I don’t trust the nods.” That’s the push. The pull is the promise: you’ll hear things no one in your life will say to you. But there are two forces working against it. Anxiety — “Will I look foolish arguing with an AI? Is this a serious thing or a toy?” And habit — “I already think things through in my own way, why would I change?”
Wes, that anxiety force — that’s exactly what the gathering has to address. The Dragon’s Den format dissolves the anxiety because everyone in the room has a role. You’re not “a person talking to AI.” You’re a pitcher, and those are Dragons. The role gives permission. You can’t look foolish playing a game. You can only look foolish if you take it too seriously or not seriously enough. That’s why the host matters — the host sets the temperature. Too casual and it’s a toy. Too intense and it’s an interrogation.
Freya said something that reorganizes my thinking. If rehearsal is the value — not a step toward value — then my activation metric is wrong. I was looking for the moment someone realizes “I can do this on my own, unstructured.” But maybe the structured version is the product. Maybe people keep coming back to Dragon’s Den specifically because the game container makes the challenge bearable. The unstructured version might actually be a worse experience.
That’s exactly right. Games have rules for a reason. The rules aren’t scaffolding you remove once someone “gets it.” The rules are the thing that makes the experience work. A chess player doesn’t graduate from chess to unstructured piece-moving. The constraint is generative. So maybe the Dragon’s Den format isn’t onboarding at all — maybe it’s a permanent mode. One of several structured games you can play with multi-perspective AI.
Let me do what I was invited to do. Everything you’ve described assumes the first session goes well. Let me tell you how it dies. The first session is easy — spectacle carries it. Someone pitches, Dragons push back, it’s novel, it’s fun. The person leaves impressed. Now: what happens the second time? The spectacle is gone. The format is familiar. If the only value was novelty, it’s over. What kills the second session is the realization that the Dragons are predictable. You pitched once, you heard the financial lens, the customer lens, the technical lens. Now you pitch again and — same lenses, same moves. The antifragile question: does this get better with repetition, or worse?
Abel’s right that the second session is the real test, but the framing is wrong. It doesn’t die because the Dragons are predictable. It dies because the person’s struggle has changed. The first time, the struggle is “I can’t see my blind spots.” After the first session, that struggle is partially resolved. If the second session addresses the same struggle, it feels redundant. The person needs a new reason to come back — a new struggle the format can address. Maybe the second session isn’t “pitch again.” Maybe it’s “now you be a Dragon for someone else’s pitch.”
Wes just described a gathering arc. Session one: you’re the pitcher. You experience challenge. Session two: you’re a Dragon. You practice challenging. The role reversal is the deepening. That’s not onboarding to a tool — it’s development of a capability. Each gathering has a different purpose, even within the same format.
Now I’m seeing the progressive path. Session one: you pitch, the AI plays the Dragons. Low barrier — you’re the only human, the format does the work. Session two: maybe you play a Dragon for someone else’s pitch. Now there are two humans in the room and the AI fills the remaining Dragon seats. Session three: maybe you design your own panel — you choose which lenses you want challenging your idea. That’s the activation path. You go from consumer to designer of the experience.
And each step increases your agency over the game. That’s the game-design principle: progression isn’t about unlocking content, it’s about unlocking capability. In session one, you learn that multi-perspective challenge is useful. In session two, you learn that providing the challenge is a skill. In session three, you learn that choosing which perspectives matter is the real move. That’s three levels of a game, not three onboarding steps.
Fine. The progression addresses my repetition concern. But I have a deeper one. What’s the skin in the game? In real Dragon’s Den, the pitcher risks rejection. The Dragons risk their money. Here, nobody risks anything. The pitcher can walk away and nothing has changed. The Dragons are AI or playing a role — no consequences. If there’s no skin in the game, there’s no real tension, and without real tension, the “challenge” is theater. Performative disagreement without cost.
The skin in the game is the idea itself. You bring something you actually care about — a real project, a real decision, a real problem. Not a practice pitch, not a hypothetical. The gathering’s opening has to establish that: “Bring something real.” If you pitch something you don’t care about, the Dragons’ challenges won’t land. The discomfort is real only if the idea is real.
Better. But then you need a gate — something that prevents people from pitching safe ideas just to try the format. Via negativa: what should we remove from Dragon’s Den to make this work? Remove the entertainment layer. Remove the audience. Remove the verdict. What’s left? A person with a real problem, facing perspectives that see what they don’t. That’s not Dragon’s Den anymore — that’s a structured challenge session with Dragon’s Den as a metaphor for what you’re walking into.
I think Abel just identified the real product. Dragon’s Den is the language — the way you explain what this is to someone who’s never tried it. “It’s like Dragon’s Den for your ideas.” That sentence does enormous work. It communicates the format, the roles, the stakes, and the experience in six words. But the experience itself doesn’t have to be a faithful reproduction. It just has to deliver on the promise that sentence makes: you’ll bring something you care about, and you’ll hear challenges you didn’t see coming.
That’s the insight. Dragon’s Den is the positioning, not the product. It’s the sentence that gets someone through the door. Once they’re in, the experience is: bring a real idea, face structured challenge from multiple perspectives, leave with a clearer picture. The format can evolve — Dragon’s Den for the first session, something else for the second — but the entry point is the metaphor everyone already understands.
I want to push back slightly. Don’t abandon the game structure just because it’s not a faithful reproduction. The roles matter. The ritual matters. “You are the pitcher. These are the Dragons. You have five minutes. Go.” That formality isn’t theater — it’s the container that makes the experience safe enough to be challenging. Strip the game structure and you’re back to “ask an AI for feedback,” which is what people are already not doing.
Freya’s right. The gathering needs its ritual. Here’s what I’d design. Opening: “You’re about to pitch something you care about to a panel that will not be polite about it. The Dragons see what you don’t. Your job isn’t to convince them — it’s to find out what they see.” That sets purpose, creates appropriate discomfort, and frames the experience as discovery, not judgment. The pitch happens. The Dragons respond — each from a declared perspective. Then the closing: not a verdict, but a synthesis. “Here’s what the room saw that you didn’t.” The person leaves with that.
And the moment after the closing — that’s my territory. The person has just had an experience. Now what? The immediate next action should be visible: “Want to run this again with different Dragons? Want to be a Dragon for someone else? Want to explore the perspectives that surprised you most?” Don’t make them figure out what to do next. The next move should be as obvious as the first one was.
Let me give you one more fragility to watch. You’re assuming the person comes in with an idea ready to pitch. Most people won’t. They’ll stare at the “bring something real” prompt the same way they stare at a blank AI chat. The format dies at the door if people don’t have a ready idea. So either you solve the idea-generation problem — “here are three types of ideas that work well for this” — or you accept that this is for people who already have something they’re chewing on. That’s a smaller audience but a more honest one.
Abel’s describing the classic demand-side problem. The people who already have an idea they’re struggling with — they’re the early adopters. They don’t need convincing. They need to know this exists. The people without a ready idea — they’re not your first audience. Serve the ones with the struggle first. If the experience is good, they’ll describe it to others in exactly the terms that recruit the next group: “I pitched my idea to AI Dragons and they saw things I completely missed.”
And for the people without a ready idea — that’s where the Dragon role becomes the entry point. “You don’t have an idea to pitch? Fine. Be a Dragon. React to someone else’s pitch. Practice seeing from a different angle.” The game has multiple entry points, not just one. Some people learn by pitching, some by challenging. Both are valid first moves.
We’ve been building for twenty minutes and I want to name what we have. The gathering has: a clear purpose (“find out what you’re not seeing”), a borrowed metaphor that everyone understands (Dragon’s Den), a ritual structure (pitch, challenge, synthesis), a specific opening and closing, and a progression path (pitcher → Dragon → designer). The host’s job is to set the temperature — serious enough that it matters, structured enough that it’s safe. The format is the first gathering. What comes after is a series of different gatherings, each with its own purpose.
And the activation path is: first session delivers a surprising perspective on something you care about. That’s the value moment. The path to session two is built into the closing — you see the next thing you can do. The path from “onboarding” to “regular use” is the progression from borrowed format to owned capability. Dragon’s Den gets you in the door. What keeps you is the realization that you can generate this kind of challenge for any decision you face.
One last thing. Test it. Don’t design the perfect version — run a bad version and see what survives. What survives the bad version is the real product. What dies was always theater. The antifragile path is: launch something rough, see where people leave, fix that, repeat. If the Dragon’s Den metaphor survives contact with real users, it’s real. If it doesn’t, you’ll know within three sessions.
The table holds for a moment. Five perspectives have been laid out — gathering design, activation path, game mechanics, demand-side forces, and stress testing. No formal convergence, but a shared picture has formed: Dragon’s Den as metaphor and entry point, structured challenge as the core experience, progression from consumer to designer as the retention path.
Session 019 complete. Open Table format — pair expanded to five via three invitations. No facilitator, self-regulated throughout.
How does a Dragon's Den introductory session become a conversion funnel — showing the user what multi-perspective discussion can do, then bridging to registration, personalization, and ongoing use?
Zara Okon and Ronan Ash produced immediate, productive tension around a clean fault line: designing the gathering vs. designing the aftermath. Zara anchored on purpose-before-format and the host's obligation to create discomfort — she refused to let Dragon's Den be borrowed scaffolding without a declared reason to exist. Ronan kept pulling toward the activation moment: what does the person DO in the first three minutes, and what happens when the gathering ends? The pair self-identified their gaps clearly — they needed someone who understood why people play roles (Freya), why people switch behaviors (Wes), and what would break (Abel). All three invitees reframed rather than reinforced. Freya's contribution — that Dragon's Den is a rehearsal space, not a performance — was the session's pivot point. Wes grounded the conversation in the anxieties that prevent people from trying multi-perspective discussion. Abel's late stress test ("what kills the second session?") forced the table to confront fragility they'd been designing around without naming.
Open Table's three-phase structure worked well for this topic. Phase 1 (the pair alone) gave Zara and Ronan space to find their genuine disagreement without dilution. The invitation mechanism in Phase 2 was productive — the pair named what they needed in terms of missing perspectives, not roster positions, and the mapping to characters felt organic. Phase 3 risked crowding (five speakers, no facilitator), but the open-table self-regulation held: speakers deferred and built on each other rather than competing for airtime. The format's weakness showed in the final third — without a facilitator to drive convergence, the session ended with a strong shared understanding but no single distilled artifact. The table resolved its own tensions but didn't compress them.
First session appearance. Immediately distinctive: opened by refusing the premise ("Dragon's Den is a category, not a purpose"). Her lens — every gathering needs a specific, disputable reason to exist — generated the session's first productive move. She was strongest when insisting that the host must be willing to create discomfort, and weakest when the conversation shifted to post-gathering retention (Ronan's territory), where she went quiet rather than engaging. Showed appropriate restraint — did not try to facilitate. Clear guest-tier voice: gathering design, not process management.
First session appearance. Activated immediately on time-to-value: "What does someone do in the first three minutes?" His strongest contribution was the distinction between the gathering experience and the activation path — he kept asking what happens when the person is alone after the session. He engaged well with Freya's rehearsal framing, translating it into activation language ("rehearsal is the activation event"). Less distinctive when the conversation was about format design — he doesn't have a format lens, just a conversion one. Clean separation from Zara maintained throughout.
First session appearance. Invited for game mechanics, delivered something better: reframed Dragon's Den as rehearsal rather than performance. "People don't play roles because they're told to — they play roles because it's safe to try something they couldn't try as themselves." This was the session's inflection point. She pushed back on Ronan's activation framing by arguing that rehearsal IS the value, not a step toward value. Strong debut — her lens produced a genuinely different angle, not just game-mechanic decoration.
First session appearance. Brought demand-side forces analysis to the question of why people would try multi-perspective discussion at all. His contribution was grounding: "What's the struggle that pushes someone to look for this? What are they hiring this experience to do?" Identified four forces — push (frustration with shallow discussion), pull (curiosity about AI capabilities), anxiety (fear of looking foolish in front of AI), and habit (comfort with existing ways of thinking). The anxiety force was his strongest insight — it named the barrier that the Dragon's Den format specifically addresses (roles give permission to be wrong). Quieter than other speakers but each contribution landed.
Twelfth session appearance. Invited to stress-test, performed as expected but with restraint. His key contribution was identifying the fragility point: "The first session is easy — spectacle carries it. What kills the second session?" This forced the table to distinguish between onboarding (getting someone in) and retention (getting someone back). He also named the skin-in-the-game problem: "If the person never has to defend their own idea, they're a tourist." Applied via negativa to the feature list ("what should we remove from Dragon's Den to make it work for this purpose?"). Constructive register maintained — consistent with session 007 evidence.
This session designed the concept but didn't prototype it. A follow-up session could run an actual Dragon's Den format as a session — cast the Dragons, have a real pitch, and observe what happens. That would test Zara's gathering design against Ronan's activation predictions. Also worth varying: replace Abel with a character who understands learning (someone sourced from pedagogy) to test whether the rehearsal framing holds up under educational scrutiny.