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.

View case studies View Resume

Selected work

Work that started with more questions than answers.

The selected cases span an evolving enterprise platform, a shared product system and a mobile product prototype with working behavior.

MeralisWorkforce operations
PeoplePayrollSettings
Active roles8
Workflow maps30
Components42
Payroll
Catalogs
Permissions
01 / Featured case
Enterprise SaaSWorkforce OpsProduct Strategy

Meralis

Four years of turning fragmented HR, payroll and staffing requirements into one operational model that could keep growing without becoming a collection of disconnected screens.

Role
Sole Product Designer
Scope
8 roles, 30 workflow maps
System
42 components, 149 CSS tokens
Outcome
3 legacy platforms consolidated
Open case study
Design System case study cover
02 / Product system
Design SystemB2B + HRUI Foundations

Design System 1.0

A shared system built to stop recurring UI and behavior decisions from being solved again on every screen.

Open case study
WattlePay mobile fintech case study cover
03 / Mobile product
Mobile UXInteraction DesignReact Prototype

WattlePay

A mobile wallet concept with seven connected flows, shared product state and a working prototype built to test behavior, not only presentation.

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.

Irene Porro traveling in EuropeDesigning 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.

Product designInteraction designDesign systemsMulti-role workflows

What I tend to own

The decisions between the brief and the build.

I work across the path from understanding an ambiguous request to helping the team deliver a product that still makes sense in real use.

01

Frame the right problem

Connect user needs, business context and delivery constraints before committing to a solution.

02

Design the system, not only the screen

Resolve workflows, permissions, states and patterns so the experience holds together beyond the happy path.

03

Stay accountable through implementation

Give engineering clear behavior, reusable decisions and enough context to build without guessing the intent.

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.

ireneporro6@gmail.com LinkedIn Behance Portfolio PDF

Irene Porro · Senior Product Designer · 2026