Planning (DPE)Facilitation (Pronoia)Analysis (DAE)· researcher, facilitator, developer-partner

Ecosystem overview

The Delphi ecosystem is three products that form one pipeline but also work apart:

Planning (DPE) Delphi Planning Ecosystem (DPE) — the research design: orientation, phenomenon, panel and question architecture.

Facilitation (Pronoia) Pronoia, descriptive facilitation — running the panel: rounds, dialogue, the pause, and descriptive reports.

Analysis (DAE) Delphi Analysis Ecosystem (DAE), interpretive analysis — in-depth analysis of the collected data under quality gates and human review.

The pipeline runs as handoffs: Planning → Facilitation (Pronoia) → Interpretive analysis (DAE). Each part can also be used on its own.

🗺️ Interactive ecosystem map: open the visual, clickable overview — tabs, phases, quality gates and foundations. Offline, projectable.

Getting started

Type metodix (in Claude Code /metodix) — it opens the Metodix start menu and routes you to the right part of the ecosystem (planning · pre-analysis · DAE analysis · single method · resume). Everything begins there.

What do you want to do?

Design a study (orientation, panel, questions)
→ Planning (DPE) Run a panel: rounds, dialogue, reports
→ Facilitation (Pronoia) Interpret collected data in depth
→ Analysis (DAE) Understand how the parts connect end-to-end
→ Integration

Three levels: operate → delegate → system

You don't move up a level by gathering more knowledge — you move up by ceasing to do something by hand. That is the through-line of these guides: each part makes visible the one next line whose crossing actually raises your level — not "here is every feature".

Level 1

Operate

The ecosystem is a tool you use. You stop doing nothing yet — you do it yourself, just faster: design theses, open rounds, read the results.

Level 2

Delegate

You give the system tasks. Individual steps drop away: AI panelists, the R0 intake chat, PIRE round-gap suggestions, the AI helpdesk. You confirm.

Level 3

System

Infrastructure your work runs on. The whole chain leaves your hands: the plan flows as handoffs into facilitation and analysis (Plan → Pronoia → DAE).

The methodological guardrail stays. Delegation does not mean losing control: AI suggestions are drafts (they require an audit), interpretation happens in DAE under quality gates, and a panelist's speech/dictation is edited before sending. The arc runs operate → delegate → system, not human out of the loop.

Descriptive vs. interpretive — a key boundary

The most methodologically important boundary runs between Pronoia and DAE:

	Facilitation (Pronoia)	Analysis (DAE)
Role	Descriptive facilitation	Interpretive analysis
Question	What did the panel say and how did views move?	What does it mean?
Output	Distributions, central tendencies, consensus/dissensus, arguments as-is	Theming, scenarios, causal layers, synthesis
Authority	Source material	Methodological interpretive authority

A Pronoia report is not an analysis — it is the source material for one. "What it means" belongs to DAE, under quality gates (κ / QVG) and human review.

Where to go next

As a designer → Planning (DPE) (orientation, panel, questions)
As a facilitator → Facilitation (Pronoia) (rounds, dialogue, reports)
As an analyst → Analysis (DAE) (CP-0…CP-20, quality gates)
For the whole picture → Integration guide (handoffs end-to-end)