When I joined, the platform lacked structure, documentation was minimal, and user flows were unclear, making it hard to plan our work.
I requested the service architecture from developers and used it to create a site map. I identified key user flows and pages, then aligned priorities with the product owner, lead developer, QA.
We gained a clear vision of the product’s structure and scope. The site map became the basis for user flows and interface design, making the process systematic and transparent.
Initially, UX/UI tasks were handled manually and without a clear system—there were no defined stages, handoffs, reviews, or synchronization.
I introduced and visualized a new workflow:
The team began working within a unified, predictable process, leading to higher quality and consistency. The workflow diagram became the foundation for the team's future work.
When designing user flows, I frequently used flowcharts. This helped me dive deeper into the logic behind each scenario and communicate with the product owner and developers on a structural—not just visual—level.
It allowed us to focus on user logic, clarify key paths, and ensure everyone was aligned on how the product should work.
This is the central hub of the platform and its most frequently used page. Here, participants spend the majority of their time: tracking statuses, collecting feedback, and navigating every stage of the competition.
The initial task sounded simple: “just redesign it to look nice.” But once I started, it became clear that the documentation was incomplete and, in places, unclear.
The biggest challenge was figuring out the statuses — not just redesigning them, but structuring them and making them truly understandable for participants. The documentation didn’t provide direct answers, so I gathered information from: existing materials and guidelines, the working test version of the website;, conversations with colleagues.
It took several iterations, as even team members were sometimes confused and gave contradictory answers. Eventually, I compiled a complete list of existing statuses, removed duplicates and unnecessary ones. Then I presented the structured version to the team, explained the logic, and got final approval.
The stage card replaces the old table layout with a clear “journey” format, inspired by transit route maps. It presents each stage and substage in a structured hierarchy with clear statuses and concise descriptions, making navigation easier while instantly showing progress, context, and next steps.
Finally, I documented the entire page — describing the logic, structure, statuses, and visual rules — so that it could be easily maintained and scaled in the future.
One of the first competition stages — and the one where most participants drop out.
Initially, the task was simply to “make it look better with a new UI.” But once I saw this wall of text, I was genuinely shocked. I actually felt sorry for our users. Some sections — for example, Career — were incredibly long, containing hundreds of questions. Filling this out on mobile was almost impossible.
I decided to postpone UI work and focus on UX first. After studying the questionnaire in detail before a team meeting, I proposed:
Beyond the Questionnaire and Competition Roadmap, I redesigned key participant and admin flows — registration, login, password recovery, email/phone verification, profile, video interview, moderation, and support — applying one principle: clarity first, friction last.
One of my proudest achievements on the project was creating a design system from scratch — a unified framework that kept the platform visually coherent and technically scalable.Before starting, I collaborated closely with the brand team to ensure the system fully reflected the visual identity and spirit of the competition.
The system became the single source of truth, cutting inconsistencies and speeding up delivery.
LeadTrack was a project where I not only delivered design solutions but also restructured the entire product experience under tight deadlines and incomplete documentation.
I combined deep user empathy, systematic thinking, and active cross-team collaboration. When faced with unclear requirements — like the Competition Stages statuses — I gathered input from stakeholders, structured it, and proposed a clear model that was approved.
Despite strict timelines, I balanced UX quality with technical feasibility, iterating quickly and aligning closely with development.
While some ideas remain for future iterations, the project showed how communication, empathy, and structured design thinking can directly improve both user satisfaction and business results.