Case Study 04 — EdTech · Portal · Research-led

Gerar University Portal

One platform for an entire university — admissions, payments and academic processes for applicants, students, faculty and staff.

Role
Lead Product Designer & Product Manager
Timeline
Nov 2023 — Jun 2025
Company
Devignerly · Lagos, NG
Platform
Web
Tools
Figma · Notion · Slack

Gerar University of Medical Sciences needed a comprehensive portal to run its academic life digitally — a system where new applicants apply, students manage their studies, and faculty and staff run admissions, payment tracking and administrative processes.

Through Devignerly, I spearheaded the design and development of that portal end to end — leading stakeholder research, defining the product, designing the interfaces, and working with the development team through delivery. It became the university's operational backbone.

  • Four audiences, one system. Applicants, students, faculty and staff each needed different things from the same platform — and each had a different level of digital fluency.
  • Processes lived in people's heads. Admissions and administrative workflows existed as practice, not documentation. They had to be extracted, understood and encoded into software.
  • Money flows through it. Payment tracking for fees and processes meant the portal carried the same trust obligations as any fintech product.
01

Interviewing the university

I interviewed administrative staff and stakeholders to deeply understand the needs of the university — how admissions actually moved from application to offer, where payments got tracked, and what slowed staff down daily. Those interviews directly informed the design of intuitive, user-friendly interfaces grounded in how the institution truly operates.

The workflow docs didn't exist — the admissions officers were the documentation. So we designed from their day, not from an org chart.
02

Designing for four audiences

The portal was structured as distinct experiences sharing one design system: a guided application journey for first-time applicants, a self-service home for students, and administrative tooling for faculty and staff managing admissions and payment tracking. Each audience saw only what they needed — clarity by subtraction.

03

Building it to scale

I collaborated with the development team to translate designs into a scalable and technically efficient platform — making component-level decisions early so the system could grow with the university rather than be rebuilt each session. The goal was a frictionless user experience that also survived real-world load.

04

Listening, adjusting, shipping

I actively listened for feedback and made timely adjustments to satisfy user needs — treating launch as the start of the research, not the end of the project. Staff feedback loops kept the administrative tools aligned with reality as processes evolved.

A digital backbone

A comprehensive portal enabling academic processes that previously ran on paper, spreadsheets and hallway conversations.

Served all four audiences

Applicants, students, faculty and staff each got purpose-built experiences within one coherent platform.

Built to last

A scalable, technically efficient platform delivered with the development team — designed for growth, not just launch.

  • Institutions run on unwritten process. The most important requirements live in people's routines — interviews are how you excavate them.
  • Audience separation is a kindness. Showing every user everything overwhelms; showing each user their own things empowers.
  • Post-launch feedback is a product stage. The timely adjustments after real use mattered as much as the original designs.

Next project

DREST