Knowledgebase

Measuring Whether a System Delivers Print

  • businesssystems, business, errors, troubleshooting, guide, howto, solution, zillionkinghost
  • 0

Assessing value.

WHAT TO ESTABLISH BEFORE IMPLEMENTATION

The measures that will demonstrate value.

WHY BEFORE

Baselines cannot be captured afterwards.

WHAT TO MEASURE

Time taken for key processes Error rates Time to close a period Days to collect receivables Stock accuracy Cost of the function

WHY PROCESS TIMES SPECIFICALLY

They are the clearest evidence of whether work became easier.

WHAT TO MEASURE ABOUT ADOPTION

Proportion of transactions entered in the system Timeliness of entry Users actively using it Reports being used

WHAT LOW ADOPTION INDICATES

That benefits will not materialise, whatever the system does.

WHAT TO REVIEW AFTER SIX MONTHS

Whether the measures moved What was deferred and whether it is still needed What problems persist What the actual cost has been

WHAT TO BE HONEST ABOUT

Benefits that did not materialise.

WHY

It informs the next decision, and prevents repeating the error.

WHAT TO AVOID

Measures nobody acts on Claiming benefits without evidence

WHAT TO DO WITH THE FINDINGS

Decide what to improve, and act.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot