A county agency choosing a new case system
The system chosen before the questions
The challenge. A county office is about to replace its case-management software. Three vendors have demonstrated their products. Staff like the second one, the budget fits the third, and nobody has asked where the data will live, who will sign in and how it connects to the state’s systems.
The insight. Security is cheapest at the design stage. A short design that states the data, the people, the connections and the rules lets every vendor answer the same questions, and turns a comparison of demonstrations into a comparison of fit.
The decision. The office paused the choice for three weeks to write the requirements first and ask each vendor to answer against them.
The action. We mapped the data and who touches it, drew how the system would connect to others, and wrote the security and privacy requirements in plain language: sign-in, roles, logging, encryption, backup, data location, exit terms. We scored each vendor’s written answers and listed the open questions for a second round. The vendor and the IT provider handled the build; we reviewed the design before go-live.
The result. The office chose a vendor on written answers, signed a contract that carries the requirements, and has a design diagram it can hand to the next person.