PROJECT EXCLAMATION / ORGANIZATIONAL PERCEPTION
The factory records the event.
It loses the explanation.
Project Exclamation asks how physical-world organizations could preserve the hard-won knowledge exchanged face to face.
THE PROBLEM
Important knowledge vanishes in plain sight.
A machine alarms. An experienced operator spots the pattern. Two people talk through the fix and get production moving again. The system records the alarm and the work order, but not the reasoning that made the difference.
That gap creates repeated problems, thin handoffs, and expertise that leaves with the person who carries it.
THE IDEA
The system notices.
The people decide.
- Detect a possible knowledge moment.Weak signals such as proximity, conversation, and an operational event combine to suggest attention.
- Ask before capturing.A visible interaction gives participants the choice to capture, pause, reject, or correct.
- Connect the context.The episode links people, place, asset, work, time, evidence, and outcome.
- Promote learning carefully.Reviewed claims can become reusable procedures or guidance while provenance and access stay attached.
WHY IT MATTERS
A memory layer for work that happens away from a screen.
The manufacturing floor is a useful first lens because the gap is easy to see: operational systems know what happened, but often miss why. The broader idea applies anywhere valuable work is physical, contextual, and shared between people.
Exclamation is not a surveillance pitch. Its central design question is whether an organization can learn from real work while keeping participation visible, governed, and human controlled.
Talk about the idea →