My approach is rooted in treating each project lying within an opportunity space, ready to be explored. My process is highly iterative between research, synthesis, prototyping and reflection. As AI tools have improved the “act of creating” exponentially, my passion lies in using them not just as solutions, but as tools to think, bring more clarity and feed into the vision itself. I am a visual thinker as I obsess over details and have strong opinions about how user experience should feel. Let me help you understand my design process.

The process begins very broadly- exploring the problem space, core assumptions, context, and user motivations within the following framework.

While working for PFI, we questioned the core assumptions when trying to visualise population welfare. This led us to understand which opportunities got ignored and pain points that emerged from previous design approaches. The old design reflected a traditional stance towards population as just a “count”.

There also needs to be a feasible goal for all the explorations to strive towards within the given project timeline. Nordic Ocean Watch and Lokalt Byrå wanted to create a digital communication platform for Oslo Løa, a floating pavilion structure in the Oslofjord. The key impact Lokalt Byrå wished to achieve was to provide the public with a better understanding of the sources of litter to find local solutions.

I would also reframe goals and challenges into actionable design questions through "How Might We" (HMW) method.

• How might the NRK TV mobile app make discovering and interacting with its content more appealing for teenagers and young adults?

For Oslo Løa, we framed questions like:

• How might we localise the problem for people to make an impact?
• How might we uncover the unintentional ways that lead to marine littering.
• How might we make the whole experience motivating and hopeful so people would wanna contribute?

While working for Blink, I explored the richness of the problem through a broad spectrum of primary, topical and secondary research, and expert interviews. Using the insights, I conduct workshops, design sprints, user interviews, competitive analysis, and data reviews. Then, I cluster my findings into themes or opportunity areas. The opportunities with validated assumptions set a good foundation for prototyping.

Due to my background in visual design, I enjoy sketching and building designs, as it helps me think clearly— more than static discussions ever can.

Explorations are guided by a framework of themes and questions from the research synthesis. For Oslo Løa, we explored along few “How might we” questions. With Blink, the sketches explored user journey flows that helped in identifying some early design tradeoffs.

Emerging Themes begin to surface from exploration. I grouped concepts for Blink under key experience themes. I use expert feedback to evaluate the idea based on user value and technical feasibility.

I turn promising ideas into interactive prototypes — in Figma, often with lightweight animations for richer feedback. Recently, I have upskilled my prototyping abilities with vibe-coding to create higher fidelity prototypes quickly for faster and better feedback.

User testing can begin early to test the user entry flow, where we tested Oslo Løa right outside the structure’s location. For Blink, I conducted a short, detailed workshop with a prototype where users tested the usability and shared their reviews. Observing user behaviour and friction points feed into actionable takeaways for the next iteration. Experts help me gain a broader perspective from my observations and reflections from user testing. Reaching out to subject-matter experts and sharing prototypes through digital and personal interviews, posting on X, and LinkedIn are common ways to refine my design directions.

Based on feedback, we refined Oslo Løa’s micro interaction, user interface, and storytelling to make sense of its overall purpose. We used a lot of local storytelling, for example, using the scenario of a trash bin in Oslo and how it ends up in the Fjord. The buildup from the first and second parts is concluded in the end to make sense of Oslo Løa's purpose and how they can be part of the solution.

Communicating your design involves some storytelling for both users and teams through scenarios, which justify the rationale behind design choices. For Blink, I communicated the potential of my design concept into a well-organised system with clear flows, states, and annotations for dev handoff. I also filmed my friend acting as a user in the different scenarios where my concepts fit in.

At Cognite, I worked with a cross-disciplinary team on CDF’s Diagram parsing application. I would have weekly meetings with the team to negotiate design trade-offs based on deadlines, architecture setup, available frontend capacity and PM's priorities. I have collaborated with engineers using Figma dev mode and recently started with MCP integration on Cursor to validate designs and reduce design–dev friction.

After a feature release, we measure the designs based on various metrics like activation, adoption, success rate and retention, etc. This builds a solid baseline for the next iteration cycle. I also share my experience and constructive feedback with the design system team regarding component scalability. Every project also wraps up with connecting more deeply with my process, ways of working and clarity on work environments that suit me. I document and reflect on my design decisions and often open a dialogue about challenges I faced with my teammates and manager.