DEV Community: Crismo Team

Process Mapping with Crismo: From Import to Shared Workflow

Crismo Team — Wed, 22 Apr 2026 08:33:11 +0000

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.

Process Stakeholder Alignment: Getting Sign-Off Without the Politics

Crismo Team — Mon, 20 Apr 2026 13:15:51 +0000

The hardest part of process improvement is not drawing the diagram. It is getting the people who need to change their work to agree that the change is worth making.

Why most process changes stall

You run a discovery workshop. You produce a clear as-is model. You design an improved to-be state that saves the team hours every week. You present it to leadership. They nod, say "looks great," and nothing happens.

Three months later, everyone is still running the old process.

This is not a modeling problem. It is an alignment problem.

Step 1: Map your stakeholders before you map the process

Before you touch a modeling tool, list every person or group that will be affected by the process change. For each stakeholder, answer three questions:

What do they care about?
What do they stand to gain or lose?
What level of involvement do they need?

Use a simple 2x2 grid: influence on one axis, impact on the other. High influence + high impact stakeholders need co-design. It takes ten minutes and saves weeks of politics.

Step 2: Frame the change in their language

The number one mistake: explaining the process change in process language.

For executives: Focus on outcomes and numbers.
For team leads: Focus on workload and clarity.
For frontline workers: Focus on daily experience. Be honest about what gets harder.
For IT teams: Focus on integration and system impact.

Step 3: Align at the right moments

Alignment is not a single meeting. It is a series of touchpoints:

Before discovery: Set expectations
After discovery: Share the as-is model in plain language
During design: Co-create the to-be state
Before implementation: Get explicit sign-off in writing
After implementation: Close the loop with results

How to handle resistance

Resistance is information about what you missed.

"We tried this before" - Ask what specifically failed. Usually it was the rollout, not the design.
"This will create more work" - Quantify current vs projected workload.
"My team was not consulted" - Own it. Late involvement beats no involvement.
"The current process works fine" - Show the data if it does not.
"I do not understand the diagram" - Translate into narrative. The model is a visual aid, not the deliverable.

Five alignment anti-patterns

The big reveal - Working in isolation then presenting a finished design
Consensus theater - Meetings where everyone nods but nobody commits
The BPMN lecture - Explaining gateway types to people who never asked
Ignoring the silent objector - The person who says nothing but undermines later
Alignment without authority - Getting the team excited without securing the decision maker

Checklist

Stakeholders mapped by influence and impact
Change framed in stakeholder-specific language
Alignment touchpoints scheduled at each phase
Process model translated for non-technical audiences
Sign-off documented in writing
Results reported back after implementation

Read the full guide on ProcessCamp with instructor tips, detailed resistance handling, and FAQ.

The Process Governance Playbook

Crismo Team — Mon, 20 Apr 2026 13:09:20 +0000

Process documentation without governance is a snapshot that goes stale the moment it is published. This playbook gives you the framework to keep processes owned, reviewed, and aligned with how your organization actually works.

Originally published at processcamp.io

Why process governance matters

Every organization has process documentation somewhere. SharePoint folders, Confluence pages, Visio files on a shared drive. The problem is rarely that documentation does not exist. The problem is that nobody maintains it.

After a few months, diagrams drift from reality. People invent workarounds that never make it back into the model. New hires read the documented process and then learn that "we do not actually do it that way."

Process governance is the set of roles, rules, and rituals that prevent this decay. It answers four questions:

Who is accountable for each process?
How often does each process get reviewed?
What happens when a process changes?
How do you know which processes need attention?

The three pillars of process governance

1. Ownership

Every process has a named owner who is accountable for its accuracy, performance, and improvement. Ownership is assigned at the process group level, not at the individual diagram level.

A process owner has five responsibilities:

Accuracy: The documented process reflects how work actually happens.
Performance: The owner tracks whether the process meets its objectives.
Improvement: When gaps appear, the owner drives redesign.
Compliance: For regulated processes, the owner ensures control requirements are met.
Communication: When a process changes, performers need to know.

