Automation of SACCOs - FSD Kenya
Automation of SACCOs - FSD Kenya
Automation of SACCOs - FSD Kenya
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
16 • AUTOMATION OF SACCOS: ASSESSMENT OF POTENTIAL SOLUTIONS<br />
Chapter 4<br />
requirementS gAthering AnD buSineSS<br />
AnAlySiS<br />
4.1 FIELD VISIT oBSErVATIonS<br />
The project team carried out visits to five <strong>SACCOs</strong> in four different towns and<br />
one city across four provinces. 6 The institutions visited proved to be diverse in<br />
several aspects and provided insight to different versions <strong>of</strong> the SACCO model.<br />
The project team got practically unlimited access to the senior management<br />
teams and could hold the necessary meetings without restrictions.<br />
Due to the pattern <strong>of</strong> required features that evolved as expected the project<br />
team regards the 190 requirements captured as a comprehensive and<br />
practically exhaustive list. It is unlikely that any additional requirements would<br />
significantly alter the outcome <strong>of</strong> any evaluation <strong>of</strong> available automation<br />
solutions.<br />
The outcome <strong>of</strong> the field visits is provided in three sections: the first describes<br />
a number <strong>of</strong> ‘experiences’ <strong>of</strong> specific conditions at the <strong>SACCOs</strong> that are very<br />
important to understand as they have a direct bearing on the probability <strong>of</strong><br />
a successful acquisition, implementation and operation <strong>of</strong> a new application.<br />
This recommendation does not claim to fully exhaust these topics but primarily<br />
create awareness and a starting point for mitigation. The majority <strong>of</strong> the<br />
<strong>SACCOs</strong> did not have a capacity to directly articulate business requirements. In<br />
the interviews they would rather explain how business is done and leave it to<br />
the project team to analyse this information and articulate the requirements.<br />
Thus are these experiences pre-requisites and a relevant context. Secondly,<br />
the actual functional and technical requirements are described and thirdly,<br />
a number <strong>of</strong> potential business process and operating model improvement<br />
opportunities are listed.<br />
4.1.1 Decision making rationale<br />
SACCO strategy and decision making process are highly relevant context for<br />
this project as the system needs to be aligned with the strategy and support<br />
each executive in their decisions.<br />
We have observed three issues with regards to these topics that could result in<br />
<strong>SACCOs</strong> acquiring a less than optimal or even directly unsuitable system and<br />
prevent them from getting the full benefit from the investment.<br />
Firstly the project team has observed that nepotism is prevalent in the<br />
movement. Executives do not base decisions solely on the factors that one<br />
would expect given the SACCO operations but also very much relationships.<br />
E.g. not only or even primarily operational fit and suitability, cash flow, pr<strong>of</strong>it,<br />
risk management and outreach to the community but they would also consider<br />
or set as a prerequisite if a board candidate, executive manager or supplier has<br />
a relationship to powerful entities in the <strong>Kenya</strong>n society and if they personally<br />
know the person. A relationship with e.g. a vendor provides tangible benefits<br />
such as increased transparency and predictability but they are unlikely to be<br />
6 Central, Rift Valley, Eastern and Nairobi Province.<br />
more important than the operating, technical and financial aspects <strong>of</strong> the<br />
system. Even more importantly decision deviating from the explicit strategy<br />
<strong>of</strong> the SACCO and with no clear business logic creates significant confusion and<br />
undermines employee morale.<br />
It will also be very difficult to articulate objectives and set targets for the<br />
automation project that are aligned with the rest <strong>of</strong> the SACCO if the acquisition<br />
decision is not aligned with the explicit strategy and requirements for the<br />
system. E.g. if the system does not fulfil the requirements for loan issuing<br />
how can the corresponding manager be held responsible for the efficiency<br />
gains and delinquency decrease expected from the investment in the system?<br />
Relationships appear to compensate for a lack <strong>of</strong> competence. When a manager<br />
or board is unable to make a proper assessment and negotiate a contract that<br />
protects the SACCO’s interest they rather deal with someone they know. The<br />
project team sees any discrepancy between the actions <strong>of</strong> the board and the<br />
executive management respectively the explicit strategy and objectives <strong>of</strong> the<br />
SACCO as a major risk to a successful acquisition and utilisation <strong>of</strong> the system.<br />
The logic <strong>of</strong> decisions will become a highly relevant topic as the regulations<br />
trigger not only the need for investments in technical infrastructure but also a<br />
review <strong>of</strong> the fundamental financial viability and competitiveness <strong>of</strong> <strong>SACCOs</strong>.<br />
In many locations the market is already heavily fragmented and members<br />
would benefit significantly from economies <strong>of</strong> scale created by consolidation.<br />
These benefits will increase as <strong>SACCOs</strong> have to carry the cost <strong>of</strong> IT systems.<br />
Quality systems are associated with minimum costs but can handle significant<br />
volume. Consequently, small <strong>SACCOs</strong> will struggle to achieve an attractive<br />
return on investment whereas larger <strong>SACCOs</strong> can leverage the scalability<br />
and also fully utilise advanced functionality. However, consolidation leads to<br />
a lower number <strong>of</strong> <strong>SACCOs</strong> and significant redundancy. Junior staff who can<br />
adapt to the computerised environment are not likely to be redundant as the IT<br />
systems will facilitate growth <strong>of</strong> the entire SACCO industry through increased<br />
outreach and thus more business. However, the number <strong>of</strong> board members<br />
can be reduced as the number <strong>of</strong> institutions and boards are decreased.<br />
The second observation is that there is a contradictory paradigm on an<br />
operational level by which members are considered to have rights to get<br />
loans even when they do not fulfil eligibility criteria and clearly would risk<br />
reducing the surplus available as dividends to other members and in the long<br />
run the sustainability and capital <strong>of</strong> the institution. This behaviour implies<br />
that one member is more important than another and is likely to originate<br />
in a combination <strong>of</strong> lack <strong>of</strong> understanding <strong>of</strong> asset liability management and<br />
empathy with or pressure from the applicant in need <strong>of</strong> capital. The project<br />
team sees an opportunity to use information from the system to train staff in<br />
ALM, to use the rigour <strong>of</strong> automated processes to enforce policy, document<br />
deviation from policy and hold decision makers accountable and to reward the<br />
intended behaviour.