Back to work

SC KPI

Rebuilding the Student Council's website and the admin panel that runs it.

SC KPI admin panel — the Roles members roster
Role
Design Lead · UI/UX · Design System
Team
4 designers + me · engineering · project manager
Year
2026
Status
Closed(April 2026)

SC KPI is the Student Council of the Igor Sikorsky Kyiv Polytechnic Institute. Their old site was slow to update and inconsistent in accessibility and architecture, so we needed to rebuild its public site and the admin panel the council members use to manage content. I led the design while directing four junior designers and aligning decisions with engineering and the project manager. It closed before the public site reached visual design, so what follows is the foundation that landed: the architecture and the admin panel.

My role in practice

  1. Leading designers

    I split the work with the PM and engineering lead, we set a clear bar for 'done', and kept the team aligned on a single shared goal.

  2. Structuring feedback

    I ran a repeatable review loop alongside the PM to deliver specific, actionable feedback.

  3. Aligning with dev and PM

    I balanced design intent with engineering constraints and PM expectations, prioritizing what could ship first and what mattered most.

Everything started from these priorities.

We mapped the structure of both the admin panel and the public site before drawing a single screen. Getting the information architecture right first meant we could design in parallel without constant confusion about what to build.

The admin panel is a working tool, so the system had to favour clarity and consistency over anything fancy. That meant components the council could assemble themselves, and that engineering could build once and maintain easily.

Design solution

The admin panel is where most of my finished work lives. Only the Roles flow was fully designed before the project closed.

Roles

Documents

What shipped, and what I learned

  1. Admin panel

    Part of the content-management admin panel enough for the council to manage added roles and documents.

  2. Information architecture

    The information architecture for both the public site and the admin panel.

  3. Component foundation

    Individual interface elements and the component foundation underneath them.

The project was closed at the end of April before starting the main visual part of the site. The real outcome for me was establishing a working system to collaborate directly with engineering and PM, and the experience of leading a design team.