Product Strategy · EdTech · B2B · K–12
From Session Delivery to Driving Classroom Implementation
A product teardown diagnosing a K–8 math curriculum's Professional Learning program — and a measurement-driven model to fix it.
TL;DR
A professional learning program can be well designed, well attended, and highly rated — and still fail to change classroom practice. This teardown diagnoses why, and proposes a product-management approach to fix it.
- The PL program is optimized for session delivery, not behavior change — a structural gap, not a quality problem
- Every stakeholder operates with a partial view; information doesn't accumulate into a shared picture of implementation reality
- No instrument at any tier reliably answers whether teaching practice is actually changing in classrooms
- The root cause: PL is managed as a delivery model, not an outcome-driven product
- The fix isn't an overhaul — it's adding product management around a continuous discovery cycle
- A three-phase roadmap builds measurement infrastructure first, then adapts delivery based on evidence
PM Artifact Checklist — click to jump
The K–8 math curriculum's Professional Learning program provides implementation support to schools that have adopted the curriculum. The service is optimized to deliver sessions, not to determine whether sessions change classroom practice.
"Professional learning can be well designed, well attended, and highly rated, and still fail to shift practice. This gap is between what the service delivers and the outcome it is meant to produce."
Implementation signals are fragmented, infrequent, and difficult to act on across the adoption cycle. Facilitators — who have the closest view of teacher practices — have limited visibility into what happened before a session and no consistent way to capture what can be observed on site. Joyce & Showers (2002) found that professional learning has limited transfer to classroom practice without sustained coaching and follow-up.
The path forward is not a complete overhaul of the service model. It is a shift from an output-driven delivery model to an outcome-driven product orientation built around implementation health — defined as the extent to which target instructional practices are attempted, supported, sustained, and visible across the system.
What the Product Is
PL is a fee-based service delivered to K–8 districts adopting the core mathematics curriculum. Districts are the buyers; classroom teachers are the primary users. New adopters receive a structured sequence of facilitated sessions across three years, supplemented by on-demand digital courses.
Value Proposition: Intended vs. Actual
Intended
Move teachers from early adoption toward high-quality math instruction, achieving the curriculum's promise of improved student outcomes.
Actual
Deliver a sequence of professionally facilitated training sessions with content aligned to each implementation stage. Post-session surveys collect satisfaction data. Between sessions, districts manage implementation independently.
"The gap between Intended and Actual is not session quality — sessions are consistently well designed and delivered — but visibility into what happens once teachers leave the room."
Classroom Teacher — Primary User
| Job Type | Job |
|---|---|
| Functional | Implement the curriculum well enough that students engage and the classroom doesn't fall apart |
| Emotional | Maintain professional competence and identity through a transition they did not choose |
| Social | Be seen by their administrator, colleagues, and students as a capable, confident teacher |
Hall and Hord's Concerns-Based Adoption Model predicts that early adopters concentrate on self and task concerns. In early implementation, knowing what to do on Monday often matters more than understanding the underlying pedagogy. When the gap feels unmanageable, teachers often revert to familiar practices.
District Administrator — Buyer
| Job Type | Job |
|---|---|
| Functional | Justify the PL investment to stakeholders and confirm adoption is on track |
| Emotional | Avoid making a costly, visible instructional bet that doesn't pay off |
| Social | Be seen as a leader who made a sound, evidence-based curriculum decision |
PL Facilitator — Internal User
| Job Type | Job |
|---|---|
| Functional | Deliver prepared session content and support teacher engagement |
| Emotional | Feel equipped, credible, and effective in the room with teachers |
Facilitators typically arrive without detailed knowledge of what has been happening at the school site between sessions. Post-session notes are informal and not structured around specific aspects of implementation.
User Journey: The Implementation Lifecycle
Each stage is connected operationally — but what's observed at one stage rarely shapes the next.
"Each stakeholder operates with a partial view, and information generated across the lifecycle does not accumulate into a shared picture of implementation reality. That is not a gap attributable to any individual — it is a structural property of how the service is organized."
Ten instruments span three measurement tiers — but none reliably answers whether classroom practice is changing.
| Metric | Level | What it measures | What it cannot tell us |
|---|---|---|---|
| Renewal rate | Business | Whether districts recontract | Why — or whether implementation quality drove the decision |
| Expansion PL purchase | Business | Whether districts bought additional services | Whether demand reflects strong engagement or insufficient scoping |
| PL purchased vs. delivered | Business | Whether contracted sessions were completed | Whether delivered sessions produced any change in practice |
| Post-session NPS | Product outcome | Whether teachers found a session worthwhile | Whether anything changed in classroom practice — NPS measures perception, not behavior |
| Self-reported implementation survey | Product outcome | Teachers' self-estimated implementation behaviors | Whether self-reports reflect actual practice; twice-yearly cadence limits connection to PL delivery |
| Facilitator notes | Product outcome | Facilitator observations of session engagement | Comparable data — unstructured, not anchored to the framework, captures nothing between sessions |
| Session attendance | Product traction | Whether teachers showed up | Whether content transferred to classroom practice |
| Feature usage | Product traction | Whether teachers engage with digital components | Whether engagement produced any change in instructional behavior |
"Coverage does not mean completeness. No instrument at any level reliably answers whether implementation is occurring in classrooms."
Finding A
Structural mismatch — episodic model vs. behavior change research
The PL model is built around discrete sessions, with the expectation that teachers carry what they learn into independent practice. Joyce & Showers found that without coaching and follow-up, this model has limited impact. The outcome — sustained instructional change — is decided in the between-session period, when support is least available.
Finding B
Feedback and learning system gaps — data cadence and instrumentation
Information is collected throughout the implementation journey but doesn't feed back into how PL is conceived or delivered. The result: a service that generates data without generating organizational learning.
Finding C
Missing change infrastructure — inconsistent coordination across stakeholders
Fixsen's implementation science framework treats organizational conditions — leadership alignment, shared language, coordinated support structures — as prerequisites for implementation success. No structured framework exists to coordinate that alignment across accounts. Where coordination happens, it reflects local capacity and initiative, not a provided process.
Five whys tracing from inconsistent student outcomes to a single root cause.
"PL is managed as a delivery model, not as an outcome-driven product. Success is defined by whether PL is designed, scheduled, delivered, and rated positively — not by whether target instructional behaviors are changing in classrooms."
Much of the infrastructure for a more responsive system already exists: a nascent implementation framework, some implementation data collection, and expert professional learning facilitators. What's missing is product management around a continuous discovery cycle that defines behavioral outcomes, measures progress toward them, and adapts delivery based on evidence.
An output-driven model defines success by sessions designed, scheduled, and delivered. An outcome-driven model defines success by measurable changes in user behavior — in this case, teaching practices. Five behavior shifts follow:
Shift 1
Measuring outcomes: defined behaviors → measurement designed around them
Begin with the instructional framework, then ask how the service team will know if they are having an impact. Implementation progress becomes observable rather than assumed.
Shift 2
Facilitator role: fixed sequence delivery → implementation diagnosis
Facilitators currently arrive with prepared content and little knowledge of what's happened at the site since the last visit. An outcome-driven orientation makes implementation data the basis for session decisions instead.
Shift 3
Implementation visibility: episodic data → continuous practice signals
Replace end-of-session satisfaction signals with a regular cadence of behavior-focused check-ins that track how practice is actually changing.
Shift 4
Data synthesis: fragmented signals → shared implementation picture
Combine facilitator observations, satisfaction surveys, implementation surveys, and account check-ins into a coherent view of implementation health at the site level.
Shift 5
From delivery system to learning system
A service that measures outcomes and adapts support based on what's learned — rather than one that just delivers sessions and hopes for the best.
Success by User Type
| User Type | What Success Looks Like |
|---|---|
| Teacher | Attempts, refines, and sustains new instructional practices between sessions rather than reverting to previous habits |
| School Leader | Proactively supports implementation through planned walkthroughs and coaching — not just responding after problems surface |
| District Admin | Can point to implementation evidence, not satisfaction scores alone, when making support and renewal decisions |
| Facilitator | Adapts support based on implementation evidence rather than predefined content sequences |
Leading vs. Lagging Indicators
| User Type | Leading | Lagging |
|---|---|---|
| Teacher | Session attendance; intent to change practice (self-reported); facilitator-observed implementation barriers | Feature usage; self-reported implementation survey; facilitator classroom observations; planning tool utilization |
| School Leader | Implementation support plan established; attendance at PL sessions | Walkthrough frequency and focus; coaching notes; reported reduced variability across classrooms |
| District Admin | Implementation leadership plan established | Additional PL/coaching purchase; engagement with implementation reporting; reduced variability across sites |
| Facilitator | Adaptation of content based on prior site signals | Structured implementation observations |
"These indicators will only matter if they change how the organization acts before a renewal conversation, not during one."
| Constraint | What It Requires or Risks |
|---|---|
| Cost of data collection at scale | Real investment in new tools and maintenance overhead; skipping it reproduces today's fragmented signal at a larger scale |
| Measurement quality | The model depends on observation quality; weak inputs produce misleading implementation-health readings |
| Facilitator capacity | Facilitators vary in bandwidth and comfort with structured observation; training closes some of the gap, not all of it |
| Teacher trust | Classroom observation data raises legitimate trust concerns unless teachers see clear benefit and retain some control |
| District buy-in | Many districts already run their own PL systems; the implementation framework must earn its place against existing structures |
| Organizational coordination | PL, partner success, and sales need a shared view of implementation health — without it, facilitators never receive the signals they need |
"The choice is not between a costly new model and a free existing one — it's between two sets of trade-offs, one of which is currently opaque because of inadequate measuring tools."
Each phase advances only when evidence from the last one justifies it — sequenced to the school calendar.
Phase 1 · Spring / Summer
Measurement Foundation
Goal: Define target behaviors and establish structured data collection on existing touchpoints.
Structured facilitator session notes, automated post-session intent surveys, pre-session progress surveys, and existing product usage signals — reframed, not replaced. Three small experiments run in parallel: survey framing variance, between-session check-in pilots, and low-stakes classroom observations.
Evidenced by: Published framework, consistent structured capture, and early working-group signals worth building on.
Phase 2 · Fall → Spring
Model & Facilitator Adaptation
Goal: Synthesize data into an implementation-health view; enable facilitators to adapt sessions based on evidence.
Build an Implementation Health Model from Phase 1 data streams. Test model validity with facilitators and ISTs. Develop a facilitator menu of session adaptations focused on emphasis and questioning — not wholesale content changes.
Evidenced by: Active model use in pilot accounts, facilitator-reported value in session prep, and early signs of variation in how teachers respond.
Phase 3 · Spring Onward
Scale & Iterate
Goal: Expand the model across accounts and refine based on system-wide implementation learning.
Working-group reviews now informed by cross-account patterns. Identify which behaviors predict sustained implementation. Future work: greater content modularity and district-level views for renewal decisions grounded in implementation evidence.
Guiding principle: Scaling before proof risks embedding a tool that doesn't work — expansion follows evidence.
"The roadmap is best read not as a fixed plan but as the continuous discovery cycle in practice: each phase tests assumptions, generates evidence, and determines what the next phase should be."