The internal application is intended to facilitate the specific work of the team. Pilotage on the selected process helps to check assumptions before the company moves all its activities into the system.
Select a process with a visible problem
Do not start with the list of all modules you can build. Choose a job where delays, data copying or unclear division of responsibilities are repeated. Describe where the case comes from, who makes the decision and after which it is known that it has been completed.
For example, service applications may require one place to accept cases and assign performers. Before an expanded analysis panel is created, it is worth checking whether the team consistently records the basic events.
Invite future users
The person ordering the system does not always perform all daily activities. Invite employees who receive, transmit and close applications to review the scenarios. Examples of them will help to discover exceptions invisible in the general description.
Ask what happens in the absence of data, the absence of an employee or the reopening of a case. The pilot needs to be able to report a problem and indicate the specific place where the work is stuck.
Specify the conditions of the check
Before launching, specify:
- the group of participants and their extent of access;
- the types of cases sampled;
- how to prepare safe data;
- the recipient of the comments;
- the criteria for ending pilotage;
- proceedings where a return to an earlier trial is needed.
Do not judge success only with the number of logins. Observe whether the case can be handled from beginning to end and whether people still need to keep parallel, unagreed notes.
Expand after explanation of exceptions
In a company from Warsaw, like in a distributed team, implementation requires common rules. After piloting, improve the instructions, status names and responsibility for data. Then decide about further departments or integrations. Read more about roles and state of application and preparation of data portability.
