Executive roadmap

Prove the foundation. Scale the path. Retire the burden.

We are proving SP Foundation while supporting the products and retirement work the business depends on today.

Active now

Current support portfolio

These workstreams are being supported today. That does not mean their Foundation adoption or retirement is complete.

Product

LCMS

Active support

Product

SP Live

Active support

Product

Talent Marketplace

Active support

Retirement

Legacy retirement

Active support

Retirement

Streaming Teacher retirement

Active support

Progression

Each stage earns the next.

Capacity and recovery proof create confidence. Evidence makes that confidence demonstrable. Adoption compounds the value. Simplification removes the old paths we no longer need.

  1. ProveCapacity · resilience · self-service
  2. EvidenceControls · training · sign-off
  3. AdoptProducts · pods · SP Dev
  4. SimplifyMigrate · retire · reduce burden

Only Prove and Evidence are date-bound here. Adopt and Simplify are directional until their schedules are approved.

Four stages

The detailed roadmap.

Every phase has a purpose, concrete work, and evidence that tells us when it has achieved its intended outcome.

Phase 1 · Prove

Now through September 30, 2026

SP Foundation

  • Prove twice-peak RPS capacity
  • Implement release-health detection and rollback
  • Complete the pod self-service demonstration
  • Define the production-readiness standard

Compliance kickoff

  • Finalize required internal policies
  • Publish and assign acknowledgements
  • Launch workforce walkthroughs and training
  • Establish the GDPR gap and evidence tracker

Phase 2 · Evidence

October 1–31, 2026

Complete the agreed scope

  • Reach 100% acknowledgement and training completion
  • Close every critical and high-priority GDPR gap
  • Give lower-priority items an owner, date, and risk decision

Demonstrate operation

  • Validate privacy and incident procedures in practice
  • Centralize supporting evidence
  • Obtain appropriate organizational sign-off

Phase 3 · Adopt

Next · directional

Deepen adoption

  • Advance Foundation adoption across supported products as readiness and sequencing are approved
  • Expand pod self-service to more services
  • Make supported capabilities easier to discover and consume

Make the path discoverable

  • Turn SP Dev into the product interface for consuming Foundation capabilities
  • Connect documentation, templates, automation, and supported services

Phase 4 · Simplify

Then · directional

Complete retirement work

  • Carry current retirement support through approved migration and decommission plans
  • Complete Streaming Teacher retirement when its exit criteria are met
  • Migrate, replace, or remove remaining Legacy workloads

Reduce the burden

  • Decommission obsolete infrastructure and delivery paths
  • Track reductions in risk, operating work, and infrastructure cost
  • Consolidate on supported paths
The adoption interface

SP Dev makes the paved path usable.

SP Dev should not sit beside the platform as a separate experiment. It is intended to become how pods discover, understand, and consume SP Foundation capabilities.

Future-state language

SP Dev is intended to become this product interface. The roadmap does not claim that the complete experience or full adoption already exists.

Related delivery work

Individual migration is one visible step in simplification.

Moving customers safely requires dependable migration infrastructure before the larger cutover. The work is tracked operationally in Jira and documented in this repository.

Build the migration job and completion-reporting layer

SPPLT-17956 covers the isolated queued job, independent lock, failure report, and dedicated infrastructure needed for reliable individual-customer migration runs. It is one implementation slice within the larger migration epic—not the full migration.

Status and schedule can change. Jira remains the source of truth for the current owner, acceptance criteria, dependencies, and delivery state.

Exit evidence

How we know a phase has done its job.

Prove

Load-test result, game-day record, service configuration coverage, and a pod-led production operation.

Evidence

Completed acknowledgements and training, closed priority gaps, process walkthroughs, and approved sign-off.

Adopt

Products using Foundation capabilities and pods completing the operating loop through the supported interface.

Simplify

Obsolete paths decommissioned and measurable reductions in risk, operational burden, and infrastructure cost.

Exploration

Fun Side Projects

No side projects are listed yet.

Next chapterSee the ownership model that makes independence safe.
Explore how we work →