Process owner vs. process steward vs. process modeler

Role	Focus	Typical person
Process owner	Accountability for performance and design	Department head
Process steward	Day-to-day documentation maintenance	Business analyst
Process modeler	Creating and updating BPMN diagrams	BPM analyst

2. Review cycles

A process review is a scheduled check where the owner and stakeholders confirm that documentation still reflects reality.

Frequency	When to use	Example
Quarterly	High-change, customer-facing	Customer onboarding
Semi-annual	Moderate-change, cross-functional	Order fulfillment
Annual	Stable, low-risk	Fixed asset accounting

A review produces one of three outcomes: Confirmed (matches reality), Updated (changes applied), or Flagged (needs redesign).

3. Process maturity tracking

Level 1 (Ad hoc): Process exists but is not documented.
Level 2 (Documented): Modeled and accessible, but nobody checks accuracy.
Level 3 (Governed): Owner assigned, reviewed on schedule, changes tracked.
Level 4 (Optimized): Performance metrics drive continuous improvement.

Rate each process group on this scale. The result is a maturity heat map that shows where to invest.

Implementation roadmap: 90 days

Days 1-30 (Foundation):

Build or validate your process landscape (L0 and L1).
Assign owners for the 5-10 most critical groups.
Rate maturity for each group.

Days 31-60 (First review cycle):

Run initial reviews for critical groups.
Update documentation where reality drifted.

Days 61-90 (Scale):

Extend ownership to remaining groups.
Set review cadence per group.
Publish maturity heat map to leadership.

Common mistakes

Governance by committee: One name per process group, not a committee.
Treating governance as a project: It is a continuous practice with no end date.
Ownership without authority: Owners need mandate to act on findings.
Reviewing for compliance only: Verify accuracy, not just existence.
Skipping the landscape: Without structure, you cannot assign ownership systematically.

Choosing a tool

Look for: ownership assignment, automatic version history, review tracking, permission controls, and frictionless sharing for stakeholder review.

Read the full guide with FAQ and structured data at processcamp.io/guides/process-governance-playbook.

Process Harmonization After a Merger: A Practical Guide

Crismo Team — Mon, 20 Apr 2026 13:09:08 +0000

After a merger, two organizations bring two sets of processes, two sets of tools, and two sets of assumptions about how work gets done. Without deliberate process harmonization, those differences persist long after the deal closes.

This guide covers the practical framework for harmonizing business processes post-M&A: how to assess both organizations' processes, identify overlaps and gaps, design a target operating model, and manage the transition.

Why Process Harmonization Matters

Most M&A integration plans focus on systems, headcount, and financial consolidation. Process harmonization rarely gets its own workstream until something breaks.

A customer order falls through the cracks because the two fulfillment processes have different approval logic. Finance cannot close the books because procurement runs on different controls. Support tickets get routed to the wrong team because escalation paths were never aligned.

McKinsey estimates that 70% of mergers fail to achieve their projected synergies. Process misalignment is a primary contributor.

What Harmonization Actually Means

Harmonization is not about picking one company's process and forcing it on the other. True harmonization produces three types of outcomes:

Adopt: One organization's process is clearly superior. The other team adopts it.
Merge: Both organizations have strong processes. The target combines elements from both.
Redesign: Neither process works for the combined entity. Something new is needed.

A Step-by-Step Framework

Step 1: Build Both Process Landscapes

Before you can compare processes, you need to see them. Each organization should produce a process landscape at the L0 (value chain) and L1 (process group) level.

Use the same leveling convention for both. If Company A uses "Order to Cash" and Company B calls it "Sales Operations", normalize the naming before comparing.

Step 2: Identify Overlaps and Gaps

Place both landscapes side by side. For each L0 area, ask: does the other organization have an equivalent? You will find full overlaps, partial overlaps, and unique areas.

Step 3: Assess at the Detail Level Where It Matters

Focus the detailed analysis on overlapping process areas that are on the critical path. Typically: order management, customer service, procurement, financial close, and employee onboarding.

