Reference method

How to write a procedure: the Sinfony method in 8 steps

Writing — or simplifying — a procedure is not something you improvise: it is a craft and a method. Here is the Sinfony method, in 8 steps, from raw material to the RACI and the learning path.

In brief

To write a clear procedure, you don't write as you go: you follow a method. The Sinfony method structures this work in 8 steps, from raw material to the RACI and the learning path. It works for simplifying what exists as much as for creating from scratch.

  1. Normalise the language
  2. Unify the glossary
  3. Clean up the administrative content
  4. Break into knowledge grains
  5. Classify by level — why / what / how
  6. Link to the process and set the foundational RACI
  7. Detect redundancies and contradictions
  8. Rearrange towards the target architecture
The method

The 8 steps, in detail

1. Normalise the language

One language, one action style: action verbs, short sentences, zero ambiguity. This is the condition for a procedure that is genuinely applicable.

2. Unify the glossary

One term = one meaning. You remove floating synonyms and undefined acronyms, so that everyone understands the same thing.

3. Clean up the administrative content

You separate the useful content from the noise (headers, notices, version history). Anything that does not help at the workstation leaves the body of the procedure.

4. Break into knowledge grains

You fragment the content into knowledge grains: self-contained, reusable units of knowledge. One grain = one idea or one action, usable elsewhere without rewriting.

5. Classify by level — why / what / how

Each grain is filed by logical level: the why (the intent), the what (the rule, the procedure) and the how (the action, the work instruction).

6. Link to the process and set the foundational RACI

Each grain is linked to a process, and responsibilities are set by a foundational RACI: a single Responsible, a single Accountable, no vague collective.

7. Detect redundancies and contradictions

You remove duplicates, resolve conflicts between documents and reveal the knowledge-gap map: the critical actions that were written down nowhere.

8. Rearrange towards the target architecture

You recompose everything into clear deliverables: a flowchart, the RACI, and a 70/20/10 learning path linked to the procedure.

The vocabulary

The key terms of the Sinfony method

Sinfony method

The 8-step method for writing or simplifying a procedure: from raw material to knowledge grains, levels, the foundational RACI and the learning path.

Procedure grain

A self-contained, reusable unit of knowledge (one idea or one action), obtained by breaking documentation down. The basis of modularity and reuse.

Why / what / how levels

The logical classification of a grain: the intent (why), the rule (what) and the action (how). It avoids mixing policy, procedure and work instruction.

Foundational RACI

The RACI (Responsible, Accountable, Consulted, Informed) used as the foundation of responsibilities: a single R, a single A, reachable roles, no collective.

Knowledge-gap map

The inventory of critical know-how that is written down nowhere, revealed during simplification — so it can be captured before it disappears.

70/20/10 learning path

The skills-development model: 70% through practice, 20% through peers, 10% through formal learning — linked to the procedure and the RACI.

Create or simplify

The same method, both ways

Whether you start from an overloaded body of documents or a blank page, the 8 steps are the same. In simplification, Maestro applies the method to your existing documents (up to 80% less volume). In creation, it captures your experts' knowledge through interviews and observation, then produces procedures, RACI and training — even when nothing is written down.

Go further

Explore Maestro

Frequently asked questions

Your questions

How do you write an effective procedure?

By following a method rather than writing as you go: normalise the language, unify the glossary, break it into knowledge grains, classify by level (why/what/how), set the foundational RACI, remove duplicates and contradictions, then produce a flowchart, RACI and training. That is the Sinfony method in 8 steps.

What is a procedure "grain"?

A self-contained, reusable unit of knowledge — one idea or one action — obtained by breaking documentation down. Knowledge grains make a procedure modular: you recombine them without rewriting everything.

What is the difference between a policy, a procedure and a work instruction?

It is the logic of levels: the policy says why (the intent), the procedure says what (the rule and the sequence), the work instruction says how (the action at the workstation). Mixing them makes the document unreadable.

Do you need software to apply the method?

No, the Sinfony method is independent of any tool. Maestro automates it (breaking content into knowledge grains, RACI, knowledge-gap map, learning path) and lets you prove it on your own documents through the Flash Audit.

Does the method also work for creating from scratch?

Yes. The same 8 steps apply when starting from interviews and observation: you capture your experts' tacit knowledge and turn it into procedures, RACI and training, even when nothing is written down.

Proof, not promises

Test Maestro on your own documents

A fixed-scope Flash Audit: you walk away with concrete simplification leads, produced by Maestro.

Book a Flash Audit