Search results for query: *

What aspect of it are you referring to? System led audits and greenfield reporting didn't exist. It was not possible to see who had an incorrect AIS unless you manually went thru the list and checked each location visually. System led audit finds baffles in about 50% of generated locations and...

Yes, it's true that you could see that before. But because of the improvement in system led backroom audit, you have better information about who did it incorrectly or not.

>85 is Green. 80-84.99 is yellow. Less than 80 is red.

It looks like it is live. Our score is 85.5. Anyone see anything different?

It's the memorial day weekend. I doubt we'll see anything until Tuesday.

It's working fine for me! Make sure you have the correct time frame selected and that the dataset has updated since your last scan date.

If a calendar falls into the compactor, and nobody (important) is around, does it make a sound?

They're less likely to do replenishment maintenance on an individual item than class level. I currently have about 150 eaches of every single type of hair color. I asked them to cut it out, and they claim they're going to send less... we'll see about that

This is a opportunity that they are looking to address by integrating it into existing systems in the future. For now, this is our upgrade from paper copies, filed in an elusive binder.

Yes. I see that. I was hoping to avoid double work by having to scan everything twice. So now I know that won't work!

I was recently doing a system led backroom audit and came upon Style Hang where there were three backroom location hangers, but only one of them was being used for the whole bar, which is of course, the location I was asked to audit. Seeing an opportunity for correction, and prior to completing...

I use a barcode generator. I got the idea after the one that was in the myStore app was decommissioned. I also create private greenfield reports that allow me to display various things I might need barcodes for. Lots of potential for misuse, so I don't tend to share this idea with TMs...

You guys make good points, but you're also probably not the team members causing all the problems. It's clearly expressed that the pattern reporting isn't meant to be the end-all-be-all for coaching team members, but rather a starting point for validating the team members training and actions...

That's because you've worked in a system that lacked sophisticated root cause reporting. This is a major step in the right direction. Instead of applying band-aids, surfacing the patterns that lead to chaotic backrooms. Of course, it's only as good as the leaders driving accountability to best...

I believe that all backroom location management tasks have recently migrated to only being accessible to Team Leads and above.

I have holding peer sessions with my fellow team leads to teach them about the change and give them tips on how to hold huddles with their teams. It's not up to me to talk to every team member about it, but I'll be damned if their leads say it was because they didn't know.

No. I'm pretty sure it's the SPT team in India who have absolutely no clue what they're doing, in combination with some technology issues involving migration and integration from legacy systems

This is extremely common. It's why there's a thread on the new backroom accuracy indicator because old metrics were falling short of measuring the true inaccuracies

If you know for sure that you backstocked it in the correct quantity, there will be reporting indicating the last activity of someone interacting with it. Whether that was in take, fill, audit or ePick

T0332