Take Advantage of the Exhibition Questionnaire

Monday, February 10, 2014
The questionnaire paper, it leaves the tough work of 'Data entry'.

Even though... passing a pen and a sheet are realistic at 'Exhibition fair' or 'Housing Exhibition'. The next day, facing with its enormous "bunch of questionnaire", to input into Excel with division of labor. (as is often ...) The finished Excel file will be added pie graph and bar graph, and finally will be reported at the meeting.... (Is that all?)

Still, I would like to standardized approach business for "the prospects". (Follow-up plan)

If the procedure can be defined, it is better to input to Workflow (process-oriented system) rather than entering Excel such as (data-oriented systems). (You can export to Excel at ANY time.)

In the following Workflow, each one of the 'prospective client' will be handled in the flow. That is, prospective client data that has been entered, will be underwritten by a salesperson to be confirmed whether or not to visit, with 'appointment by phone'. Then, if it should be visited, the salesperson will approach to see if it could become business talk by visiting.

You can monitor the progress of getting into business talk in real time.

And at the same time, information about 'whether or not got into business talk' will be added to the data written on the questionnaire. Awesome.

[Prospective Client Questionnaire]

[Prospective Client Questionnaire:'3. Visit, etc. (Business Judgement)' screen]

[List of Process Data Items]

By the way, an excellent point of this workflow example is reducing input error by utilizing "Regular Expression check" during data entry.
  • Zip code: "[0-9]{3}-[0-9]{4}" -> '3 digit number, hyphen, 4 digit number'
  • Phone number: "[0-9]{1,4}-[0-9\-]{4,9}" -> '1 to 4 digit number, hyphen, 4 to 9 digit number'
  • Email address: "[a-zA-Z0-9][a-zA-Z0-9_\.\-+]*@[A-Za-z0-9_\.\-]+

A regular expression is "notation that defines the pattern of the string", and is widely used in the world of computers in the fields such as "search" and "substitution". Every time I see them, it looks like a "cipher" to me. Having said so, you should understand only basic methods of the expression.
  • [0-9] -> "A number of 0 to 9" (It may be written as "\d")
  • [0-9a-zA-Z] -> "A character of alphabet or a number" (It may be written as "\w")
  • {3,7} -> "Specifies the minimum and maximum number of times for the preceding item"
  • * -> "Preceeding item must match zero or more times."
  • + -> "Preceeding item must match one or more times."
  • ? -> "Preceeding item must match one or zero times."

By the way, the important thing is to run a business improvement cycle properly. Instead of exploring "higher matching rate regular expression", you should raise the flexibility using the regular expression that meets "level of your own" and "needs of the field". For example, the regular expression may be amended as the following, if happens 'Hyphen missing' and 'area code missing' only in typing phone numbers.

Phone number: "0[0-9]{1,4}-[0-9]{1,4}-[0-9]{4}" -> 'Begins with 0, 1 to 4 digit number, hyphen, 1 to 4 digit number, hyphen. 4 digit number'

<Similar Models>
<<Related Articles>>