WEBVTT

00:00:00.900 --> 00:00:04.352
Before discussing value, describe the work your team does today.

00:00:04.612 --> 00:00:09.290
The review effort worksheet compares your current workload with a target you choose.

00:00:09.550 --> 00:00:14.765
It helps frame an evaluation, without assuming that a saving has already been achieved.

00:00:16.012 --> 00:00:17.965
Here is an illustrative example.

00:00:18.225 --> 00:00:24.002
Twenty projects, one review per month, and four hours per review require eighty hours

00:00:24.075 --> 00:00:24.903
each month.

00:00:25.150 --> 00:00:29.278
Use your own representative workload when you build the real case.

00:00:30.480 --> 00:00:33.558
Select Try an example to see the worksheet in action.

00:00:33.818 --> 00:00:38.195
A target of two and a half hours per review gives fifty hours per

00:00:38.195 --> 00:00:38.658
month.

00:00:38.905 --> 00:00:43.120
Current effort minus target effort leaves a thirty hour difference.

00:00:44.308 --> 00:00:47.435
That difference is a capacity target to validate.

00:00:47.707 --> 00:00:52.110
Multiplying by an hourly team cost estimates capacity value.

00:00:52.370 --> 00:00:56.698
It is not automatically cash savings or net return on investment.

00:00:56.970 --> 00:01:01.685
Software charges and implementation effort also belong in your decision.

00:01:02.920 --> 00:01:05.323
Use a focused pilot to test the target.

00:01:05.558 --> 00:01:10.735
Compare similar reviews, record actual effort, and check that the required review

00:01:10.735 --> 00:01:12.398
quality is maintained.

00:01:12.670 --> 00:01:17.472
Keep the assumptions with the result so another manager can understand the comparison.

00:01:18.692 --> 00:01:23.058
Build your own scenario, download the worksheet, and use it to agree what the

00:01:23.058 --> 00:01:24.632
evaluation should measure.

00:01:24.880 --> 00:01:30.232
A transparent case gives your team a stronger basis for deciding what comes next.
