The anatomy of a request that never needed a meeting

Dana started on a Monday. The request for her laptop started eleven days earlier, in a Slack thread that opened with “hey, can someone sort a laptop for the new hire?” We followed that one request from the first message to the box arriving on her desk, and wrote down every step it took along the way.

Nothing about it was hard. It needed an owner, a model, a budget check, an approval and a shipping address, and every one of those answers already existed somewhere in the company on day one. It still took eleven days, two reminders, one escalation and a fifteen-minute meeting to get done.

Where the time actually goes

When we mapped real requests end to end, the work itself rarely took long. Ordering the laptop took four minutes. The waiting is what took eleven days: waiting for someone to notice, waiting for a missing detail, waiting for an approver to get back from lunch, waiting for the next weekly sync where someone would finally ask where Dana’s laptop was.

Here is how those eleven days broke down:

• Days 1 to 3. The message sat in a busy channel. Three people saw it and nobody owned it.

• Day 4. IT picked it up and asked which model and which cost center. The answer came back two days later.

• Day 6. Anything above $2,000 needs a manager’s approval, and the manager was traveling.

• Day 8. Someone booked a fifteen-minute call to “unblock the laptop”.

• Day 9. Approved, ordered in four minutes, shipped two days later.

Most of that waiting is invisible because no single person owns it. Each handoff looks reasonable on its own. Together they add up to a week and a half.

The three questions every request needs answered

Across a thousand requests, nearly all of the delay came from three questions that stayed open for too long:

1. Who owns this? A request without an owner waits for someone to volunteer.

2. What is missing? Requests stall on a detail nobody asked for up front: a cost center, a start date, a size.

3. Does a person need to approve it? Most approvals follow a rule everyone already knows. They still wait in someone’s inbox.

What we changed

We gave every request an owner from the first second, made the agent ask for missing details once and clearly, and let policy handle the approvals that never needed a human in the first place.

In practice, the agent reads the Slack message, recognizes a hardware request, files it in the IT queue and replies in the thread within a minute. If the cost center or start date is missing, it asks for both in one message instead of trickling questions over two days. If the laptop is a standard model under $2,000, policy approves it on the spot. If it isn’t, the right approver gets one clear request with everything they need to say yes.

The same request, rerun

We replayed Dana’s request through the new flow. It was filed in 40 seconds, the missing cost center was asked for and answered within the hour, policy approved it automatically, and the order went out the same afternoon. Eleven days became six hours, and nobody had to book a meeting to find out where it was.

What we didn’t change

People still make the calls that need judgment. Anything above a threshold, anything unusual and anything that touches access to sensitive systems still goes to a person. The difference is that the person gets a clean request with the context attached, instead of a thread they have to read from the top.

The rule of thumb

If a person has to ask the same question twice, the system is broken. Fix the system, not the person.