Process Mapping with Crismo: From Import to Shared Workflow

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. If you want the neutral methodology first (what process modeling is, which notation fits which situation, process diagram examples), start with the Process Modeling Guide on ProcessCamp and come back here when you are ready to act.

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. If you are mapping the order-to-cash process for a specific subsidiary, that subsidiary gets its own workspace.

The workspace gives you two things that raw files do not: shared context (everyone on the team sees the same state) and structure (your processes sit inside a value chain, not in a folder tree).

For a first pass, create one workspace and add the people who will collaborate on the mapping. Free tier allows up to three members, which is enough to pilot.

Step 2: Import What You Already Have

Process mapping rarely starts from scratch. Crismo imports from the three most common sources:

• BPMN XML files - any tool that exports standards-compliant BPMN 2.0 (Camunda, bpmn.io, Signavio, ARIS)
• Visio diagrams - convert via the free Visio to BPMN converter
• Lucidchart exports - convert via the Lucidchart converter
• draw.io / diagrams.net - convert via the draw.io converter

Import does not mean perfect translation. Visio, Lucidchart, and draw.io diagrams are often informal flowcharts rather than valid BPMN. The converter produces a best-effort BPMN model that you can then clean up. This is a feature, not a bug: it surfaces the ambiguity in the original diagram so you can fix it in the model.

If you have no existing documentation, skip to Step 3 and start directly in the workspace.

Step 3: Model in BPMN with Workspace Context

Crismo's modeler produces valid BPMN 2.0. Every diagram you create in a workspace is standards-compliant XML you could hand off to a developer or an execution engine.

What makes this different from a generic BPMN editor is the context around the diagram. The process lives inside a value chain. The elements inside the process reference entries from a shared dictionary. The document has an owner, a status, and a history. These are not features you bolt on after the diagram exists - they are the frame the diagram lives in.

For a first process map, focus on getting the happy path right: start event, the main activities, decision points, end event. Add exception paths in a second pass. Mapping everything at once is the most common reason first drafts never ship.

Step 4: Reuse Definitions Across Processes

Process maps accumulate. By the time you have ten diagrams, the same terms appear across all of them: "Customer", "Order", "Fulfillment Team". In most tools, these are ad-hoc text labels. A rename in one diagram does not propagate.

Crismo includes a workspace dictionary. When an element in a diagram references a dictionary entry, renaming that entry updates every diagram it appears in. When a new diagram needs the same participant, you pull it from the dictionary rather than retyping.

This sounds like a minor quality-of-life feature until you are six months into a process mapping program and someone reorganizes the department. Without dictionary reuse, that means manually touching dozens of diagrams. With it, you change one entry.

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.

For process mapping, this matters because stakeholders rarely ask about individual workflows in isolation. They ask "what do we do in Order to Cash?" The landscape answers that question in a way a flat list of diagrams cannot.

For the methodology behind building a landscape, see the Process Landscapes Guide on ProcessCamp. Crismo implements the methodology; the guide explains the thinking.

Step 6: Share for Review

A process map that nobody reviews is a process map that does not get used. Crismo has three sharing modes:

• View-only share links - send a URL to a stakeholder who just needs to see the diagram
• Comment access - invite reviewers who can leave comments on elements without editing
• Full collaboration - add team members with edit rights

Review cycles are where process maps earn their keep. Someone in the review finds a step that does not actually happen. Someone else points out a missing approval. The diagram improves because more eyes are on it.

Step 7: Govern and Iterate

Process maps go stale. The process changes, but nobody updates the diagram. Six months later, the diagram does not match reality and nobody trusts it.

In Crismo, every diagram has an owner, a last-updated timestamp, and a version history. You can set a review cadence per process (quarterly for critical ones, annually for stable back-office processes). When a diagram crosses its review date, the owner gets a reminder.

This is the boring but essential layer. A process mapping program that does not treat models as living artefacts reverts to the shelf-ware pattern within a year.

When Crismo Is the Right Fit

Crismo is built for teams that want BPMN-native process mapping with collaboration, landscape context, and reuse. It fits well when:

• You are mapping more than a handful of processes and need a repository, not just individual files
• Multiple people across different locations need to collaborate on the same models
• Your processes will eventually feed into automation, analytics, or audit evidence
• You want to consolidate scattered documentation from Visio, Lucidchart, and draw.io into one place
• You need a landscape view that connects L0 value chains to L2 workflow details

Crismo is probably not the right fit if you just need to sketch a single diagram for a meeting next Tuesday. For that, draw.io or a whiteboard app is faster. It is also not a replacement for large enterprise platforms like ARIS or SAP Signavio when you need deep process architecture, SOX-grade governance, and thousands of diagrams.

The sweet spot is teams of 3 to 300 people who want real BPMN, want to collaborate, and do not want to run an enterprise platform.

Try It

Open the Crismo playground to see the editor with no signup. If you want to model inside a workspace with dictionary reuse and value chains, create a free account.

For the neutral methodology behind process mapping and modeling, read the Process Modeling Guide on ProcessCamp and How to Map a Business Process in 6 Steps.