Track-Launch: A Market Launch Timeline Management Tool

Track-Launch: A Market Launch Timeline Management Tool

Track-Launch: A Market Launch Timeline Management Tool

Customer

Customer

Customer

Leading Consumer Goods Manufacturer

Timeline

Timeline

Timeline

Jan 2025 - May 2025

Tools/Software

Tools/Software

Tools/Software

Research: Miro, MS Forms
Design: Figma, Adobe Illustrator

Team

Team

Team

01 Lead UX Designer
02 Developers
01 Product Manager

My Role

My Role

My Role

Lead UX Designer

I led this project as User Experience Designer, journey from initial exploration to final implementation, which included understanding the brief, conducting research, ideating, designing, and prototyping. Throughout, I maintained close collaboration with the product manager, end-user and stakeholders, also partnered closely with engineers.

How it all started?

How it all started?

How it all started?

A leading manufacturer set out to simplify and automate the way they managed product launch timelines. Previously, the process relied on juggling Excel sheets, long email threads, and manual updates—often resulting in delays and Errors.

I joined this journey as the UX Designer, helping design Track Launch—a centralized platform that brings all stakeholders together and makes the product launch process more efficient, transparent, and collaborative.

Challenge

Challenge

Challenge

What was the problem?

What was the problem?

What was the problem?

  • Manual workflows
    Launch preparation required data to be pulled from multiple sources, cleaned, and organized manually—causing delays and errors.

  • Lack of central visibility
    Teams lacked a unified platform to track progress, timelines, and responsibilities across stakeholders.

  • Poor coordination
    Communication relied heavily on email threads and spreadsheets, leading to misalignment and missed deadlines.

Solution Points

Solution Points

Solution Points

  • Less Busywork, More Focus
    Automating repetitive tasks meant teams could stop wrestling with spreadsheets and start focusing on what really matters — getting products out the door smoothly.

  • Clarity at a Glance
    A central dashboard gave everyone a bird’s-eye view of where things stood. No more digging through emails or guessing who’s handling what.

  • Clear Roles, No Finger-Pointing
    With role-based tasks, responsibilities were crystal clear. Everyone knew their part, which led to better follow-through and fewer last-minute surprises.

  • Fewer Mistakes, Fewer Delays
    Built-in checks ensured that all the right files and data were in place — before it was too late. That meant fewer launch delays caused by missing or incorrect info.

  • Saving Time = Saving Money
    By streamlining the entire process, we helped cut down the hidden costs of miscommunication and rework — which adds up fast over multiple launches

Design Process

Design Process

Design Process

We followed a user-centered design process — starting with real-world problems, exploring user insights, and iterating solutions that balance usability, feasibility, and business impact.

We followed a user-centered design process — starting with real-world problems, exploring user insights, and iterating solutions that balance usability, feasibility, and business impact.

We followed a user-centered design process — starting with real-world problems, exploring user insights, and iterating solutions that balance usability, feasibility, and business impact.

Hybrid Mode: How I Research

Hybrid Mode: How I Research

Hybrid Mode: How I Research

My research starts with document reading, flows into stakeholder calls, gap-spotting, and ends with a smart survey to validate pain points—mixing methods to get sharp, prioritized insights.

My research starts with document reading, flows into stakeholder calls, gap-spotting, and ends with a smart survey to validate pain points—mixing methods to get sharp, prioritized insights.

My research starts with document reading, flows into stakeholder calls, gap-spotting, and ends with a smart survey to validate pain points—mixing methods to get sharp, prioritized insights.

Research Findings

Research Findings

Research Findings

To build something truly useful, we spoke to 12 users across 7 departments, spanning 4 distinct roles. Their insights shaped every part of the experience — from feature prioritization to workflow design.

To build something truly useful, we spoke to 12 users across 7 departments, spanning 4 distinct roles. Their insights shaped every part of the experience — from feature prioritization to workflow design.

To build something truly useful, we spoke to 12 users across 7 departments, spanning 4 distinct roles. Their insights shaped every part of the experience — from feature prioritization to workflow design.

Insights

Insights

Insights

Task Flow

Task Flow

Task Flow

A side-by-side look at how we transformed a complex, manual task flow into a streamlined, user-friendly process.

A side-by-side look at how we transformed a complex, manual task flow into a streamlined, user-friendly process.

A side-by-side look at how we transformed a complex, manual task flow into a streamlined, user-friendly process.

Create New Project → “Before Design Intervention”

Create New Project → “Optimized Flow”

Update Timeline → “Before Design Intervention”

Update Timeline → “Optimized Flow”

Design Thinking in Action

Design Thinking in Action

Design Thinking in Action

A glimpse of research synthesis, user flows, task mapping, and ideation — all captured in one collaborative space.

A glimpse of research synthesis, user flows, task mapping, and ideation — all captured in one collaborative space.

A glimpse of research synthesis, user flows, task mapping, and ideation — all captured in one collaborative space.

Design Goals

Design Goals

Design Goals

Blueprinting the Experience

Blueprinting the Experience

Blueprinting the Experience

Low-fidelity wireframes: Early explorations on paper to map layout, interactions, and structure — focused on user needs before pixels.

