A suggestion ? A question ?
Your contact Frankie H0U
Template to deal with your problem : HERE
Discover and contact the best in Office
See below specific Examples, Standards and Tools for you to duplicate in your Organization. Do not hesitate to share your own good practices to the referent of this page.
Here is the list of observable situations to allow you to evaluate your Organization
This grid corresponds to version 11.2 for which we have changed the vocabulary to make it accessible to all actors at Decathlon (stores, warehouses, factories, brands & services).
To reach a level (A/B/C/D), all the observable situations of the level must be fulfilled.
If none of the observable situations are applied, it means that you have the level E.
Everything in red indicates the people involved in the action.
Everything written in bold black corresponds to the important points of the action.
❶ Some routines are used to detect problems
❶ Gaps between real & expected situations are highlighted (example by color management gree/red).
❸ The gaps are recorded.
❹ Reaction rules are standardized to turn detected problems into corrective actions. The reaction rules explain when to react, who to inform, what to do, etc...
❶ Example : Monitoring Committee, Steering Committee, Debrief...
❸ Example: an RPM which is higher than its target, immediately triggers a RED alert on a product
❶ To ensure a preventive reaction system, the choice of the alert levels, allow to detect drift as early as possible.
❷ Detected problems are systematicaly turned into formalized preventative action plans.
❶ Example: For an RPM whose target is 1,000, it has been around 900 for a period. We set an alert threshold at 900, from which we trigger a 30 min weekly routine to analyze the drift.