Every university's real org chart is feudal: departments with their own cultures, coordinators, curricula and politics, nominally unified by central IT. LMS rollouts fail when they flatten this structure — one template forced on every faculty — or fragment it — every department its own island. Ukkera's groups model the federation properly: departmental autonomy inside university-wide standards.
The implementation sequence #
- 1. University account: standards, branding, integration and policy set centrally
- 2. Department groups: each with its own coordinator role, content library and calendar
- 3. Course mapping: courses to groups; cross-listed courses live in both with shared content control
- 4. Analytics roll-up: department dashboards aggregate to programme and university views
- 5. Term rhythm: coordinators clone last term's structure in hours, not weeks
What department coordinators gain #
The coordinator role is the linchpin: scoped administration of the department's courses, instructors and content — onboarding a new lecturer in minutes, cloning a course for a new section, reviewing completion before the programme committee meets. None of it requires central IT tickets. Departments that control their own pacing adopt platforms; departments that queue for help desks quietly abandon them.
A department chair: 'Central IT used to own our courses. Now we do. Strangely, that is when we finally started using the platform.'