Strategy, program design, performance measurement, grants, governance, and operations, written for the people who have to make these decisions with real constraints and finite capacity. No theory for its own sake, and nothing you cannot act on this quarter.
The people who leave are rarely the ones who cared least. Burnout in mission-driven work is mostly a question of how the work is designed, and resilience training aimed at a staffing problem is the wrong instrument.
Passing money through to smaller organizations looks like administration. It is a fiduciary role, and the obligations do not end when the funds leave your account.
Most capacity building is delivered as training and measured by attendance. Technical assistance is a different thing, and the difference decides whether anything is left when the funding stops.
Trauma-informed care is usually treated as a training to send staff to. It is actually a set of decisions about how an organization is run, and the difference shows up in the numbers.
Four very different people arrive at your website, each needing something different within about ten seconds. What they find there decides whether they act.
The discipline is the same everywhere. The constraints are not. Clinical attention is the scarce resource, several deadlines belong to somebody else, and go-live is a patient safety event.
The question is almost never whether the need is real. It is whether a new organization is the right vehicle for it, and whether you want the job that comes with one.
A few concentrated days with the people who do the work and the authority to change it in the room. Done badly it produces a list of action items and spends goodwill you needed.
A standard operating procedure is not a policy, and it is not a manual nobody opens. It answers one question: what happens when the person who knows how is not here?
Applying costs sixty to a hundred staff hours whether you win or not. Five questions, answered before anyone opens a document, settle most opportunities either way.
The award document is the real scope, the reporting calendar is the real schedule, and the first ninety days decide whether the grant is managed or merely survived.
The difference between a consulting engagement that changes an organization and one that produces a report is mostly decided by the client, before the work starts.
Nonprofits rarely fail for lack of good ideas. They stall because nobody owns the work, the sequence was never mapped, and the finish line was never defined.
Most declined proposals are not rejected because the program was weak. They are rejected because the organization could not document, on deadline, what it was already doing well.
You do not need a database, a dashboard vendor, or a data analyst to start. You need five measures, one owner each, and a spreadsheet you actually maintain.
Counting the people you served tells a funder how busy you were. It does not tell them whether anything changed. Here is the difference, with examples.
Board approval is the midpoint of a strategic plan, not the finish line. What happens in the ninety days afterward determines whether the plan becomes an operating system or a binder.