Model the as-is state from both organizations using BPMN. Look for differences in approval chains, system touchpoints, exception handling, and roles.

Step 4: Design the Target Operating Model

For each overlapping area, design the to-be state. Involve process owners from both organizations. The people who run the processes daily have context that no integration consultant can replicate.

Resist the temptation to optimize during harmonization. The goal is alignment, not improvement. Get to one stable process first.

Step 5: Plan the Transition

Cover training, migration timeline, parallel-run periods, and rollback criteria. For complex processes, consider phased rollouts by region or business unit.

Step 6: Govern and Iterate

Assign process owners for each harmonized area. Schedule quarterly reviews. Track whether the synergies projected in the deal thesis are materializing.

Common Mistakes

Winner takes all - Forcing the acquirer's processes destroys institutional knowledge
Harmonizing everything at once - Prioritize by business impact
Skipping the landscape step - You cannot compare what you cannot see
Confusing harmonization with optimization - Align first, optimize later
Ignoring culture - Processes carry cultural assumptions about risk, speed, and control

When to Harmonize (and When to Leave Alone)

Harmonize: Customer-facing processes, financial processes, processes tied to shared systems, employee-facing processes with consistency requirements.

Leave alone (for now): Business-unit-specific processes, back-office processes that can run in parallel, processes scheduled for sunsetting, areas with regulatory constraints.

Read the full guide with tools comparison, FAQ, and cross-links: Process Harmonization Guide on ProcessCamp

How to Run a Process Discovery Workshop

Crismo Team — Mon, 20 Apr 2026 13:02:07 +0000

Discovery workshops are where process knowledge lives. Someone explains how work gets done, and a facilitator captures it in notes, recordings, or sticky notes on a wall.

The problem comes afterward. Most process improvement projects fail before the first diagram is finished. Not because the modeling tool was wrong, but because the modeler never talked to the right people, asked the wrong questions, or mapped what they assumed instead of what actually happens.

This guide covers the most common format: a facilitated workshop with 3 to 8 participants.

Step 1: Pick the process and define the scope

Before you invite anyone, decide what you are discovering. A discovery session that tries to cover "everything the operations team does" will produce nothing useful. Pick one process. Give it a name. Define where it starts and where it ends.

Use the trigger-to-outcome pattern: "This process starts when [trigger] and ends when [outcome]."

If the process is large, break it into sub-processes and run separate sessions for each. A 90-minute workshop can usually cover 10 to 20 steps with reasonable depth.

Step 2: Invite the right people

The room needs people who do the work, not just people who manage it. Managers describe the designed process. Frontline workers describe the real one. You need both, but start with the people who do the work.

Aim for 3 to 8 participants. Fewer than 3 and you miss perspectives. More than 8 and the session becomes a meeting where half the room checks email.

Role	Why they need to be there
Frontline workers	They execute the process daily
Team lead / supervisor	They see the bigger picture
Upstream / downstream contact	They hand work in or receive it
Process owner	They are accountable for the process

Step 3: Prepare your questions

Good discovery is structured conversation, not free-form brainstorming.

Opening questions:

"Walk me through what happens when [trigger]. Start from the very beginning."
"Who touches this process? In what order?"
"How do you know when this process is done?"

Drill-down questions:

"What happens if [step] goes wrong? Who handles it?"
"Is there a decision point here? What determines which path is taken?"
"How long does this step usually take? What causes delays?"
"What information do you need to start this step? Where does it come from?"
"Is this step always done the same way, or does it vary?"

Validation questions:

"Let me play it back: [summarize]. Does that match how it works?"
"What did I miss?"
"If a new hire joined tomorrow, what would surprise them about this process?"

The best question for uncovering the real process: "What would you tell a new colleague on their first day?" People drop the official language and describe what actually happens.

Step 4: Run the session (90-minute structure)

Minutes 0 to 10: Frame the scope. State the process name, trigger, and outcome. Confirm participants agree on the boundaries.

