A slow hour on shared storage is hard to explain until you can say whose work is in it

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 Your busiest hour

   Your answer, and where it is written down (with the date) Which hour was your busiest, the one where the array's performance graph peaks? Write the day and the hour from the graph.

   Your answer

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

   How to raise it

   Where to find it:

   The array's performance screen (the name varies by brand), with the time range set wide enough to show the peak. Read the hour off the graph, not from the hour people remember complaining.

   To get it to a 2:

   A day and an hour read from the graph and written down with the date you looked, from a period your plan sets. No period written down? Write your guess (the last week, the last month) and score against it.

   What this does not prove:

   One busy hour is not every hour. The peak may fall at a different time next week.

2. 2 The top five volumes

   Your answer, and where it is written down (with the date) In that hour, which five volumes did the most work? List them here with the number for each. (A volume is the slice of storage one system or application uses. Work done can be operations per second: reads and writes handled each second.)

   Your answer

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

   How to raise it

   Where to find it:

   The same performance screen with the time range set to that hour. Sort the volumes by operations per second. The array already collects these figures for each volume, so nothing new is needed.

   To get it to a 2:

   Five volumes and their numbers, written from a screen on a dated day, for the hour in row 1.

   What this does not prove:

   A busy volume may not have caused any slowness. Averaged readings can hide short spikes.

3. 3 The business system on each

   Your answer, and where it is written down (with the date) Next to each of the five, which business system is on it? Write the system and who confirmed it.

   Your answer

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

   How to raise it

   Where to find it:

   The volume's name, or the server list on the same array (which servers are connected to that volume). Where the name does not say, ask the owner of the server.

   To get it to a 2:

   All five tied to a named business system, checked against the server list or the system's owner, with the date.

   What this does not prove:

   A volume name can be out of date. A name that looks right may hold something else.

4. 4 A name nobody recognizes

   Your answer, and where it is written down (with the date) Is any of the five a name nobody on the team recognizes? Write it down too, with who you asked and what they said.

   Your answer

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

   How to raise it

   Where to find it:

   Ask the team, then look at the server list for that volume. "None, checked on 3 Nov" counts as a record.

   To get it to a 2:

   Every one of the five has a known system, or each unknown one is written down with who is finding out and by when.

   What this does not prove:

   An unfamiliar name is not a problem in itself. It is a question for someone to answer.

5. 5 The next look

   Your answer, and where it is written down (with the date) Is the next look at this list on the calendar, for a second busy hour, and who runs it?

   Your answer

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

   How to raise it

   Where to find it:

   Your team calendar or change schedule.

   To get it to a 2:

   A date on the calendar inside your plan's interval, with a named person, and the list saved where the team can find it.