Look at the job requirements for almost any senior field role across our sector. We ask for ten years of institutional grant management, proven mastery of complex financial reporting, deep familiarity with donor regulations, and fluency in our sector’s specialized terminology. Somewhere near the bottom of the page, under desirable attributes, we mention local knowledge, relational skills, and experience in community-led problem-solving.
We did not write these job descriptions out of indifference to the work on the ground. We wrote them out of self-preservation. After years of facing severe financial disallowances, audit findings, and institutional scrutiny, our sector reached for people who could guarantee compliance. We needed managers who would keep the reporting clean, protect the contract, and ensure that every dollar could be accounted for on paper. That instinct was logical. When an organization faces structural liability for a single oversight, hiring for administrative precision feels like simple prudence.
The cost of that default is visible in every project that stalls when circumstances change. By prioritizing contract mechanics over contextual intelligence, we build teams designed to execute a grant agreement rather than solve a problem. The people who excel at navigating institutional platforms and writing quarterly narratives are not automatically the people who know how to resolve a local conflict, read shifting community dynamics, or build quiet trust across lines of division.
When the situation on the ground deviates from the proposal, a team hired for compliance naturally reaches for the safety of the original plan. They refine the indicators, adjust the timeline, and submit the change request. The work shifts from responding to the reality in front of us to managing the contract we signed. We end up with impeccably documented programs that miss the moment, managed by capable professionals who were never hired to do anything else.
Redesigning how we define capability
The build is to stop treating contextual knowledge and relational skill as secondary attributes, and to hire for the courage and judgment the work actually demands.
First, we rewrite the weighting in our recruitment profiles. We treat deep contextual awareness, network access, and the demonstrated ability to build community trust as core qualifications, equal to technical and financial management. If a candidate holds the relational trust but lacks familiarity with a specific reporting mechanism, we can teach the mechanism. We cannot easily teach a manager how to care for a community or understand the unspoken power dynamics of a valley they have never walked.
Second, we unbundle administrative compliance from operational leadership. When we require every field director to be a full-time grant administrator, we ensure that their time is absorbed by spreadsheets instead of relationships. We can invest in dedicated compliance support that holds the administrative weight, freeing operational leaders to stay close to the ground, listen to community feedback, and make timely decisions when conditions shift.
Third, we evaluate our managers on the health of their relationships and the relevance of their actions, not only on the timeliness of their reports. An operational review should look at whether a team adapted intelligently to a changing crisis, not merely whether they delivered the pre-approved items on the pre-approved date.
We got exactly what we wrote into our job descriptions. We hired for the audit, and we received flawless reporting alongside rigid operations. If we want teams capable of navigating uncertainty with humility and resolve, we have to start by asking for those qualities on the page, and valuing them when candidate selection begins.