Field review finds SLED experimentation broadening faster than capacity, strategy, and outcome evidence

Problem and stakeholders: State and city CIOs, program owners, budget and procurement leaders, universities, and civic partners may have many pilots but insufficient sustaining capacity.

Discovery

Which experiments have an operational owner, baseline, funding, and evidence for graduation or closure?

Value hypothesis

Matching scope to local capacity could improve portfolio decisions and reduce unsupported expansion.

Potential engagement

Review a bounded portfolio and assess one shared-platform or service-integration candidate.

Evidence boundary

The qualitative review and legislation counts describe activity and experience. They do not establish causal return, the success rate of all pilots, or a universal preference for state sandboxes or city stand-alone tools. Transfer depends on staffing, data, and service conditions.

Fit

Consider shared model/data services where states can operate common controls and narrower integrations where cities have limited capacity.

Architecture

Reuse approved identity, data boundaries, model access, evaluation, logging, and incidents while keeping service accountability explicit.

Prerequisites

Scoped workflow, data readiness, support skills, budget, and partner stewardship agreements.

Constraints

A walled garden is controlled only if maintained; procurement and integration effort may dominate model choice.

Security

Verify approved data paths, partner access, confidentiality, and exit arrangements.

Proposed validation

Run representative tasks, measure quality and operational effort, and have the intended support team handle a failure and model change. Demonstrate maintainability rather than accepting a successful initial demonstration as production readiness.

Work and dependencies: Record hypotheses, baselines, funding, ownership, dependencies, and graduate/stop/continue decisions in the portfolio.

Ownership

Programs own mission outcomes; central technology and procurement provide shared controls; external partners have explicit data, access, intellectual-property, and exit duties.

Skills and adoption

Include scoping, service design, support, and workforce training before access expands.

Governance checkpoints

Review evidence and operating funds at graduation and capture lessons from stopped pilots.

Proposed acceptance

The workflow has measured service outcomes, staffed support, tested incidents, and an evidence-based decision.

Risks

Pilot counts and legislation can be mistaken for capability, partners can create dependency, and modest workflow benefits may not justify a platform local staff cannot sustain.