Experiment Library

Most teams use AI in private. The wins stay private, the misfires definitely stay private, and nobody builds a shared picture of what AI actually does and doesn't do well. Over time that means the team's collective judgment about AI never develops. This experiment makes those interactions visible, without it becoming a debrief or a debate. Try it when AI use is common but unspoken, or when you sense people are either over-trusting or quietly embarrassed by how they use it.

When AI joins a brainstorm from the start, it sets the frame. People riff on what it suggests rather than where their own thinking goes. Try it when you suspect AI is quietly narrowing the range of ideas rather than expanding it.

Most teams never decided to record their meetings. It just became the default. AI meeting assistants and auto-transcription made it frictionless, so nobody questioned it. But knowing a conversation is being recorded changes it, subtly and reliably. People hedge. They perform. The real conversation happens after the call ends. Try it when you notice people are careful rather than candid, or when sensitive conversations feel like they're being managed rather than had.

Fika is a Swedish workplace ritual: a proper break, mid-morning or afternoon, for coffee and a chat with no agenda. Not a meeting. Not a check-in. Just people being people for 15 minutes. In remote and hybrid teams, that kind of unstructured contact has mostly disappeared, replaced by scheduled calls that always have a point. This experiment brings the ritual back, in whatever form works for your team. Try it when the team feels productive but a bit flat, or when most of your contact has an agenda attached.

Most of us use AI alone, prompting from our own mental model and never seeing how colleagues approach it differently. Building a prompt together makes that thinking visible, and starts to shift AI from a solo habit into something the team shares. Try it when the team is using AI a lot but separately.

Teams adopt AI tool by tool, person by person, with no shared conversation about what feels right. Those differences quietly create tension and misalignment. Writing an agreement together surfaces that, and gives the team a shared language for it. Try it when the team has been using AI for a while but never talked openly about how, or when you sense unspoken friction around AI use.

When AI does the work and you just take the output, you get the answer but miss the learning. Over time that compounds quietly: AI gets more capable, your own skills plateau or drift. This experiment is about prompting differently, adding a question that forces understanding alongside the output. Try it when you notice you're using AI a lot but couldn't fully explain the work it helped you with.