A Reddit user posted recently: "I'm finding switching back to default Visio BPMN diagrams agonizing." The replies were a cascade of tool recommendations — Lucidchart, draw.io, Miro, BPMN.io. Everyone had a favourite. Nobody asked the obvious question: why are you drawing BPMN diagrams at all?
That exchange captures the problem with most "process mapping software" evaluations. McKinsey research found that 70% of large-scale process transformation programmes fail to achieve their targets — not because teams chose the wrong diagramming tool, but because they confused documentation with improvement. If your evaluation is Visio vs Lucidchart vs draw.io, you are evaluating the right tools for the wrong problem.
This post separates what those tools actually do from what process improvement platforms do, so you can make a choice grounded in what you need — not just what shows up in the same Google search.
One Search Term, Two Completely Different Categories
"Process mapping software" is doing a lot of heavy lifting as a search term. Type it into any search engine and you get results ranging from drag-and-drop flowchart builders to full operational intelligence platforms. These are not the same category of product. They do not produce the same outputs. They do not solve the same problems.
Here is how to tell them apart.
Category 1: Diagramming Tools
Diagramming tools let you draw a process map. The output is a static diagram — a visual artifact that communicates what a process looks like at a given moment. Leading tools in this category include Visio, Lucidchart, draw.io, Miro, and BPMN.io.
These tools are genuinely excellent at what they do. A compliance officer who needs to document a process for an audit, a business analyst who needs to walk a stakeholder through a workflow, or an IT team preparing a handover document — all of these people have a legitimate need for a good diagramming tool. The output is communication.
Category 2: Process Improvement Platforms
Process improvement platforms measure, analyze, and improve processes. The output is not a diagram. It is a diagnosis and an improvement hypothesis — specific, testable, tied to measurable outcomes like cycle time, error rate, and cost per transaction.
This is the category ESSAM occupies. The output of an ESSAM engagement is not a prettier map. It is a structured account of where value is being lost, why it is being lost, and what a changed process would produce in quantifiable terms.
The confusion between these two categories is expensive. A Kuwaiti bank documented its loan origination process meticulously — accurate BPMN diagrams, clean swimlane charts, every handoff mapped. The process still took 139 days to complete. It took an ESSAM engagement, not better diagrams, to reduce that to 57 days — a 59% reduction in cycle time. The maps were right. The process was wrong.
The Decision Framework: Four Questions
Before you open a trial account for any tool, answer these four questions.
1. Do you need to communicate a process, or fix one?
If someone needs to understand what a process looks like — a new hire, a regulator, an integration partner — you need a diagramming tool. Category 1. If a process is generating complaints, delays, errors, or cost overruns, you need to fix it. Category 2.
2. Is this for compliance documentation or operational improvement?
Regulatory submissions, audit trails, ISO certification packages, SOC 2 evidence — these require documented, versioned process maps. Diagramming tools are purpose-built for this. But compliance documentation does not make a broken process faster or cheaper. If your goal is operational performance, documentation is a by-product, not the output.
3. Are you measuring cycle time, error rate, or unit cost?
If you are tracking how long something takes, how often it goes wrong, or what it costs per transaction, you are in improvement territory. A static diagram cannot tell you any of those things. You need a platform that ingests operational data and surfaces the delta between your current state and a better one.
4. Do you have 200 diagrams and a process that still isn't working?
This is the most honest diagnostic question. Many operations teams in banking have invested years in Lucidchart documentation. Their loan origination maps are accurate. Their credit decisioning swimlanes are thorough. And the process still takes 47 days. The maps are correct. The problem is that accuracy and improvement are different things. If your documentation is solid but performance is not moving, you are in the wrong category.
Diagramming Tools: What Each One Does Best
If your answer to the framework above points to Category 1, here is a practical breakdown of the major diagramming tools.
| Tool | Best For | BPMN Support | Collaboration | Cost |
|---|---|---|---|---|
| Visio | Enterprise IT, complex technical diagrams, Microsoft ecosystem | Full BPMN 2.0 | Limited (SharePoint-based) | £15–£28/user/mo (Microsoft 365) |
| Lucidchart | Cross-functional teams, cloud-first orgs, Google Workspace users | Good BPMN support | Real-time, strong | £7–£27/user/mo |
| draw.io | Budget-constrained teams, self-hosted environments, open-source preference | Good BPMN support | Via integrations (Confluence, Notion) | Free (open source) |
| Miro | Workshop facilitation, service design, journey mapping | Basic BPMN | Real-time whiteboard | £8–£16/user/mo |
| BPMN.io | Developers, technical architects, pure BPMN standards work | Native BPMN 2.0 | Minimal (code-first) | Free (open source) |
A few notes on this comparison.
Visio remains the standard in large enterprise IT environments — particularly in banks and insurers with mature Microsoft infrastructure. Its BPMN support is comprehensive, and its diagram library is the deepest in the category. The collaboration story is weaker than its cloud-native competitors; version control through SharePoint is functional but not fluid.
Lucidchart has largely become the default for teams that need diagramming and live collaboration without an enterprise IT procurement process. Its Google Workspace integration is clean, and the BPMN templates are usable out of the box.
draw.io is worth serious consideration for any team with budget constraints or a preference for open-source tooling. The self-hosted option is particularly attractive for organisations with data residency requirements. It lacks some of the polish of Lucidchart, but for straightforward process documentation it is more than adequate.
Miro sits at the facilitation end of the spectrum. It is not the right tool for precise BPMN notation, but for process workshops — where you need a digital whiteboard that a room full of people can contribute to simultaneously — it is excellent.
BPMN.io is a tool for people who care deeply about BPMN standards compliance. It is open-source, technically rigorous, and largely friction-free if you are comfortable working in a code-adjacent environment. It is not designed for business stakeholders.
None of these tools will tell you why your process is slow.
What AI-Assisted Process Mapping Actually Means
"AI process mapping" has become a marketing phrase that covers a wide range of capabilities. For diagramming tools, AI typically means autocomplete for shapes, smart layout suggestions, or the ability to generate a rough flowchart from a text description. These are useful features for diagram creation. They do not constitute process analysis.
ESSAM's approach is different in kind, not just degree. A structured 40-minute conversation with a process owner — guided by ESSAM's methodology — produces a comprehensive process documentation without manual diagramming. But the documentation is a by-product. The primary output is a structured analysis: where the process loses time, where errors compound, where handoffs break down, and what a redesigned process would produce in terms of measurable outcomes.
This matters in banking specifically because process interviews in financial services tend to surface a category of insight that diagrams miss entirely: the informal workaround. Every operations team has them — the spreadsheet that sits outside the core system, the approval that gets handled by WhatsApp message, the exception that became a rule without anyone updating the documentation. A diagram drawn from a process map shows what the process is supposed to do. A structured analytical conversation surfaces what it actually does.
For more on the methodology behind this kind of analysis, what is business process analysis covers the foundational concepts in depth.
The Banking Context: Why Diagrams Aren't Enough
Banking operations carry a specific burden that makes the Category 1 / Category 2 distinction particularly consequential. Regulatory compliance requirements mean that banks genuinely need good process documentation — that part of the Category 1 value proposition is real. But compliance documentation and operational performance are not the same objective, and optimising for one does not deliver the other.
The loan origination process is the canonical example. It involves credit assessment, KYC checks, collateral valuation, credit committee approval, documentation, and disbursement — across multiple systems, multiple teams, and in many institutions multiple geographies. Every one of those steps can be diagrammed with precision. The diagram will not tell you that 23 days of cycle time are consumed by a manual data re-entry step that exists because two systems don't share a field format. It will not tell you that a credit committee review stage that is nominally two days is actually eight days because the committee only meets twice a week. It will not tell you that your error rate on KYC documentation is 34% because the instructions are ambiguous, not because staff are undertrained.
These are improvement problems, not documentation problems. They require a different category of tool — one that asks analytical questions, not just documentation questions.
Value stream mapping is one methodology that bridges documentation and analysis in banking contexts. Value stream mapping in banking walks through how that approach applies to financial services processes specifically.
If your process performs well on diagrams but poorly in production, the issue is not your diagramming tool. The issue is that you've been measuring the wrong thing.
Choosing the Right Tool for What You're Actually Trying to Do
The practical summary is straightforward.
If you need to document, communicate, or comply — choose a diagramming tool. Lucidchart if you are cloud-first and collaborative. Visio if you are Microsoft-entrenched. draw.io if you are budget-conscious or need self-hosting. Miro if you are running workshops. BPMN.io if you are a developer who cares about standards.
If you need to improve — choose a process improvement platform. Specifically, if you are in banking and your target is cycle time reduction, error rate reduction, or cost per transaction, you need a platform that measures those things and produces a hypothesis about how to change them. That is what ESSAM does.
The two are not mutually exclusive. Many organisations use diagramming tools for compliance documentation and a process improvement platform for operational performance. They serve different purposes. The mistake is expecting one to do the job of the other.
For a broader view of the capability landscape, the ESSAM features overview covers what a process improvement platform does that diagramming tools do not.
Frequently Asked Questions
What is the difference between process mapping software and a process improvement platform?
Process mapping software — tools like Visio, Lucidchart, and draw.io — produces static diagrams that communicate what a process looks like. A process improvement platform measures, analyzes, and produces improvement hypotheses tied to operational outcomes like cycle time, error rate, and cost. The outputs are fundamentally different: one is a document, the other is a diagnosis.
Can I use Visio or Lucidchart for process improvement in banking?
You can use them to document your process as a starting point for analysis. The diagram itself, however, cannot surface where time is being lost, where errors are compounding, or what a changed process would produce. For improvement work, you need a platform that asks analytical questions — not just documentation ones.
How long does it take to map a process using ESSAM?
A structured 40-minute conversation with a process owner produces comprehensive process documentation and an initial diagnostic. This compares to days or weeks of manual diagramming, workshop facilitation, and documentation work with traditional approaches.
What banking processes does ESSAM work best for?
ESSAM has been applied across loan origination, credit decisioning, KYC and onboarding, trade finance operations, and back-office reconciliation workflows. Any process where cycle time, error rate, or cost per transaction is a performance concern is a strong candidate.
Is ESSAM a replacement for diagramming tools like Lucidchart?
Not necessarily. If your organisation has compliance documentation requirements — and most banks do — a diagramming tool serves a legitimate purpose. ESSAM addresses the improvement objective: reducing the time, errors, and cost in processes that are already documented but still underperforming.
The Real Evaluation Question
The process mapping software evaluation most teams run looks like this: compare Visio vs Lucidchart on features, pricing, BPMN support, and integrations. Choose the one that fits the team's workflow best.
That is a reasonable evaluation — if your goal is better diagrams.
If your goal is better processes, the evaluation looks different. The question is not which tool draws the most accurate map. It is which platform gives you the clearest diagnosis of what is wrong and the most rigorous basis for fixing it.
Two hundred diagrams in Lucidchart, and loan origination still takes 47 days. The maps are accurate. The process isn't improved. That gap — between documentation and performance — is what a process improvement platform exists to close.
If you are working on operational performance in banking and the diagramming tools have taken you as far as they can, talk to the ESSAM team.