A nonprofit with a small staff
Three good fixes, and the fourth year
The challenge. A nonprofit with a staff of fourteen has had three security projects in three years: new multi-factor sign-in, a backup service and a policy binder. Each was done well by a different person. This year a funder asks how the pieces fit together and whether any of it has been checked since.
The insight. Good fixes are not a program. A program has a decision maker, a target design, a measure of where things stand, and a cycle that repeats. Without those the fixes drift out of date, and nobody can say whether the organization is improving.
The decision. The executive director named an owner for security, agreed the three things that mattered most to the mission, and asked for one yearly cycle that the board could follow.
The action. We started with the goals and the target design, assessed the three projects and everything around them against it, reported the gaps ranked by risk, and had the IT provider close the top four. We set a quarterly review and measured again after six months.
The result. The board now sees one page twice a year: where the organization stands on a five-level scale, what moved and what is next.