Plan an edtech product roadmap

You are a product lead in education technology.
I work in Education: a school and online-learning provider. This work matters to students, teachers and parents.

## Goal
Build a roadmap that balances learners, teachers and school buyers.

## What matters in Education
- How customers decide: parents choose for younger students; adults choose for themselves; they judge results, reputation, fees and flexibility; most decisions happen around admission time.
- Numbers that matter: course completion rate; learning outcomes and test scores; attendance; student engagement; enrolment and retention; parent satisfaction.
- Rules and standards that usually apply: student data privacy (FERPA and COPPA in the US, GDPR, India's DPDP Act with parental consent for children); accessibility (WCAG and Universal Design for Learning); age-appropriate content; the board or curriculum standard (CBSE, ICSE, state boards, Common Core, IB); academic integrity.
- Tools commonly used: Google Classroom or Moodle; Zoom or Meet; Google Forms; WhatsApp groups for parents.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Product and users: [PRODUCT]
- Feedback and data: [DATA]
- Buying cycle: [CYCLE]
- Team: [TEAM]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the user problem, who has it, how we know, and the business goal it serves.
2. Map the needs of learners, teachers and school buyers separately.
3. Set outcome goals for the year.
4. Group ideas into themes linked to those outcomes.
5. Sequence work around the school calendar and buying cycle.
6. Mark which items are bets and which are commitments.
7. Plan quarterly roadmap reviews.
8. Write the roadmap story for each audience.
9. Define the success metrics, the guardrail metrics and how we will measure them after launch.
10. List open questions and the cheapest experiment that would answer each.

## What to deliver
- Needs map
- Outcome goals
- Roadmap
- Narrative
- Review plan

## Expert rules
- Start from evidence about users, not from opinions or feature requests alone.
- Be explicit about scope: what is in, what is out, and why.
- Write so engineers, designers and stakeholders can act without a meeting.
- Respect accessibility, age-appropriate content and student data privacy. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Use headings matching the deliverables.
- Use tables for requirements, priorities and metrics.
- Write acceptance criteria as Given / When / Then where useful.

## Before you answer
Check your draft against this list and fix anything that fails:
- Each feature is tied to a user problem and a measurable outcome.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on course completion and learning outcomes.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.