Collaborative investigation and organizational knowledge: the lesson behind Knowledge Files

The problem almost nobody trains for: reconstructing what actually happened

When a project goes wrong at a company, the complete explanation almost never lives inside a single person's head. Sales knows what was promised to the client. Tech knows what could actually be delivered. Legal knows which clause never got reviewed. Each department holds one true piece of the puzzle, and the most common organizational failure is that those pieces never get put together: each team tells its own isolated version, and the real root cause stays buried between departments that don't talk to each other.

Reconstructing that full story — cross-referencing information from different departments until you find the real causal chain — is a skill that can be trained. It's called collaborative investigation, and it's the heart of Knowledge Files.

The mechanic: private evidence, shared board

In Knowledge Files, each department of a fictional company (Sales, Tech, Operations, Legal, Finance) receives private documents: emails, tickets, memos, invoices. At first, nobody sees another department's documents. The game's first move is simple but decisive: each person has to decide what to share, and with whom, pinning their evidence to a shared board.

From there, the team connects evidence from different departments — connecting two documents from the same department is never enough — and decides how they relate: do they contradict each other? Does one explain the other? Do they confirm one another? Only when the relationship is correct does a verified fact appear. With enough facts, the team builds a timeline and puts together a root-cause report.

It's, quite literally, the job of an analyst reconstructing what happened in a real incident — just compressed into 45 minutes, with nobody actually at risk.

Why this is different from just "sharing information"

A meeting where every department "shares their side" isn't collaborative investigation — it's a string of monologues. What makes the Knowledge Files mechanic valuable is that connecting evidence across departments is mandatory to make progress. It's not enough for everyone to talk; someone has to actively look for the overlap between what Sales said and what Legal said, and propose a hypothesis about how they relate.

That trains a specific muscle: active curiosity about what another department knows, instead of the very human habit of staying comfortable inside what you already know.

Mistakes as part of the learning

In Knowledge Files, connecting two pieces of evidence that don't actually relate, or getting the timeline wrong, doesn't end the game — it gets logged as part of the session's observable facts. That's key for the debrief afterward. The goal isn't "who figured it out fastest" — it's identifying the moment the team had a clue and didn't connect it, or treated a hypothesis as confirmed without a second piece of evidence to back it up. Those are exactly the same mistakes that lead to bad decisions in real investigations, and watching them happen in a safe context is far more effective than reading them off a list of "best practices."

What this dynamic actually measures in a team

After facilitating dozens of sessions, we've noticed Knowledge Files exposes three team behaviors pretty clearly:

• Who shares information without being asked. Some people wait to be specifically asked; others offer up their evidence the moment they see it might be relevant.
• Who confirms before acting. The team that builds a hypothesis and validates it against a second source before moving forward usually solves the case faster than the one that runs with the first explanation that "sounds right."
• How disagreement gets handled. When two pieces of evidence seem to contradict each other, some teams argue it out until they understand why; others ignore the contradiction and push ahead. The latter almost always leads to a wrong conclusion, both in the game and in real life.

When this specific game is worth using

Knowledge Files performs especially well for:

• Teams where different departments work together but rarely cross-reference information in depth (Product and Support, or Sales and Legal, for example).
• Organizations building or revisiting cross-department communication processes.
• Onboarding sessions where it helps to show, experientially, how the real company's departments connect. If that angle interests you, we cover it in our note on onboarding with cooperative games.

With teams of 4 to 20 people split into up to 4 groups, each team solves its own case in parallel, so it works just as well for a small team as for training an entire department.

What to ask in the debrief

After a Knowledge Files session, instead of asking a generic "how did it go?", it's far more productive to anchor the conversation in concrete facts from the round: "at what point did you have a piece of evidence that turned out to be key, and took a while to connect it to another?" or "was there a hypothesis you treated as confirmed without checking it against a second source?" These questions carry the game's collaborative-investigation logic straight into a reflection on how the team handles information in its real work, with no need to force the comparison.

How to get started

You can set up your first session from the platform, picking Knowledge Files from the six cooperative games available. If you'd rather understand the mechanic before inviting your team, you can also try it solo against bots — teammates who play by the same rules and with the same level of information a real person would have.