Skip to content

Shared infrastructure for implementation

Evidence does not
implementitself.

Strong interventions often lose force somewhere between a research finding and everyday classroom use. Open Implementation is shared infrastructure for that difficult middle: helping people prepare, coordinate, try, adapt, document, and improve — without reducing implementation to compliance or a single fidelity score.

Figure 1 — The implementation gap

The chain from evidence to sustained practice

An effect found under study conditions has to survive selection, scheduling, training, timetables, staff turnover, and a thousand small judgement calls. Each link is a place where force can be lost.

  1. 01

    Research finding

    Effect established in study conditions

  2. 02

    Program or practice

    Materials, routines, training

  3. 03

    Local adoption

    Selection, purchase, scheduling

  4. 04

    Everyday use

    Real classes, real constraints

  5. 05

    Sustained practice

    Still working three years later

Where force is lost — the recurring missing work

  • Judge fit
  • Prepare people
  • Coordinate learning
  • Enact
  • Reflect
  • Respond
  • Adapt
  • Learn across contexts
The chain rarely breaks at the evidence. It breaks in the unfunded, undocumented work between adoption and sustained use.

Roles

Four pathways, four different jobs

Implementation is not one task performed by one kind of person. Each role carries a distinct job, a distinct friction, and needs distinct competencies from shared infrastructure.

PATHWAY 01

Researchers & intervention developers

JobSpecify what must hold, learn how it travels, and see use beyond the trial.

FrictionOnce a study ends, the intervention leaves your line of sight. Variation arrives as anecdote, and the core mechanisms get lost in local retellings.

  • Express core components and permissible adaptation
  • Register measures and structured field tasks
  • See enactment evidence across participating sites
  • Export governed datasets for secondary analysis

PATHWAY 02

Teachers & educators

JobMake the practice work with these students, this week, without extra paperwork.

FrictionTraining happens once, far from the classroom. Afterwards the judgement calls are yours alone, and documenting anything feels like surveillance.

  • Short, purposeful learning tasks in context
  • Reflections that inform your next lesson first
  • Discussion with colleagues doing the same work
  • Visibility into what your data is used for

PATHWAY 03

Implementation leaders, coaches & interventionists

JobCoordinate learning across people and keep support proportionate to need.

FrictionYou are the connective tissue between a program and its use, usually with a spreadsheet and instinct rather than a shared picture of what is happening.

  • Configurable role-based pathways for cohorts
  • Feedback loops that surface where support is needed
  • Structured records of adaptation and rationale
  • Shared language for fit, capability and constraint

PATHWAY 04

District & system leaders

JobInvest in things that keep working after the launch year, and know why.

FrictionAdoption decisions are made with study effects and vendor claims; sustainment is measured by whether anyone complains. Data governance is an afterthought.

  • Portfolio view of implementation, not just purchase
  • Explicit data-stewardship and access boundaries
  • Evidence of sustained use, not launch-year activity
  • Comparability across schools without flattening context

Figure 2 — Implementation learning loop

A continuous loop, not a launch plan

Implementation does not end at rollout. The same six moves recur — at the scale of a lesson, a term, and a multi-site programme of research.

PREPAREENACTREFLECTRESPONDADAPTLEARN ACROSS CONTEXTSCONTINUOUSNOT A PHASE PLAN
Figure 2. The loop runs at several timescales at once — a lesson, a term, a cohort.
  1. 01

    Prepare

    Read the context, build shared purpose and capability.

  2. 02

    Enact

    Use the practice in real conditions, with real constraints.

  3. 03

    Reflect

    Look at what happened with structured, low-burden evidence.

  4. 04

    Respond

    Act on what the evidence says now, not next year.

  5. 05

    Adapt

    Change form deliberately while protecting the active ingredients.

  6. 06

    Learn across contexts

    Compare patterns across sites without flattening them.

Pathway

Extend what every partner can accomplish

See how the platform supports teachers, coaches and researchers today—and the capabilities partners can help shape next.

A working foundation already supports teacher learning, coaching and research. The next capabilities will help partners connect implementation support, learning and evidence across more roles and settings.

Live in TRANSLATEBuilt / under validationPlannedExploring with partners
  • Teachers

    Modules, sessions, reflections and submitted tasks.

    Live in TRANSLATE
  • Coaches and POD leaders

    Coach workspace, POD-scoped resources and reflection review (released 31 Aug 2026).

    Live in TRANSLATE
  • District and principal leaders

    Aggregate visibility of engagement, sessions and resources across authorized PODs and sites.

    Planned
  • Researchers

    See how participants engage with tasks, discussions, resources, reflections and coaching across the program.

    Live in TRANSLATE
  • Administrators

    Consistent reports for recurring questions, with visible choices behind AI-supported work.

    Planned

Technical foundation

A working foundation you can build on

Explore the core workflows, understand the architecture and help shape the next capabilities.

Built from real implementation work

Core workflows adapted from the live TRANSLATE platform bring learning modules, teacher reflections, coach review, private feedback, progress tracking and group exports into a working evaluation application.

A foundation for new capabilities

Partners can use this foundation to plan extensions to teacher and coaching workflows and explore how their intervention materials could fit. AI-assisted coaching, assessment integrations and district reporting are directions for future development.

Request the working application, setup guide and a technical walkthrough.

The current evaluation runs locally with invented personas and synthetic data. Production authentication and deployment remain development work; access terms and the final license are still being resolved.

RepositorySetup & documentationAccess may be required.

The technology

Familiar tools. An adaptable foundation.

  • React + TypeScript

    Typed interfaces for learning modules, reflections and coaching workflows.

  • Node.js + Vite

    A local evaluation server and fast development tooling, with no partner services required.

  • Automated checks

    Tests cover reflection handling, progress, coaching scope and access-denial cases.

  • Portable evaluation

    Synthetic content, local persistence and JSON/CSV exports let developers follow the workflow from input to output.

Projects & partnerships

Partnerships that move research into practice

We bring research teams, educators and technology together to strengthen implementation—and build tools that others can use.

From professional learning and coaching to AI-assisted feedback and assessment-informed instruction, our partnerships shape a shared platform for putting research to work. Bring a program, help develop a capability, or join a research initiative.

Licensing & governance

Shared improvements, protected context

Reusable platform improvements are intended to return to the shared codebase through review and agreed contribution terms. Program content, confidential configuration and participant data remain separately governed.

Shared

Reusable platform improvements

Interfaces, data models, construct definitions and interoperability specifications. Intended to return to the shared codebase through review and agreed contribution terms.

Licensed

Program content

Curricula, assessments and materials owned by their developers. Referenced by the platform, licensed on the developer's terms.

Private

Confidential configuration

How a district, school or program configures pathways, cohorts and supports. Visible to that partner, not the public.

Restricted

Participant data

Practitioner and student-linked records, held under consent and governance agreements. Access is granted, logged and revocable.

The license and reusable release are still in preparation. Reusable improvements are intended to return to the shared codebase through review and agreed contribution terms.

Join the work

Three ways in

Bring your program, explore implementation support, or help shape the next capability.

01

Evaluate the codebase

Request access, documentation and a technical walkthrough.

Request early access

Tell us more using the form below.

03

Participate

Reach out if you are a district, funder or researcher interested in collaborating on a specific aspect of this work, supporting a new function, or developing a grant initiative together.

Explore a collaboration

Tell us more using the form below.

What would you like to build?

Tell us about your research, your setting or what you hope to explore. We welcome conversations at any stage.

We use these details to respond to your inquiry. Please don’t include student records or confidential participant information.

Or write directly: lawrence.josh@gmail.com

Optional: repository — access may be required.