One-to-one

One-to-one technical support is when an organisation is given support on an individual basis. Often the support is specifically designed to meet the needs of the organisation and can more readily take into account the capacities and particular circumstances of the individuals and the organisation.

One-to-one technical support is one of the most effective technical support mechanisms. While not appropriate in every case, it allows NGO/CBO support providers (NSPs) to gain a first-hand understanding of a project and of the problems and perspectives of a group or organisation. It also offers greater opportunity for interactive exchange between those involved and the establishment of closer relationships based on trust. Face-to-face meetings are a good way to establish relationships, but telephone, email and post are also an important way to maintain regular contact and provide resources.

One-to-one consultation is usually the best way of solving entrenched organisational problems, so that technical assistance is based on the real-life circumstances of the particular NGO or CBO and not just theory. It can also be very useful when establishing new systems (for example, setting up an accounts system or database), or when it is involved in unfamiliar and complex planning (for example in community assessment, designing projects, report writing or annual review).

However, one-to-one support is usually the most costly form of technical support, and is not appropriate if rapid dissemination of basic technical assistance is needed by many NGOs and CBOs. Because it depends on the quality of the personal relationships developed between individuals, there is the possibility of unforeseen conflicts or incompatible personalities. It is also difficult to monitor because the exact content of the technical support is hard to predict in detail.

Issues to consider

  • One-to-one technical support is both costly and labour intensive and NSPs need to take a realistic view of these costs in developing their technical support workplans and budgets.
  • Although it may be more convenient for staff from partner organisations to come to the NSP’s office, often more learning takes place in the environment in which it will be practised.
  • Because of the increased exposure to the organisation being supported, it is tempting to try to tackle everything that could be improved in its work. It is important to stay focussed on the most important issues that need to be addressed.
  • The quality of one-to-one support will depend much on personal and individual skills. Thus, it is important for both the NGO and NSP to ensure that there are clear terms of reference defining objectives, outcomes, and arrangements for supervision, reporting, and evaluation.
  • One-to-one technical support can lead to a sense of hand-holding and NGOs and CBOs may become too reliant on outside help. This may be necessary for nascent and developing groups, but should otherwise be avoided by keeping to a technical support plan that is owned and updated by the partner organisation.
  • An individual technical support visit can be used to facilitate problem solving within an organisation, when an independent or objective perspective may help to resolve differences. However, such involvement may undermine the perceived objectivity of the NSP and also increases the sense of dependence upon the NSP.

Resources

Checklist for monitoring visit to Lead Partners and Implementing NGOs

A brief checklist for NGO support organisations visiting implementing partners.
International HIV/AIDS Alliance, 2001, Word, 1 pg, 23 kb

, ,

Mentoring for change

Description of a partnership between NGOs and the Government of South Africa.