Five stops
The method is a route, not a ritual
Every stop has an output you can hold and a check you can run. If a stop does not add value for your project, we skip it and say so.
01Survey the route
One to two weeks. We shadow at least one shift per key role, collect paper forms, spreadsheets and screenshots of current tools, and write down every exception staff mention ("customer not home", "pallet damaged", "scanner dead").
- Output: role map, task frequency table, exception list
- You check: does the exception list match reality?
02Draw the blueprint
Information architecture, then clickable prototype for the top tasks. Tested with five or more staff; we fix what fails and retest.
- Output: prototype, usability report, prioritised backlog
- You check: participants finish primary tasks unaided
03Build in increments
Two-week increments. Each ends with a demo build you can install, a changelog and an updated list of open risks. Code lives in your repository from day one.
- Output: working build, tests, changelog
- You check: demo against the agreed criteria per screen
04Pilot one depot
One site, one shift pattern, two to four weeks. We measure the indicators chosen in survey — time per task, error corrections, sync failures — and compare against the baseline.
- Output: pilot report with numbers and fixes
- You check: go / adjust / stop decision
05Roll out and hand over
Staged release, store submission, one-page training sheets per role, runbook, access transfer. Optional support line afterwards.
- Output: release, docs, credentials in your custody
- You check: your team can deploy without us