Minutes 10 to 50: Walk through the happy path. Ask one participant to describe the process from start to finish. Do not discuss exceptions yet. Park them visibly.

Minutes 50 to 70: Add exceptions and decisions. Go through the parking lot. For each exception, ask: "How often does this happen? Who handles it?"

Minutes 70 to 85: Validate and assign roles. Read the process back to the group. Mark who owns each step.

Minutes 85 to 90: Wrap up. Summarize open questions. Assign who creates the clean diagram.

Step 5: Capture notes in a way that translates to BPMN

Each sticky note or line item should answer: Who does what, when, and what happens next.

Some teams model live during the workshop using a projected BPMN tool. Others prefer sticky notes first and model afterward. Both approaches are valid. The key is that whoever models the result was in the room.

Step 6: Clean up and validate

Within 48 hours of the workshop, produce a clean diagram. The longer you wait, the more context fades. Send it to all participants and ask: "Is this what we discussed?" and "What did we miss?"

Five mistakes that derail discovery workshops

Jumping to solutions. Discovery maps what IS, not what should be.
Inviting only managers. Frontline workers describe the real process.
Boiling the ocean. One process, one session.
No visible capture. Make the model visible throughout.
No follow-up. A workshop without a clean diagram within a week was a wasted meeting.

Discovery workshop checklist

Process name, trigger, and outcome defined
3 to 8 participants invited (including frontline workers)
Opening, drill-down, and validation questions prepared
Capture method chosen (sticky notes, projected tool, or recording)
Happy path mapped before exceptions
Parking lot for improvement ideas
Roles and handoffs marked on the model
Clean diagram produced within 48 hours
Validation review scheduled within one week

FAQ

How many processes can I discover in one workshop?
One. A 90-minute session can cover one process with 10 to 20 steps.

Should I model live during the workshop or capture on sticky notes?
Both work. Modeling live is faster if the facilitator is comfortable with the tool. Sticky notes are better when participants are not familiar with BPMN notation.

What if participants disagree about how the process works?
This is expected and valuable. Document all variants as separate paths. Do not force consensus during discovery.

Can I do process discovery remotely?
Yes. Use a shared screen. Record the session (with consent). Keep remote sessions to 60 minutes.

What is the difference between process discovery and process mining?
Discovery uses interviews to map how people describe their work. Process mining uses system event logs. They are complementary.

Process Landscapes: From Value Chain to Detailed Processes

Crismo Team — Mon, 20 Apr 2026 13:00:14 +0000

A single BPMN diagram tells you how one process works. A process landscape tells you how the entire organization fits together.

The folder-of-diagrams problem

Most process documentation starts the same way: someone models their first diagram, then their tenth, then their fiftieth. Before long you have 50 BPMN files in a folder structure that only one person understands. No overview. No hierarchy. No way to see how a customer order flows from sales through fulfillment.

What is a process landscape?

A structured hierarchy with three tiers:

L0: Value Chain — The 5 to 10 major end-to-end process areas. "Order to Cash", "Hire to Retire", "Procure to Pay". No BPMN at this level.

L1: Process Groups — Each L0 breaks into 3 to 8 named groups. "Order to Cash" becomes Lead Qualification, Order Entry, Fulfillment, Invoicing.

L2: Detailed Processes — The actual BPMN diagrams with pools, lanes, gateways, and tasks.

How to build one (5 steps)

Step 1: Define the value chain (L0)

List the major "noun-to-noun" flows: Lead to Customer, Order to Cash, Idea to Product, Hire to Retire. Use the "X to Y" naming convention.

Step 2: Break down into process groups (L1)

Each L0 gets 3 to 8 process groups. Each group should be assignable to a single process owner.

Step 3: Map detailed processes (L2)

This is where BPMN lives. Do not model everything at once. Start with the most critical processes.

Step 4: Connect the levels

Each L0 links to its L1 groups. Each L1 links to its L2 diagrams. Two clicks from value chain to any process.

Step 5: Validate with stakeholders

Show the L0 to leadership. Ask: "Does this cover what we do?" You will get corrections that make the landscape real.

