UX & Product Designer

Complexity Deserves
Better Design

A Different Vantage Point

My Approach to Design!

My perspective was shaped by working across multiple disciplines and organizations, from startups to large enterprise environments. Each experience offered a different lesson about products, people, teams, systems and the decisions that connect them.

Product Design

The longer I worked in design, the less I focused on individual screens.


The real challenge is creating systems and experiences that remain consistent, scalable and useful long after the initial design is delivered.

Collaborating With Devs

Years of working alongside developers taught me to think beyond the mockup.

Understanding implementation helped me see how design decisions impact scalability, maintainability and the long-term success of a product.

Cybersecurity

Working in cybersecurity taught me how to unify disconnected experiences into a cohesive system.

The real challenge was making a complex platform feel simple while preserving the power and flexibility behind it.

Technical Support

Supporting clients taught me to see products through the eyes of the people using them.

It strengthened my ability to identify friction points, anticipate future needs and design with empathy.

Working With Sales

Working alongside sales teams helped me understand how different audiences evaluate the same product.


Communication is often just as important as delivering it.

How I Work

Tools of the Trade

Figma

Figma

Product Design

Claude AI

Claude AI

AI & Productivity

Chat GPT

Chat GPT

AI & Productivity

Adobe Illustrator

Adobe Illustrator

Visual Design & Content Creation

Davinci Resolve

Davinci Resolve

Visual Design & Content Creation

Jira

Jira

Collaboration & Project Management

Miro

Miro

Product Design

Teams

Teams

Collaboration & Project Management

Notion

Notion

AI & Productivity

Slack

Slack

Collaboration & Project Management

I Use An Adaptable Design Process

Before I even open Figma and start designing, I need to clarify four steps:

01

What is the problem?

I work with the team to understand it properly. Along the way we talk through edge cases, dependencies and anything that might have been missed when brainstorming a solution.

02

Who are the users?

I'd like to know who we're designing for: how often they use it, whether they're business or consumer and how comfortable they are with technology. I also like to know how well they know the way the product works today.

03

What are the business goals?

Understanding the business goals shows me where to focus. It helps me separate must-haves from nice-to-haves and shape a solution that brings value to both the users and the business.

04

What are the technical limitations?

I talk to engineers early to find out what is realistically possible to build. It makes both design and delivery smoother.

Then I Choose The Right Path

Path A is for improvements to an existing product where the problem is well understood. This allows for a shorter, more direct process without unnecessary research or exploration.

1. Understand the Change/Request

I clarify what needs to change, why and which parts of the existing experience are affected.

2. Design & Adjust

I first look for existing patterns, components and behaviors that already solve part of the problem. I reuse what works and introduce something new only when there's a reason to.

This keeps the experience familiar for users and reduces design, development and maintenance effort.


To speed things up, I also use AI Support for:

  • Solution comparison
  • Rapid ideation
  • Quick mockups and Gap analysis.

3. Validate, Review & Refine

I gather feedback, reduce risk and improve the solution through multiple review cycles. Adjust the experience based on new insights, identified friction points, technical considerations, or evolving business requirements.


Validation channels can include:

  • User testing (if available)
  • Analytics
  • Stakeholder reviews
  • Heuristic evaluation
  • AI-assisted reviews.

Because I proactively build flexible design systems and reusable component structures, many changes can be explored and demonstrated during the review session itself.

By anticipating future needs and common requests, stakeholders can compare alternatives, discuss scenarios and make decisions faster, reducing the need for additional review cycles.

4. Deliver & Support Implementation

I closely collaborate with developers to ensure the intended experience is successfully implemented.


My involvement includes:

  • Review requirements
  • Clarify behaviors
  • Provide specifications
  • Answer questions
  • Review builds
  • Support QA

My Expertise

What I Really Specialize In

A concise overview of the areas where I create the most impact.

Design Systems

Scalable, token-driven systems built to evolve at any team size.

TokensComponentsDocumentationWCAG

Enterprise Product Design

Claims, billing and retirement platforms used daily by large insurance clients.

  • Insurance
  • Claims
  • Legacy migration

SaaS Product Design

Heimdal's security suite, from admin dashboards to the endpoint agent.

  • Cybersecurity
  • Dashboards
  • B2B

Handling Complex Workflows

Interconnected flows where every step touches other teams, roles and data.

  • Dependencies
  • Multi-role
  • Edge cases

Product Thinking

Weighing user pain against legacy constraints, cost and what ships next.

  • Trade-offs
  • Requirements
  • Roadmap

AI Design Implementation

An agentic assistant that turns call transcripts into notes and actions.

  • Agentic AI
  • Transcripts
  • CSR tools

Scalable Design

Anticipating how requirements will evolve, so future updates fit, not break.

  • Future-proofing
  • Modular
  • Patterns

User-Centered Design

Years in IT support taught me how users actually describe what's broken.

  • Interviews
  • Validation
  • Accessibility

Stakeholder Alignment

Product owners, engineers and clients across four countries and time zones.

  • Remote teams
  • Reviews
  • Clients

Workshop Facilitation

Discovery sessions that turn vague requirements into an agreed backlog.

  • Discovery
  • Refinement
  • Mapping

Every Product Has a Story

The most interesting ones usually begin with a challenge worth solving.