A job description lists duties. A scorecard defines success. The difference is why most nonprofit hires underperform and most reviews feel arbitrary.
Ask five people what success looks like in a given role and you will usually get five answers. That is not a people problem. It is a definition problem — and it is entirely fixable in an afternoon.
Typical job descriptions list activities: "manages donor communications, supports events, maintains the database." Nothing in that tells the person what winning looks like, and nothing gives a manager a fair basis for feedback. So reviews become impressions, and impressions feel personal.
Why this role exists, in plain language. "Grow and retain the individual donor base so program capacity is never limited by funding." If you cannot write this in one sentence, the role is probably two roles.
What must be true in twelve months. Not activities. Outcomes with numbers and dates.
| Weak | Strong |
|---|---|
| Improve donor communications | Donor retention improves from 42% to 52% by year end |
| Support fundraising efforts | Monthly giving grows from 40 to 120 donors |
| Manage the database | 100% of gifts acknowledged within 48 hours, measured monthly |
The five to seven behaviors required. Include both craft competencies and cultural ones. This is where values become assessable rather than decorative: if "we treat people with dignity" is a value, name what that looks like in this role.
Often skipped, frequently decisive. What season of life does this role require? What travel, what pace, what pressure? A capable person in the wrong season fails, and both parties experience it as personal failure when it was a matching error.
The test: hand the scorecard to a candidate. If they can tell you honestly whether they would succeed in the role, it is well written. If they cannot, it is still a job description.
The scorecard turns reviews from opinion into evidence. You are no longer discussing whether someone is doing well — you are reviewing agreed outcomes together. That shift removes most of the defensiveness from performance conversations.
Add one section that most organizations omit: formation. How is this person growing? What is their capacity right now? What season are they in? A review that only measures output will eventually produce burnout, because the system is asking for performance while nothing is asking about the person.
A caution on succession. Once you have scorecards, ask a harder question of each: if this person left tomorrow, who could step in? If the answer is nobody for more than one or two roles, you have a key-person dependency that no amount of hiring speed will solve in a crisis.
Where this sits in the Flourishing Framework™. People & Leadership work only holds when the layer beneath it is solid. The free Flourishing Index shows you which layer is actually constraining you — in six minutes. Take the Index →
This guide describes practitioner method rather than published research. The frameworks here — moves management, story pipelines, decision-rights matrices, and role scorecards — are standard practice in professional fundraising and organizational development, refined through our own work running an international organization. Where we cite statistics elsewhere in this library, we name the source. Where we don't, we're telling you it's practice.