Common mistakes

Starting with L2 — Build the structure before modeling detailed processes
Too many L0 areas — If you have more than 10, some are L1 groups in disguise
Inconsistent naming — Pick a convention and enforce it
No process owners at L1 — Every group needs an accountable person
Modeling everything at the same depth — Not every process needs full BPMN detail

Which tools support process landscapes?

ARIS — Enterprise, deep process architecture. Expensive.
SAP Signavio — Repository with hierarchies. Enterprise pricing.
Crismo — Landscapes as default. Free tier. Real-time collaboration.
Bizagi — Desktop modeler with grouping. Free tier.

Most open-source editors (bpmn.io, draw.io) work at the individual diagram level and do not support hierarchical navigation natively.

Read the full guide with FAQ and framework details. Part of the ProcessCamp BPMN guides.

Visio BPMN Alternatives: Tools That Produce Standards-Compliant BPMN

Crismo Team — Mon, 20 Apr 2026 08:26:51 +0000

Visio has a BPMN stencil. But .vsdx files are proprietary XML, not BPMN 2.0 XML. If you need real BPMN that process engines can read and other tools can import, here are 5 alternatives.

Why Visio Falls Short

Visio saves proprietary XML describing shapes on a canvas. No <bpmn:userTask>, no <bpmn:sequenceFlow>. Process engines reject .vsdx files. Validators cannot check them. Your models are locked in the Microsoft ecosystem.

5 Alternatives With Real BPMN Export

1. Crismo

Import existing Visio files, get valid BPMN 2.0. Free tier, real-time collaboration, process landscapes. Try free

2. Bizagi Modeler

Free desktop modeler. Full BPMN 2.0, clean interface. Windows/Mac.

3. bpmn.io

Free, open source, browser-based. Valid BPMN XML. Single-user.

4. Camunda Modeler

Free desktop modeler for executable processes.

5. ARIS

Enterprise platform supporting BPMN + EPC. Strong governance. Expensive.

Already Have Visio Files?

Use the free Visio to BPMN converter to convert .vsdx files to standards-compliant BPMN 2.0 XML.

Read the full guide. Part of the ProcessCamp BPMN guides.

Lucidchart BPMN Alternatives: Tools That Export Real BPMN 2.0

Crismo Team — Mon, 20 Apr 2026 08:25:51 +0000

Lucidchart has a BPMN template that looks professional. But it does not export valid BPMN 2.0 XML. The shapes are cosmetic. If you need standards-compliant process models, here are better options.

Why Lucidchart Falls Short

Lucidchart exports .lucidchart JSON, PDF, PNG, or Visio .vsdx. None contain BPMN XML. No process engine can read them. No validator can check structural correctness.

5 Alternatives With Real BPMN Export

1. Crismo

Real-time collaboration (like Lucidchart) PLUS valid BPMN 2.0 export. Free tier with unlimited diagrams, process landscapes, AI discovery. Try free

2. Bizagi Modeler

Free desktop modeler. Full BPMN 2.0, clean interface, publish as web portals. Windows/Mac.

3. bpmn.io

Free, open source, browser-based. No signup. Valid BPMN XML. Single-user only.

4. Camunda Modeler

Free desktop modeler for developers building executable processes.

5. SAP Signavio

Enterprise platform with governance, approval workflows, process mining. Expensive.

Already Have Lucidchart Diagrams?

Use the free Lucidchart to BPMN converter to convert existing diagrams to BPMN 2.0 XML.

Read the full guide. Part of the ProcessCamp BPMN guides.

draw.io BPMN Alternatives: 5 Tools That Actually Export Valid BPMN

Crismo Team — Mon, 20 Apr 2026 08:25:35 +0000

draw.io is great for quick diagrams. But it does not export valid BPMN 2.0 XML. If you need standards-compliant process models, here are 5 alternatives that actually produce real BPMN.

Why draw.io Falls Short for BPMN

