Running it

The project ends at go-live; the system generates work every week. The refusal rate is the number, and most deployments do not track it.

8 notes

Is the Data Any Good

Four checks that show whether the record will bear weight, and what each means when it moves.

Procedure

Phone operating systems and vendor releases both change what the app can do. The check that catches it before the refusal rate does.

Procedure

Every deployment generates corrections. How to handle them so they do not become pay errors, and what the volume tells you.

Procedure

Vendor savings figures assume the problem was large. What to measure before and after, and the costs that arrive later.

Procedure

The recurring work a clock-in deployment generates, and what happens in the usual case where nobody was assigned to it.

Analysis

Ending a deployment, changing vendor, or someone leaving. The app and the data both outlive the arrangement unless someone handles it.

Procedure

A record of when each person arrives at each site, and where they were when they did. What a breach here exposes.

Procedure

Five numbers that say whether the system works, and the ones that mostly describe the workforce.

Reference