Everyone is using the system. Almost nobody is using it while the work is happening.

Adoption reporting typically measures completeness: what proportion of the work was recorded in the system.

The more revealing measure is timing. When did the entry happen, relative to the event it describes?

A system used correctly but always retrospectively is not carrying the work. It is functioning as a reporting layer over an unchanged process, and every downstream promise that depended on live information is quietly false.

Completeness cannot see this. Login patterns cannot see it. Accuracy cannot see it, because retrospective records are often perfectly accurate.

This is the specific shape of the failure that nobody notices: the work carries on as it did before, and the system faithfully records that it happened. Every indicator reads positive.

The interval between an event and its record is one line of analysis, and in most implementations nobody has ever run it. It usually takes an analyst an afternoon.

More on this in chapter 22 of Built to Be Used.

#DataQuality #UserAdoption #BusinessIntelligence

Adoption reporting typically measures completeness: what proportion of the work was recorded in the system.

The more revealing measure is timing. When did the entry happen, relative to the event it describes?

A system used correctly but always retrospectively is not carrying the work. It is functioning as a reporting layer over an unchanged process, and every downstream promise that depended on live information is quietly false.

Completeness cannot see this. Login patterns cannot see it. Accuracy cannot see it, because retrospective records are often perfectly accurate.

This is the specific shape of the failure that nobody notices: the work carries on as it did before, and the system faithfully records that it happened. Every indicator reads positive.

The interval between an event and its record is one line of analysis, and in most implementations nobody has ever run it. It usually takes an analyst an afternoon.

More on this in chapter 22 of Built to Be Used.

#DataQuality #UserAdoption #BusinessIntelligence

This article accompanies the book Built to Be Used.

Read more

Geef een reactie