Discovery synthesis
Brings every source together into a narrative of the real process, with evidence, discrepancies and pain points.
Command: /ef:discovery-synthesis · Methodology: Is2Be Process · Phase: Phase 2 · As-Is discovery
When to use it
Section titled “When to use it”Once discovery evidence is in; it is the direct input to the As-Is model.
It’s working if
Section titled “It’s working if”- Every statement carries at least one source tag.
- Contradictions between what’s declared and what’s done appear as discrepancies, without picking a side.
- Opinions are separated from facts, with the number of independent sources counted.
Where it fits
Section titled “Where it fits”- Before: Interview, workshop or observation guide, Existing documentation analysis, Event log analysis (process mining)
- After: As-Is model
Requirements
Section titled “Requirements”-
Your AI connected to the service with your licence key (how to connect).
-
The project set up once with
/ef:setup. -
The outputs of the previous steps (see Where it fits).
Why doesn’t it pick a version when sources disagree?
Because the contradiction is a finding. The gap between the procedure and what people actually do is usually where the problem lives; it’s resolved with the people in the validation workshop.
Can I give it full transcripts?
Yes, anonymized. The more concrete the evidence (real cases, figures with a period), the better the synthesis.