Most teams already have some form of process documentation. It lives in Visio files on a SharePoint drive, in a Lucidchart folder nobody has opened in two years, or in draw.io diagrams scattered across Confluence. The problem is rarely that there is no documentation. The problem is that the documentation cannot be compared, reused, or trusted.
This post walks through how to do process mapping in Crismo end to end. For the neutral methodology first (what process modeling is, which notation fits which situation), start with the Process Modeling Guide on ProcessCamp.
Step 1: Start with a Workspace
In Crismo, every process landscape lives inside a workspace. A workspace represents an organization, a business unit, or a scope of work. The workspace gives you shared context and structure: your processes sit inside a value chain, not in a folder tree.
Step 2: Import What You Already Have
Process mapping rarely starts from scratch. Crismo imports from:
- BPMN XML files - any tool that exports standards-compliant BPMN 2.0
- Visio diagrams - via a free converter
- Lucidchart exports - via a converter
- draw.io diagrams - via a converter
Import does not mean perfect translation. Visio and Lucidchart diagrams are often informal flowcharts. The converter produces a best-effort BPMN model that surfaces the ambiguity so you can fix it.
Step 3: Model in BPMN with Workspace Context
Crismo produces valid BPMN 2.0. What makes this different from a generic BPMN editor is the context around the diagram: the process lives in a value chain, elements reference entries from a shared dictionary, the document has an owner, a status, and history.
For a first process map, focus on the happy path: start event, main activities, decisions, end event. Add exceptions in a second pass.
Step 4: Reuse Definitions Across Processes
Process maps accumulate. The same terms appear across all of them: "Customer", "Order", "Fulfillment Team". In most tools these are ad-hoc labels. A rename in one diagram does not propagate.
Crismo includes a workspace dictionary. When an element references a dictionary entry, renaming that entry updates every diagram it appears in.
Step 5: Place Processes in a Value Chain
Individual processes make more sense when they sit in a landscape. Crismo's value chain view lets you lay out L0 segments ("Order to Cash", "Hire to Retire") and assign each process to a segment.
Step 6: Share for Review
Three sharing modes: view-only links, comment access, full collaboration. A process map nobody reviews is a process map that does not get used.
Step 7: Govern and Iterate
Process maps go stale. Every diagram has an owner, a last-updated timestamp, and a version history. Set a review cadence per process; when a diagram crosses its review date, the owner gets a reminder.
When Crismo Is the Right Fit
Fits well when you are mapping more than a handful of processes, multiple people collaborate on the same models, your processes will feed automation or audit evidence, or you want to consolidate Visio, Lucidchart, and draw.io documentation into one place.
Not the right fit for sketching a single diagram for next Tuesday's meeting (draw.io is faster) or replacing enterprise platforms like ARIS or Signavio when you need thousands of diagrams with SOX-grade governance.
The sweet spot: teams of 3 to 300 people who want real BPMN and collaboration without running an enterprise platform.
Try the Crismo playground (no signup) or read the neutral methodology at ProcessCamp.
Top comments (0)