The manager of each store inputs "Report of store summary" by every Monday morning. Report contents are the following 6 items.
- The number of customers of a week (Numeric type data)
- Item which sold quite (Select type data)
- Cause of Good sales (String type data)
- Item which did not sell many (Select type data)
- Cause of Bad sales (String type data)
- The outcome of this week, and the goal for the next week (String type data)
Area manager at Headquarters checks the manager's report in the morning of Monday, and makes "comments" and "questions" to each one the report. An email goes to the store manager whose report has been commented. Also an email goes to the store manager whose report has been asked questions, and the store manager is required to input "Answer to the question from Headquarter".
In addition, it should be reported surely every week with minimum labor of making the report, because it is a day-to-day operation to be performed repeatedly. Also, the report content should be opened to all store managers so that they can browse the reports at any time.
<Organization Info>
- Company
- Kanto; Tokyo store, Shinagawa store, Yokohama store
- Chubu-area; Nagoya store
- Kansai-area; Kyoto store, Osaka store
(This blog, "Workflow Sample" is falling into a rut recently. Suddenly, a thought of posting in a format of 'Business designing exercise' (Process Modeling exercise) came to me...)
[Data Items list screen]
[Weekly Report flow-Common Choices]
[Weekly Report flow-Common Choices;"2. Comment/Question" screen]
- How many customers did the other stores attract, last week?
- Which item was sold well in the other stores?
In fact, each report from the other stores is a information which a store manager concerns. Fresh "information of the week" will be a big reference for management of own store. Specifically, a store manager can compare the performance of its own store with the other store's trend, or can apply the best practices at other stores for own store. Of course, you should be better altering the frequency of information updates (daily / weekly / monthly), for it varies according to the business scale or Management Principles.
By the way, both of data items [2. Item which sold quite] and [4. Item which did not sell many], are 'Select type data'. And the choices such as "Espresso" or "Bagel", will be the same list. In such a case, by setting as referring to the cafe-menu.xml, management (maintenance) of reporting system becomes easier.
＜cafe-menu.xml＞
<items>
<item value="h1" display="Espresso" />
<item value="h2" display="Americano" />
<item value="h3" display="Latte" />
<item value="h4" display="Black Tea" />
<item value="c1" display="Iced House Blend" />
<item value="c2" display="Iced Tea" />
<item value="c3" display="Organge Juice" />
<item value="c4" display="Lemonade" />
<item value="c5" display="Soda" />
<item value="e1" display="Bagel" />
<item value="e2" display="Oatmeal" />
<item value="e3" display="Serial" />
<item value="e4" display="Cheese Burger" />
<item value="e5" display="Pan Cake" />
<item value="m1" display="Prix fixe A" />
<item value="m2" display="Prix fixe B" />
<item value="m3" display="Prix fixe C" />
</items>
[Free Download]
- Business Template: Weekly Report flow-Common Choices (including Choices XML file)
- Meanings of Taking In the Meteorological Data to "Daily Reports" (Utilizing Weather API) (2013-10-21)
- Automatic Conversion of Sales on the Exchange Rate of the Day (Utilizing of Currency API) (2013-10-23)
- Accelerate Daily Report Flow with 'HEAT Map' (2013-09-02)