Message me

Senior Product Designer · B2B SaaS & Product Systems

I’m Irene. I design digital products.

Most of my experience is in B2B SaaS: products with multiple roles, dense workflows and requirements that keep changing. I work from product logic and interaction through interface design and delivery.

Selected work

Work that started with more questions than answers.

Two multi-role B2B platforms, a staffing marketplace and the design system they share.

Foundry design system: the same components in two product brands
03 / Product system
Design SystemAccessibilityAI-assisted

Foundry

The design system I created for two B2B products: 177 shared tokens, accessible colors and written rules that developers and AI tools follow.

Open case study
Relay open orders grid with urgency states and fill progress
04 / Staffing marketplace
B2B SaaSWorkflow RulesDesign System

Relay

How a staffing order moves from the client company to the MSP and agency branches: ownership, urgency, outcomes and what each side is allowed to see.

Open case study
Explore more work

How I work

I do not start with screens.

I start by finding the decision hidden inside the request. That means understanding the business context, the people involved, what can go wrong and what the team needs to keep moving.

  1. 01

    Frame the problem

    Clarify the real need, the constraints and whose decision the product has to support.

  2. 02

    Model the system

    Map roles, flows, states and dependencies before they turn into screen-level inconsistencies.

  3. 03

    Make decisions tangible

    Use flows, interface design and prototypes to test the logic and give the team something concrete to challenge.

  4. 04

    Stay close to delivery

    Work through edge cases and implementation questions so the product keeps its intent after handoff.

AI-assisted product development

Use AI to make product decisions testable earlier.

I use Claude and Codex alongside Figma and code-based prototypes to turn product decisions into working behavior before engineering implementation. The goal is not to generate more screens—it is to test flows, states, logic and edge cases earlier, then bring clearer decisions into delivery.

01

Prototype behavior

Test connected flows and shared state instead of relying only on static screens.

02

Challenge product logic

Use functional prototypes to expose missing states, unclear rules and edge cases earlier.

03

Reduce handoff ambiguity

Give Engineering something closer to intended behavior, not only visual specifications.

Portrait of Irene PorroDesigning with purpose

About

I like making sense of messy systems.

I am Irene Porro, a Senior Product Designer with 5+ years of experience across B2B SaaS, platform products, dashboards, CRM systems and data-heavy interfaces.

I am most useful when requirements arrive as a list of features, different people hold different parts of the context and the product still needs to feel simple. I find the structure, make the trade-offs visible and turn them into something the team can discuss and build.

I care about visual craft, but not as decoration. Hierarchy, interaction and consistency are part of how a product communicates. The small details matter because they are where users understand what happened and what to do next.

Outside work

Most of my free time goes to traveling, to art and design of any kind, and to my cats. I’m an optimist by nature: when something breaks, my first question is how we fix it, not whose fault it was. That works at work, and it works on a trip when the train doesn’t show up.

What I want most is to share what I build. One day I’d like to take the people I love on a trip with me, all of them, and keep leaving the places I go, and the teams I work with, a bit happier than I found them.

Product designInteraction designDesign systemsMulti-role workflows

How I judge the work

A polished screen is not enough.

I look at whether the product explains itself, survives edge cases and gives the people building it a clear, reusable logic.

Product quality

I look for what breaks when the happy path ends.

  • The next action is clear without extra explanation.
  • Empty, loading, permission and error states are intentional.
  • The same product rule behaves consistently across flows.
  • Engineering can understand the decision, not only copy the screen.
Consistency

Patterns should remove decisions.

A shared pattern is useful when it reduces ambiguity for users and the team, not simply because it looks the same.

Delivery

Handoff is part of the design.

Implementation questions often reveal missing logic, so I stay involved while the experience becomes a real product.

The goal

Make the next decision easier.

For the user and for the team building the product.

Start a conversation

Let’s connect.

Irene Porro · Senior Product Designer · 2026