New product setup — Summary
Merchandising · Merchandise Planner · Runs weekly100% complete
1 waiting for a decision
Biggest wins in this workflow
- SimplifySupplier form to product system, no re-keying (step 2)≈ 30h/yr · ~35m/run
Hands-on time per run
2.3h
≈ 121 h a year
Planned to free (accepted)
0m per run
≈ 0 hours a year back to the team once done
Still open (recommendations to review)
35m per run
0m planned + 35m open + 1.8h untouched = 2.3h per run
≈ 30 hours a year if all adopted. Accepted ones sit under Planned to free; nothing here counts more than its step costs
Already automated today
0 of 7 steps
0m of hands-on time is on partly systematised steps — honest baseline, not opportunity
Top friction points
Worst first — how much a step hurts, multiplied by how long it takes. So a long mildly annoying step can outrank a short painful one.
| Step | Who does it | Kind of pain | Hurts | Time | Why it hurts |
|---|---|---|---|---|---|
| Rank 1, step 2, Re-key every attribute from the form into the product system | Category Assistant | — | badly | 45m | Pure double handling — the supplier already typed all of this |
| Rank 2, step 3, Chase and resize product images | Content Coordinator | — | a bit | 20m | — |
Recommendations
To review1
🔧 Change how these are done (1)~35m/run
Step 2Simplifyneeds setting up
Supplier form to product system, no re-keying
~35m per run of the step's 45m
How ▾
The supplier already typed every attribute. A build reads the completed form and pre-fills the product system record for approval — double handling becomes a quick check and a click.
Accepted0
None
Not now0
None
Manual hand-offs between systems
- 2 → 3Data moves from Product system to SharePoint by hand here.
- 3 → 4Data moves from SharePoint to Retail ERP by hand here.
- 5 → 6Data moves from Retail ERP to Ecommerce platform by hand here.
Worked out from the systems named on each step, so check it against how the work really goes. No time or cost is counted for these.