What this is
Process mapping documents how work actually moves through an organisation — not how it's described in a manual, but who genuinely does what, in what order, through which systems, and where it stalls. Most operations carry a gap between the two, and that gap is where the cost usually lives.
Map before you automate. Skipping this step is the most common reason automation and AI projects fail to deliver — they take an existing failure and run it faster, at scale.
What's produced
- Current-state process maps — BPMN notation, showing every step, handoff and decision point as they actually occur
- RACI matrices — who is Responsible, Accountable, Consulted and Informed at each step, which frequently surfaces steps with no clear owner at all
- A ranked improvement backlog — findings ordered by effort against quantified impact, not a flat list of observations
- A savings roadmap — the case for each recommendation, in hours or cost, before any implementation spend is committed
The process
- Scoping — the process or function in scope is agreed, along with what "done" looks like for the engagement.
- Discovery — stakeholder interviews and a review of existing documentation and system data build the current-state picture.
- Mapping — the current state is documented in BPMN, with a RACI matrix layered over it.
- Analysis — waste, duplication and unclear ownership are identified and quantified.
- Backlog and roadmap — findings are ranked and costed, and delivered as the basis for what to fix first.
Timeline is set by the scope agreed at the outset and is confirmed project by project, not quoted generically.
What you need to provide, and where it comes from
- Existing process documentation, where it exists — SOPs, work instructions, or prior mapping — typically held internally or in a document management system
- A stakeholder list covering everyone who touches the process — usually pulled from an org chart or team structure
- Throughput or volume data — whatever system of record already tracks the work: an ERP, a ticketing system, a CRM, or manual logs where no system exists yet
- The specific pain point driving the engagement — what prompted the review matters for scoping it correctly
Why this approach
GENCO's positioning on this is deliberately narrow: map first, automate second. That sequence is what separates process work that produces a real, defensible number — hours saved, cost avoided — from generic consultancy that produces a slide deck and nothing measurable afterward.
Common questions
What is process mapping?
Documentation of how work actually happens — who does what, in what order, using which systems — represented in BPMN so that waste and bottlenecks become visible rather than assumed.
Why map before automating?
Automating a broken process makes it fail faster and at greater scale. Mapping identifies what's actually worth automating, what should be eliminated, and what needs redesigning first.
What does a RACI matrix add?
It names who is accountable at each step. It's common for a process map to reveal a step nobody is clearly responsible for — that's usually where delay accumulates.
How is the backlog prioritised?
By effort against quantified impact, so the highest-return fixes are visible first rather than buried in an undifferentiated list.