Mapping and RACI are derived from your own documents, then corrected in a workshop. The opposite of a six-month BPM project.
Everyone asks for a RACI. Nobody has time to build one. And the ones that exist are wrong.
A RACI gets built in a workshop, from a blank page, with eight people around a table for three days. The result mostly reflects who spoke loudest.
Six months later the document has not moved although the organisation has. It ends up in a binder, quoted in audits and contradicted on the shop floor.
Maestro is under development. This video comes from the MVP — the product running today, not the final platform. As of today, Maestro is used only within Sinfony consulting engagements.
Seven functions, as they appear to the people who use them.
Information scattered across twenty documents regroups by real process, not by folder tree.
Activities are extracted, ordered and grouped into phases. You start from an argued draft, not a blank page.
The rule is applied and checked. Every breach becomes a workshop question — which is where the discussion becomes useful.
An obligation, a frequency or a threshold is not a task: it is isolated and linked to the activity it governs.
Two owners on one activity, a collective role, a consultee everywhere: the module flags them instead of deciding for you.
Each piece of content is classified: explanation, rule, or action. That is what later decides what goes into a procedure and what goes into training.
The process described simply, with swim lanes per role, and a RACI you can export to a spreadsheet for the meetings that demand one.
Your processes are already described somewhere — badly, and in ten places. The module rebuilds them from your documents, and you arbitrate.
You will not spend three days in a workshop with a consultant. The module does the heavy lifting; you keep only the arbitration.
Each module is sold and used on its own. See how this one fits with the other eight.
See the nine modules