1 of 7

Slide Notes

Mako translating for me and yukako/merch team. Eiko for logi, and Tenda for murata-San.

Close your computers for the beginning, please.

2 hours.

FH taking notes: important and "save for later" topics and solutions.

Goal today: identify a solution that will reduce time spent preparing product for shooting and can be implemented within 2 weeks.

In the next 20-30 minutes I will explain my proposed solutions and why they are viable. Then, let's hear solutions from everyone, discuss how and why, and pick the agree which solutions we would like to implement.



DownloadGo Live

NoPO Solutions v2

Published on Nov 18, 2015

No Description

View Outline

MORE DECKS TO EXPLORE

PRESENTATION OUTLINE

1.

NOPO SOLUTIONS

SAVE TIME. RELIEVE PAIN. QUICKLY.
Mako translating for me and yukako/merch team. Eiko for logi, and Tenda for murata-San.

Close your computers for the beginning, please.

2 hours.

FH taking notes: important and "save for later" topics and solutions.

Goal today: identify a solution that will reduce time spent preparing product for shooting and can be implemented within 2 weeks.

In the next 20-30 minutes I will explain my proposed solutions and why they are viable. Then, let's hear solutions from everyone, discuss how and why, and pick the agree which solutions we would like to implement.



Photo by FreddieBrown
2.

SOLUTIONS

No Data:
Why is this a roadblock? Current rule is misguided, POs are late. No one is managing upload "accuracy."
1. Improve the rule
2. Manage accuracy

Code Discrepancies:
Why roadblock? We can't put incorrect labels on product.
1. Logi - more receiving power/receiving specialist.
2. Receive discrepancies as NoPO.
3. (Optimise - receiving, sku creation, report/id process)

Reporting
1. Google doc
2. Jira
3. Dashboard
- what do we need to know?
- who needs to know?
- what do we need to do?
- who needs to do it?
Photo by Juantf74
3.

ROOT CAUSES

  • Symptom: Pain
  • Causes: Delays & Recieving Roadblocks.
Pain = symptom.

Things that prevent us from receiving = cause.

What are receiving roadblocks? (P. 1-2)
How often do these roadblocks occur? (P. 3)

We need to eliminate roadblocks that can be eliminated and reduce those that cannot.

I think we can eliminate "No Data" delays and reduce delays caused by "Code Discrepancies" immediately.


Photo by stephenjohnbryde
4.

SOLUTIONS

No Data:
Why is this a roadblock? Current rule is misguided, POs are late. No one is managing upload "accuracy."
1. Improve the rule
2. Manage accuracy

Code Discrepancies:
Why roadblock? We can't put incorrect labels on product.
1. Logi - more receiving power/receiving specialist.
2. Receive discrepancies as NoPO.
3. (Optimise - receiving, sku creation, report/id process)

Reporting
1. Google doc
2. Jira
3. Dashboard
- what do we need to know?
- who needs to know?
- what do we need to do?
- who needs to do it?
Photo by Juantf74
5.

DOING NOPO

  • Eliminate NoPO?
  • Intentions.
Kat: why do we do NoPO?

So, we need NoPO report and identification process.

Masae: why do we do NoPO?

We wanted to make the old process easier and more efficient. But we didn't. We can correct this.
Photo by Tris Linnell
6.

QUICK, SHIP NOPO!

  • Ship first, size/material after.
  • Ship and perform size/material at Shiomi.
  • (Various other solutions.)
  • All this for a band-aid?
We discussed this in our last meeting and I have received feedback that many of you are interested in pursuing this solution.

I want to address this now, quickly, and return to this topic when you have the floor.
Photo by Autumn Welles
7.

THE PAIN

  • After everything else.
  • LATE.
Doing: identifying, deciding: keep/RTV, verifying: do these units need to be shot, communicating, editing/updating product/sale info via admin.

Everything Else: the last of many issues that prevent SB from receiving, requiring logi communication and merch attention.

LATE: by the time NoPO is reported. It's late!
Photo by dbtelford

C I