A Worthy Mission Needs a Capable Team

Public benefit organizations attract people who want their work to matter. That commitment is valuable, but a shared sense of purpose does not automatically produce strong performance. Staff also need suitable skills, clear responsibilities, effective supervision and the resources to do their work.

Building a high-performing team begins before a vacancy is filled and continues throughout a person's employment. Leaders shape performance through decisions about recruitment, induction, reporting structures, objectives, coaching, pay, recognition and accountability. In organizations implementing multiple projects, they must also help staff work as one organization.

1. Recruit for the work and the values it requires

When an organization urgently needs someone, it can be tempting to select the most available candidate or the person with the most impressive CV. Neither is enough.

Start with the actual demands of the position. What must the person deliver? Which skills are essential from the first day, and which can be developed? Does the role require field judgment, careful documentation, community engagement, technical expertise or supervision of others?

Use a fair selection process that tests relevant abilities. Structured interviews, practical exercises and reference checks can help the organization assess competence and conduct. In work involving children or other vulnerable people, recruitment must also follow the organization's safeguarding requirements.

Values should be assessed through evidence. Ask candidates how they handled an ethical concern, worked with people from different backgrounds or responded when a project did not go to plan. Avoid relying on general claims that someone is "passionate about the mission."

2. Give new staff a proper induction

A signed contract and a brief introduction to colleagues do not amount to induction. New hires need to understand the organization, their role and the standards that govern their work.

A useful induction covers the organization's mission and current programmes; the employee's objectives and reporting line; relevant policies and safeguarding duties; systems for finance, procurement, data and documentation; key partners; and the decisions the employee may make independently.

Pair that information with practical support. Introduce the new colleague to the people they will work with, provide access to essential tools and schedule check-ins during the first weeks and months. Ask what remains unclear. Early confusion can become a performance problem if no one notices it.

3. Establish clear reporting and decision structures

Team members should know who supervises them, who approves their work and where to take an issue that exceeds their authority. This becomes especially important when staff work across projects, counties, partner organizations or technical departments.

An organogram can show formal reporting lines. Day-to-day work also needs clear handovers and escalation routes. For example, a field officer may report administratively to a county coordinator while receiving technical guidance from a technical specialist. Both relationships should be explained so that advice, approvals and accountability do not become confused.

When assigning work, clarify:

• Who is responsible for delivery
• Who reviews or approves the result
• Who provides technical guidance
• What decisions are reserved for a line manager
• How urgent concerns are escalated
• Who acts when the usual decision-maker is absent

These arrangements protect staff as well as the organization.

4. Agree on results-based objectives

People perform better when they understand the results expected of them. A long activity list can keep someone busy without showing whether their work is advancing the project.

Translate organizational and project priorities into a manageable set of individual and team objectives. Each objective should make the expected result, timeframe and means of assessing progress clear. Where a result depends on factors outside an employee's control, reflect that reality in how performance will be judged.

For example, "conduct household visits" describes an activity. A stronger objective might specify the agreed caseload, standards for timely follow-up, accurate documentation and appropriate referral. It connects the work to service quality without treating a raw number as the whole measure of performance.

Review objectives when project conditions change. Performance management should guide work throughout the year, not appear only at appraisal time.

5. Coach staff in a structured way

Telling an employee to "improve" rarely provides enough guidance. Coaching starts by identifying a specific skill or performance need and agreeing on how the person will develop it.

A manager might observe a community meeting, review a draft report with its author or discuss how a staff member handled a difficult partner conversation. The manager and employee can then identify what worked, what should change, what support is needed and when they will review progress.

Structured coaching does not require a complicated programme. Regular one-to-one conversations can be effective when they have a purpose, a record of agreed actions and a follow-up date. As staff grow, give them opportunities to apply new skills with suitable supervision.

6. Manage performance fairly and promptly

Performance problems are easier to address when expectations have been clear from the start. Managers should use evidence, discuss concerns early and give staff a chance to explain barriers.

A missed target may reflect an individual performance issue, but it may also arise from delayed funds, an unrealistic workload, unclear instructions or conditions in the field. Understand the cause before deciding on a response.

When improvement is needed, agree on the expected standard, the support available and a reasonable review date. Document significant concerns and follow organizational procedures. The same fairness should apply to strong performance: assess the quality and integrity of results, not only who is most visible to senior leaders.

7. Recognize achievement and contribution

People should know when their work has made a difference. Recognition reinforces good practice and shows that effort, initiative and integrity are noticed.

Recognition can include specific feedback, opportunities to present work, professional development or formal awards where the organization has an appropriate process. It should be timely and tied to a clear contribution. "Your careful follow-up helped the team resolve the outstanding referrals" is more meaningful than routine praise without explanation.

Rewards and recognition need fair criteria. If only easily counted results are celebrated, staff may neglect less visible but essential work such as mentoring colleagues, improving data quality or protecting service standards. Recognize team achievements alongside individual contributions.

