A score target distracts from the reported delay

What to change

Start with the observable delay and reproduce the actual route, device conditions and relevant dependency. Ask the supplier which measurement captures that experience and use it as the acceptance evidence. A broader score can provide context but should not replace the original issue. Preserve a short before-and-after account of the same task so the practice can judge whether the reported problem improved, even if an aggregate score moves differently.

A worked example

Illustrative example

Illustrative test: The same task is observed before and after the proposed correction.

How to check the result

The acceptance decision addresses the original user-visible problem.

A mistake to avoid

An improved aggregate can coexist with an unresolved practical delay.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordRecord the exact action and waiting point reported by the manager.Reproduce it with a representative test setup.Choose a measurement that relates to that specific delay.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.