Reconstructing a request fulfilment baseline from records you already have
Nobody measured the before state. It is usually still recoverable.
The evidence to look for: a request type or catalogue column separating requests from faults
An artefact can only evidence the practice it is a record of. A ticket export shows what was captured on tickets. It is silent about strategy, and a reconstruction that pretends otherwise is the kind of number that discredits everything beside it.
Absent is evidence. Present but mostly empty is different evidence, and usually a more interesting finding: somebody configured the field and the work went on around it.
Label it reconstructed everywhere it appears, quote the file and the line for every score, and let the person who has to defend it override anything they disagree with before it is locked. What good looks like for request fulfilment: Common requests are distinguished from incidents, have a published lead time, and follow a repeatable path rather than being negotiated each time.
Do this with Adoption Evidence
One engagement free. Curate the questions, baseline the team, and generate a report where every number traces to a response or a file. No card.
Already have a The Art of Service account? Sign in.
Related
- Reconstructing a incident categorisation baseline from records you already have
- Reconstructing a incident prioritisation baseline from records you already have
- Reconstructing a incident ownership baseline from records you already have
- Reconstructing a service level targets baseline from records you already have
- Reconstructing a change approval baseline from records you already have
- Reconstructing a change recording baseline from records you already have