J.
Jess Kim (b. Seoul)  is a NYC based Product Designer. She reads where people stall inside complex tools, then designs to move them. E-commerce trained, fast to ship. An artist at heart.
Get in Touch: jess.young.design@gmail.com
The human behind it
PRODUCT DESIGN


CRAFT
©2026 J.Young EmailLinkedInResume
.zoom { transition: transform .3s; width: 200px; height: 200px; } .zoom:hover { transform: scale(1.1); } .shimmer-text { background: linear-gradient( 90deg, rgba(255,255,255,0.35) 0%, rgba(255,255,255,0.7) 40%, rgba(255,255,255,0.99) 50%, rgba(255,255,255,0.7) 60%, rgba(255,255,255,0.35) 100% ); background-size: 200% auto; -webkit-background-clip: text; -webkit-text-fill-color: transparent; background-clip: text; animation: shimmer-pass 13s ease-in-out infinite; animation-delay: 0.5s; } @keyframes shimmer-pass { 0% { background-position: 150% center; } 35% { background-position: -50% center; } 100% { background-position: -50% center; } }
003  Operational Chaos to Zero Rework: Engineering a Single Source of Truth Eliminating Repetitive Production Loops During Platform Migration to Save 1.5 Days Per Production Brief
WCONCEPT


Experience a Team That Ships Without Friction
"By engineering a centralized production gateway that mapped live-coded assets to unique Page IDs, we eliminated redundant resolution loops and reduced production lead time by 1.5 days per brief."






Overview: When Wconcept migrated from Magento to a custom internal system (BO), I identified a structural breakdown: planners kept requesting features that no longer existed in the new system. Team meetings addressed it. The requests kept coming. The problem wasn't that people weren't listening. There was simply no persistent reference to check against. I built a centralized system that reduced internal rework from 60% to near-zero and cut production lead time by 1.5 days per brief.
 Context:
Migration meant daily chaos — new bugs, broken features, and growing backlogs layered on top of existing workloads. Planners defaulted to last season's references, unaware that features which worked seamlessly in Magento had simply ceased to exist in BO. In this environment, the same "this isn't possible" conversation kept happening — with different planners, in different weeks — quietly consuming designer bandwidth that should have gone toward building, not blocking.





 A. Problem Discovery
Identifying the Structural Root of a Communication Loop




The Pattern No One Had Named Yet
Because every production brief was routed through me before being assigned to the design team, I had a uniquely complete view of incoming requests. What I saw wasn't random — it was a pattern. The same unsupported features were being requested again and again, by different planners, in different weeks. Team lead meetings had been used to communicate limitations, but in the middle of a migration, information didn't stick. The problem wasn't that people weren't listening. The problem was that there was no persistent, accessible reference to check against.



a.
Action Mapped recurring unsupported requests and traced their downstream impact on designer workload.
b.
Impact Confirmed a systemic loop that verbal communication had consistently failed to break.
a.
Action Mapped recurring unsupported requests and traced their downstream impact on designer workload.
b.
Impact Confirmed a systemic loop that verbal communication had consistently failed to break.





B. Strategy: The Proactive GatewayShifting from Reactive Blocking to Proactive Validation




a.
Action Repositioned the framework as a mandatory pre-validation step in the planning workflow — a reference planners could consult before submitting a brief, rather than receiving a rejection after.
b.
Impact Shifted the team's operating model from "individual memory" to "shared system reference," aligning strategic intent with technical feasibility from the very first stage of planning.
a.
 Action
Repositioned the framework as a mandatory pre-validation step in the planning workflow — a reference planners could consult before submitting a brief, rather than receiving a rejection after.
b.
 Impact Shifted the team's operating model from "individual memory " to " shared system reference," aligning strategic intent with technical feasibility from the very first stage of planning.





a.
Action Audited Magento-era constraints against BO's capabilities — clearly mapping what was possible, impossible, and newly available — then translated that into reusable page archetypes (Type 01–05).
b.
Impact Eliminated the guesswork that drove redundant requests. Planners now had a reliable boundary map, and designers no longer had to re-explain the same limitations repeatedly.
a.
Action Audited Magento-era constraints against BO's capabilities — clearly mapping what was possible, impossible, and newly available — then translated that into reusable page archetypes (Type 01–05).
b.
Impact Eliminated the guesswork that drove redundant requests. Planners now had a reliable boundary map, and designers no longer had to re-explain the same limitations repeatedly.





C. Systemic ProductionA Living Library for Direct BO Access
TYPE 01  Video-Integrated
TYPE 02 Img Transition
TYPE 03 Interactive Img Mapping
TYPE 04 Custom Navigation Controls
TYPE 05 Category Tab Product
a.
Action Built a visual indexing system in Figma — each layout mapped to a specific BO Page ID. Live pages linked directly. Archived pages accessible via ID for immediate code reference.
b.
Impact Gave the design team instant access to verified, deployable code — eliminating search time and repetitive troubleshooting entirely.
a.
Action Built a visual indexing system in Figma where each layout type — categorized by behavior and technical platform — is mapped to a specific BO Page ID. Live pages are linked directly; archived pages are accessible via ID for code reference.
b.
Impact Gave the design team instant access to verified, deployable code — eliminating search time and repetitive troubleshooting entirely.





D. Performance & ValidationQuantifying the Impact Across 100+ Migrated Pages
~0%Internal Rework Rate Reduced from 60% to nearly 0% by giving planners a reliable feasibility reference before submission.
1.5daysLead Time Saved Average time saved per brief by eliminating redundant loops and enabling direct code access.
100%Execution Success
 Rate of immediate execution for incoming production briefs following framework adoption.
System
DrivenProduction Logic
 Shifted from reactive fixes and
repeated explanations to a scalable, self-serve reference framework.
~0% Internal Rework Rate Reduced from 60% to nearly 0% by giving planners a reliable feasibility reference before submission.
1.5 daysLead Time Saved Average time saved per brief by eliminating redundant loops and enabling direct code access.
100% Execution Success  Rate of immediate execution for incoming production briefs following framework adoption.
  System Driven Production Logic Shifted from reactive fixes and
repeated explanations to a scalable, self-serve reference framework.

*Rework: a production brief that came back for a repeat feasibility or reference request after handoff.
*Measurement: counted from the shared MD/MKT/Design tracking sheet and email briefs, not a ticketing system. The 1.5-day gain reflects the rise in briefs cleared per week once the reusable library existed.

a.
Action Monitored rework rates and production lead times across the migration of 100+ pages to validate the framework's real-world impact.
b.
Impact Achieved near-zero internal rework rate and reduced average production lead time by 1.5 days per brief. More than an operational fix — this project demonstrates how design-led systems thinking can eliminate structural friction at the organizational level.
a.
Action Monitored rework rates and production lead times across the migration of 100+ pages to validate the framework's real-world impact.

b.
Impact
Achieved near-zero internal rework rate and reduced average production lead time by 1.5 days per brief. More than an operational fix — this project demonstrates how design-led systems thinking can eliminate structural friction at the organizational level.