Testimonials from the people who use our research
Public servants, agency analysts, and technology leads describe how our government technology research shaped their procurement, service design, and daily work.
Why we publish reader stories
Government technology decisions are rarely made by one person. A single purchase can pass through budget officers, security reviewers, program managers, and frontline staff before it reaches the public. We publish these testimonials to show how our research performs in that setting, not only in theory.
Each account below was shared with us by a reader who has applied our guidance in a real project. We have kept their words close to what they wrote or said, and we have described their roles rather than attaching names where a reader asked for discretion.
Reader reviews
We used the vendor comparison framework before our records system renewal. It made us ask for evidence of accessibility testing in the first round, which saved us from a contract we would have regretted.
County records department
The service design notes gave our team a shared vocabulary. Engineers, caseworkers, and our legal office finally discussed the same workflow in the same terms.
State benefits agency
I read the cloud migration checklist several times before presenting to our board. The questions it raised about data residency were the ones the board actually asked.
Municipal technology office
As a school district reviewer, I appreciated that the research did not assume unlimited budgets. The phased adoption guidance matched how we actually fund and staff our projects.
Regional school district
From a single review to a lasting process
Several readers told us the most valuable outcome was not a single recommendation but a repeatable habit. Teams began scheduling short evidence reviews before each major decision, and they kept the notes for the next cycle.
- Define the public outcome before comparing tools
- Ask vendors for documented security and accessibility evidence
- Pilot with real users before committing to a full rollout
In practice
Questions readers ask about testimonials
Are these reviews edited?
We lightly trim length and correct typographical errors. We do not change the substance of a reader's account, and we confirm the wording with the reader before publication.
Why are some names withheld?
Many public employees cannot speak on the record about active procurements. We publish their role and organization type instead, so readers can judge how closely the experience matches their own.
Can I share my own experience?
Yes. Readers who have applied our research are welcome to send a short account describing the project, the guidance used, and what changed as a result.
If our research has changed how your agency evaluates technology, we would like to hear the story. Share your experience with our team