Caro Torres

Scaling Through Process

Scaling a product is not just about features — it’s about enabling repeatable decisions.

— PROJECT TYPE

UX Migration


— ROLE

Design Lead

Designed and led a migration framework that enabled multiple business units to transition legacy dashboards into a centralized platform efficiently and strategically.

01.

Context

CHALLENGE

Dashboards existed across multiple external platforms, each with unique structures and expectations. Without a defined process, migrations created rework, misalignment, and technical friction.

GOALS & KPIS

  • - Reduce iteration cycles between stakeholders and development.
  • - Align business needs with technical capabilities early.
  • - Create a repeatable framework for future migrations.
  • - Enable scalable onboarding of junior designers into the process.
  • - Support cost reduction by accelerating migration timelines.

02.

Strategic Approach

2.1

Cross-Unit Discovery

Each business unit had:

  • - different workflows
  • - unique dashboard structures
  • - varying expectations

I facilitated discovery sessions to understand:

  • - non-negotiable requirements
  • - decision-making patterns
  • - dependency on legacy tools


This helped define realistic migration goals.

2.2

Migration Framework Design

Many legacy features were technically impossible to recreate directly.

I used design prototypes as negotiation tools to:

  • - translate constraints visually
  • - propose alternative solutions
  • - align stakeholders with technical feasibility


Design became the communication bridge between business and engineering.

2.3

Iterative PRD & Design Collaboration

Since no process existed, I designed a structured framework defining:

  • - required sessions
  • - stakeholder roles
  • - documentation flow
  • - design deliverables
  • - PRD evolution


The framework transformed migration from reactive work into a repeatable system.

2.4

Strategic Mediation

Instead of static PRDs, requirements evolved alongside design exploration.

This:

  • - reduced rework
  • - improved alignment
  • - accelerated decision-making

2.5

Scalability by Design

The framework was intentionally designed so junior designers could later execute migrations with guidance.


This allowed leadership transition from execution to strategic focus.

03.

Impact & Results

Process Efficiency

Iteration sessions reduced significantly (from ~11–12 sessions to ~3 for similar project scopes).

Scalable Operational Model

Created a reusable framework now being adopted by junior and mid-level designers.

Strategic Impact

Influenced feature prioritization and roadmap alignment by balancing user needs, business goals, and technical feasibility.


col 4 placeholder

Design became the coordinating layer that enabled teams to move faster without sacrificing clarity or scalability.