iTulek is a learning management system built for Kazakh technical college students and educators. The platform covers the full academic cycle — from assignment distribution and grading to attendance tracking, progress dashboards, and direct student-teacher messaging.

The project was designed to replace a fragmented ecosystem of WhatsApp groups, email chains, paper handouts, and manual grade sheets with a single, coherent product both sides would actually want to use.

Students were managing coursework across 4+ disconnected tools with no single source of truth. Teachers had no real-time visibility into student engagement or progress — tracking performance meant manually collecting data from multiple places.

The challenge was to design a full LMS from scratch that could handle complex institutional workflows while remaining accessible to users with varying levels of digital literacy.

The platform serves two distinct user roles — each with different needs, mental models, and workflows.

• Consolidate academic workflows into one platform
• Replace paper-based and multi-app processes with a unified digital flow
• Give teachers real-time visibility into class performance
• Design for varying digital literacy — low entry barrier, high capability ceiling
• Build a scalable module structure that can grow with the institution

I led UX/UI design end-to-end — from discovery and information architecture to final screens and a reusable component library.

• Conducted interviews with students and teachers to map pain points
• Designed role-based information architecture and user flows
• Built 5 core modules: Assignments, Grades, Schedule, Attendance, Messaging
• Developed a component library of 40+ reusable UI elements
• Delivered implementation-ready screens with full developer specifications

I started with structured interviews across both user groups to identify the highest-friction moments. The key insight: students didn't struggle with technology — they struggled with fragmentation. Teachers weren't asking for more features — they needed clarity.

The information architecture was designed to mirror how academic workflows actually unfold — not how an institution might categorize data. Each module was scoped to a single job: submit, grade, view, or communicate.

The visual language was designed to feel calm and focused — a deliberate contrast to the notification-heavy chaos of WhatsApp-based coordination. A consistent component library ensured predictable interactions across all five modules. The interface was tested with real students throughout, with design iterations driven by observed friction.

Teacher Dashboard

The teacher's home screen prioritises class oversight — today's schedule, plan completion rates per group, and system activity at a glance. Group-tagged lessons and real-time fill metrics replace manual tracking across spreadsheets.

Student Dashboard

Students land on a personal view — today's classes, attendance and grade summaries front and centre. The calendar and activity chart provide passive awareness of their own academic rhythm without any extra navigation.

Three modules form the backbone of the teacher's daily workflow — each built around a single, well-defined job to be done.

Module 01 — Planning

Schedule

The weekly schedule renders every lesson across all groups in a structured day-by-day grid — group code, module title, and classroom on each slot. Teachers switch between "by teacher" and "by group" views, filter by shift, and navigate weeks via date-range chips. High information density handled through clear visual hierarchy: group codes anchor each cell in purple, supporting metadata recedes below at reduced weight.

Module 02 — Planning

Lesson Plans

Each active lesson plan is surfaced as a card with a real-time fill-percentage donut — making completion status immediately scannable without opening individual records. Teachers see at a glance which subjects are on track and which need work. Academic year tabs and Excel export bridge daily use with institutional reporting, without adding a separate tool to the workflow.

Module 03 — Learning

Journal

Four journal types — Theoretical, Individual, Industrial, and Elective — are separated by tabs to match how the institution classifies coursework. Within each type, teachers toggle between their own journals and all journals, filtered by academic year. Each card shows only the group code and subject name: the minimum needed to locate any journal entry without visual noise.

The platform delivered a single entry point for the entire academic workflow — replacing the 4+ tools students and teachers previously juggled.

• Students gained instant access to all assignments, grades, and schedules in one place
• Teachers could monitor class-wide performance without manual data collection
• Role-based navigation reduced onboarding friction for both user types
• The modular architecture made the system extensible for future institutional needs