Forthcoming
A Field Guide for Nonprofit IT
Decades of running technology for advocacy organisations — from the servers to the studio to the satellite truck — distilled into a working reference for the people actually doing the job.
Most technology writing assumes a budget, a team and a roadmap. Nonprofit IT has none of those. It has one person, a board that needs the donation form working by Thursday, and a press conference at ten tomorrow morning.
This is the reference I wanted twenty years ago and never found: what actually breaks, what it costs, what to buy and what to build, and how to keep a national platform running when the whole technology department is you.
What it covers
Web and CMS architecture for organisations with a decade of filings to keep findable. Email deliverability, which is the single most common silent failure in the sector. Telecom — yes, still, because a press office is a phone system. Live production and broadcast integration. Donor data and the CRM boundary. Security posture on no budget. And the operational discipline that makes one person able to hold it.
Who it is for
The accidental sysadmin at a nonprofit. The communications director who inherited the website. The one technical person on staff who is expected to be all of the above, and the executive director trying to work out what to hire for.
Status
Chapters in progress. The title is a working one. If you want to know when it ships, say so and I will tell you — no list, no sequence, just an email when there is a book.
