Education software has to fit the way teaching is delivered. A course marketplace needs discovery, purchases and creator payouts. A school platform needs enrolment, class membership and records that stay consistent across terms. A tutoring product needs the right curriculum, useful feedback and a clear boundary between what the assistant can answer and what a teacher should review. These are different products, even when they share a login screen.
We begin with the learner, educator and administrator journeys, including the work outside the classroom. Who creates a course? Who can change a result? What happens when a learner moves between groups? That operating model determines the permissions, data structure and integrations. We agree the first complete journey before adding a long feature list, so the initial release can be reviewed against a real educational task.