Lessons From Conversations With Public Sector Change-Makers
Why Conversations Beat Case Studies
Most writing about public sector modernisation relies on polished case studies published long after the difficult work is done. Conversations are different. They expose the hesitations, budget fights, and small victories that never make it into an official report. Over the past year, GovTech Research has spoken with founders selling into government, funders backing civic technology, and civil servants trying to improve services from the inside. Their combined perspective offers a more honest picture of what change actually requires.

The first lesson is that nobody has a monopoly on good ideas. A civil servant may understand procurement law better than any vendor, while a founder may see a user experience problem that staff have learned to tolerate. Progress happens when those perspectives are treated as complementary rather than adversarial.
"The best projects I have seen started with a civil servant and a vendor disagreeing respectfully for an hour."
What Founders Keep Getting Wrong
Founders often arrive with a finished product and a pitch deck, expecting government to adapt to them. The change-makers we interviewed consistently described this as the fastest route to rejection. Successful founders instead spend their first months mapping decision-makers, understanding budget cycles, and learning which problems are genuinely painful for officials.
Another repeated theme is patience with pilots. A pilot that looks slow to a startup may be moving at record speed for an agency bound by procurement rules and public scrutiny. Founders who interpret caution as hostility tend to burn bridges early.
- Map the budget cycle before writing a proposal.
- Find an internal champion, not just a buyer.
- Treat pilots as relationship-building, not just revenue.
- Document outcomes in language auditors accept.
What Funders Underestimate
Funders frequently look for scalable products and clean metrics, but public sector change rarely scales in a straight line. What works in one municipality may fail in another because of local politics, legacy systems, or union agreements. Grant-makers who allow for adaptation tend to see better long-term results than those demanding rigid milestones.
The change-makers also noted that funding for the maintenance phase is scarce. Everyone wants to finance the launch, few want to pay for the unglamorous work of keeping a service running and secure.
| Stakeholder | Common Blind Spot | Helpful Shift |
|---|---|---|
| Founders | Assuming speed is always valued | Respect procedural timelines |
| Funders | Chasing clean scaling metrics | Fund adaptation and upkeep |
| Civil servants | Underestimating external allies | Engage vendors earlier |
The View From Inside Government
Civil servants described a constant tension between delivering better services and avoiding public failure. One official explained that a failed pilot can end a career, which makes risk aversion rational rather than lazy. Recognising this changes how outsiders should frame their proposals.
Insiders also said that small, unglamorous improvements often matter more than flagship digital projects. Reducing a form from twelve pages to four can save citizens hours and staff considerable effort, even if it never generates a press release.
- Start with a problem citizens already complain about.
- Measure time saved, not technology deployed.
- Protect the team from political turnover.
- Share credit generously across departments.
Practical Lessons for the Next Conversation
The through-line across every interview is that modernising public services is a relational activity, not a technical one. Tools matter, but trust, timing, and shared language matter more. Founders, funders, and civil servants all described the same turning point: the moment they stopped defending their own position and started solving the problem together.
For anyone entering this space, the advice is consistent. Listen longer than you pitch. Study the constraints before proposing solutions. And remember that the person across the table wants the service to work as much as you do, even if their path to getting there looks different.
