Nonprofit service operations guide
Guide 7: Run a quarterly software service review
Use a compact evidence review to choose what to sustain, improve, reduce, or retire.
Review one service record
Bring together ownership, support demand, incidents, reliability, access, data quality, adoption, staff effort, vendor commitments, cost, risks, and open improvement decisions.
Use trends and representative evidence. A dashboard without decisions can create the appearance of control while recurring issues remain ownerless.
Choose the next operating commitments
Decide which controls need attention, which backlog items advance, which risks are accepted, which vendor actions are escalated, and which measures no longer help. Give every commitment an owner and date.
Protect staff capacity by limiting active improvement work. A smaller owned backlog is more useful than a long list with no execution path.
Reassess the service boundary
Ask whether mission work, users, data, integrations, funding, regulation, product behavior, staffing, or risk has changed enough to revise the charter or start a larger initiative.
The review should make renewal, replacement, expansion, and retirement decisions easier because the operating evidence already exists.