- Joined
- Sep 12, 2015
- Messages
- 264
If you were given free reign in your store, how would you spend your days?
The current structure of the store stays the same- leadership is the same, work centers are the same (and still have the same TMs)- literally the only difference is you are now given the freedom to decide what you work on.
And no, "quality tester" at Starbucks doesn't count!
Personally, I'd be really in to the idea of being in charge of everything that falls through the cracks. Capacity problems, finding all of the expired food/broken/defective items on the salesfloor/in the back, maintaining the quality of WACOs and shelf labels, managing challenge (or, rather, enforcing challenge and holding TMs accountable) I love finding mistakes, not because I like the idea of a "gotcha moment" but because you have 100% proof that you just took something that was broken and fixed it.
Obviously over time I'd rather this be about fixing broken processes and coming up with the most efficient solution instead of fixing a million tiny errors that are bound to repeat themselves with the broken system, but I think you'd need to focus on the tiny errors at first in order to 1. understand what is going wrong 2. develop new strategies, and 3. rid the store of them so you can start new and not have to worry about old errors popping up.
The current structure of the store stays the same- leadership is the same, work centers are the same (and still have the same TMs)- literally the only difference is you are now given the freedom to decide what you work on.
And no, "quality tester" at Starbucks doesn't count!
Personally, I'd be really in to the idea of being in charge of everything that falls through the cracks. Capacity problems, finding all of the expired food/broken/defective items on the salesfloor/in the back, maintaining the quality of WACOs and shelf labels, managing challenge (or, rather, enforcing challenge and holding TMs accountable) I love finding mistakes, not because I like the idea of a "gotcha moment" but because you have 100% proof that you just took something that was broken and fixed it.
Obviously over time I'd rather this be about fixing broken processes and coming up with the most efficient solution instead of fixing a million tiny errors that are bound to repeat themselves with the broken system, but I think you'd need to focus on the tiny errors at first in order to 1. understand what is going wrong 2. develop new strategies, and 3. rid the store of them so you can start new and not have to worry about old errors popping up.