-
1. Introduction
-
2. Translating data into action: essential components of a TB recording and reporting system
-
3. Designing an optimal information system
-
4. Recommended process of development
-
5. Resource requirements
-
6. Measuring the impact of the information system
-
References
4.2 Pilot
Before going live, each feature should be piloted in the field to ensure that it is working as expected.
There are many reasons as to why a system may not function as intended, for example:
- The software development team did not understand exactly what was needed.
- The programme team did not understand field realities.
While there is no guarantee that the pilot will bring all gaps in an information system to light, the process usually serves to highlight any major issues. It is important to remember that exposing a large number of users to a problematic system on day one may lead to a loss of trust that is very hard to rebuild, even once the problems are fixed. By piloting the system with a small number of users in a specific area, this risk is minimized. Programmes must plan for pilots, building them into budgets and project timelines. Not planning for pilots and rushing to roll systems out quickly to meet unrealistic timelines can result in the complete failure of an information system.