Warehouse Workflow LabPlan your starting measurementsPublished by Voodoo Robotics · workflows.voodoorobotics.comPerson responsible for this worksheetDateVersion01Decision to supportWhat to do: State the decision the data must resolve.Decision / hypothesisWrite the decision this information will help you make.Example: Should Zone A change from one-order picking to eight-order carts?Current-state boundaryState exactly which work, area, shift, or cases are inside and outside the worksheet.Example: Zone A day shift; oversize orders excludedCandidate future stateBriefly describe the proposed method that will be compared with today’s method.Example: Pick eight orders per cart with one labeled tote per orderPrimary KPIName the main result the change should improve.Example: Completed order lines per direct labor-hourGuardrail KPIName a result that must not get worse while the main result improves.Example: Order accuracy must remain at least 99.8%02Metric definitionsWhat to do: Make each measure reproducible.This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.Metric nameName the exact measurement used at baseline, 30, 60, and 90 days.NumeratorWrite what gets counted on top of the formula.DenominatorWrite what the counted result is divided by.Clock start / stopState the exact actions that start and stop timing.Inclusions / exclusionsState exactly what is counted and what is left out of the metric.System of recordName the system whose number is treated as official.Metric name, row 1Numerator, row 1Denominator, row 1Clock start / stop, row 1Inclusions / exclusions, row 1System of record, row 1Metric name, row 2Numerator, row 2Denominator, row 2Clock start / stop, row 2Inclusions / exclusions, row 2System of record, row 2Metric name, row 3Numerator, row 3Denominator, row 3Clock start / stop, row 3Inclusions / exclusions, row 3System of record, row 3Metric name, row 4Numerator, row 4Denominator, row 4Clock start / stop, row 4Inclusions / exclusions, row 4System of record, row 4Metric name, row 5Numerator, row 5Denominator, row 5Clock start / stop, row 5Inclusions / exclusions, row 5System of record, row 5Metric name, row 6Numerator, row 6Denominator, row 6Clock start / stop, row 6Inclusions / exclusions, row 6System of record, row 6Metric name, row 7Numerator, row 7Denominator, row 7Clock start / stop, row 7Inclusions / exclusions, row 7System of record, row 7Metric name, row 8Numerator, row 8Denominator, row 8Clock start / stop, row 8Inclusions / exclusions, row 8System of record, row 8+ Add 4 more rows03Sampling planWhat to do: Protect against a convenient but biased sample.Dates and shiftsList the calendar dates and shifts that must be included in the sample.Example: July 20–24, 2026 · day and night shiftsOrder / SKU strataList order and product groups that must be represented separately.Example: 1-line, 2–5-line, and 6+-line ordersPeak periodsList the busy hours, days, or seasons that the sample must include.Example: Weekdays 2–4 p.m. and the final five shipping days of each monthWorkers / experience levelsName the role or person and shift when it matters.Example: Day-shift picker; 6 months experienceMinimum transactionsEnter a measured count and the period or group it covers.Example: 1,200 order lines during the day shiftKnown confoundersList other changes that could make the result look better or worse.Example: Three new workers started during week 204Data qualityWhat to do: Name the validation and owner.Missing-data ruleState what happens when a required record or value is missing; do not silently treat it as zero.Example: Exclude the row, count it as missing, and investigate if more than 2% are missingOutlier handlingState when an unusual result stays in the data, is reported separately, or is removed with a reason.Example: Keep ordinary shortages; report network outages separately and never delete them silentlyManual cross-checkDescribe the small manual count used to confirm the system data is trustworthy.Example: Compare 50 WMS completions with video timestamps and supervisor tallyData ownerName the person responsible for this decision, task, or approval.Example: A. Rivera — Operations ManagerApproval dateEnter the exact date, due date, or review frequency.Example: July 22, 2026