PRODUCT DESIGN · WEB · 2026

Project
Punku

A ground up redesign improving the experience and performance of [product],

under a tight [X] month deadline, directly impacting [key business metric].

MY ROLE

Product Designer

MY ROLE

Product Designer

MY ROLE

Product Designer

TEAM

5 Designers

1 PM

TIMEFRAME

Apr 2026

Sep 2026

TIMEFRAME

Apr 2026

Sep 2026

IMPACT

Live in IOS

IMPACT

Live in IOS

IMPACT

Live in IOS

BACKGROUND

Fixing the foundations

In [year], [company/product] faced a tough decision — [describe the core situation]. The product had key foundational issues creating real pain for users and the business:

Problems

Performance

The legacy product was slow and unreliable — sometimes failing to load critical information entirely, causing users to abandon the flow.

Performance

The legacy product was slow and unreliable — sometimes failing to load critical information entirely, causing users to abandon the flow.

User Experience

Design debt and inconsistencies had accumulated over years, creating a confusing experience with poor accessibility across key flows.

User Experience

Design debt and inconsistencies had accumulated over years, creating a confusing experience with poor accessibility across key flows.

Technical Debt

The aging architecture made adding new features extremely difficult, slowing down the entire product team and blocking roadmap items.

Technical Debt

The aging architecture made adding new features extremely difficult, slowing down the entire product team and blocking roadmap items.

Cognitive Overload

Flows were overly complex and filled with technical jargon, making the product inaccessible for new users and day-to-day tasks unnecessarily hard.

Cognitive Overload

Flows were overly complex and filled with technical jargon, making the product inaccessible for new users and day-to-day tasks unnecessarily hard.

Low accessibility scores and confusing information hierarchy

Low accessibility scores and confusing information hierarchy

HOW WE WORKED

Process

Given the aggressive [X]-month deadline, we adopted a zero-to-one approach to reach decisions quickly and maintain strategic alignment across distributed teams. We split the redesign into smaller focused projects — each one following the same process:

Strategy & Alignment

I kicked off each project with full team alignment sessions and set up regular syncs with Product and Engineering to align on technical scope, prioritization, and design decisions. Regular presentations to senior leadership kept everyone bought in throughout.

Strategy & Alignment

I kicked off each project with full team alignment sessions and set up regular syncs with Product and Engineering to align on technical scope, prioritization, and design decisions. Regular presentations to senior leadership kept everyone bought in throughout.

Competitive Benchmarking

I conducted analysis of leading competitors and category leaders, which was essential to establish familiar and intuitive patterns — reducing the learning curve for new users while meeting expectations set by best-in-class products.

Competitive Benchmarking

I conducted analysis of leading competitors and category leaders, which was essential to establish familiar and intuitive patterns — reducing the learning curve for new users while meeting expectations set by best-in-class products.

Rapid Iteration

I managed multiple rounds of design critique, incorporating feedback from stakeholders and end users across every cycle. Nothing shipped without being validated — either through testing or explicit stakeholder sign-off.

Rapid Iteration

I managed multiple rounds of design critique, incorporating feedback from stakeholders and end users across every cycle. Nothing shipped without being validated — either through testing or explicit stakeholder sign-off.

Low accessibility scores and confusing information hierarchy

THE WORK

The Redesign

Core Experiences

I redesigned the product's core screens making sure they feel familiar to users on every platform. It was important to default to platform-native patterns where possible — this reduced customization options but ensured user familiarity and was essential for implementation speed given the tight timeline.

Low accessibility scores and confusing information hierarchy

Feature Enhancement

I overhauled legacy flows for critical features to meet the specific needs of the target user base. We prioritized providing core functionality with a reliable implementation — this didn't provide a full feature set, but it guaranteed the stable experience our users needed within the time available.

Low accessibility scores and confusing information hierarchy

Low accessibility scores and confusing information hierarchy

Design System

I acted as the key design contact for the new design system, working closely with engineering. Rather than building an all-encompassing system from day one, we chose to build a library of core components — both custom and native — with our styling applied. This streamlined the process and gave engineering a stable foundation to build on from the start.

Low accessibility scores and confusing information hierarchy

RESULTS

Impact

We successfully delivered a performant, simple, and consistent user experience — eliminating the primary friction points of the legacy product. The redesign directly contributed to the company's key metrics:

50%

Of total company revenue in the first year post-launch

50%

Of total company revenue in the first year post-launch

9mo

From kickoff to shipped on iOS and Android

9mo

From kickoff to shipped on iOS and Android

4×

Faster feature delivery after design system adoption

Beyond the numbers, the redesign rebuilt trust with existing clients and opened doors with new enterprise accounts who had previously passed on the product due to the experience quality. This was one of the most complex and rewarding projects of my career.

Design & developed

by Ramiro M. Chavez

2026 — All Rights Reserved
Made with Figma + Framer