tech2018:s2:poa_design
Table of Contents
1. Understand the process and roles (who is doing what)
The first thing you have to to is to mature the complete understanding of “who is doing what” to achieve your expected result. If you are lucky enough this understanding should be based on a documented process that the business consultant should have shared.
2. Define the POA, forms fields and exit scenarios
Based on the simple process we have, this is the list of activities we assume to have:
| Activity type | Role | process | deliverables |
|---|---|---|---|
| VC_CALL | FO_SALES | The user will call the prospect and ask if there is any interest on the product Vacuum Cleaner. If YES then he/she will create a new activity for back-office in order to create and send a customized quotation. Otherwise the operator will just close the thread | The RESULT variable will tell if the process should proceed or not |
| VC_QUOTATION | BO_SALES | The backoffice operator will create and deliver a customized quotation for the Vacuum Cleaner | The DATE of sending can be a reasonable info to be stored. |
3. Define companies and routings
The scenario is pretty straight-forward:
- We have 2 roles: FO_SALES and BO_SALES
- We have 2 companies, FO_COMPANY and BO_COMPANY.
When the first activity is created it must be assigned to the company FO_SALES. When the second activity is created it must be assigned to the company BO_SALES.
4. Define reporting/KPI on forms data
Based on the process info we can suppose to have 2 KPI:
- How many thrads landed in a quotation;
- What is the date of sending of the quotation.
tech2018/s2/poa_design.1528143245.txt.gz · Last modified: 2018/06/06 10:36 (external edit)
