Operational Coordination
Someone currently holds the thread in their head
They remember what happened, who is next and what was decided. When they are away, the work waits. Eddy keeps that context attached as responsibility changes hands.
Coordination is invisible labour until something breaks
Someone chases the next person. Someone translates the background for each new arrival. Someone answers every status question because the process has no place to live except their inbox.
That work is real. It does not show up as a task. It shows up as delay, rework and a Friday message that starts with "just circling back".
One packet of context, handed on
The next person should see what happened, what was decided and what comes next — without a briefing call.
A Map holds the stages and the Map Roles. Each Session carries the submissions, the decision and the timing forward. The thread stays with the work.
One visible process, then the same pattern elsewhere
The University of Gothenburg ran The Work Environment Week as one Map. After the week, Luciano began mapping onboarding, purchasing, compliance reporting, survey intake and other administrative work that had lived in email and spreadsheets.
That is not a general operating model. It is one institution recognizing the same coordination problem in more than one place.
86.4%
post-pilot satisfaction score
10+
maps now active or in development
Since the pilot, I have been creating many more processes. I see huge potential in this tool and am actively looking for processes where Eddy can improve our administrative life.
Bring the process that is harder than it should be
Start with the handover everyone already knows. Lay out who acts, in what order and what must travel with the work.