Government That Ships: Modern Procurement for Public Technology

The strongest objection is that "digital service delivery" can become its own ideology: teams chase clean interfaces and agile rituals while ignoring statutory complexity, fraud risk, privacy, labor rules, paper access, and the fact that many public programs are hard because the law itself is hard. A critic could argue this issue risks making government look modern without making it lawful, equitable, or accountable.

That critique is strong because it has happened before. The answer is to make service metrics and legal accountability travel together. A faster eligibility system that increases wrongful denials is not a success. A reusable identity component that excludes people without smartphones is not a success. A modular contract that ships increments no program lawyer can defend is not a success. The position holds because it defines shipping as working public capability under law, with appeals, security, accessibility, and completion evidence included in the metric set.

Agencies bear the first cost: changing procurement practice, hiring technical owners, writing better contracts, publishing metrics, and accepting earlier scrutiny. Incumbent vendors bear the cost of weaker lock-in, stronger documentation, and more frequent recompetes. Program offices bear transition burden when a long-running system is split into increments or when a failed path is stopped. Taxpayers bear the cost of building public technical capacity and maintaining reusable components.

The public bears the larger cost if this issue is not adopted: failed launches, long waits, duplicate forms, opaque denials, security incidents, and systems that can be neither fixed nor replaced. This issue accepts near-term institutional friction and vendor-disruption costs as the price of making public technology governable before the failure becomes permanent.