Immersion dashboard
The memory of a three-day immersion became a navigable interface: decisions, schedule and references, with an embedded guide that answers questions about the content itself.
Where it came from
We came out of a three-day immersion with dozens of hours of transcripts and decisions scattered across team chat, documents and memory. A week later it was already hard to answer why something had been decided that way.
All the information existed. What was missing was any way back into it.
On the bench
Instead of writing a report, we built an interface. Each kind of content became a data-driven view: schedule, decisions, graveyard of ideas, external references.
The guide was embedded inside the dashboard itself, reading the same archive the person is browsing, so asking what was decided about a topic became possible without hunting. The archive lives in versioned text files, and the guide's brain is assembled from them by a script, which keeps a single source.
Where it fits
It fits any process that produces a lot of conversation and little memory: immersions, training, consulting, strategic planning.
We replicated the format at VIEX and it worked as a learning copilot, keeping the training alive between sessions. In healthcare, the same design turns an accreditation standard into a trail that guides the team, instead of a manual nobody opens.
What we learned
The dashboard travels better than the document. The same information, laid out as a navigable interface, still gets consulted months later; laid out as a report, it is read once and filed away.
Still open
We still have not solved who feeds the dashboard once the event is over. As long as the archive depends on someone remembering to update it, it ages, and an outdated dashboard misleads more than an old document.