From fragmented experience to collective intelligence.
Intelligence systems fail most often at the point where they stop listening and start asserting. This method is designed around that failure. Eight stages carry an experience from a first-hand account to a measured, retained lesson — and each one has an explicit limit: a line it must not cross.
- Stages
- 8
- Cycle type
- Closed loop
- Status
- Proposed method
The governing constraint
Every stage below states what it is not allowed to do. These are not footnotes. They are the part of the design that determines whether the system is worth trusting, and they are the reason the method can be published before it has been run.
A method with no stated limits is indistinguishable from a press release.
Eight stages, and what each one is forbidden to do
Read these in order. The loop matters more than any single stage: the eighth stage exists to feed the first, and a system that records outcomes without routing them back into listening is a filing cabinet, not a learning system.
01ListenCaptureCapture stakeholder experiences, needs, failures, and emerging opportunities in the participants' own terms.
Inputs
- First-hand accounts from across the ecosystem
- Existing research, industry data, and prior work
- Structured interviews, roundtables, and listening sessions
- Consent-based submissions through defined channels
What happens
- Design channels that reach people who are not already inside a network
- Record accounts with their original language, context, and framing intact
- Establish informed consent and a stated purpose before anything is collected
- Track representativeness of the record as it is built
Outputs
- A growing, consented corpus of first-hand accounts
- An honest assessment of whose experience is still missing
- A record of provenance for every item collected
Typically involved
Everyone in the ecosystem · Researchers and listening facilitators · Community and association partners
Limit
Listening does not establish that a problem is common. A single account is a signal to investigate, never a measurement of prevalence.
02StructureOrganiseTurn unstructured accounts into organised, contextualised signals without flattening their original meaning.
Inputs
- Consented accounts
- Contextual metadata
- Existing taxonomies and vocabularies
What happens
- Classify the substance of an account into a problem signal
- Preserve the original wording alongside any derived structure
- Record the industry, region, language, role, and scale context of each signal
- Flag near-duplicates and possible conflicts rather than resolving them silently
Outputs
- Structured signals with linked provenance
- A maintained taxonomy of problem categories
- A visible distinction between what was said and what was derived
Typically involved
Research and analysis staff · AI-assisted classification tooling · Subject-matter reviewers
Limit
Structure organises information. It must never quietly upgrade a report into a finding, or merge accounts that disagree into a false consensus.
03ValidateTestExamine evidence, corroboration, limitations, and counterevidence before anything is treated as established.
Inputs
- Structured signals
- Corroborating and contradicting material
- Comparative cases
What happens
- Assess source credibility and independence of corroboration
- Test whether the same cause explains multiple independent accounts
- Actively search for counterevidence and competing explanations
- State sample limitations and the population any claim applies to
Outputs
- An explicit evidence level for every signal
- Documented confidence, limitations, and disconfirming evidence
- A standing record of what would change the conclusion
Typically involved
Researchers · Domain experts · Independent reviewers · Practitioners with relevant experience
Limit
Validation raises or lowers an evidence level. It never produces certainty, and a large number of reports is not by itself proof of a shared cause.
04ConnectRelateLink related problems, stakeholders, causes, capabilities, and resources into a navigable structure.
Inputs
- Validated signals
- Stakeholder and capability records
- Existing interventions
What happens
- Map relationships between problems, causes, stakeholders, and resources
- Identify capabilities that could plausibly address a cause
- Surface near-duplicate problems described in different vocabularies
- Record the reasoning behind each relationship, not only the relationship
Outputs
- A connected graph of problems, causes, parties, and capabilities
- Documented reasoning for every asserted relationship
- Identification of connections that no single participant could see alone
Typically involved
Graph and knowledge tooling · Analysts · Domain experts
Limit
A connection is a hypothesis about relevance. It must carry the reason it was drawn, so that it can be challenged and later corrected.
05PrioritizeChooseDecide where investigation or intervention could create meaningful value, and be explicit about the reasoning.
Inputs
- Connected problem structure
- Evidence levels
- Stakeholder input
What happens
- Weigh severity, affected population, evidence quality, and urgency
- Assess feasibility, equity impact, leverage, and likely unintended consequences
- Consider what happens if the problem is left alone
- Publish the criteria and the uncertainties alongside the ranking
Outputs
- A ranked and explained shortlist
- A published record of the criteria used
- An explicit statement of what is not yet known
Typically involved
Investigators · Stakeholder representatives · Policy and practice partners
Limit
Prioritisation is a judgement about attention under constraint. It is always revisable, and the reasoning must be visible so it can be contested.
06ActivateMobiliseBring the right people together around a defined intervention, with responsibilities made explicit.
Inputs
- Prioritised shortlist
- Capability and stakeholder records
- Available resources
What happens
- Define the intervention precisely enough to be tested, including what it is not
- Identify who can responsibly implement it, and who must consent to it
- Establish a baseline before anything changes
- Agree success metrics, evaluation timeframe, and how feedback will be handled
Outputs
- A defined intervention with an owner and a baseline
- An agreed measurement and review plan
- A record of the assumptions the intervention rests on
Typically involved
Implementing organisations · Practitioners · Communities affected · Researchers
Limit
Activation transfers responsibility to the people who can act. The system does not implement on the industry's behalf, and does not present participation as endorsement.
07MeasureAssessEstablish what actually changed, against a baseline that was defined before the intervention began.
Inputs
- Pre-intervention baseline
- Outcome data
- Qualitative feedback from participants
What happens
- Compare the outcome against the agreed baseline, not against a general impression
- Capture what did not change alongside what did
- Assess whether the result is attributable to the intervention or to something else
- Note any unintended effects, including on groups not originally targeted
Outputs
- A measured outcome with an explicit baseline
- A record of what did not change and why
- An honest assessment of attribution and its limits
Typically involved
Evaluators · Implementing organisations · Affected communities
Limit
Measurement without a pre-agreed baseline is an anecdote. Where attribution is weak, the result must be reported as association, not effect.
08LearnRetainPreserve verified outcomes, uncertainty, failures, and reusable lessons — and feed them back into listening.
Inputs
- Measurement results
- Participant feedback
- Failed and abandoned attempts
What happens
- Record what was attempted, why, by whom, and against what baseline
- Capture what did not work, and the reasoning that led to it
- Assess whether a lesson transfers to a different context or region
- Route reusable findings back into the listening and structuring stages
Outputs
- A reusable learning record, including failures
- An updated evidence base for future investigations
- A closed loop from completed work back to new listening
Typically involved
Researchers · Implementing organisations · Practitioner communities
Limit
Learning is only real if it changes future practice. A recorded outcome that no future investigation consults is documentation, not learning.
Why the eighth stage is the most important one
Most research fails quietly. A finding is produced, a report is written, the report is filed, and six months later the same question is asked again from scratch — this time by someone who has never heard of the previous work. That is not a knowledge problem. It is a routing problem, and it is fixable by design.
Every completed intervention produces a record, including the ones that failed.
Each record states what would need to be true for its lesson to transfer elsewhere.
Reusable findings are routed back into the listening stage, not just into the archive.
Nothing is generalised beyond the context in which it was learned.
Method at a glance
- ListenCapture
- StructureOrganise
- ValidateTest
- ConnectRelate
- PrioritizeChoose
- ActivateMobilise
- MeasureAssess
- LearnRetain
Stage 8 feeds stage 1. The loop only closes when learning returns to listening.
The record
What every completed intervention has to preserve.
An intervention that is not measured produces an opinion. An intervention that is measured but not recorded produces nothing at all. The loop above only closes when the record survives the project that produced it — which is what the nine fields below are for.
A static information platform collects. A learning system returns its conclusions to the people who produced them, and changes what it looks for next.
What every completed intervention preserves
A result without its context cannot be reused. Each intervention closes with a record that carries the reasoning, the baseline, the negative findings, and the limits of what may be concluded.
- 01What was attempted
- 02Why it was attempted
- 03Who was affected
- 04What the baseline was
- 05What changed
- 06What did not change
- 07What evidence supports the conclusion
- 08What limitations remain
- 09Whether the learning transfers to another context
Two things follow from taking this seriously. Failures must be recorded as first-class results, not quietly dropped. And a lesson must never be generalised past the context in which it was learned — which is why transferability is itself a field.
What the method deliberately does not do
It does not optimise for the most visible problem.
Visibility, capital, and attention in this ecosystem follow measured revenue and public profile. A system that ranks by volume of complaint would rediscover the same well-resourced stakeholders every time and call the result a map of the industry.
- It does not claim to know which problems are most common before it has looked.
- It does not treat silence as satisfaction, or absence of complaint as absence of problem.
- It does not publish identifiable accounts, allegations, or commercial intelligence about named parties.
- It does not present a hypothesis, a correlation, or a finding as the same kind of thing.
- It does not succeed on the volume of activity it generates, but on whether the ecosystem is measurably more capable afterwards.