# See who does what, at last.

Mapping and RACI are derived from your own documents, then corrected in a workshop. The opposite of a six-month BPM project.

## The problem

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.

## The walkthrough

The walkthrough 2 min 51 — click to play. The video only downloads at that point.

[Download the video (MP4)](/assets/videos/module-2.mp4)

**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.

## What the module does

Seven functions, as they appear to the people who use them.

1

### Every grain is attached to its process

Information scattered across twenty documents regroups by real process, not by folder tree.

2

### The RACI comes from reading, not from a workshop

Activities are extracted, ordered and grouped into phases. You start from an argued draft, not a blank page.

3

### One R and one A per activity

The rule is applied and checked. Every breach becomes a workshop question — which is where the discussion becomes useful.

4

### Business rules are separated from activities

An obligation, a frequency or a threshold is not a task: it is isolated and linked to the activity it governs.

5

### Every anomaly becomes a question

Two owners on one activity, a collective role, a consultee everywhere: the module flags them instead of deciding for you.

6

### The logical level is assigned

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.

7

### Flowchart and export

The process described simply, with swim lanes per role, and a RACI you can export to a spreadsheet for the meetings that demand one.

## Two kinds of company, two uses of the same module.

Regulated large enterprises

### A defensible RACI, in weeks rather than quarters.

Your processes are already described somewhere — badly, and in ten places. The module rebuilds them from your documents, and you arbitrate.

-   A draft drawn from reality, not from participants' memory
-   Ownership ambiguities surfaced explicitly
-   A deliverable that stands up in an inspection

Expert SMEs & mid-market

### The RACI you could never afford to build.

You will not spend three days in a workshop with a consultant. The module does the heavy lifting; you keep only the arbitration.

-   No three-day workshop to fund
-   The areas where two people both think they are responsible
-   A base that updates instead of ageing

[RACI: definition, example and 9 best practices →](/en/generate-a-raci/)

## The nine Maestro modules

Each module is sold and used on its own. See how this one fits with the other eight.