Our methodology
We look for bottlenecks holding a field back, choose an intervention that could loosen them, and test what changes. An intervention can combine more than one tool.
Identify opportunity spaces and the changes that would make new capabilities possible.
Make the constraint explicit. Check what others are already doing and where PL can add something.
Resource a bounded piece of work with a delivery plan and observable evidence.
Read the evidence, update the hypothesis, and continue, change course, or stop.
A program has one primary type and can draw on supporting types. Narrative, culture, and talent cut across the work.
Make bottlenecks and opportunities legible through maps, roadmaps, and benchmarks.
Browse orient interventions →Bring the right people into sustained work around a shared problem.
Browse coordinate interventions →Provide catalytic grants, prizes, fellowships, or other resources.
Browse resource interventions →Test whether an approach works through credible, inspectable evidence.
Browse prove interventions →Help useful work reach adoption through capability, standards, and deployment support.
Browse enable interventions →This catalog uses Orient, Coordinate, Resource, Build, Prove, and Enable from the Economies & Governance draft. The unpublished Impact Preview and the Interventions Console currently use seven labels: Legibility, Connection, Funding, Policy, Infrastructure, Translation, and Culture. Public classification here is reviewed edition metadata. Operational Console types are unchanged.
Fields move with or without PL. We name the work we run and watch whether the field moves. Field-level attribution is not cleanly identifiable; making that link clearer remains research work. A hypercert, dataset, or report can evidence a program — it is not the intervention itself.
Browse the catalog →