Education technology often begins with the learner: the app, the content, the assessment. That is important. But an institution is also an organization with staff, schedules, admissions, records, finance, facilities and a constant stream of small decisions. When those operational layers are weak, the learning layer struggles regardless of how good it is.
The unglamorous layer
Timetables that change mid-term. Records that live in three places. Staff who wear several roles. Reporting that is assembled by hand at the end of every cycle. These are the everyday problems that consume an institution's attention, and they are exactly the problems software is good at when it is designed around how the institution works.
Infrastructure, not a feature list
We use the word infrastructure deliberately. Infrastructure is what everything else stands on. It has to be reliable, understandable and adaptable to the specifics of each institution, because no two are organized the same way.
Note: This piece describes a design perspective, not a specification of any particular product's capabilities.
Getting the operational layer right is slow, careful work. It rarely makes headlines. But it is what allows an institution to spend its energy on teaching instead of administration, and that is where we believe technology earns its place.