UI and Artifacts
Product Documentation & Process Work
Real artifacts from product work at Sierra Living Concepts — process maps, workflows, and documentation that show how I think about cross-functional execution and operational clarity.
New Product Development Process
End-to-end NPD workflow designed for Sierra Living Concepts — mapping two initiation paths across 8 departments, 4 stage gates, and a 12-day launch cycle. Adopted as the standard operating procedure and onboarding reference across teams.
Management Trainee (Product Strategy) · Jun–Oct 2025
8
Departments mapped
12 Days
End-to-end launch cycle
2
Initiation paths documented
4
Stage gates with approvals
Process Map — PDF
New Product Development Process
Best viewed on desktop. Tap below to open the full PDF or Canva view.
Sierra Living Concepts · New Product Development Process · 2025
Process Overview
Departments Covered
Stage Breakdown
Proposal & Research
Category Manager or Product Team initiates. Keyword research, competitor analysis, and Product Definition Document (PDD) created covering variants, dimensions, price range, and target persona.
Idea Screening & Go Decision
Heads of all departments screen the idea. Feasibility, target price, sourcing, and construction issues discussed. Output is a formal Go/No-Go decision that prevents later redesigns.
Design & Content
Designer assigned with start and end dates. Initial draft with dimensions and knockdown image sent to 4 departments for approval. Final render triggers content writing and SEO work.
Pricing, Inventory & Launch
Pricing prepared from final render dimensions. Inventory set up. Final approval from Category Manager, Product Team, Operations, and Logistics before launch.
Two Initiation Paths
Initiated by Category Manager
Category Manager identifies a market gap through keyword research, competitor analysis, and customer demand signals. Shares requirements with the Product Team who lead research and ideation.
Initiated by Product Team
Product Team identifies and proposes a new product opportunity. Submits proposal to Team Lead and Category Manager for approval before research and ideation begins.
Why This Process Was Built
Eliminate ambiguity in cross-functional launches.
Before this process map, different departments had different understandings of when they were involved and what they needed to deliver. This map made every touchpoint, approval, and handoff explicit.
Prevent late-stage redesigns.
The formal Go decision at Stage 1 — covering feasibility, pricing, and sourcing — was specifically designed to surface blockers early and prevent costly design changes after the Design phase had begun.
Create institutional knowledge.
The process map plus post-launch review documents were adopted as the onboarding reference for new team members and a handover document when categories changed managers.
View More Work
Case Studies →