Utilizing Workflow for Smooth Web Site Operation

Monday, March 3, 2014

"Updating the Website" is operations that exist in most companies.
And the "Workflow" for it is shrouded in secrecy...

First of all, speaking about "site update", there are a variety of "levels".
  1. Correcting the typographical errors.
  2. Adding a blog post
  3. Adding information such as press release news, etc..
  4. Adding the introduction page of product service.
  5. Replacing the induction banner on the homepage. 
  6. Changing the site design as far as leading to advertising campaign.
  7. Changing the platform (CMS), major relocation and major modification.
  8. Outsourcing to a professional company, build a project of large-scale modification.

In the following Workflow, it aims to up to "level 5" of the above 8. In plain words, this workflow smoothes the "operations of the Web site on a daily basis". And it records adding or editing on the Web page automatically.

At any time, people who concerned will be able to see who created which content (= governance point of view), how many times a month each member makes updating (= personnel evaluation point of view), as well as the history of the Website (= governance point of view).

[Website Updating]

[Website Updating;'1. Layout & Page Update' screen]

[List of Process Data Item]

What brings a good sensation of "Process Modeling" is that it has been designed in "perspective of day-to-day operation".

For example, people would not think modeling (try to populate to Workflow) [Typographical Errors Correction] which would be completed in a single step. In ordinary thinking, it would not motivate input operators since it will end only in [1. Layout & Page Update]. But in this Workflow, it is set Numeric type data item of "Activity Score" and its "Default Value" of '1'. That is, the operator will be able to earn activity rating "1pt", even in "Typographical Errors correcting". We may call this "Gamification".

<<You may enter "self-evaluation", though your leader will give the final evaluation.
Guideline: Typo Correction (1pt), Blogging (3pt), Case Article (5pt), Manual appending (5pt), Manual renewal (7pt), Adding Excellent page (10pt)>>

Moreover, it is also good that it is not defined "irregular processing". You would be apt to draw a lot of "Sending-Back flow" somehow, but if there is missing information in the upstream Step, it can be complemented in the Enterprise Social Network that is at its height of prosperity. You don't need to waste precious time by sending back the cases all the way.

[Free Download]
<Similar Models>
<<Related Articles>>