01/Capture processes
Document a process in one session, not weeks of interviews.
Start from the conversation, not a blank page.
Capture how work is really done while people describe it, or build a first draft from the SOPs, recordings and old diagrams you already have.
Existing documents
Start from the files and recordings you already have
Point Sapeum at the material that already exists. It becomes a first draft rather than something you ignore.
- Ingest SOPs, procedures and old process maps
- Transcript-to-workflow from recorded calls
Live sessions
Capture the process as your team talks through it
Nobody stops to describe a box. People describe the work, and the steps, owners and decisions appear as they talk.
- Live voice capture, in the room or remote
- Steps, roles, handoffs and decisions extracted automatically
Getting it right
Experts correct the map in the room, not weeks later
The map updates live for every participant, so the people who know fix it in the session rather than reviewing a document a week later.
- Shared live sessions with real-time updates
- Extract undocumented knowledge from interviews
Document a process in a single session
The write-up step disappears entirely.
Much less time asked of your experts
One shorter session, not three rounds.
Knowledge kept before someone leaves
Captured before a resignation makes it urgent.
Related features
All featuresProcesses as data
Process maps you can query, update and reuse, with owners, timing and handoffs held as data.
Process telemetry
Compare live run data against the documented process, and see where the two have drifted apart.
Common questions
Do we need to prepare documentation before a capture session?
No. The point of live capture is to start from the conversation. If you do have SOPs, older maps or recordings, Sapeum can ingest them so the session starts from a draft rather than a blank canvas, but nothing is required up front.
Does this work for remote workshops?
Yes. Sessions are shared and update in real time, so remote participants see the map evolve exactly as people in the room do, and can correct it themselves.
What happens to processes we already mapped in another tool?
Existing process maps, along with SOPs and procedure documents, can be ingested as source material. They become an editable Sapeum workflow rather than a static import you have to redraw.
Who needs to be in the session?
The people who actually do the work, plus whoever is facilitating. That is the whole point of capturing live: the map is corrected by the person who knows, while they are still in the room, rather than by an analyst guessing a week later.
How much preparation does this create for our SMEs?
Less than a traditional engagement, which is the main reason teams adopt it. There is no pre-reading to produce and no write-up to review afterwards, because the session output is already a structured map.