Working with government is often described as slow and frustrating. Sometimes it is. But after years of civic partnerships for road safety, government interactions and policy advisory, I have learned that public systems follow their own logic. Understand the logic, and programs move. Ignore it, and even good ideas stall.
These lessons also apply to corporates: regulated industries, public-private projects, market entry, CSR with government partners, and any transformation where many stakeholders have to say yes.
1. Understand the mandate and the calendar
Every department has a mandate, a budget cycle and a planning calendar. Officials move between roles. A proposal that arrives after budgets are set, or that falls outside the mandate, waits regardless of its merit.
Try this: before any proposal, map whose mandate it serves, which budget line it fits and when that budget is decided.
2. Process is the product
Approvals, documentation and audit trails protect officials and the public. Treating them as obstacles creates friction; building them into the design creates speed. A well-documented pilot is easier to approve, extend and defend.
3. Start with a pilot that someone can point to
A small, visible, successful pilot does more than a large proposal. It gives an official something concrete to show, a basis for the next decision, and evidence for colleagues who were not in the room.
4. Share the credit
Public-private-people partnerships work when every party can claim part of the success: the department, the corporate partner, the community and the citizens who participated. Programs that make one party the hero tend to lose the others.
5. Speak the language of public value
Government decisions are made on public value: safety, cost to the exchequer, jobs, environment, citizen satisfaction. Translate your proposal into those terms, with numbers, before you talk about technology or process.
A one-page public-value brief
- The public problem, in citizens’ terms, with one number
- What the pilot will do, where, and for how long
- What it costs the department, if anything, and who else contributes
- How success will be measured and reported, and when
- What scaling would look like if the pilot works
6. Build relationships that survive transfers
Individuals move; institutions remain. Relationships matter, but the program must not depend on one person. Formal agreements, standard operating procedures and regular reporting keep a program alive when the official who championed it moves on.
7. Transparency builds trust
Public data, visible progress and honest reporting of what did not work build credibility with officials, media and citizens alike. PotHoleRaja’s citizens could track reported potholes online; that openness made partnerships easier, not harder.
Why this matters in consulting
This experience now shapes how GroundReality advises on regulated change, public-private programs, market entry and stakeholder strategy: map the mandates, design for approval, pilot visibly, share credit and report honestly. Part of the series The other side of the table.
