Walk into almost any organization that has adopted a large software system and you will find a second, invisible system running alongside it: the spreadsheets, the group chats, the paper registers and the workarounds that people use to do what the software would not let them do.
That shadow system is not a failure of the people. It is a signal. It shows exactly where the software's model of the organization and the organization's model of itself disagree.
Rigid software has a cost that never appears on an invoice
When software is rigid, every mismatch becomes a small tax paid daily by the people doing the work. A department that does not fit the dropdown. A process with one extra approval step. A term calendar that does not match the academic year. Each of these is minor. Together they decide whether a system is used or merely tolerated.
No organization should have to reshape itself around rigid software.
Platform and customization are not opposites
The usual answer is a choice: buy a platform and accept its constraints, or build something custom and accept the cost. We think the more interesting answer is a platform that is designed from the start to be shaped. Shared infrastructure where it makes sense. Custom deployment where the organization's own logic matters.
- Model the organization's real structure, not an idealized one.
- Treat workflows as data that can change, not code that must be rewritten.
- Make customization a first-class path, not an exception.
- Keep the parts that benefit from scale shared across deployments.
This is the philosophy behind how we build Aison Edu and, more broadly, how we approach every system we design. It is harder to engineer. It is also the only version that respects the people using it.