Skip to content

Industry

Education

Education software should respect the teacher’s time and the learner’s attention.

Challenges

What tends to break first.

Many roles, one product

Students, teachers, admins, and parents do not need the same interface with the labels changed.

Content is operational

Authoring, versioning, and access are the product, not a CMS sidebar.

Adoption is fragile

A tool that adds steps to a class will be abandoned, however well funded.

Opportunities

Where digital work actually pays.

Focused learning products

A specific subject or job, done with care, beats a portal of modules.

Campus operations

Enrolment, scheduling, and the administrative work that steals teaching hours.

Assessment that teaches

Feedback loops, not only scores.

Product examples

Kinds of software, not claimed deliveries.

Course platforms

Authoring, cohorts, and progress that an instructor can run.

Campus portals

Narrow tools for a job — attendance, rooms, advising — rather than one infinite dashboard.

Practice products

Software that is the exercise, not a wrapper around a PDF.

Technology

What to get right.

Identity across institutions

SSO, rostering, and the messy reality of school IT.

Offline and low bandwidth

Learning does not only happen on a fast laptop.

Accessibility as a requirement

If a student cannot use it, the product is incomplete.

Delivery

How we would approach it.

We watch a class or a back-office day before we draw screens. Then we design for the constrained role — usually the teacher or the registrar — because that is whose time is scarcest.

FAQ

Before you write.

Rarely the whole category. More often a learning product, an authoring tool, or the operational layer a generic LMS cannot hold.

Start a project

Build in education.

A short note is enough. We will come back with questions, not a pitch deck.