Playbooks and field notes
Curated learning from Action Labs and practitioners: what was tried, what failed and what conditions mattered.
Governance Collective
The Collective is not an open upload platform. Its value comes from curation.
We are not trying to list thousands of solutions. We are building high-potential, curated and context-aware solution pathways around real governance problems.
Solution pathways
Evidence-aware pathways around specific problem statements, with adoption conditions and failure notes.
Requests board
Structured needs from districts, fellows and governance actors seeking advice, solutions or collaborators.
District canvas
A living picture of what is happening, pending and possible in a district or local operating context.
People and organisations
Verified profiles of practitioners, mentors, solution providers and partner institutions.
Learning commons
Case-based learning capsules and guides for working with government.
Knowledge object model
The Collective should make practical learning reusable without stripping away context.
Each object has a different job. The common discipline is specificity: problem statement, conditions, evidence, failure notes, review status and visibility level.
Case note
Short learning from a field situation: context, what was tried, what changed, what failed and what conditions mattered.
Solution pathway
A problem-specific route that combines workflows, actors, evidence, adoption conditions and implementation risks.
Request
A structured need from a public actor or practitioner seeking advice, collaborators, models or evidence.
Learning capsule
A 30-45 minute unit that turns reviewed field learning into role-specific capacity building.
Curation pipeline
Field learning becomes public knowledge only after review.
The Collective is designed as a high-trust knowledge layer. Raw logs, operational notes and sensitive field material should never move directly to the public website.
01
Capture
Collect field notes, review observations, practitioner inputs and problem statements.
02
Synthesise
Convert raw material into a structured case note, pathway or request.
03
Review
Check evidence, sensitivity, contributor permissions and adoption conditions.
04
Publish
Release only the public-safe knowledge object with clear limits and attribution.
05
Reuse
Feed the learning into Action Labs, GovCap modules and partner conversations.
Quality bar
Every published entry should help someone who was not part of the original work understand whether, how and under what conditions the approach may be useful.
Required evidence
Specific problem statement, field conditions, adoption pathway and evidence level.
Required honesty
Failure notes, implementation risks and conditions under which the approach should not be copied.
Contributor verification comes before publication.
The Collective depends on trust. Contributors, solution providers and practitioner profiles should be verified before public display, and the reviewer must be accountable for what moves from private workflow to public knowledge.
Before review
Inputs stay private until the contributor, source, evidence level, sensitivity and permissions are clear.
Before publication
Entries need a named reviewer, visibility level, attribution rule and explicit statement of adoption conditions.
Access model
Different knowledge objects need different levels of access.
The public website should explain the Collective without exposing operational detail before workflows, permissions and review responsibilities are mature.
Public
Mission-safe explainers, curated summaries, learning capsules and non-sensitive solution pathway previews.
Verified network
Practitioner profiles, deeper playbooks, requests and working notes for trusted contributors and government-facing partners.
Restricted
Operational logs, identifiable field material, counterpart-specific notes and politically or administratively sensitive information.