E-Governance Rollouts Stall at Adoption, Not Procurement

The procurement took eighteen months. The system works. The training was delivered, attendance was recorded, and the go-live was announced with a ribbon and a press release.

Six months on, half the frontline staff are still running the old paper process alongside the new system — entering things twice, or entering them into the system at the end of the week from a stack of forms they filled out by hand. The dashboard shows the platform is being used. It does not show that it is being used as a transcription tool for a workflow nobody actually abandoned.

This is the characteristic failure mode of digital government in the Philippines, and it is almost never a technology failure.

(For the broader methodology behind this, see What Relational Change Management Actually Is.)

Procurement discipline creates an adoption blind spot

Public procurement is rigorous by design. Specifications get written, budgets get defended, bids get evaluated, and every peso is accountable. That discipline is a genuine strength, and it produces something predictable: enormous institutional attention on everything up to contract award, and comparatively little on what happens after the system is delivered.

The vendor's obligation ends at deployment and training delivery. The agency's project team, having spent two years on procurement, treats go-live as the finish line. And the budget line that funded the system rarely includes a line for the eighteen months of behavior change that actually determines whether it works.

So the system is procured well and adopted badly, and because usage statistics exist, nobody notices for a year.

Where public sector adoption actually breaks

The approval layer and the usage layer are different people. The officials who authorized the system are not the ones who will use it forty times a day. Standard change practice says secure executive sponsorship — and in government you can secure it fully, at the highest level, and still have no traction, because the frontline staff who determine adoption were never part of the conversation and have no relationship with the people who were.

The old process is a legitimate risk-management strategy. When staff keep the paper trail running in parallel, that is not resistance in the pejorative sense. It is a rational response to accountability. If something goes wrong and an audit follows, the paper is what protects them. Until the new system is trusted to withstand that scrutiny — and until staff have been explicitly told, by someone whose word carries weight, that the digital record is sufficient — the duplicate process is the safe choice. Training does not fix this. Only assurance from a trusted source does.

Leadership turns over mid-initiative. Administrations change, department heads rotate, and an initiative championed by one office can find itself orphaned under the next. Any change strategy that depends on a single sponsor's continued presence is fragile in government by default.

Service continuity is non-negotiable. A private company can absorb a rough transition week. An agency issuing permits, disbursing benefits, or responding to emergencies cannot — the public does not pause while you stabilize. This constraint is real, and it means transition design has to be built around uninterrupted service delivery rather than treating it as an afterthought.

Nobody says the initiative is failing. In a hierarchical environment where a senior official is visibly invested, the social cost of delivering bad news upward is high. Problems get softened at each level. By the time the status report reaches the top, it says "adoption is progressing." It is not.

What we do differently

Assess the frontline, not just the steering committee. Readiness assessment starts with the people who will touch the system daily — what their current workflow actually is, including the informal workarounds that keep service moving, and what they think will go wrong. That last question is usually the most valuable one asked in the entire engagement.

Identify the influencers who are not the officials. In every agency there are people whose judgment shapes how their unit works — the long-tenured staff member others check with before doing something new. Their genuine endorsement moves adoption more than a memo from the top. Their quiet skepticism kills it.

Design for sponsor turnover. Build ownership across multiple offices and levels so the initiative survives a leadership change. If the change depends on one champion, plan for the day that champion is reassigned.

Address the audit fear directly. Get explicit, documented, authoritative confirmation that the digital record is the record of account. Then communicate it repeatedly, from a source staff actually trust. This single item resolves more parallel-process behavior than any amount of additional training.

Create a safe channel for bad news. Feedback has to reach decision-makers without passing through everyone who has a stake in it looking successful. That means direct, structured, low-stakes channels — and leadership visibly responding well the first time someone uses one.

Measure behavior, not logins. Usage statistics are not adoption. The honest metrics are whether the parallel process has actually stopped, whether processing time genuinely improved, and whether staff would choose the new system if the old one were still available.

The reframe

Digital government initiatives are usually run as technology projects with a change management component attached near the end.

They are change management initiatives with a technology component. The platform is the easier half — it can be specified, procured, and tested. Getting several hundred public servants to trust it enough to let go of the process that has protected them for fifteen years is the harder half, and it is the half that determines whether citizens ever see the improvement the system was bought to deliver.

That work does not fit in the procurement timeline. It has to be budgeted, staffed, and planned for on its own terms.

If your agency is planning a digitalization initiative — or already launched one that hasn't landed the way you expected — let's talk. Schedule a Consultation →