draw.io has a BPMN shape library, but the file it saves is mxGraphModel XML, not BPMN 2.0 XML. You get shapes on a canvas, not a process model. No process engine can read it. No BPMN validator can check it.

5 Alternatives That Produce Real BPMN

1. Crismo

Free tier with unlimited diagrams. Real-time collaboration. Process landscapes. AI-powered process discovery. Import from draw.io, Visio, Signavio. Try free

2. bpmn.io

Free, open source, runs in the browser. No signup needed. Produces valid BPMN XML. Single-user only, no collaboration.

3. Bizagi Modeler

Free desktop application (Windows/Mac). Full BPMN 2.0. Clean interface. No web version in free tier.

4. Camunda Modeler

Free desktop modeler from the Camunda team. Designed for developers building executable processes.

5. Trisotech

Enterprise platform supporting BPMN, DMN, and CMMN. Best multi-standard support.

Already Have draw.io Files?

Use the free draw.io to BPMN converter to convert existing .drawio files to standards-compliant BPMN 2.0 XML. Runs in your browser, no upload needed.

Read the full guide. Part of the ProcessCamp BPMN guides.

Best BPMN Tools in 2026: 10 Modeling Platforms Compared

Crismo Team — Mon, 20 Apr 2026 08:25:13 +0000

Not every tool that has BPMN shapes produces valid BPMN. Some generate standards-compliant XML that process engines can execute. Others draw pretty pictures that look like BPMN but export as proprietary formats.

We evaluated 10 tools on BPMN 2.0 compliance, collaboration, ease of use, ecosystem, and pricing.

Quick Comparison

Tool	Valid BPMN 2.0?	Collaboration	Free Tier	Best For
Camunda	✅ Full	Limited	✅ Community	Process automation
SAP Signavio	✅ Full	✅ Multi-user	❌	Enterprise BPM
ARIS	✅ Full	✅ Multi-user	❌	Multi-notation
Bizagi	✅ Full	✅ Cloud	✅ Desktop	Free desktop modeling
bpmn.io	✅ Full	❌	✅ Open source	Quick sketches
Crismo	✅ Full	✅ Real-time	✅ Unlimited	Team collaboration
Trisotech	✅ Full	✅ Multi-user	❌	BPMN + DMN + CMMN
draw.io	❌ Shapes only	Via Drive	✅	Quick informal diagrams
Lucidchart	❌ Shapes only	✅ Real-time	Limited	Cross-functional visuals
Visio	❌ Shapes only	Via SharePoint	❌	Microsoft ecosystem

The BPMN Compliance Divide

The most important distinction is whether the tool produces real BPMN 2.0 XML or just draws shapes.

Tools that produce valid BPMN 2.0 (Camunda, Signavio, ARIS, Bizagi, bpmn.io, Crismo, Trisotech) give you files that any other BPMN tool can open. You can validate, simulate, and automate.

Tools that draw BPMN shapes (draw.io, Lucidchart, Visio) give you proprietary files that look correct on screen but cannot be imported by other tools, validated, or executed.

Tool-by-Tool Breakdown

Camunda

Best for: Developer teams building executable BPMN processes.
The gold standard for process automation. Open-source community edition available, large connector ecosystem, active developer community. The modeler is basic compared to dedicated tools, and the learning curve is steep for non-developers.

SAP Signavio

Best for: Large organizations with dedicated process teams.
Process mining integration, governance workflows with approval chains, SAP integration. Very expensive (typically $30k+/year), complex interface, SAP acquisition shifted focus toward SAP ecosystem.

ARIS

Best for: Organizations needing multi-notation support (EPC + BPMN).
Decades of BPM methodology, supports BPMN/EPC/value chains in one platform, strong governance. Interface feels dated, expensive, cloud offering still catching up.

Bizagi

Best for: Teams wanting free modeling with optional automation.
Free desktop modeler with no feature limits, clean interface, can publish as web portals. Desktop-only free tier, cloud version has limited free tier.

bpmn.io

