One of those liberating structures that feels well....
You set the stage, invite people in, and then… hope.
Hope that someone brings something interesting.
Hope the energy lifts.
Hope it doesn’t drift into that polite-but-pointless territory where everyone nods and no one really says anything.
Back in May 2025 at the Business Agility Conference, I decided to direct that chaos just a little.
Instead of relying purely on people arriving with fully-formed ideas, I brought a deck of prompt cards.
ELMO (Enough, Let’s Move On) for when a conversation had run its course
WOLF (Working On Latest Fire) to bring in a fresh, real problem
Redraw to ditch a topic and pull a new one
Reverse to flip the perspective and challenge the direction
It didn’t over-engineer the session. It just gave people permission to intervene. That was the shift. Instead of waiting for a facilitator to steer things, the group could steer itself.
One of the comments afterwards stuck with me. Not about the session itself, but about the potential. Someone mentioned it could be used as an icebreaker, or even as a lightweight retrospective tool. Something teams could pick up and use without needing a full workshop wrapped around it.
Then I forgot about it. For a while. Then, recently, I picked it back up again.
It was the friction around turning a physical concept like this into something interactive that stopped me. That would normally mean a fair bit of effort. Design decisions, frontend work, state management, hosting…and lots of my time.
I leveraged AI. I treated the build less like engineering and more like shaping. By feeding in the rules, nudging the structure, breaking things apart when they got too tangled. Keeping an eye on how it felt rather than obsessing over how it was written.
A couple of hours later, there was something real. Something recognisably the thing I had in my head.
Over a few evenings, spending an hour here and there, it turned into a working prototype. Something that looked decent, behaved as expected, and could realistically be used in a session.
There were bumps along the way. Questions around how keys were handled, what should and shouldn’t live in a URL, how to stop things being easily manipulated. The kind of stuff that matters once something moves beyond “just a demo”.
I wasn’t buried in syntax or wrestling with layout quirks for hours. I was making decisions. Breaking things into components. Thinking about how the experience should flow. Adjusting structure so it didn’t collapse under its own weight.
If I’d tried to build this the traditional way, it probably would have dragged out over weeks or months. Not because it’s massively complex, but because all the small decisions stack up. And somewhere along the way, the energy dips and you shelve it or just give up.
It felt closer to getting an idea out of your head before it has time to fade. There’s a broader point in here, that this isn't about tools replacing people. It’s about how experience gets used.
Give this kind of capability to someone without experience, and you’ll likely get something that works… until it doesn’t.
I’ve put the prototype up and made the code available here if you want to explore, or run your own sessions with it.
It’s still evolving. Like most things worth keeping around.
But it started with a simple problem: how do you help a room full of people have better conversations without over-controlling them?
Turns out, sometimes the answer is just a small deck of cards… and a nudge in the right direction.