Which product boundaries should be set for levels, spaced review, and certificates?
Plan levels, paths, vocabulary or skills practice, lessons, assessment, spaced review, progress, live instruction, peer practice, streaks, and certificates. Treat levels, paths, and spaced review as one operated product boundary. A credible first release makes certificates observable and defines how exceptions involving streaks are recovered.
Best for: Teams planning Language Learning Platform that need to agree on levels, spaced review, and certificates before detailed scope.
The first release should connect levels to certificates and expose a clear recovery path for exceptions involving streaks.
Good fit / poor fit
Test whether levels and spaced review require an operated product
This topic is specific enough when levels has durable state, spaced review changes that state, and the team can own exceptions around streaks while observing certificates.
Good fit when
Language Learning Platform needs a durable workflow connecting levels, spaced review, and observable evidence for certificates.
People in the learner role need a repeatable path from vocabulary or skills practice through spaced review.
The learning team must govern paths and intervene when exceptions involve streaks.
Progress can be observed through certificates, not merely visits or screen activity.
Choose a narrower model when
An existing tool or simple information surface can already handle levels without owning its lifecycle.
paths does not need separate permissions, history, or accountable state.
No operated workflow must connect vocabulary or skills practice to spaced review.
The team cannot yet name who resolves exceptions around streaks or what evidence is needed for certificates.
End-to-end workflow
Trace levels through spaced review and evidence for certificates
Use one representative Language Learning Platform journey. Keep paths, exceptions around streaks, and manual operator work visible so the release boundary reflects the real product rather than an idealized happy path.
1
Frame Vocabulary or skills practice
Learner
A person in the learner role enters with vocabulary or skills practice and enough context to begin working with levels.
Learning team
The learning team function defines eligibility, ownership, and the initial state for levels.
Boundary question
Who may begin with vocabulary or skills practice, and what makes levels ready?
2
Establish Paths
Learner
A person in the learner role creates, selects, or confirms paths before progressing.
Learning team
The learning team function validates permissions, quality, and lifecycle rules around paths.
Boundary question
Which version of paths is authoritative, and which changes need history or review?
3
Operate Spaced review
Learner
A person in the learner role moves through spaced review with visible state, next actions, and feedback.
Learning team
The learning team function observes progress, stalled work, and interventions that cannot be safely automated.
Boundary question
Which state changes prove progress through spaced review, and where does progress branch?
4
Handle Streaks exceptions
Learner
A person in the learner role receives a clear recovery path when an exception involving streaks interrupts the expected journey.
Learning team
The learning team function resolves the exception, records the result, and captures evidence for certificates.
Boundary question
Who owns exceptions around streaks, and what evidence is needed for certificates?
First-release boundary
Scope the smallest release that makes certificates observable
The first release of Language Learning Platform should connect vocabulary or skills practice to certificates before expanding every variant of live instruction, integration, automation, or reporting need.
Prove in the first release
Name one primary learner segment and the exact role of levels in its journey.
Model the minimum state and permissions needed for paths and vocabulary or skills practice.
Implement one complete path through spaced review, including the essential branch around progress.
Give the learning team a practical way to detect, inspect, and recover exceptions involving streaks.
Capture evidence of certificates so the team can continue, narrow, or revise the product boundary.
Hold until evidence justifies it
Additional audiences, variants, and advanced permissions around levels and paths.
Automation, integrations, and optimization for live instruction before the core workflow is reliable.
Sophisticated reporting or personalization beyond the evidence needed to verify certificates.
Decisions that materially change effort
The number of roles and permission boundaries controlling levels and paths.
Lifecycle branches, approvals, reversals, and recovery paths across spaced review and progress.
Operational exposure when exceptions involving streaks occur repeatedly or at scale.
External systems that create, change, or depend on vocabulary or skills practice or live instruction.
Audit, accessibility, availability, localization, and support expectations attached to certificates.
Trust, exceptions, and operations
Assign ownership for spaced review, exceptions around streaks, and certificates
The interface for Language Learning Platform is only the visible layer. The operating model must also govern levels, keep paths trustworthy, and make recovery from exceptions involving streaks practical.
Ownership of Levels
The learning team function needs explicit rules for creating, changing, and retiring levels while keeping paths consistent.
Who creates or approves levels, and which roles may change it?
What happens when levels and paths disagree?
Which changes need history, notification, approval, export, or deletion controls?
Control of Spaced review
Every important transition through spaced review needs a visible owner, especially where progress changes the normal path.
Which states make progress through spaced review visible to each role?
Where can progress be automated safely, and where is review required?
How is duplicated, abandoned, or contradictory work returned to a valid state?
Recovery for Streaks exceptions
A credible release makes exceptions involving streaks visible, gives the learning team a workable response, and preserves evidence for certificates.
What can the learner do when an exception involving streaks occurs without contacting support?
Which evidence does the operator need to investigate and resolve exceptions around streaks?
Which signal demonstrates certificates without relying on vanity metrics?
Useful next steps
Turn the planning boundary into an evidence-backed first release
For Language Learning Platform, use the Learning Platform guide to verify the wider product model, then choose whether a quick range or a detailed plan is the useful next step. These links are limited to routes that advance this decision.
Plan tutor and learner roles, subjects, matching, availability, bookings, packages, live or in-person sessions, notes, assignments, progress, payments, and safeguarding.
Planning basis and review
A complete catalog brief with room for deeper research
This page is generated from the reviewed WebGrid opportunity catalogue and application-type decision model. The baseline was reviewed 17 August 2026; its next scheduled review is 17 February 2027.
This guide defines product responsibilities. Payment, tax, consumer, identity, privacy, and marketplace obligations depend on jurisdiction, provider configuration, contracts, and operating choices; verify them with the relevant specialists.