Nokia · 2025
Streamlining the Frostbuster submission process for developers
Frostbuster is a merge request process that allows developers to merge their code within a locked branch. During code-freeze, developers (if needed) will submit a request to merge their code. Each merge request requires approval from a panel of reviewers. For the most part, this current process has not been updated for 20 years. This project was showcased as my final case study presentation at the end of my 8-month co-op with Nokia.
problem
Developers face an inefficient process when implementing necessary code changes after a code freeze, resulting in excessive effort for both developers and reviewers. How might we optimize the process and reduce the manual effort and time it takes for developers and reviewers to submit/process a frostbuster request.
process
User Research
I conducted 30+ user interviews with developers across multiple Nokia teams to understand their current workflows, pain points, and mental models around the submission process. I also facilitated developer workshops to identify usability gaps and translate findings into actionable design improvements.
Defining the Flow
Using the research findings, I mapped the end-to-end submission journey and identified the key moments of friction. I redesigned the information architecture to create a clear, linear flow with explicit step indicators and contextual guidance throughout.
Design and Prototyping
I led the design and prototyping of user flows for creating and editing complex network configurations, collaborating closely with product managers and developers to ensure seamless integration with existing systems. Multiple rounds of iteration were driven by feedback from usability testing sessions.
