The life of one request
FIN0001043, start to finish.
Not a feature list. One ordinary expense claim, and every point where the platform did something so that a person did not have to.
- 09:11
Priya, Sales
Looks for the answer first
As she fills the form in, the portal ranks the articles she is allowed to read against what she has typed and offers them under the fields. The ranking is company-wide rather than confined to the desk she picked, so an IT article can answer a Finance question. Nothing covers hers this morning, so she carries on. When one does answer somebody, that is recorded as a request the desk never had to open, which is the only honest way to count the ones you prevented.
- 09:12
Priya, Sales
Raises a request
She picks Finance from the portal and answers that desk's questions: what she bought, which client, how much, and the receipt. She chooses a department and a kind of work. She does not choose a queue, a priority or a person, because none of those are hers to know.
- 09:12
Techottic
Routes it and numbers it
Expense claim is a Finance category, so it goes to the Finance queue rather than a general inbox, and it takes the next number from Finance's own counter: FIN0001043. The on-call rule puts it with Marcus. Nobody triaged anything, which matters most on the morning nobody is free to triage.
- 09:31
Marcus, Finance
Asks one question
The receipt is missing a sales tax line. He asks on the request itself rather than by email, so the answer lands where the next person will look for it. Priya is told wherever she already reads things and replies in the same thread. Marcus moves the request to waiting on her, and that stops the desk's clock. It starts again when he moves it back, and the whole paused stretch is added onto the target then, so the wait is not counted against Finance. Her reply on its own does not restart it: a person has to move the request.
- 11:04
Dana, Finance lead
Approves
The second step of Finance's expense form is a sign-off, so it opened as an approval the moment the first step finished. It was waiting because the form says so, not because somebody remembered the rule. Dana sees the claim, the receipt and the thread on one screen, and signs off. Nothing downstream had opened while the decision was outstanding.
- 11:06
Techottic
Opens the fulfillment work
The approval opens the payment task in Finance's own queue, numbered FIN0001044, routed by the same rules the claim went through. Two numbered items, each with an owner and a clock. The payment task is raised in Priya's name, so it appears on her list too, opened by the approval rather than by her.
- 16:40
Marcus, Finance
Closes it, in writing
Closing takes a resolution note, and that note can be published as an article belonging to Finance, staff-only until somebody decides it should be readable by everyone. It is filed under the desk the request was for rather than the desk of whoever closed it, so it is in front of the people who will be asked the same thing next month.
- 16:40
Techottic
Asks Priya what she thought
The request she already has open asks her to rate it: five stars, twenty seconds. The score attaches to the desk that did the work, which is the only place a satisfaction number is worth reading. A request that is resolved but never confirmed closes itself once it has sat three days, the next time somebody's page load runs the background rules. There is no separate scheduler, so on an instance nobody opens, nothing closes.
Seven and a half hours, three people, one question. Nothing here needed a chase, a forwarded email, or somebody remembering to tell Finance. The parts that look like admin are the parts the platform did. What it did not do is decide anything: the step that required a second signature, the questions the form asked, the rota that chose Marcus and the resolution the article carries are all Finance's, set by Finance, and every one of them is visible to Finance afterwards.
The same day told badly reads like this. An email to a shared mailbox, a reply asking for the receipt, a forward to a manager for sign-off, a second thread with whoever pays it, and a fortnight later nobody can say whether it was paid without asking three people. None of the work is different. The difference is that in one version the record is the work itself, and in the other it is scattered across four inboxes and leaves the company when one of those four people does.