Best for: Quick sketches, learning, embedding in custom apps.
No signup required, produces valid BPMN XML, open source, maintained by Camunda. No collaboration, no cloud storage, minimal validation.

draw.io

Best for: Quick informal diagrams, Confluence integration.
Free with no limits, tight Jira/Confluence integration. Does NOT export valid BPMN 2.0 XML. BPMN shapes are cosmetic only.

Lucidchart

Best for: Cross-functional teams needing many diagram types.
Excellent real-time collaboration, polished interface, Google Workspace integration. No valid BPMN export, template is cosmetic only.

Microsoft Visio

Best for: Organizations already in the Microsoft ecosystem.
Deep M365 integration, familiar to enterprise users. Does NOT export BPMN XML, proprietary .vsdx format, requires subscription.

Crismo

Best for: Teams wanting collaborative BPMN with process landscapes.
Process landscapes as default starting point, real-time collaboration, AI-powered process discovery, import from Visio/Signavio/draw.io. Free tier with no time limit. Newer platform, still building governance features.
Disclosure: we build Crismo.

Trisotech

Best for: Organizations needing BPMN + DMN + CMMN.
Best multi-standard support, strong decision modeling, active in OMG standards bodies. Enterprise pricing, smaller ecosystem.

How to Choose

Want to automate? → Camunda
Need enterprise governance? → Signavio or ARIS
Want free desktop modeling? → Bizagi
Want real-time team collaboration? → Crismo or Lucidchart (Crismo produces valid BPMN)
Just need a quick browser sketch? → bpmn.io
Need BPMN + DMN + CMMN? → Trisotech
Team uses Confluence? → draw.io (but it won't produce valid BPMN)
Learning BPMN? → bpmn.io or Crismo (both free)

FAQ

Which BPMN tool is completely free?
bpmn.io (open source), Bizagi Modeler (desktop), and Crismo (free tier) are genuinely free.

Can I switch tools later?
If your tool exports valid BPMN 2.0 XML, yes. Files are portable across compliant tools.

Which tool should beginners start with?
bpmn.io for zero-friction start, or Crismo for a guided experience with process landscapes.

Read the full comparison with detailed reviews. This post is part of the ProcessCamp BPMN guides.

Miro Is Great for Brainstorming, Not Process Models

Crismo Team — Fri, 10 Apr 2026 12:14:40 +0000

The meeting went well. Everyone gathered around a Miro board, dropped sticky notes, drew arrows, and mapped out how work actually gets done. By the end, you had something that looked like a process flow. People nodded. It made sense.

Then someone asked you to turn it into a BPMN diagram.

And you realized the gap between a brainstorm and a process model is wider than it looks.

Miro Is a Whiteboard. Not a Modeling Tool.

Miro is exceptional at what it was built for: collaborative visual thinking. Sticky notes, freeform shapes, dot voting, templates for retrospectives, user story maps, and workshop facilitation.

But a whiteboard is not a process modeling tool.

BPMN 2.0 is a formal standard. Every element has defined semantics. A parallel gateway means all outgoing paths execute concurrently. A timer start event means the process triggers on a schedule. A pool defines an organizational boundary.

Miro has none of this. A rectangle is just a rectangle. An arrow is just a line between shapes.

The Graduation Problem

Phase 1: Discovery. Workshop participants map the current process on Miro. Sticky notes, quick arrows, informal language. This is appropriate.

Phase 2: Documentation. The Miro board needs to become a proper process diagram. Someone rearranges the sticky notes into swimlanes, adds diamond shapes for decisions. It starts to resemble BPMN.

Phase 3: Realization. The diagram needs to be shared with a compliance team, imported into a process engine, or analyzed by an automation consultant. And the Miro board can't go anywhere. It exports to PDF, PNG, or a Miro backup file. None of these carry process semantics.

This graduation from brainstorm to model happens in every process improvement project. The question is whether you plan for it or stumble into it.

What You Lose by Staying in Miro

Structural validity. BPMN has rules. Every exclusive gateway split must eventually merge. Miro lets you draw anything, valid or not.

Process semantics. A BPMN user task means a human performs this step. A service task means a system does it. In Miro, both are rectangles with text.

Portability. A .bpmn file opens in Camunda, ARIS, Signavio, Bizagi, or Crismo. A Miro board opens in Miro.

Scale. Ten process diagrams in Miro are manageable. A hundred are chaos.

The Fix: Convert Miro Diagrams to Real BPMN

We built a free Miro to BPMN converter that extracts the process structure from Miro's export and produces standards-compliant BPMN 2.0 XML.

Three steps:

Export your Miro board
Drop the file into the converter
Download the .bpmn file and open it in any BPMN-compliant tool

Convert your first Miro diagram now.

The Better Workflow: Brainstorm in Miro, Model in Crismo

Miro is great for phase 1. Keep using it for workshops and collaborative discovery.

But when the brainstorm needs to graduate into a process model, switch to Crismo. Real-time collaborative BPMN modeling, structural validation, token simulation, and process landscapes. Every diagram is valid BPMN 2.0 from the first drag.

The best workflow isn't Miro vs. Crismo. It's Miro then Crismo.

Try the free Miro converter to bridge the gap.

This post is part of the Crismo BPMN series. Crismo is a free, AI-native BPMN modeling platform. Try it here.

Lucidchart BPMN Templates Look Right. They Aren't Valid.

Crismo Team — Fri, 10 Apr 2026 12:14:24 +0000

Lucidchart has a BPMN template. It's one of the first results when you search "BPMN diagram tool" and it shows up in the template gallery with a clean, professional-looking process model. Start events, tasks, gateways, end events. Textbook BPMN.

Except it isn't.

The shapes look correct. The labels are right. But what Lucidchart produces is a drawing that resembles BPMN, not a file that complies with the BPMN 2.0 standard.

Cosmetic BPMN vs. Structural BPMN

BPMN 2.0 is two things at once. It is a visual notation (the shapes and their meaning) and a data model (the XML that defines process semantics, connections, and execution logic). A valid BPMN file must satisfy both.

Lucidchart satisfies the first and ignores the second.

When you export a Lucidchart BPMN diagram, you get a .lucidchart JSON file, a PDF, a PNG, or a Visio .vsdx. None of these contain BPMN 2.0 XML.

This means:

No structural validation. Does your exclusive gateway have a default flow? Does every parallel gateway fork merge correctly? Lucidchart can't tell you because it doesn't understand the semantics.

No execution. Process engines (Camunda, Flowable, Zeebe) expect .bpmn files. A Lucidchart export is useless to them.

No interoperability. A Lucidchart file opens in Lucidchart and nowhere else.

The Template Trap

Lucidchart's BPMN template is well-designed. That is actually the problem. It looks so correct that teams use it confidently for months before discovering the limitations.

A business analyst uses Lucidchart to document processes for an ERP implementation. Diagrams go through multiple review cycles. Stakeholders sign off.

Then the implementation partner asks for the BPMN files. Not screenshots. The actual .bpmn files so they can import them into their process automation platform.

The analyst discovers there is no export path. The months of work exist only as drawings. They need to be redrawn from scratch in a BPMN-compliant tool.

What Lucidchart Gets Right (and Where It Stops)

Credit where due: Lucidchart is excellent at collaboration, polished visuals, and integration with Google Workspace.

If your goal is to create a clean visual for a slide deck, Lucidchart works fine.

But BPMN was designed for portability, validation, simulation, and automation. Lucidchart participates in the notation but not the standard.

The Fix: Convert Lucidchart Diagrams to Real BPMN

We built a free Lucidchart to BPMN converter that bridges the gap. Export your diagram, drop it into the converter, and get a standards-compliant BPMN 2.0 file.

Three steps:

Export your diagram from Lucidchart
Drop the file into the converter
Download the .bpmn file and open it in Camunda, Crismo, or any BPMN tool

Convert your first Lucidchart diagram now.

This post is part of the Crismo BPMN series. Crismo is a free, AI-native BPMN modeling platform. Try it here.