Describe one process and its boundaries
Select the recurring activity, the process owner, and the expected result. Separate the preparation of the draft from the action with consequences: sending a letter or recording in CRM requires a separate decision.
Training task: a manager sorts out requests for the supply of equipment from the mail. The pilot retrieves the equipment type, quantity and city, notes the gaps and prepares a response. The manager checks the fields and confirms the next step. The system does not promise price, availability and delivery without a verified source.
Prepare the input data
Samples must show the actual composition of the work. Agree on the transmission method and accesses; For the first discussion, impersonal examples will suffice.
- Common requests and complex cases: omissions, contradictions, repeated requests.
- Description of the required fields, their formats and examples of the correct result.
- Documents and reference books with owners, versions and access rules.
- Current systems, available APIs and test connection capabilities.
- An employee for checking, the procedure for analyzing errors and observing the time of manual work.
Agree on criteria before development
Set aside some examples for final review. For each criterion, define the measurement method and acceptable result with the process owner. The table below is a test template, not ITTECHE test results.
| Criterion | How to check | What to agree on |
|---|---|---|
| Extracting fields | Check each field against the standard and the original request. | A set of required fields and acceptable errors for each. |
| Omissions and contradictions | Provide examples without a city and with different numbers in the sources. | Clarification route; prohibition on inventing meanings. |
| Validity of the answer | Check every promise and source link. | Allowed sources and response in the absence of confirmation. |
| Action control | Check draft, event replay and test API failure. | Confirmation by an employee and no re-entry. |
| Workload | Measure manual entry, checking, and exception handling with comparable examples. | What we consider an improvement and what costs we take into account. |
Submit the prototype for joint review
Go through a consistent set of examples, save errors and reasons for manual corrections. Don't judge a solution based on a successful demo alone. Discuss quality, relevance of sources, reviewer workload, and cost of operation.
Select next step based on results
The solution can be different: refine the rules, improve the data, connect business systems, or stop the hypothesis. Fix the restrictions and composition of the next stage. Evaluate the freed up time separately from the actual reduction in cash expenses.
Apply to your task
Describe one process, its participants and the expected result. We will agree on the initial data, checks, exceptions and composition of the first stage.
Discuss first pilot →