Low-fidelity wireframes: Early explorations on paper to map layout, interactions, and structure — focused on user needs before pixels.

Low-fidelity wireframes: Early explorations on paper to map layout, interactions, and structure — focused on user needs before pixels.

Concept Review & Iteration

Concept Review & Iteration

Concept Review & Iteration

After completing wireframes, we approached to our users and stakeholders and presented the initial wireframe concept for early feedback and alignment.

After completing wireframes, we approached to our users and stakeholders and presented the initial wireframe concept for early feedback and alignment.

After completing wireframes, we approached to our users and stakeholders and presented the initial wireframe concept for early feedback and alignment.

The initial review that we got was as follows:

The initial review that we got was as follows:

The initial review that we got was as follows:

  • Stakeholders appreciated the dashboard but suggested deeper filtering options for timeline views.

  • Instead of just showing delayed or on Track, can we also show which stage the task got stuck at?

  • In same timeline row can we show the comparision of last and latest timeline?

  • Can we also have a tab for level management to create level presets?

Blueprinting the Experience

Blueprinting the Experience

Blueprinting the Experience

Here are a few selected wireframes from my Figma board—showcasing critical paths and core interactions shaped through user feedback.

Here are a few selected wireframes from my Figma board—showcasing critical paths and core interactions shaped through user feedback.

Here are a few selected wireframes from my Figma board—showcasing critical paths and core interactions shaped through user feedback.

Design System

Design System

Design System

To future-proof the experience, I put together a solid design system—ready to handle new modules, features, or whatever comes next.

To future-proof the experience, I put together a solid design system—ready to handle new modules, features, or whatever comes next.

To future-proof the experience, I put together a solid design system—ready to handle new modules, features, or whatever comes next.

Accessibility Basics Done Right

Accessibility Basics Done Right

Accessibility Basics Done Right

I ensured a minimum font size of 12px for readability, maintained a 4.5:1+ color contrast ratio, and clearly labeled UI components for developers to support semantic structure.

I ensured a minimum font size of 12px for readability, maintained a 4.5:1+ color contrast ratio, and clearly labeled UI components for developers to support semantic structure.

I ensured a minimum font size of 12px for readability, maintained a 4.5:1+ color contrast ratio, and clearly labeled UI components for developers to support semantic structure.

Design Tokens

Design Tokens

Design Tokens

To build a scalable and consistent design system, I created primitive and semantic tokens using Figma variables. These tokens streamline design decisions, boost collaboration with developers, and ensure visual consistency across future modules.

To build a scalable and consistent design system, I created primitive and semantic tokens using Figma variables. These tokens streamline design decisions, boost collaboration with developers, and ensure visual consistency across future modules.

To build a scalable and consistent design system, I created primitive and semantic tokens using Figma variables. These tokens streamline design decisions, boost collaboration with developers, and ensure visual consistency across future modules.

Feature Highlights at a Glance

Feature Highlights at a Glance

Feature Highlights at a Glance

A closer look at the key components that bring clarity, control, and collaboration into one streamlined experience. From tracking progress to managing workloads, these UI blocks are the building blocks of smarter product launches.

A closer look at the key components that bring clarity, control, and collaboration into one streamlined experience. From tracking progress to managing workloads, these UI blocks are the building blocks of smarter product launches.

A closer look at the key components that bring clarity, control, and collaboration into one streamlined experience. From tracking progress to managing workloads, these UI blocks are the building blocks of smarter product launches.

Does It Even Work? Let’s See!

Does It Even Work? Let’s See!

Does It Even Work? Let’s See!

I test with fellow designers, run heuristic reviews, then share clickable flows with users. Every round improves clarity, efficiency, and that "just works" feeling in the design.

I test with fellow designers, run heuristic reviews, then share clickable flows with users. Every round improves clarity, efficiency, and that "just works" feeling in the design.

I test with fellow designers, run heuristic reviews, then share clickable flows with users. Every round improves clarity, efficiency, and that "just works" feeling in the design.

What We Finally Shipped

What We Finally Shipped

What We Finally Shipped

After research, brainstorming, and countless wireframes—this is the final version that ticks all the boxes: simple, intuitive, and built to make product launches easier for everyone involved.

After research, brainstorming, and countless wireframes—this is the final version that ticks all the boxes: simple, intuitive, and built to make product launches easier for everyone involved.

After research, brainstorming, and countless wireframes—this is the final version that ticks all the boxes: simple, intuitive, and built to make product launches easier for everyone involved.

Key Takeaway

Key Takeaway

Learnings from this Project:

Learnings from this Project:

Learnings from this Project:

  • Collaboration is everything – Working closely with stakeholders, end users, and developers helped align design with real needs.

  • Simplicity is powerful – Turning a complex, scattered workflow into a streamlined tool proved that good UX can untangle anything.

  • Design-Dev handoff matters – Guided developers on Figma’s developer mode, making implementation smoother and more efficient.

  • Empathy leads to impact – Observing how users interacted with the old process helped design a solution that truly fit their workflow.

  • Scalability starts early – Building a robust design system laid the groundwork for future feature expansion.

Explore My Other Work

Explore My Other Work