Bottleneck diagnosis
Find where cases actually wait using the log rather than the process diagram.
— Operations & Process
Computes activity volumes and profiles from an event log, then diagnoses bottlenecks, rework loops and variant paths with root-cause hypotheses and capacity gains.
1–2 weeks → ~15 minutes
For a full population, not a sample
No coding required
— USE CASES
Find where cases actually wait using the log rather than the process diagram.
Quantify rework loops and off-path variants that never appear in the documented process.
Attach a capacity gain to each bottleneck so remediation can be prioritised.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Each row of your export is processed on the same basis, so no process step is skipped however long the table is.
Ambiguities about the end-to-end process are resolved with you up front, so the run does not quietly assume the wrong scope.
Movement across the end-to-end process is visualised from the computed data, so the trend is legible at a glance.
Findings on the end-to-end process are written up as a document that reads like professional output, with each claim tied back to a process step.
Detail rows are summarised into the grouped view of the end-to-end process without losing the underlying process steps.
Event logs hold the truth about how a process really runs, and almost nobody has time to mine them. In practice it shows up as bottleneck diagnosis: find where cases actually wait using the log rather than the process diagram. The value sits in the rigour, not the typing — yet the rigour is exactly what gets traded away when there is only 1–2 weeks of capacity for it.
Here the same job runs as a Skill. Your material goes in; computed activity volumes and log profile comes out, alongside bottlenecks, rework loops and variant paths with root-cause hypotheses. The criteria, ordering and review points that make the answer trustworthy are encoded in the Skill itself — which is the difference between a structured method and a prompt someone pastes in. Net effect: 1–2 weeks down to ~15 minutes, no drift between runs, and every conclusion traceable back to the evidence behind it.
Process mining from event logs exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
Identifies where adoption of a new system, process or way of working stalls after go-live, with an evidence-backed report on barriers, workarounds and differences between functions.
Assesses AI readiness through anonymous staff evidence, identifying where AI can improve day-to-day work and the practical barriers that could prevent those gains.
Maps how an organisation actually operates using anonymous accounts from its people, producing an evidence-backed diagnostic of responsibilities, decisions, handoffs and duplicated effort.
Reads a set of weekly status notes for progress, blockers and RAG, charts the trend, and writes an executive digest focused on trajectory.
Reviews a proposed change against your change policy and returns a governed advisory decision — approve, approve with conditions, defer to the change board or reject — weighing risk, blast radius and rollback, with a change manager sign-off required before anything reaches production.
Assesses a refund or compensation request against the contract terms and refund policy that govern it, then returns a decision on approving it in full, in part, offering a goodwill gesture or declining, with every element of the remedy traced to the clause that allows it and anything beyond an agent's authority routed for review.