CAQA Digital / Knowing Whether It Worked

Declared complete at go live, when nothing has been proven

Switching something on is the beginning of the test, not the conclusion of it.

The moment a new arrangement goes live is treated across most institutions as the end of the project. Reports are closed, the group that ran it returns to other duties, and the budget stops. What has actually been demonstrated at that point is that the thing can be turned on. Whether the work it supports has become faster, clearer or less error prone is entirely unknown, because nobody has yet done the work under real conditions with real volumes and real exceptions.

The consequence of closing the project at that moment is that the hardest phase is the one with the least support. The first weeks after a change are when the unanticipated cases arrive, when the workarounds get invented, when people quietly decide which parts they will use and which they will route around. Those decisions harden fast and are difficult to revisit later. If there is nobody with authority still paying attention, the settled outcome is whatever the busiest people improvised in the first fortnight.

A more honest structure keeps a small amount of capacity and attention in place well past the switch on, with an explicit expectation that things will be adjusted in response to what is found. That means resisting the pull to declare victory, which is considerable, because the announcement is the visible moment and the months afterwards are not. The institutions that get this right tend to be the ones that treat go live as a milestone in an ordinary sentence rather than as the headline.