Document issues that come up during the pilot and consult the SLG on major changes that need to be made.
This example status report from Namibia shows how to report issues that arise to the stakeholders and make recommendations for actions to take in response. Use this report as a model for documenting issues during the pilot test.
Issues and Risks: Concepts
The pilot is an opportunity to test the system requirements and customizations made during deployment. New issues and needs that weren’t considered will almost definitely arise during this time. It should also become clear whether the system requirements are adequate to support the goals that the stakeholders want to accomplish.
While implementing the pilot, analyze its capabilities for meeting such needs as:
- The system’s capacity to accept the HR data generated
- The ability of the system to generate the reports required to effectively manage the health workforce
- Users’ ability to understand and use the system
- The ease with which the system can be implemented on a larger scale.
Also identify any potential problems associated with using the system during the pilot, such as inadequate ICT expertise to provide technical support or deficiencies in infrastructure. Document the maintenance needs of the system and any technical problems experienced, such as data corruption, system crashes, or issues with security of the data. This information will be helpful when planning for resources and technical support during the scale-up phase.
If major changes are needed—for example, the pilot reveals that the system will need extensive customization before it is ready for scaling up—present the findings to the SLG for a decision.