Enter password to view case study
2026
Workflow intelligence platform
Role
Founding Product Designer
Timeline
3 months
Team
Product + Engineering + Stakeholders
My role
End-to-end workflow design from discovery to production
The Problem - fragmented research, low confidence
TLDR; Skincare teams need answers to simple questions about trends, products, and consumers, but the data was fragmented across multiple tools and sources. Analysts spent hours manually stitching insights together, making it difficult to validate trends and make confident decisions.
User Identification
Contextual inquiry revealed 3 user types: Brand managers, analysts, and product stakeholders
John Doe
Skincare market analyst
Core Pain Points
Hard to validate a trend
Decision paralysis
Too many steps to reach a decision
32%
Trust legacy tools
2-3
Hours manual analysis
Goals - View Data, analyze trends
Contextual inquiry revealed 3 user types: Brand managers, analysts, and product stakeholders
40%
Time lost switching
5–7
Tools used
The time problem solved, the tracking resolved and the proofing addressed
I started out with solving for tracking and a central place to acheive this Maybe the problem is just that the senior needs one place to send and collect declarations.
“Responses were scattered” → One team-level view
“Leads kept checking who was pending” → Visible progress + statuses
“Follow-ups were repetitive” → Actions directly from the tracker
“Conflicts needed separate attention” → Exceptions surfaced clearly
“People needed proof/history” → Activity / audit trail
“Clearance leads to another task” → Next-step CTA to the letter
Let's get down to business
#1 first try
I started out with solving for tracking and a central place to acheive this Maybe the problem is just that the senior needs one place to send and collect declarations.
What it solved :
✓ Better than email
✓ Centralized who was in the team
✓ Made sending requests easier
What it didn’t solve
✗ Still too passive
✗ The lead still had to scan every row to understand progress
✗ No clear sense of what is blocking the team
✗ No strong feeling of “are we ready yet?”
Feedback
Centralizing requests is useful, but it doesn’t reduce the mental effort of tracking the whole team.
Design rationale
Better than email
#2 Trying to solve tracking
I started out with solving for tracking and a central place to acheive this Maybe the problem is just that the senior needs one place to send and collect declarations.
What it solved :
✓ Better than email
✓ Centralized who was in the team
✓ Made sending requests easier
What it didn’t solve
✗ Still too passive
✗ The lead still had to scan every row to understand progress
✗ No clear sense of what is blocking the team
✗ No strong feeling of “are we ready yet?”
Feedback
Centralizing requests is useful, but it doesn’t reduce the mental effort of tracking the whole team.
Design rationale
Better than email
Killed directions
I started out with solving for tracking and a central place to acheive this Maybe the problem is just that the senior needs one place to send and collect declarations.
Final solution
I started out with solving for tracking and a central place to acheive this Maybe the problem is just that the senior needs one place to send and collect declarations.