8. Make pay fair, consistent and explainable

Staff do not need access to one another's individual salaries to understand how pay decisions are made. They should, however, know the salary grade for their position, the range attached to that grade, the criteria for progression and how allowances or exceptional appointments are approved.

An organization may discover that a junior employee earns more than someone in a senior position. That difference should prompt a careful review, not an immediate assumption of wrongdoing. The junior role may require a scarce technical skill, carry a location allowance or reflect a salary protected when the employee moved into a new position. Job titles alone do not establish the value or conditions of the work.

The concern arises when the difference has no documented, consistently applied explanation. This can happen when salaries are negotiated individually, new hires receive market adjustments while existing staff do not, or managers approve exceptions without reviewing their effect on other grades.

A sound pay system starts with evaluated roles, defined grades and salary ranges. It sets criteria for starting pay, progression, promotion, allowances and exceptions. Human resources and leadership should periodically check for unexplained differences within and across grades, including whether comparable work is being paid consistently.

Where an unjustified gap is found, the organization should identify its cause and agree on a documented correction plan. This may require adjusting an underpaid employee's salary, correcting a grading error or phasing changes into the budget. Reducing another employee's agreed pay should not be treated as the automatic solution. Staff should have a safe way to ask how their own pay was determined and to raise a concern.

9. Hold leaders accountable to the same standards

Accountability cannot stop with field staff and supervisors. A director or chief executive who sets performance expectations for others must also have clear objectives, decision limits and a body that reviews their performance.

In a public benefit organization with a board, the board should provide that oversight. It should approve strategy and key policies, review programme and financial performance, monitor significant risks, evaluate the director against agreed objectives and address serious concerns. The director should have authority to manage day-to-day operations within approved limits and report openly on progress, problems and decisions that require board attention.

An effective board does more than receive reports. Members should read them, ask informed questions, record decisions, follow up on agreed actions and manage conflicts of interest. They should understand the organization's work well enough to challenge weak explanations while respecting management's operational role. A board that exists only on paper leaves staff and the communities served without meaningful oversight.

Leadership accountability also needs routes for concerns to be raised. Staff should know how to report suspected misconduct or a serious management failure when the concern involves their usual supervisor or the director. Those concerns need a fair process and protection against retaliation.

When leaders accept scrutiny of their own decisions, accountability becomes an organizational practice rather than a demand directed only at junior staff.

10. Integrate teams across projects

An organization may implement several projects at once, each with its own donor, budget, targets and reporting requirements. Those differences are necessary for accountability. They should not cause staff to work as though they belong to separate organizations.

When project teams operate in silos, they may duplicate activities, compete for the same partners or withhold useful information. Staff can begin to see colleagues on another project as rivals rather than people working toward a shared mission. Morale suffers when access to training, equipment, recognition or career opportunities depends mainly on which project employs a person.

Pay differences can also emerge when projects recruit separately or offer different salary packages for comparable roles. Funding arrangements may explain some differences, but they should not replace an organization-wide approach to grading and pay. Leadership should review proposed positions and compensation across projects, document any justified exceptions and address inequities that develop over time.

Integration requires deliberate management. Senior leaders should set shared standards for recruitment, induction, supervision, safeguarding, performance and staff development. Project managers should coordinate plans, share relevant learning and identify opportunities to use skills across teams. Where funding agreements permit, staff with specialist expertise can support more than one project through clear assignments that respect their existing workload and the costs charged to each project.

Joint planning meetings should address practical dependencies: work in the same communities, relationships with the same government departments, shared facilities and staff capacity. Leaders should also create opportunities for colleagues to learn about one another's work and contribute to organizational improvements.

A project needs its own accountability. Its staff also need to know that they are part of one organization, treated by consistent standards and working alongside colleagues toward a common purpose.

11. Protect capacity and learn from results

Even capable staff struggle when priorities compete, vacancies remain unfilled or workloads are unsustainable. Leaders should review what has been assigned, including travel, documentation, partner follow-up and urgent requests that may be missing from workplans. When new responsibilities are added, decide what must be delayed, reassigned or simplified.

Teams also need room to examine results honestly. After a milestone or difficult period, ask what was intended, what happened, what the evidence shows and what should change. Follow through on the answer. Learning becomes valuable when it improves the next decision.

The test of a strong team

A team's strength becomes visible when a new employee joins, a manager is away or circumstances in the field change. Can people identify the priority, work within their authority, find the support they need and maintain service quality?

That capacity grows when an organization recruits carefully, inducts thoroughly, clarifies reporting lines, sets meaningful objectives, coaches consistently, manages performance fairly, explains its pay decisions, integrates work across projects, recognizes valuable contributions and holds its leaders accountable.

Written by Kenneth Otieno
Director, Edge Point Solutions