How these notes are written

Structure

Most notes follow the same shape: what the thing is, why it is harder than it looks, the method, where the method misleads, and how to tell whether it worked.

The sections on what does not work are not optional. A description of process discovery that omits the filtering problem describes a picture that is partly an artefact of its settings.

Aggregation by default

A principle running through the collection: almost every process question is answerable at role or team level.

The resource column is where individual attribution enters, and these notes recommend aggregating it at ingestion unless there is a stated reason not to. Handover analysis between teams is a specification finding; the same analysis between named people is a personnel matter, and conflating them costs the cooperation the log quality depends on.

The uncomfortable material

Most deployments produce diagrams and no change, for a small number of recognisable reasons.

Deviation is not error. Many variants are correct responses to circumstances the designed model never anticipated.

Simulation outputs are the least reliable thing these tools produce, and their inputs are frequently derived from elapsed times that include waiting.

Automating a step that should not exist is the most common expensive mistake this field enables.

Legal material

Descriptions of monitoring obligations, consultation requirements, retention limits and audit frameworks are general and jurisdiction-dependent. They are not legal advice and the notes say so.

Commercial position

No vendor material. No sponsored content. No affiliate links. No product rankings.