Business process management, without the diagram theatre
Most companies don’t have processes. They have habits. A habit is a process nobody wrote down: it works until the person holding it goes on holiday, resigns, or is simply having a bad week. A business process that lives in someone’s head is not a process — it is a dependency.
The short version
- What BPM is. Business Process Management is the discipline of turning undocumented habits into something explicit, testable and — the part most people skip — executable.
- Why companies adopt it. In the BPM Study 2023 the leading drivers were transparency (73%), efficiency (67%) and regulatory compliance (55%).
- Why projects fail. The same study found the leading causes are insufficient resources (67%) and weak management commitment (35%) — not bad software.
- The notation. BPMN 2.0 is an ISO standard, ISO/IEC 19510, maintained by the Object Management Group. It is the only notation both management and IT can read.
- How HYA applies it. Watch the work, model it, cut before building, make it executable, concentrate human control where risk lives, hand it over.
What the research actually says
We are not going to tell you BPM works because we sell it. Here is what the independent evidence says, with the sources named so you can check them.
Why BPM projects fail
The same BPM Study found the leading causes of failure are insufficient resources (67%) and weak management commitment (35%). Not bad software. Not the wrong notation.
In other words: BPM fails when nobody senior is holding it. Buying a tool and handing it to the operations team is the documented way to waste the budget.
That is the gap we fill. One senior professional, accountable for the result, present until the process runs.
Six steps, in this order, every time
We watch the work, not the org chart
Interviews, observation, and the documents that actually move — not the ones that are supposed to.
We model in BPMN
Standard notation, so the model survives us and can be handed to any competent party later.
We cut before we build
Automating a bad process gives you a fast bad process. Steps that exist only out of habit are removed first.
We make it executable
The model becomes the system: decision branches, automatic checks, generated documents, timers, notifications. The engine runs the process; people are asked only where judgement is genuinely required.
We keep control where control matters
Automation should concentrate human approval at the few points that carry risk, not remove it. Addressed to named roles, never a shared inbox.
We hand it over
Documentation, ownership, and a client who does not need us to keep operating.
We have run this method to its conclusion.
DREAM is a business process platform we designed and built: 247 processes modelled and running, 94.8% of operational steps executed by software, 10,113 business rules codified.
It is one client, one industry, over several years — a case, not a catalogue. But it answers the only question that matters about a method: does it survive contact with a real company for a long time?
A firm this size should not be able to stay current across six jurisdictions.
We do it because we built ourselves the same kind of system we build for clients: roughly 1,150 structured documents covering the UAE, Italy, Monaco, France, Hong Kong and China, five AI advisors trained on those collections, and an automated regulatory watch that reads the official legislative sources every week and reports what changed.
It is not a marketing claim. It is the reason the answer to a client question is usually the same day.
Sources cited on this page
- BPM Study 2023 — BOC Group & Institute of Information Systems (300+ respondents).
- Bosilj Vukšić et al. — Business Process Management and Organisational Performance (120 companies).
- CIIMA — BPM Maturity and Process Performance, inter-organisational processes.
- Bitkowska — BPM and Knowledge Management, JEMI, 2020.
- Object Management Group — BPMN 2.0, standardised as ISO/IEC 19510.
Figures quoted are the published findings of the studies named, not HYA results. HYA’s own measured figures are on the DREAM case study, where their limits are stated.
Business process management, answered plainly
What is business process management, in plain language?
Business process management is the discipline of writing down how work actually moves through a company, improving it deliberately, and then making the improved version executable by software rather than dependent on people remembering it. The written model is the deliverable that outlives everyone involved.
What is BPMN and why does it matter?
BPMN — Business Process Model and Notation — is the international standard notation for process diagrams, published by the Object Management Group and standardised as ISO/IEC 19510. It matters because it is readable by both management and developers, and because a BPMN model can be executed by a process engine rather than filed as a picture. Using a standard also means the model can be handed to any competent party later, including one that is not us.
Why do BPM projects fail?
According to the BPM Study 2023, the leading causes are insufficient resources (67%) and weak management commitment (35%) — not software quality and not notation. In practice, projects fail when a tool is bought and handed to the operations team with no senior owner. That is why HYA engagements have one senior professional accountable throughout, and why we do not sell tools.
How long does a process redesign take?
The diagnostic phase is two weeks. The build depends on scope, but the useful mental model is that mapping and redesign are measured in weeks and implementation in months, not years — because we cut before we build, and a smaller process is a faster build.
Will automation remove our controls and approvals?
No, and it should not. Well-designed automation concentrates human approval at the few points that carry real risk rather than scattering it across every step. In the platform we built and measured, 45 processes contain an explicit human approval or signature step, each addressed to a named role rather than a shared inbox.
Do we need to replace our existing systems?
Frequently not. Many engagements end with the systems you already own configured correctly and integrated, plus automation on top. Replacement is a recommendation of last resort, and because we sell no licences we have no incentive to reach for it.
Start with a Process Audit.
Two weeks looking at how your company actually works. You get the map, the bottlenecks that cost you most, and a costed plan to fix them in order of return — including whether the answer is software at all.
Two weeks · one senior consultant · scope and fee agreed before we start · you own the output either way.