between the low‐tech MIS solutions, the local situation for the implementing organizations, and the capacity of the end‐users contributed to a high degree of local ownership of the MIS.

# **Local solutions**

Developing simple, accessible technical solutions also contributed to establishing an effective MIS. An Ethiopian IT firm developed the technical solutions locally, which were based on free software with a user‐friendly design, so even if many of the individuals involved lacked technical capacity to develop, use, and maintain the IS solutions, which the literature has identified as a risk factor, the low‐tech solution helped overcome this challenge.

Developing the MIS was a long process, starting with initial specification of the core data requirements for the project and development of a full M&E manual. The first steps in registering clients involved developing and testing of an Excel‐based registration form, which provided useful insights into what a functioning MIS should look like.

# **Attention to Data Quality**

The WEDP intended to provide several services to clients, mostly financial services and training. Because clients could access many combinations of services from different service providers that were not linked to each other, it was essential from the planning stage of the MIS that WEDP services provided should be identified for each client. The first step was therefore to develop a unique client identifier.

Another important challenge was to ensure basic data quality. Given that so many diverse users were accessing and uploading data to the system, it was important to develop quality checks to minimize errors in data entry and avoid misunderstandings. To avoid confusion, training and demonstration videos were complemented with pop‐up boxes that would explain in the local language exactly what information needed to be entered. If an incorrect data format was used, the user would receive an error message with an explanation of the correct format or type of information to enter. In addition, experience suggested that pull‐down menus with fixed choices simplified data entry and minimized likelihood of errors.

In the initial phase, tests were run on the database to ensure data quality. The database could be exported to Excel and then used with any statistical software. This was helpful for detecting errors in the system and refining data entry procedures. Moreover, WEDP M&E staff used exported data regularly to conduct advanced analysis. Although the built‐in reporting functions shown in the previous section worked well for basic monitoring and provided some standard evaluation tools, the richness of the database could be used in a range of ways when not restricted to prespecified parameters.

The WEDP also had a database expert conduct in‐depth advanced data quality assessments and check for errors,<sup>8</sup> which provided useful technical inputs for refining the system.

> 8 It was necessary in this case to inquire into errors leading to incorrect identifications when uploading data from the first‐phase Excel‐based system into the final version of the MIS. It is difficult to guard against human errors, but the MIS minimizes the likelihood of such errors.

21