ECOLABS is a web platform designed and implemented during my professional internship at Universidad EAFIT. The project replaced the manual equipment loan process — operating through Google Forms and Excel — with a centralized system with three differentiated user profiles: Student, Teacher, and Administrator. The process followed User-Centered Design across four phases: research, architecture, high-fidelity design, and React implementation.
ECOLABS serves ~800 students and 60 faculty with 150+ pieces of equipment. The previous system showed no real-time availability, generated no automatic confirmations or return reminders, and forced the administrator to manually cross-reference data for 2.5 hours daily. 67% of students had incurred late return fees, and no group loan mechanism existed for teachers.
I want to know if the equipment is available before going all the way to ECOLABS, and to be clear on when I have to return it.Valentina Ríos · Student · Persona 1
The student's mental model puts dates first, then equipment. The original form imposed the reverse order — the most frequent source of errors in usability testing, solved with a 3-step wizard.
I need to book equipment for my whole class in advance. The current process takes time I should spend preparing the class.Jorge Montoya · Teacher · Persona 2
Without group requests, teachers had to repeat the form for every student. This finding made the group request module a critical feature of the platform.
I spend hours cross-referencing data in Excel. I need the system to tell me what's on loan, to whom and when it comes back.Daniela Cárdenas · Administrator · Persona 3
2.5 hours a day of repetitive manual work. Automating these flows was the most significant measurable impact: the Administrator profile scored a SUS of 85.0 in final testing.
9 entrevistas semiestructuradas y observación contextual con los 3 perfiles. Revisión del sistema anterior (Google Forms + Excel). Construcción de 3 personas y 3 journey maps con emociones, dolores y oportunidades que orientaron el diseño.
Mapa del sitio diferenciado por perfil, 4 flujos de interacción detallados y 10 requerimientos UX con criterios de aceptación medibles. Esta documentación funcionó como contrato de diseño con el equipo de backend.
Sistema de diseño en Figma (paleta EAFIT, tipografía, íconos Lucide, grilla 8px, 12 componentes base). 35+ pantallas. Pruebas de usabilidad con 9 participantes — SUS 78.1. 7 problemas resueltos: wizard de solicitud por fechas primero, rediseño del módulo grupal.
React 18 + Vite + CSS Modules. 12 rutas protegidas por rol con PrivateRoute + JWT. Integración con 10 endpoints REST via Axios. React Hook Form + Yup para formularios. Coordinación semanal con el equipo de backend para pruebas de integración end-to-end.
Average SUS score of 78.1 (above the standard 68 threshold) with 9 participants. Administrators: 85.0 — manual operational workload fully automated. 35+ unique screens in Figma, 12 role-protected routes, 10 REST endpoints integrated. 7 usability problems identified and resolved before implementation.