The wait on a storage request sits in the gaps between the steps

Yes 2

Written down, with a date (a log, a screen, a document), and it meets your own plan.

Partly 1

Remembered, but not written down, or the record shows you missed your plan.

No 0

Nobody knows, or it was never done. A blank is a finding.

"None, checked on a date" counts as a record. No plan or target written down? Write your guess first, then measure: the guess is your plan.

Tap No, Partly or Yes for each question. Your score adds up as you go. Nothing you tap is saved or sent.

Five questions about your own setup

1. 1 The four times

   Your answer, and where it is written down (with the date) For the next storage request, when was it asked, approved, handed over and working? Write each time.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   Asked: the email or ticket that carried the request. Approved: the approval message or the ticket's status history. Handed over: the ticket's close time. Working: the requester's reply, or the day you checked if no reply came.

   To get it to a 2:

   Four dated times for one real request, from records, not from memory.

   What this does not prove:

   One request is a sample, not a trend. Row 4 is how it becomes one.

2. 2 What each gap waited for

   Your answer, and where it is written down (with the date) Under each gap, what did the request wait for? Pick one: the ticket queue, an approval, a change window (a set time when changes are allowed), or the work itself.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   The ticket history, or ask the people who touched the request.

   To get it to a 2:

   Every gap has one written reason.

   What this does not prove:

   A written reason shows where the request waited. It does not show why that step is slow.

3. 3 Where you think it waits longest

   Your answer, and where it is written down (with the date) Before you look at the times, where do you think your last request waited longest: the queue, the approval, the change window, or the work itself? Write the guess, then write the longest gap you measured.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   The four times from row 1 and the reasons from row 2. Write the guess first, then compare.

   To get it to a 2:

   The guess written before you measured, next to the longest measured gap and what it waited for. If they differ, that is the finding.

4. 4 Three requests, not one

   Your answer, and where it is written down (with the date) For three requests, which wait repeats?

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   Repeat rows 1 and 2 for the next two requests that come in.

   To get it to a 2:

   Three requests with four dated times each, and the wait that repeats written down.

   What this does not prove:

   Three requests show which wait repeats. They do not show the usual time for every kind of request.

5. 5 What you can say upward

   Your answer, and where it is written down (with the date) Can you say how long new storage takes, and where it waits, from your own records? Write the sentence with the date you measured it, next to the time your team promises requesters.

   Your answer

   No 0Partly 1Yes 2
   Score 0, 1 or 2This quarterNext quarter

   How to raise it

   Where to find it:

   Rows 1 to 4. The promised time is in your service targets or the request form. None written down? Write your guess and score against it.

   To get it to a 2:

   One sentence with a date, backed by the three requests, and it is inside the promised time (or the guess).

   What this does not prove:

   A sentence from three requests is a measured pattern, not a promise for every request.