This is a case study about a fictional team, written plainly because the problem it describes is plain. A distribution centre operated a modest group of self-driving warehouse carts. The operations crew, six people across two shifts, kept the fleet moving. Their big incidents were rare. Their small ones were constant: a charging dock label peeled off, a map note was out of date, an operator’s question went unanswered until the next shift. Over a few months those small things started to cost real throughput. Here is how the crew traced the problem and what they changed, using the two-minute rule.
The situation before the change
The crew tracked work in a shared board, and the board was long. A snapshot taken one Monday showed over ninety open cards. Roughly two thirds were tagged “minor”. Examples included relabelling a floor marker, correcting a note in the runbook, replying to a shift report and adding a unit to a sensor threshold description.
Nobody on the crew thought of this as a crisis. The board had become wallpaper. People scrolled past minor cards to find anything urgent, and the minor ones aged quietly. Some were three months old.
The incident that made it visible
One night, a vehicle stopped repeatedly near a junction. The overnight operator remembered a note saying that a floor marker there had been damaged, but the note sat on a card from several weeks earlier, still open. The fix would have been a few minutes with a roll of tape and a map correction. Instead, the stoppage lasted most of the shift, and an investigation was needed to rediscover what the card had already said.
In the review the next morning, the crew agreed that nothing about the cause was technical. A small, known issue had waited in a queue because queuing felt more official than fixing.
The experiment: two weeks of doing it now
The shift supervisor proposed a trial. For two weeks, any task the crew estimated at about two minutes, and that touched only the crew’s own documents or low-risk physical items, would be done on the spot. Everything else went to the board with a named first step. They wrote the boundary on the shared whiteboard:
- Allowed on the spot: relabelling markers, correcting runbook text, replying to shift reports, adding missing units or dates to notes, closing cards for work already done.
- Not allowed on the spot: changing vehicle parameters, altering routes, editing safety settings, touching anything another team owns.
The second list mattered most. In a place where machines and people share floor space, quick should never mean careless.
What happened in practice
The first days were messy. Someone decided that tweaking a speed limit on one aisle was a two-minute job; the supervisor reversed it and the crew added a line to the boundary: any parameter that affects vehicle behaviour goes through review, regardless of size. After that adjustment, things settled.
By the end of week two, the board had dropped from ninety cards to about thirty, and almost all of the remaining ones were real work: a sensor recalibration plan, a charging schedule review, a training session for new operators. Replies to shift reports went out in the same shift, so the next shift started with answers instead of questions.
A look at one ordinary shift afterwards
A few weeks into the new routine, an operator on the late shift noticed a worn marker beside a dock. In the old days that would have become a card. This time the operator replaced the strip, corrected the note in the shared map file and left a one-line message for the morning crew. The entire thing took under three minutes, and nobody downstream ever had to think about it again.
What they measured, honestly
The crew kept it modest. They counted open minor cards, the age of the oldest open card, and the number of stoppages whose cause turned out to be a known unresolved note. The first two numbers fell sharply; the third went to zero over the trial, though the crew pointed out that a two-week window is short and other things changed too. They did not claim a throughput figure, because they had no clean way to separate this change from everything else going on in the building.
Connections to the technical side
The crew’s work sits in a wider field. For an overview of the systems they operate, they pointed new colleagues to a general guide on how guided vehicle automation fits into a warehouse. Sensor-related questions, which came up often in their small cards, sent them to an explainer on fitting sensors into factory robots. Both helped explain why a small label or note can matter: the vehicles depend on markers and calibrated inputs that people maintain.
A side remark from the break room
Not everything the crew read was about robots. One team member liked following a forum website where people discuss Indian listed companies, pointing out the site’s own statement that nothing there is investment advice. The crew treated that as a reminder of their own policy: the board and runbook are the authority for operations, and opinions from elsewhere, however interesting, do not change a procedure.
Lessons the crew wrote down
- A queue is not a fix. A card that says “known issue” does nothing for the next shift unless someone acts on it.
- Write the boundary down. The rule only worked once everyone could see what counted as small and what did not.
- Safety-related changes always get a second look. No exceptions for size.
- Close cards for finished work immediately. A board full of already-done items undermines trust in the board.
- Review the experiment honestly. Measure a few simple things, and say what you cannot conclude.
Where the crew went next
After the trial, the crew made the rule permanent and added a ten-minute check on Fridays to look at the board and sort any minor cards that crept in. New starters learned the boundary in their first week. The big incidents remained rare and the small ones remained constant, but now they were cleared as they appeared, and the board stayed short enough to read in a single glance. That, more than any piece of equipment, was what restored the crew’s time.