Possible next moves

These examples show how the priorities could become practical work. Some explore new approaches; others help governments adopt and sustain what works.

They invite discussion, partners, and support. This is not an announced funding program or an invitation to apply for a grant. Each card distinguishes the work proposed from its readiness; “Committed” requires an accountable owner.

Ways to advance the agenda

01

Adoption and sustained operation

Readiness: Exploring

Help governments adopt a durable product operating model

Work with a small number of government teams on a service they choose, improving delivery while establishing public product ownership, decision rights, mixed career and temporary roles, live-work coaching, and targeted procurement changes. Document what remains after outside support and what another government would need to adapt the approach.

Better service outcomes alongside public teams that can keep improving the service and share the operating choices that made it possible.

Whether live-work coaching, clear authority and product roles, mixed teams, and specific purchasing changes improve a government-defined service and leave usable capacity after outside support ends. Whether lessons transfer across states, or from states to federal agencies, remains a hypothesis to test.

Government teams must define the need and name accountable service owners, a baseline, and room to change how work is done. Build with existing delivery providers and practitioner networks, fund hands-on support and follow-through, and agree how to measure service and institutional results. No partners or pilots are secured yet.

Find a few government teams with a live service problem, then design time-bound support with existing providers and practitioners that leaves ownership and evidence inside government.

Government partnerDelivery capacityFundingResearch and validation
BuildOrchestrateProve
02

Development and testing

Readiness: Scoping

Prove a reusable public system through child welfare

Explore a working open-source Comprehensive Child Welfare Information System (CCWIS) with a state partner as a test of reusable public systems. Pair software with changes to agency practice and policy, then publish the code, decisions, costs, and adoption playbook for a second state to test what truly transfers.

More time for caseworkers to support children and families, less repeated procurement, and a reusable model for improving software, agency practice, and public ownership together.

Whether a government-owned team and shared steward can maintain a working service, improve caseworker and family experience, and help a second state adopt the core without repeating the first build.

A willing first state and affected practitioners, a scoped service and safe migration path, federal engagement, an accountable public owner, financing for maintenance, and a credible second-state adoption path. None is secured yet.

Bring together child welfare agencies, families and caseworkers, delivery teams, federal partners, and funders to test demand, scope a first deployment, and plan long-term stewardship and a second adoption.

Government partnerDelivery capacityFunding
BuildFundOrchestrateProve
03

Development and testing

Readiness: Exploring

Startup accelerator for public-sector infrastructure

Explore an accelerator for teams building foundational products and services public agencies repeatedly need. Pair patient support with government design partners and help teams navigate procurement, adoption, and long-term stewardship.

A stronger supply of reusable, public-interest infrastructure instead of one-off solutions rebuilt agency by agency.

Whether an accelerator with government design partners can help teams solve recurring public needs, find a viable adoption path, and build products that agencies can maintain and reuse.

Identify a specific recurring government need and why existing actors or funding paths do not meet it. Find an operator, patient funders, government design partners, and a credible path to procurement, adoption, and stewardship. None is secured yet.

Find government design partners, an operator, and funders to choose a first cohort around a defined public need and test whether the model helps products reach adoption.

FundingLead organizationGovernment partner
BuildFundOrchestrate
04

Development and testing

Readiness: Exploring

Build hands-on AI capacity inside congressional committees

Explore embedded technical practitioners working with congressional committee staff on actual legislative and oversight tasks. Pair model access with institutional context, independent evaluation, and a plan for staff to retain the ability to judge and use these tools after a placement ends.

More capable committees today and a grounded institutional understanding of how AI changes legislative, oversight, and policy work.

Whether embedded expertise improves specific committee work and leaves staff better able to evaluate AI claims, commission technical work, and exercise independent oversight after the placement.

A committee-defined task, willing staff and leadership, independent technical support, secure and ethically governed model access, evaluation against existing practice, and a plan for lasting staff capability. No placement is secured yet.

Find a committee-defined task and bring staff, embedded practitioners, and independent support together to design and evaluate a first placement.

Government partnerTechnical talentTechnology partnerDelivery capacity
BuildFundOrchestrateProve
05

Development and testing

Readiness: Exploring

Make privacy rules executable

Explore a bounded privacy-as-code demonstration in one real government data-sharing workflow. Translate human-approved rules on authority, purpose, access, minimization, and retention into testable controls, then publish safe tests and evidence of how they work. Encoding a rule also exposes legal and policy interpretations that people must resolve.

A practical way to inspect and enforce approved data-use limits while identifying where the law, workflow, and technical rules diverge. A first demonstration would not settle privacy policy or prove all data sharing is safe.

Whether a specific agency workflow can connect each approved data use to legal authority, enforce limits, reveal attempted misuse, and produce inspectable evidence without increasing exposure or burden.

A willing agency and bounded use case, approved legal interpretations, participation from affected people and oversight, tests of permitted and prohibited uses, human correction paths, and a steward for changes and maintenance. None is secured yet.

Find an agency data-sharing use case and bring together legal, privacy, program, engineering, and oversight expertise to design and test a first implementation.

Government partnerTechnical talentDelivery capacityFundingResearch and validation
BuildFundOrchestrateProve

See a concrete next step?

Describe a possible response to a public need, the outcome it could produce, and what would help. An idea can be worth considering before it has an owner.

Propose an opportunity